Skip to content

Warnings following loading of yang models since last release #2487

@Krisscut

Description

@Krisscut

Hello !

I'm trying to upgrade netopeer2-2.4.5 -> netopeer2-v2.7.0-12-g2809ede
So it includes a change from sysrepo-3.7.11 -> sysrepo-v4.2.10-37-gd59ac7e7
And changes from libyang-3.13.6 -> libyang-v4.2.2-105-gb9d150a2a

(NOTE: I use versions from the devel to include some fixes related to the latest official release)

I have some warnings which doesn't seem to cause issues, but just wanted to check with you for correct behavior.

I have a yang with that kind of content: (I tried to clean it up to focus on the issue)

module o-ran-test-fm {
  yang-version 1.1;
  namespace "urn:o-ran-test:fm:1.0";
  prefix o-ran-test-fm;

  organization
    "Test org";
  contact
    "test@test.com";
  description
    "Test module";

  revision 2020-07-07 {
    description
      " - Example module";
    reference
      "test";
  }

 rpc active-alarm-test-list {
    description
      "Set a list of faults, created in the RU.";
    input {
      leaf test-input {
             type string;
              description "Test input desc";
      }
    }
	output {
	    leaf status {
        type enumeration {
          enum OK {
            description
              "Operation has been taken into account.";
          }
          enum NOK {
            description
              "Operation cannot be taken into account because of error, more detailed information can be found in error-message.";
          }
        }
        mandatory true;
        description
          "Status of the rpc";
      }
      leaf error-message {
        when "../status = 'NOK'";
        type string;
        description
          "Detailed error Message when the status is NOK.";
      }
	}
  }

It produces this warning on loading with sysrepoctl, which wasn't the case before:

[WRN] Schema node "status" for parent "/o-ran-test-fm:active-alarm-test-list" not found; in expr "../status" with context node "/o-ran-test-fm:active-alarm-test-list/output/error-message".

Is it because the output node is an "implicit" node ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    is:bugBug description.status:completedFrom the developer perspective, the issue was solved (bug fixed, question answered,...)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions