zesty cloud-init doesn't know about ds=nocloud-net;seedfrom=

Bug #1663723 reported by Ryan Harper on 2017-02-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
curtin
High
Unassigned
cloud-init (Ubuntu)
Medium
Scott Moser

Bug Description

Curtin vmtests launch maas ephemeral images and post a datasource seed via kernel command line:

-append "root=LABEL=cloudimg-rootfs ds=nocloud-net;seedfrom=http://<hostip>:31339/ console=ttyS0 "

ds-identify fails to detect this and disables cloud-init.

Related branches

Scott Moser (smoser) on 2017-02-10
Changed in curtin:
status: New → Confirmed
importance: Undecided → High
Scott Moser (smoser) on 2017-02-10
Changed in curtin:
status: Confirmed → Fix Committed
Changed in cloud-init (Ubuntu):
assignee: nobody → Scott Moser (smoser)
importance: Undecided → Medium
status: New → Confirmed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cloud-init - 0.7.9-25-g65529b6-0ubuntu1

---------------
cloud-init (0.7.9-25-g65529b6-0ubuntu1) zesty; urgency=medium

  * New upstream snapshot.
    - ds-identify: fix checking for filesystem label (LP: #1663735)
    - ds-identify: read ds=nocloud properly (LP: #1663723)

 -- Scott Moser <email address hidden> Fri, 10 Feb 2017 15:25:17 -0500

Changed in cloud-init (Ubuntu):
status: Confirmed → Fix Released

This bug is believed to be fixed in curtin in 17.1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in curtin:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers