Page MenuHomeVyOS Platform

Boot fails when config.boot content is based on output of: show config commands
Open, LowPublic

Description

To me the "show config commands" format is easier to read and compare between configfiles.

However it seems that VyOS doesnt like if the /config/config.boot is in the "commands" format.

Plenty of errors during boot that ends with "Configuration error".

I can however restore the json-format from a backup since it works to login using some of the vyos-accounts that existed before the above attempt of "cp config.cmd config.boot". After restore I just reboot with "sudo reboot now" and the box is back to how it was before my attempt.

So a bug/feature request would be if either the config.boot format can be changed to the commands format or at least that vyos-configd (or whoever is reading the config.boot during boot) can be made compatible with the commands format?

Details

Version
1.5.0-S1
Is it a breaking change?
Unspecified (possibly destroys the router)
Issue type
Unspecified (please specify)

Event Timeline

Apachez created this object in space S1 VyOS Public.

Another option/workaround would be if something like "config replace" would be supported where the input could be a "config.cmd".

I found this as a workaround but again would be handy if things would work out of the box :-)

https://forum.vyos.io/t/convert-vyos-set-commands-in-to-vyos-config-offline/11268/5

The workaround is basically:

  1. Copy /config/config.boot to /config/config.empty
  2. Edit /config/config.empty so only the section of interfaces remains and the magicstring at the bottom (so migration wont trigger when it shouldnt).
  3. Enter config-mode with "conf".
  4. Type and press enter: load /config/config.empty
  5. Now over current SSH-session simply paste in the full list of set-commands.
  6. "commit", "save" then "exit" and finally "reboot now".

Now you have transfered a config based on set-commands onto a (new) VyOS box.