-
Notifications
You must be signed in to change notification settings - Fork 837
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 drives created on RHEL/CentOS 7.1 can't be found #2688
Comments
Launchpad user Roman Podoliaka(rpodolyaka) wrote on 2016-07-04T10:05:07.848312+00:00 This should help, checking it right now |
Launchpad user OpenStack Infra(hudson-openstack) wrote on 2017-12-21T01:37:48.311764+00:00 Fix proposed to branch: master |
Launchpad user Scott Moser(smoser) wrote on 2018-02-22T22:32:57.376030+00:00 This bug is believed to be fixed in cloud-init in 18.1. If this is still a problem for you, please make a comment and set the state back to New Thank you. |
Launchpad user OpenStack Infra(hudson-openstack) wrote on 2018-02-27T17:19:54.367174+00:00 Reviewed: https://review.openstack.org/529448 commit 24365043e31a7cb0899d2222bbba654ef718da5b
|
This bug was originally filed in Launchpad as LP: #1598783
Launchpad details
Launchpad user Roman Podoliaka(rpodolyaka) wrote on 2016-07-04T10:04:39.832255+00:00
Depending on the exact version of dosfstools used when preparing a config drive FS, it may not be detected by Cirron on VM boot. This is due to the fact, that Cirros currently performs a case-sensitive comparison of FS labels:
http://bazaar.launchpad.net/~cirros-dev/cirros/trunk/view/head:/src/lib/cirros/shlib#L134
and mkfs.vfat from CentOS will create an uppercase label "CONFIG-2".
Apparently, dosfstools won't let you use lowercase labels on CentOS, while it works fine on Ubuntu:
http://paste.openstack.org/show/507193/
All the descriptions of the config drive format mention "config-2", not "CONFIG-2":
http://cloudinit.readthedocs.io/en/latest/topics/datasources.html
https://coreos.com/os/docs/latest/config-drive.html
http://docs.openstack.org/user-guide/cli_config_drive.html
Nothing is said about whether case-sensitive or -insensitive string comparison should be used for comparing of FS labels.
Looks like FAT standard does not specify how labels should be treated, but Windows (at least XP) stores those in upper-case:
"For FAT volumes, volume labels are stored as uppercase regardless of whether they contain lowercase letters. NTFS volume labels retain and display the case used when the label was created."
https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/label.mspx?mfr=true
E.g. in Debian this was considered to be a bug and was fixed:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714971;msg=2
It even was accepted to upstream:
dosfstools/dosfstools@465dd8c
and made it to 3.0.22 release.
Related bug in MOS: https://bugs.launchpad.net/mos/+bug/1587960
The text was updated successfully, but these errors were encountered: