-
Notifications
You must be signed in to change notification settings - Fork 253
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
clab config not persistent after redeploy #1685
Comments
Thanks for a detailed report @KTodts |
I can not confirm this. The message
Configure:
Check:
Destroy:
Redeploy:
Check file:
Check SRL:
So, well... someone else maybe also try this, but I can't reproduce the issue. |
I don't know if it makes any difference but I'm using startup-config in the topology file. edit: |
Hmm @hellt whats our definition of a startup-config? |
ok, if a config is present in the nodes lab dir we should use that, if not e.g. --reconfigure we should download. |
ah, startup-config takes precendence over the local dir @KTodts The idea was that our topology should be as declarative as possible, so if we have a startup config in the topo file, this file should be used as a startup config, and thus overriding any config present in the node lab directory. |
Although this note here https://containerlab.dev/manual/nodes/#embedded-startup-config says otherwise :D To be honest, I think we need to then use existing labdir config indeed |
This way after installing a project from a repo you have the possibility to build on top of that. |
Yes and the note says so... We do have the enforce-startup-config flag otherwise... |
I just found this issue has been occurred starting from version 0.45.0. The main issue that I have experienced is even though I have saved my config before destroying the topology, the config is not persistent anymore. After executing deploy command it always copies or uses the config file from startup-config definition in topo-yaml file., |
yes, this is still unresolved. |
@hellt I am having same issue. I have startup config in clab lab directory. When I deploy lab again, startup config is not seen. thank you |
I noticed after upgrading my clab version from 43.0 to 47.1 that the config is not persistent after a redeploy of the topology.
Test would be, deploy topology for the first time --> make a config change --> destroy lab --> deploy again --> verify if change is persistent.
1 upgrade clab to version 47.1
2 Start with a fresh deployment by using --reconfgure
3 Log into the node. Make a change, commit and save config. (add default network-instance with a description)
4 Destroy topology
5 Deploy again. Note that the project directory, clab-lab, is being created again
6 Verify is config change is persistent after redeployment. (default network-instance is not configured)
The text was updated successfully, but these errors were encountered: