Creating a new topic since the other thread seems to have a different trajectory. Symptoms are similar.
After upgrade from 1.2.x to 1.3.x:
- ssh logins are refused (both public key + password logins)
- password reset from option in boot-menu doesn’t help
- boot-process ends with “configure failed” (system/most services come back up but login isn’t possible)
After going back to 1.2.x, pulling config.boot and trying to load/commit in fresh 1.3.1-S1-install it turns out that there are 2 problems.
- user/login-configs can’t be commited due to: “User root can’t be created, conflict with local system account!” Apparently that doesn’t only affect the root user but the entire “system login” node in the config.
- wireguard interfaces can’t be commited due to: “Wireguard private-key not found”
The latter isn’t too much of an issue (can be fixed manually after the upgrade). But the login issue MUST NOT happen imho. I would actually rate that as a rather serious bug - even if the problem results from config-nodes that have been deprecated long ago (history of the config goes back to Vyatta 6.1 days).
Questions:
- is there any way to access logs from another version (like accessing configs with “copy file 1.2.1://config/config.boot to…”)
- what’s the recommended process to get the update done after a failure - switch back to working version, delete failed image, delete root from “system login” config node, re-add image?