-
Notifications
You must be signed in to change notification settings - Fork 10
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
[BUG] media::get_environment attempts to locate a non-existent CDROM device on AzureLinux #99
Comments
Thanks for the bug report. Azure provides initial provisioning data, We should first check for a local mounted device, then fall back to fetching from IMDS. |
Up until PR #79 and #84 azure-init was ok without the mounted media because it would check IMDS first, then fall back to the media. The approach used by azure-init and Ignition favors IMDS over mounted media, which is ok if the customer does not use custom-data (azure-init doesn't handle user-data/custom-data to begin with). If the customer users custom-data, Ignition will miss the custom-data in the mounted media I believe (most Azure customers use custom-data and not user-data) |
Oh, good point, thanks. Yeah, I think what happend was actually until prior #79, commit 2c5cbfd0f8a6, if password auth is disabled, the Another big hidden issue here is, from the beginning until now,
I am ok with keeping the current behavior for now. |
Description
When testing #92 on Azure Linux 3.0, azure-init encounters an issue attempting to retrieve block devices using
media::get_environment()
. This causes azure-init to report an error and exit pre-maturely.Impact
This is part of work to get azure-init supported on Azure Linux 3.0 (as well as many other distros)
Environment and steps to reproduce
Boot an Azure Linux 3.0 VM, if you need an image, please reach out.
tdnf install libudev-devel git -y
git clone https://github.com/SeanDougherty/azure-init.git
cd azure-init
git checkout azl
cargo build --all
./target/debug/azure-init
Unable to get list of block devices
Expected behavior
Azure-init can get a mountable device for its use.
Additional information
I explored more in my branch, and I can see that there are devices available, they just might not be CDROM devices. (See photo)
For reference, this JSON is the configuration file used by AzL build tools to compose the image. You can see the devices enumerated under
Disks:
.The text was updated successfully, but these errors were encountered: