ds-identify does not see nocloud seed in core snap

Bug #1747070 reported by Scott Moser
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
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)
Changed in cloud-init:
status: New → Confirmed
importance: Undecided → Medium
status: Confirmed → In Progress
assignee: nobody → Scott Moser (smoser)
Chad Smith (chad.smith)
Changed in cloud-init:
status: In Progress → Fix Committed
Revision history for this message
Scott Moser (smoser) wrote : Fixed in Cloud-init 18.1

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
Revision history for this message
James Falcon (falcojr) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.