Pre-seeded snaps are not necessarily available for use in cloud-init user-data
Bug #1767131 reported by
Dan Watkins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Fix Released
|
Undecided
|
Unassigned | ||
cloud-init |
Fix Released
|
Medium
|
Unassigned | ||
cloud-init (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bionic |
Fix Released
|
Low
|
Unassigned |
Bug Description
With some cloud software being moved to snaps, cloud-init needs to ensure that snaps have been preseeded before user scripts are run, as those user scripts may rely on the software within the snap being available for use.
Related branches
~smoser/cloud-init:bug/1767131-snap-seeded
- Ryan Harper: Approve
- Server Team CI bot: Approve (continuous-integration)
- Dan Watkins: Approve
- Michael Vogt: Pending requested
-
Diff: 12 lines (+1/-0)1 file modifiedsystemd/cloud-config.service.tmpl (+1/-0)
tags: | added: id-5aea2721caa979edde9fb279 |
Changed in cloud-init: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in cloud-init (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in cloud-init (Ubuntu Bionic): | |
importance: | Undecided → Low |
status: | New → Fix Released |
Changed in cloud-images: | |
status: | New → Fix Released |
To post a comment you must log in.
Ideally, we would be able to configure the images to specify whether or not they should block on preseeded snaps. We have some cases where command-line utilities are installed (and so we should block) but others where only a daemon is started (where there is limited utility in blocking).