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 | |
---|---|---|---|---|---|
cloud-init |
Fix Released
|
Medium
|
Scott Moser |
Bug Description
If ubuntu-image is built with cloud-config, it puts data into /writable/
That directory is then bind mounted to /var/lib/cloud via /etc/fstab etnry like:
/writable/
ds-identify, which is run from /lib/systemd/
Related branches
~chad.smith/cloud-init:ubuntu/devel
- Server Team CI bot: Approve (continuous-integration)
- Scott Moser: Pending requested
-
Diff: 814 lines (+371/-90)15 files modifiedChangeLog (+52/-0)
cloudinit/cmd/tests/test_clean.py (+2/-1)
cloudinit/cmd/tests/test_status.py (+2/-1)
cloudinit/sources/DataSourceOVF.py (+16/-5)
cloudinit/tests/helpers.py (+9/-11)
cloudinit/version.py (+1/-1)
config/cloud.cfg.tmpl (+2/-0)
debian/changelog (+16/-0)
tests/cloud_tests/collect.py (+3/-2)
tests/cloud_tests/platforms/lxd/instance.py (+106/-26)
tests/unittests/test_ds_identify.py (+40/-3)
tests/unittests/test_handler/test_schema.py (+7/-5)
tools/ds-identify (+34/-19)
tools/run-centos (+78/-13)
tox.ini (+3/-3)
~smoser/cloud-init:bug/1747070-snapubuntu-core-seed
- Chad Smith: Approve
- Server Team CI bot: Approve (continuous-integration)
-
Diff: 71 lines (+35/-0)2 files modifiedtests/unittests/test_ds_identify.py (+24/-0)
tools/ds-identify (+11/-0)
Changed in cloud-init: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
status: | Confirmed → In Progress |
assignee: | nobody → Scott Moser (smoser) |
Changed in cloud-init: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
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.