Activity log for bug #1673818

Date Who What changed Old value New value Message
2017-03-17 15:26:07 George Shuklin bug added bug
2017-03-17 15:26:23 George Shuklin description Current documentation states that: http://cloudinit.readthedocs.io/en/latest/topics/datasources/configdrive.html#version-2 ... a config drive: ...Must be a un-partitioned block device (/dev/vdb, not /dev/vdb1)... This is not correct. 1. Cloud-init actually, works with ConfigDrive as partition. 2. Ironic uses partition at the end of disk to write metadata, and it's absurd for baremetal provisioning to dedicate whole disk (actual SATA, SSD, SAS/FC drive) just to tiny metada. 3. According to @smoser at #cloud-init IRC, " i'm pretty sure the doc is just wrong, ... i'm pretty sure reading current code that if the filesystem has a label of 'config-2', then it will work". I think this part of documentation should be rewritten to avoid confusion with Ironic workflow for ConfigDrive. Current documentation states that: http://cloudinit.readthedocs.io/en/latest/topics/datasources/configdrive.html#version-2 ... a config drive: ...Must be a un-partitioned block device (/dev/vdb, not /dev/vdb1)... This is not correct. 1. Cloud-init actually, works with ConfigDrive as partition (e.g. /dev/sda1) 2. Ironic uses partition at the end of disk to write metadata, and it's absurd for baremetal provisioning to dedicate whole disk (actual SATA, SSD, SAS/FC drive) just to tiny metada. 3. According to @smoser at #cloud-init IRC, " i'm pretty sure the doc is just wrong, ... i'm pretty sure reading current code that if the filesystem has a label of 'config-2', then it will work". I think this part of documentation should be rewritten to avoid confusion with Ironic workflow for ConfigDrive.
2017-03-17 16:34:56 Scott Moser cloud-init: status New Confirmed
2017-03-17 16:34:58 Scott Moser cloud-init: importance Undecided Medium
2017-03-17 16:45:43 Launchpad Janitor merge proposal linked https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/320228
2017-04-04 21:52:49 Scott Moser bug task added cloud-init (Ubuntu)
2017-04-04 21:53:32 Scott Moser nominated for series Ubuntu Yakkety
2017-04-04 21:53:32 Scott Moser bug task added cloud-init (Ubuntu Yakkety)
2017-04-04 21:53:32 Scott Moser nominated for series Ubuntu Zesty
2017-04-04 21:53:32 Scott Moser bug task added cloud-init (Ubuntu Zesty)
2017-04-04 21:53:32 Scott Moser nominated for series Ubuntu Xenial
2017-04-04 21:53:32 Scott Moser bug task added cloud-init (Ubuntu Xenial)
2017-04-04 21:53:43 Scott Moser cloud-init (Ubuntu Zesty): status New Fix Released
2017-04-04 21:53:49 Scott Moser cloud-init (Ubuntu Yakkety): status New Confirmed
2017-04-04 21:53:51 Scott Moser cloud-init (Ubuntu Xenial): status New Confirmed
2017-04-04 21:53:53 Scott Moser cloud-init (Ubuntu Xenial): importance Undecided Medium
2017-04-04 21:53:55 Scott Moser cloud-init (Ubuntu Yakkety): importance Undecided Medium
2017-04-04 21:53:56 Scott Moser cloud-init (Ubuntu Zesty): importance Undecided Medium
2017-04-04 21:54:42 Scott Moser description Current documentation states that: http://cloudinit.readthedocs.io/en/latest/topics/datasources/configdrive.html#version-2 ... a config drive: ...Must be a un-partitioned block device (/dev/vdb, not /dev/vdb1)... This is not correct. 1. Cloud-init actually, works with ConfigDrive as partition (e.g. /dev/sda1) 2. Ironic uses partition at the end of disk to write metadata, and it's absurd for baremetal provisioning to dedicate whole disk (actual SATA, SSD, SAS/FC drive) just to tiny metada. 3. According to @smoser at #cloud-init IRC, " i'm pretty sure the doc is just wrong, ... i'm pretty sure reading current code that if the filesystem has a label of 'config-2', then it will work". I think this part of documentation should be rewritten to avoid confusion with Ironic workflow for ConfigDrive. === Begin SRU Template === [Impact] This is a doc only change. The related doc is not present in ubuntu binary packages. [Test Case] apt-get source cloud-init vi cloud-init*/doc/rtd/topics/datasources/configdrive.rst [Regression Potential] None. [Other Info] Upstream commit: https://git.launchpad.net/cloud-init/commit/?id=58cc8f7521725d4f00 === End SRU Template === Current documentation states that: http://cloudinit.readthedocs.io/en/latest/topics/datasources/configdrive.html#version-2 ... a config drive: ...Must be a un-partitioned block device (/dev/vdb, not /dev/vdb1)... This is not correct. 1. Cloud-init actually, works with ConfigDrive as partition (e.g. /dev/sda1) 2. Ironic uses partition at the end of disk to write metadata, and it's absurd for baremetal provisioning to dedicate whole disk (actual SATA, SSD, SAS/FC drive) just to tiny metada. 3. According to @smoser at #cloud-init IRC, " i'm pretty sure the doc is just wrong, ... i'm pretty sure reading current code that if the filesystem has a label of 'config-2', then it will work". I think this part of documentation should be rewritten to avoid confusion with Ironic workflow for ConfigDrive.
2017-04-10 22:24:36 Brian Murray cloud-init (Ubuntu Yakkety): status Confirmed Fix Committed
2017-04-10 22:24:38 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2017-04-10 22:24:39 Brian Murray bug added subscriber SRU Verification
2017-04-10 22:24:43 Brian Murray tags verification-needed
2017-04-10 22:47:08 Brian Murray cloud-init (Ubuntu Xenial): status Confirmed Fix Committed
2017-04-13 19:34:23 Scott Moser tags verification-needed verification-done-xenial verification-done-yakkety
2017-04-20 19:33:34 Launchpad Janitor cloud-init (Ubuntu Yakkety): status Fix Committed Fix Released
2017-04-20 19:34:48 Steve Langasek removed subscriber Ubuntu Stable Release Updates Team
2017-04-20 19:35:54 Launchpad Janitor cloud-init (Ubuntu Xenial): status Fix Committed Fix Released
2017-09-23 02:29:57 Scott Moser cloud-init: status Confirmed Fix Released
2023-05-10 21:48:45 James Falcon bug watch added https://github.com/canonical/cloud-init/issues/2830