If there's no data for the provision step, the device is still forced back to master image
Bug #1616726 reported by
Paul Larson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| snappy-device-agents |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
On dragonboard, and possibly others, I noticed while testing that if you don't specify data for the provisioning step, it still checks that the board is in a state where it's ready to receive an image by forcing it to the master image. On certain devices, such as dragonboard, this is a destructive process to the existing test image on the device, and may not be desirable.
Revision history for this message
| Paul Larson (pwlars) wrote | #1 |
| Changed in snappy-device-agents: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
To post a comment you must log in.
I think this will be a bigger gotcha if we have device agents that handle things via upgrade rather than destructively installing a new image. For those, we'll simply not destroy the existing image, but it's still a nice to have feature for testing things quickly in development. So I'm marking it low, but I definitely want to keep this in mind for devices that use refresh or upgrade for the provisioning part.