yahoo-eng-team team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: cloud-init (Ubuntu Yakkety)
   Importance: Undecided
       Status: New

** Also affects: cloud-init (Ubuntu Zesty)
   Importance: Undecided
       Status: New

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: cloud-init (Ubuntu Zesty)
       Status: New => Fix Released

** Changed in: cloud-init (Ubuntu Yakkety)
       Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Xenial)
       Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Yakkety)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Zesty)
   Importance: Undecided => Medium

** Description changed:

+ === 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.

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1673818

Title:
  Misleading requirements for 'unpartitioned disks' for ConfigDrive in
  documentation

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Confirmed
Status in cloud-init source package in Zesty:
  Fix Released

Bug description:
  === 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1673818/+subscriptions