[3.0][bug] Cannot resume after the germinate state
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Image |
Fix Released
|
Medium
|
Paul Mars |
Bug Description
This is not possible to properly resume when we stopped just after the germinate state. The following command will work, but the next one (executed after the first one) will crash.
sudo ./ubuntu-image --debug classic --thru germinate --workdir ~/scratch/
sudo ./ubuntu-image --debug classic --resume --thru install_packages --workdir ~/scratch/
Error: invalid steps taken count (9). The state machine only have 4 steps
Even if the command did not crash, the state "install_packages" would not installed any packages found by germinate because the list is not saved in the state written to disk.
This is not specific to the germinate state, I also reproduced this issue by stopping after the build_gadget_tree state and in this case I encountered the following panic:
sudo ubuntu-image classic -v test.yaml -w ./test -t build_gadget_tree
[0] parse_image_
[1] calculate_states
[2] make_temporary_
[3] determine_
[4] build_gadget_tree
sudo ubuntu-image classic -v test.yaml -w ./test -r
panic: runtime error: slice bounds out of range [5:4]
goroutine 1 [running]:
github.
/build/
github.
/build/
main.executeSta
/build/
main.main()
/build/
The resume feature needs fixing to be able to stop/resume at any state. This may be important for the imagecraft integration.
description: | updated |
Changed in ubuntu-image: | |
status: | Confirmed → In Progress |
assignee: | nobody → Paul Mars (upils) |
tags: | added: foundations-todo |
Changed in ubuntu-image: | |
status: | In Progress → Fix Committed |
tags: | removed: foundations-todo |
Changed in ubuntu-image: | |
status: | Fix Committed → Fix Released |