delete item on "operational" possibly corrupted the datastore about sysrepo HOT 7 CLOSED

If you are fine with it, you can send all the required YANGs and data files to me privately via email so that I can reproduce it.

from sysrepo.

To reproduce and fix it, I will need the YANG module (you seem to have some custom one), ideally the full operational datastore data of the module (not just the snippet if there is more), and the way it has been set there (pull, push oper data or something else?).

from sysrepo.

Hi there,

This is the first time I see this JSON DS file plugin. Is that a custom libyang plugin that you have in house?

from sysrepo.

Hi there,

This is the first time I see this JSON DS file plugin. Is that a custom libyang plugin that you have in house?

@rjarry I don't think so, I literally just cloned libyang and sysrepo et and did a make install for both

To reproduce and fix it, I will need the YANG module (you seem to have some custom one), ideally the full operational datastore data of the module (not just the snippet if there is more), and the way it has been set there (pull, push oper data or something else?).

@michalvasko I'm trying to reproduce it on a very small dataset, is there an easy cli way to copy a node from running to operational ?

from sysrepo.

This is the first time I see this JSON DS file plugin. Is that a custom libyang plugin that you have in house?

Is now fairly old, must be half a year at least.

I'm trying to reproduce it on a very small dataset, is there an easy cli way to copy a node from running to operational ?

If you subscribe to module changes, all the data subscribed this way will appear in the operational datastore.

from sysrepo.

@michalvasko little update, so i tried with a tiny little sub version of our work tree, and I can't reproduce it (I can still reproduce it 100% of the time with our current tree). I now have 2 options:

• Take our current tree and rename everything so it stays anonymous.
• Take our current tree and shrink it, little by little to reproduce

For your question far above, the data where placed in running with sysrepocfg --import=vrrp.json and copied to operational with a subscription.

from sysrepo.

Seems solved on branch devel for libyang/sysrepo.

Thanks michalvasko

from sysrepo.