-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to set ald-port list for o-ran-ald-port in operational datastore in sysrepo #1693
Comments
The core of the problem is that the lists are xpath = "/o-ran-ald-port:ald-ports-io/ald-port[1]/name";
xpath = "/o-ran-ald-port:ald-ports-io/ald-port[1]/port-id";
xpath = "/o-ran-ald-port:ald-ports-io/ald-port[1]/dc-control-support"; then for |
Hi @michalvasko
I am currently receiving the entry and exit logs, and the expected serialized XML string generated is visible within these logs. However, the XML string is not being stored in the operational datastore as expected. The sysrepocfg triggered successfully, but xml is not stored in the operational datastore which we would have retrieved by this command. sysrepocfg -d operational -v3 -f xml -m o-ran-ald-port -X |
I am not sure I understand, you are still using key values as predicates instead of the positions so it will not work. |
Hi Michal
I am attempting to set the O-RAN ALD-Port data in the operational datastore for the ALD-Port list; however, the fields are not being correctly populated in the operational datastore.
o-ran-ald-port yang:
The code used to set the values in the callback through sr_oper_get_subscribe is provided above, but the output I am receiving is as shown below, which does not align with the expected results. Additionally, in this scenario, we are unable to create the nodes or set the data. Notably, no internal syslog errors are being generated, but the entry and exit logs are appearing as observed in the logs.
expected result should be as follows:
Could you please suggest the possible reasons for the error scenario encountered here and how it can be resolved?
The text was updated successfully, but these errors were encountered: