Bug 1363587
| Summary: | VM shutdown is failed after executing shutdown life-cycle sub-menu. | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-node | Reporter: | Wei Wang <weiwang> | ||||||||
| Component: | UI | Assignee: | Marek Libra <mlibra> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Wei Wang <weiwang> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 4.0 | CC: | bugs, cshao, fdeutsch, huiwa, huzhao, leiwang, rbarry, tjelinek, weiwang, yaniwang, ycui | ||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||
| Target Release: | --- | Flags: | rule-engine:
planning_ack?
rule-engine: devel_ack? rule-engine: testing_ack? |
||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2016-09-01 11:25:34 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 1186957 [details]
vm_no_bootable_disk
Created attachment 1186958 [details]
log files
How the boot order looked like? Because there are basically two options how to do the install (the newer, preferred is): - create a VM with boot order in a way that the boot device will be the first - run once the VM and set it to show the boot menu + start in pause mode so you will be able to connect to console on time - connect to guest console (e.g. vnc or spice) and unpause the VM - pick the device from which you want to boot the install media - after install shutdown the VM, start again and it will boot properly Second (older) option is to rearrange the boot order before install and than back after install. About shutdown: If the VM is not up with a running guest agent, you need to use a poweoff to quickly turn a vm off. (In reply to Tomas Jelinek from comment #3) > How the boot order looked like? Because there are basically two options how > to do the install (the newer, preferred is): > - create a VM with boot order in a way that the boot device will be the first > - run once the VM and set it to show the boot menu + start in pause mode so > you will be able to connect to console on time > - connect to guest console (e.g. vnc or spice) and unpause the VM > - pick the device from which you want to boot the install media > - after install shutdown the VM, start again and it will boot properly > 1. Set vm and config the boot sequence to PXE boot(Maybe this is the reason for my issue), then add disk to vm. 2. Run once, select boot from PXE, vm begin to be installed 3. During installation, using shutdown fail. 4. After installation, vm reboot，reboot fail since cannot find a bootable disk. > Second (older) option is to rearrange the boot order before install and than > back after install. > > About shutdown: > If the VM is not up with a running guest agent, you need to use a poweoff to > quickly turn a vm off. Yes, during installation, use a poweoff can turn a vm off quickly. (In reply to weiwang from comment #4) > (In reply to Tomas Jelinek from comment #3) > > How the boot order looked like? Because there are basically two options how > > to do the install (the newer, preferred is): > > - create a VM with boot order in a way that the boot device will be the first > > - run once the VM and set it to show the boot menu + start in pause mode so > > you will be able to connect to console on time > > - connect to guest console (e.g. vnc or spice) and unpause the VM > > - pick the device from which you want to boot the install media > > - after install shutdown the VM, start again and it will boot properly > > > 1. Set vm and config the boot sequence to PXE boot(Maybe this is the reason > for my issue), then add disk to vm. Yes, this is it. Please try to change the boot sequence in the edit VM to boot from the disk. > 2. Run once, select boot from PXE, vm begin to be installed > 3. During installation, using shutdown fail. > 4. After installation, vm reboot，reboot fail since cannot find a bootable > disk. > > > Second (older) option is to rearrange the boot order before install and than > > back after install. > > > > About shutdown: > > If the VM is not up with a running guest agent, you need to use a poweoff to > > quickly turn a vm off. > Yes, during installation, use a poweoff can turn a vm off quickly. as per comment 5 it is not a bug, it is a miscofiguration of the VM, closing (In reply to Tomas Jelinek from comment #5) > (In reply to weiwang from comment #4) > > (In reply to Tomas Jelinek from comment #3) > > > How the boot order looked like? Because there are basically two options how > > > to do the install (the newer, preferred is): > > > - create a VM with boot order in a way that the boot device will be the first > > > - run once the VM and set it to show the boot menu + start in pause mode so > > > you will be able to connect to console on time > > > - connect to guest console (e.g. vnc or spice) and unpause the VM > > > - pick the device from which you want to boot the install media > > > - after install shutdown the VM, start again and it will boot properly > > > > > 1. Set vm and config the boot sequence to PXE boot(Maybe this is the reason > > for my issue), then add disk to vm. > > Yes, this is it. Please try to change the boot sequence in the edit VM to > boot from the disk. > After try with redhat-virtualization-host-4.0-20160817.0, the bug "No bootable device" is still occur, and cannot reboot automatically. > > 2. Run once, select boot from PXE, vm begin to be installed > > 3. During installation, using shutdown fail. > > 4. After installation, vm reboot，reboot fail since cannot find a bootable > > disk. > > > > > Second (older) option is to rearrange the boot order before install and than > > > back after install. > > > > > > About shutdown: > > > If the VM is not up with a running guest agent, you need to use a poweoff to > > > quickly turn a vm off. > > Yes, during installation, use a poweoff can turn a vm off quickly. (In reply to weiwang from comment #7) > (In reply to Tomas Jelinek from comment #5) > > (In reply to weiwang from comment #4) > > > (In reply to Tomas Jelinek from comment #3) > > > > How the boot order looked like? Because there are basically two options how > > > > to do the install (the newer, preferred is): > > > > - create a VM with boot order in a way that the boot device will be the first > > > > - run once the VM and set it to show the boot menu + start in pause mode so > > > > you will be able to connect to console on time > > > > - connect to guest console (e.g. vnc or spice) and unpause the VM > > > > - pick the device from which you want to boot the install media > > > > - after install shutdown the VM, start again and it will boot properly > > > > > > > 1. Set vm and config the boot sequence to PXE boot(Maybe this is the reason > > > for my issue), then add disk to vm. > > > > Yes, this is it. Please try to change the boot sequence in the edit VM to > > boot from the disk. > > > > After try with redhat-virtualization-host-4.0-20160817.0, the bug "No > bootable device" is still occur, and cannot reboot automatically. - how the VM's boot options were set? (in edit VM) - if the disk was the boot device, was it marked as bootable? Maybe you are hitting this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1365087 > > > > 2. Run once, select boot from PXE, vm begin to be installed > > > 3. During installation, using shutdown fail. > > > 4. After installation, vm reboot，reboot fail since cannot find a bootable > > > disk. > > > > > > > Second (older) option is to rearrange the boot order before install and than > > > > back after install. > > > > > > > > About shutdown: > > > > If the VM is not up with a running guest agent, you need to use a poweoff to > > > > quickly turn a vm off. > > > Yes, during installation, use a poweoff can turn a vm off quickly. 1. boot options setting: Before installation: a) Set before running vm, in the prompt dialog. Set the boot options to pxe. b) When new the vm, boot option can be set to pxe. then setting the boot sequence before running vm also to pxe. After installation: a) reboot directly b) before rebooting, reset boot option to disk. The bug is reproduced with all the two settings. 2. Yes, it hitting the bug https://bugzilla.redhat.com/show_bug.cgi?id=1365087 VM->disks->new disk the "bootable" is not marked. The same for "new vm" -> in "instance images" section "create" -> the "bootable" is not marked. ok, so marking this as duplicate of 1365087 *** This bug has been marked as a duplicate of bug 1365087 *** |
Created attachment 1186955 [details] ks file Description of problem: VM shutdown is failed after executing shutdown life-cycle sub-menu. Version-Release number of selected component (if applicable): redhat-virtualization-host-4.0-20160727.1.x86_64 imgbased-0.7.3-0.1.el7ev.noarch cockpit-0.114-2.el7.x86_64 cockpit-ovirt-dashboard-0.10.6-1.3.3.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. Install redhat-virtualization-host-4.0-20160727.1.x86_64 with kickstart file in attachment 2. Add host to RHVM, and setting up a vm. 3. During install vm, select shutdown life-cycle sub-menu. 4. Check the vm status Actual results: VM shutdown is failed after executing shutdown life-cycle sub-menu. Expected results: VM should be shutdown successfully. Additional info: When vm is booted after installation, boot fail since cannot find a bootable disk. If manually modify the "boot options" of vm via "Edit" menu in RHEVM, then power off, then run again vm, vm can boot successfully. And can be shutdown successfully.