| 2016-07-04 10:04:39 |
Roman Podoliaka |
bug |
|
|
added bug |
| 2016-07-04 10:04:46 |
Roman Podoliaka |
cirros: assignee |
|
Roman Podoliaka (rpodolyaka) |
|
| 2016-07-04 10:05:07 |
Roman Podoliaka |
attachment added |
|
config_drive.patch https://bugs.launchpad.net/cirros/+bug/1598783/+attachment/4695088/+files/config_drive.patch |
|
| 2016-07-04 10:05:29 |
Roman Podoliaka |
description |
Depending on the exact version of dosfstools used when preparing a config drive FS it may not be detected by Cirron on 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
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:
https://github.com/dosfstools/dosfstools/commit/465dd8cf8f643bdd39a732e7d7f819a6abdf3d83
and made it to 3.0.22 release.
Related bug in MOS: https://bugs.launchpad.net/mos/+bug/1587960 |
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
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:
https://github.com/dosfstools/dosfstools/commit/465dd8cf8f643bdd39a732e7d7f819a6abdf3d83
and made it to 3.0.22 release.
Related bug in MOS: https://bugs.launchpad.net/mos/+bug/1587960 |
|
| 2016-07-04 10:06:06 |
Roman Podoliaka |
description |
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
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:
https://github.com/dosfstools/dosfstools/commit/465dd8cf8f643bdd39a732e7d7f819a6abdf3d83
and made it to 3.0.22 release.
Related bug in MOS: https://bugs.launchpad.net/mos/+bug/1587960 |
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:
https://github.com/dosfstools/dosfstools/commit/465dd8cf8f643bdd39a732e7d7f819a6abdf3d83
and made it to 3.0.22 release.
Related bug in MOS: https://bugs.launchpad.net/mos/+bug/1587960 |
|
| 2017-12-15 01:00:11 |
James Penick |
bug task added |
|
cloud-init |
|
| 2017-12-15 01:01:32 |
James Penick |
bug task added |
|
cloudbase-init |
|
| 2017-12-15 17:16:04 |
James Penick |
cloudbase-init: assignee |
|
James Penick (penick) |
|
| 2017-12-15 23:23:55 |
James Penick |
cloud-init: assignee |
|
James Penick (penick) |
|
| 2017-12-16 22:44:45 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~penick/cloud-init/+git/cloud-init/+merge/335286 |
|
| 2017-12-19 23:26:36 |
James Penick |
cloud-init: status |
New |
Fix Released |
|
| 2017-12-20 20:46:30 |
Scott Moser |
cloud-init: status |
Fix Released |
Confirmed |
|
| 2017-12-20 20:46:36 |
Scott Moser |
cloud-init: importance |
Undecided |
Medium |
|
| 2017-12-20 20:46:41 |
Scott Moser |
cirros: status |
New |
Confirmed |
|
| 2017-12-20 20:46:44 |
Scott Moser |
cirros: importance |
Undecided |
Medium |
|
| 2017-12-20 20:54:55 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~smoser/cirros/+git/cirros/+merge/335476 |
|
| 2017-12-21 01:37:47 |
OpenStack Infra |
cloudbase-init: status |
New |
In Progress |
|
| 2018-01-23 21:22:55 |
Chad Smith |
cloud-init: status |
Confirmed |
Fix Committed |
|
| 2018-01-24 01:19:45 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/336513 |
|
| 2018-01-24 03:14:07 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/336514 |
|
| 2018-02-22 22:32:55 |
Scott Moser |
cloud-init: status |
Fix Committed |
Fix Released |
|
| 2018-02-27 17:19:52 |
OpenStack Infra |
cloudbase-init: status |
In Progress |
Fix Released |
|
| 2023-05-10 14:26:30 |
James Falcon |
bug watch added |
|
https://github.com/canonical/cloud-init/issues/2688 |
|
