srl-labs
arista_ceos: `service configuration terminal disabled` in startup-config breaks post deployment
When the lineservice configuration terminal disabled is present in the startup configuration of an Arista cEOS container, the post-deployment process fails. Maybe vEOS breaks, too.
This configuration prevents the use of the traditional configure terminal command in favor of the modern configure session workflow.
I haven’t tested this behavior on vEOS yet, but it might be affected as well.
From what I’ve found, the configure terminal command is hardcoded in the scrapligo library.
Replacing the escalate command with configure session and the deescalate command with commit should resolve the issue.
I’m not very familiar with the Scrapli library or Go in general, so I’m not sure whether this could (or should) be patched within containerlab itself, or if it needs to be addressed upstream in Scrapli.
If changing the post-deploy behavior is not desirable, it might be helpful to add a note to the documentation warning users not to include service configuration terminal disabled in their startup configuration.
@carlmontanari did you hear any rumblings about session support in scrapli for eos?
👋 yeah I mean its "supported" in that you can just provide a yaml platform definition that uses configure session instead if you'd like. Can also do something like this long forgotten go version of scraplicfg where the config session is created/registered as a priv level on the fly. HTH!
