fuel-qa unable to resume deployment of env destroyed just before empty snapshot creation
Bug #1580801 reported by
Sergey Yudin
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
New
|
Wishlist
|
Fuel QA Team |
Bug Description
Steps to reproduce:
1) Start deployment of any TG with fuel-qa
2) Kill deployment in the middle of provisioning of fuel master
3) Start deployment again with the same environment name
Actual result:
Fuel master will hung with message "booting to hard disk"
Expected behavior:
Fuel master will be booted from iso again and will start provision
summary: |
- fuel-qa unable to resume deployment destroyed just before empty snapshot - creation + fuel-qa unable to resume deployment of env destroyed just before empty + snapshot creation |
Changed in fuel: | |
status: | Incomplete → Confirmed |
status: | Confirmed → Incomplete |
To post a comment you must log in.
Tests are using fuel-devops which configures the following devices boot order:
hd
cdrom
At first VM boot HDD is empty, so it boots from iso and Fuel installation is being started. When you kill deployment during CentOS provisioning on master node, partition table is created and something is already written to MBR (most probably boot flag is set), but GRUB isn't installed. So during next boot (new test run) master node VM tries to boot from HDD and hangs (I believe it's a bug in BIOS used by qemu).
The easiest way to workaround this issue is set KEEP_BEFORE=no [0] or manually erase environment before restarting tests.
[0] https:/ /github. com/openstack/ fuel-qa/ blob/eaea19b42f cfb84e893618785 2f0355ebda88a17 /utils/ jenkins/ system_ tests.sh# L183-L184