-
Notifications
You must be signed in to change notification settings - Fork 97
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
🐛 config_url
is saved as part of the config during netboot
#885
Comments
labeled as ux as it doesn't block anything (workaround is known) |
As agreed during planning, we will make the agent print a warning when the config_url is not accessible and continue booting. Ideally it can retry a couple of times before giving up. Ideally, these kind of warnings should be printed in the boot messages (not |
I tried to reproduce it but although the auroraboot server is not reachable, system eventually boots. These are the relevant logs from
It tried 10 times and then quit. |
The system boots, but the service exists, so it doesn't end up the first-boot deployment code (and k3s doesn't start, etc.) |
but rather print a Warning. Fixes #885 Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
The fix was simple: https://github.com/kairos-io/kairos/tree/885-flexible-config-url but I'll check if we can have a test for this. |
A manual test for now:
and the installation keeps going (turns out The config.yaml:
and the command was: |
but rather print a Warning. Fixes #885 Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me>
Don't fail when config_url is not accessible but rather print a Warning. Fixes #885 Signed-off-by: Dimitris Karakasilis <dimitris@karakasilis.me> Co-authored-by: Dimitris Karakasilis <dimitris@karakasilis.me>
Kairos version:
1.5
CPU architecture, OS, and Version:
Describe the bug
When doing automated installs from network, for instance with
AuroraBoot
, the cloud config file used for bootstrapping it is passed as aconfig_url
, which ends up to be saved into the/oem/90_custom.yaml
file. The problem is that if we kill AuroraBoot, kairos will try to fetch the URL again and fail, preventing the agent to startTo Reproduce
Use auroraboot, like the following, and after the machine installation completes, kill the
auroraboot
process:To workaround, add
config_url
to the supplied cloud config, like so:Expected behavior
The
kairos-agent
should at least ignore such errors and print a warning instead so the deployment is not stopped. If there is something going wrong, a user having issues will already look into logs.Open question What about the
config_url
by itself? does it make sense to save it at all from the cmdline?The text was updated successfully, but these errors were encountered: