ds-identify does not see nocloud seed in core snap

Bug #1747070 reported by Scott Moser on 2018-02-02
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Medium
Scott Moser

Bug Description

If ubuntu-image is built with cloud-config, it puts data into /writable/system-data/var/lib/cloud.
That directory is then bind mounted to /var/lib/cloud via /etc/fstab etnry like:
  /writable/system-data/var/lib/cloud /var/lib/cloud none bind 0 0

ds-identify, which is run from /lib/systemd/system-generators/cloud-init-generator runs before /var/lib/cloud bind mount is done, so it does not see the seed.

Related branches

Scott Moser (smoser) on 2018-02-02
Changed in cloud-init:
status: New → Confirmed
importance: Undecided → Medium
status: Confirmed → In Progress
assignee: nobody → Scott Moser (smoser)
Chad Smith (chad.smith) on 2018-02-12
Changed in cloud-init:
status: In Progress → Fix Committed

This bug is believed to be fixed in cloud-init in 18.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