Curtin unable to deploy Ubuntu Core
Bug #1647734 reported by
Lee Trager
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| curtin |
Triaged
|
High
|
Unassigned | ||
Bug Description
I uploaded the PC Ubuntu Core image to MAAS and tried and deploy it. While it deploys it gets stuck in a reboot loop because / is mounted read-only.
Revision history for this message
| Ryan Harper (raharper) wrote | #1 |
| Changed in curtin: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| description: | updated |
| description: | updated |
To post a comment you must log in.
Currently curtin needs the following:
- Don't raise an exception if we don't find a target root device
- Detect that if the deployed image is snappy, that we don't need a root device
- Only attempt to mount the rootdev if one is found
- Allow curthooks to be skipped if our source is a dd-image source
- Changes to curtin tools for integration testing of UC images
A prototype that needs refreshing is here: lp:~raharper/curtin/trunk.snappy-dd