-
Notifications
You must be signed in to change notification settings - Fork 28
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
flatcar-openstack-hostname.service not using config-drive as default for scraping metadata #1445
Comments
Thanks a lot for your response @tormath1. I've forked both bootengine and flatcar-scripts and applied my changes on: Not sure what the next step would be. Should I raise a PR for bootengine? Thanks again. |
Perfect thanks. You can now open a pull request for bootengine and scripts for reviewing the changes, I'll start a Flatcar build to try your changes and assert that it does not bring regression on OpenStack platform. |
Hi @tormath1.
Thanks for the help and patience. |
Description
When booting up a Flatcar instance in OpenStack using Ignition and config-drive, flatcar-openstack-hostname.service is retrieving information from metadata API instead of trying config-drive first.
Impact
Information on config-drive is ignored which might be a problem on environments where metadata API cannot be used.
Environment and steps to reproduce
Expected behavior
Existing values under /media/configdrive/ should be used. As implemented on coreos/afterburn#462.
Additional information
Service logs:
Config drive exists:
Ignition used:
Unsure whether this is relevant, but https://github.com/flatcar/bootengine/blob/flatcar-master/dracut/30ignition/flatcar-openstack-hostname.service#L17 is using
openstack-metadata
instead ofopenstack
.The text was updated successfully, but these errors were encountered: