yang error messages associated with every vrf creation

[donaldsharp]

Description

Creating a vrf and establishing it always generates these yang error messages:

2025/02/26 16:45:04 ZEBRA: libyang: Invalid type uint32 empty value. (Schema location "/frr-vrf:lib/vrf/state/id".)
2025/02/26 16:45:04 ZEBRA: libyang: Invalid boolean value "". (Schema location "/frr-vrf:lib/vrf/state/active".)
2025/02/26 16:45:04 ZEBRA: libyang: Invalid type uint32 empty value. (Schema location "/frr-vrf:lib/vrf/state/id".)
2025/02/26 16:45:04 ZEBRA: libyang: Invalid boolean value "". (Schema location "/frr-vrf:lib/vrf/state/active".)
2025/02/26 16:45:04 ZEBRA: libyang: Invalid type uint32 empty value. (Schema location "/frr-vrf:lib/vrf/state/id".)
2025/02/26 16:45:04 ZEBRA: libyang: Invalid boolean value "". (Schema location "/frr-vrf:lib/vrf/state/active".)
2025/02/26 16:45:04 ZEBRA: libyang: Invalid type uint32 empty value. (Schema location "/frr-vrf:lib/vrf/state/id".)
2025/02/26 16:45:04 ZEBRA: libyang: Invalid boolean value "". (Schema location "/frr-vrf:lib/vrf/state/active".)
2025/02/26 16:45:04 ZEBRA: libyang: Invalid type uint32 empty value. (Schema location "/frr-vrf:lib/vrf/state/id".)

When I comment out the nb_op_update calls in vrf_update_state the messages go away:

static void vrf_update_state(struct vrf *vrf)
{
        if (!vrf->state || !vrf_notify_oper_changes)
                return;

        /*
         * Remove top level container update when we have patch support, for now
         * this keeps us from generating 2 separate REPLACE messages though.
         */
        nb_op_updatef(vrf->state, "id", "%u", vrf->vrf_id);
        nb_op_update(vrf->state, "active", CHECK_FLAG(vrf->status, VRF_ACTIVE) ? "true" : "false");
}

Version

latest master

How to reproduce

Create a vrf and enable it. Look at the log files.

Expected behavior

No error messages

Actual behavior

error messages

Additional context

There comes a time when you must recognize that Llama's are pretty awesome

Checklist

• I have searched the open issues for this bug.
• I have not included sensitive information in this report.

[donaldsharp]

I'm seeing the same type of error for this too:

/ospf_netns_vrf.test_b/r2/zebra.log:2025/02/26 13:27:17.017832 ZEBRA: libyang: Invalid type int32 empty value. (Schema location "/frr-interface:lib/interface/state/if-index".)

My expectation is that this is probably the same type of problem.