ds-identify finding by fslabel does not work right

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

Bug Description

in vmtest for curtin, we fail to boot the installed system because has_fs_with_label does not work right.

Scott Moser (smoser) on 2017-02-10
summary: - ds-identify finding by fslable does not work right
+ ds-identify finding by fslabel does not work right
Changed in cloud-init:
status: New → Confirmed
importance: Undecided → Medium
status: Confirmed → Fix Committed
importance: Medium → High
Changed in cloud-init (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
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 cloud-init 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 cloud-init:
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