Hide Forgot
Created attachment 944266 [details] errormessagescreenshot Description of problem: Failed to create VM based on [rhos-qe-dept] SHELLSHOCK - rhel-guest-image-6.5 (6.5-20140930.0) imported template on RHEL6.6. Version-Release number of selected component (if applicable): qemu-kvm-rhev-0.12.1.2-2.448.el6.x86_64 vdsm-4.16.5-2.el6ev.x86_64 sanlock-2.8-1.el6.x86_64 libvirt-0.10.2-46.el6.x86_64 2.6.32-502.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.Take guest image and export via iso-uploader. 2.Import template from export domain. 3.Create VM from template and stry to run it on RHEL6.6 host. Actual results: Error received and VM not starting. Expected results: VM should be created from imported guest image template and to start properly over RHEL6.6. Additional info:
Created attachment 944272 [details] logs
Allon, can someone from storage check this? During the VM creation I can see Message: VDSGenericException: VDSErrorException: Failed to HSMGetAllTasksStatusesVDS, error = low level Image copy failed, code = 261 at 2014-10-06 15:53:10,334 in the engine.log. Nikolai, I suppose the vdsm logs are not the right ones, very narrow time window is captured. We need to see the VM creation (storage task)
(In reply to Michal Skrivanek from comment #2) > Allon, can someone from storage check this? > During the VM creation I can see > > Message: VDSGenericException: VDSErrorException: Failed to > HSMGetAllTasksStatusesVDS, error = low level Image copy failed, code = 261 Sure. Tal - can you take a look please once the logs are provided: > at 2014-10-06 15:53:10,334 in the engine.log. > > Nikolai, I suppose the vdsm logs are not the right ones, very narrow time > window is captured. We need to see the VM creation (storage task)
I tried to reproduce on vt5,VM failed to start. VM started on RHEL7 host instead of RHEL6.6, then migration failed to RHEL6.6 because selinux bug. Migration fails because of the selinux is enforcing, while guest-agent crush I have no idea. vdsm-4.16.6-1.el6ev.x86_64 qemu-kvm-rhev-0.12.1.2-2.448.el6.x86_64 sanlock-2.8-1.el6.x86_64 libvirt-0.10.2-46.el6.x86_64 rhevm-3.5.0-0.14.beta.el6ev.noarch New logs attached.
Created attachment 944886 [details] newestlogs
I cannot reproduce this bug on: rhevm-3.5.0-0.14.beta.el6ev.noarch vdsm-4.14.7-3.el6ev.x86_64 qemu-kvm-rhev-0.12.1.2-2.415.el6_5.3.x86_64 I use rhevm-image-uploader instead of iso-uploader based on the steps in TCMS. 1. Upload ovf with rhevm-image-uploader 2. Import template from export domain. 3. Create VM from template and run it on RHEL-6.6-20140926.0 host. I can login to rhel-guest-image-6.5 (6.5-20140930.0) successfully through virt-viewer console.
also, needinfo on Tal still applicable?
(In reply to Wei Shi from comment #6) > I cannot reproduce this bug on: > rhevm-3.5.0-0.14.beta.el6ev.noarch > vdsm-4.14.7-3.el6ev.x86_64 > qemu-kvm-rhev-0.12.1.2-2.415.el6_5.3.x86_64 > > I use rhevm-image-uploader instead of iso-uploader based on the steps in > TCMS. > > 1. Upload ovf with rhevm-image-uploader > 2. Import template from export domain. > 3. Create VM from template and run it on RHEL-6.6-20140926.0 host. > > I can login to rhel-guest-image-6.5 (6.5-20140930.0) successfully through > virt-viewer console. Successfully reproduced again on my setup with the error message received as within the attachment, logs attached as well. Components: libvirt-0.10.2-46.el6.x86_64 vdsm-4.16.6-1.el6ev.x86_64 qemu-kvm-rhev-0.12.1.2-2.448.el6.x86_64 sanlock-2.8-1.el6.x86_64 libvirt-0.10.2-29.el6_5.9.x86_64
Created attachment 946072 [details] logs from 12_10_14
(In reply to Nikolai Sednev from comment #4) > VM started on RHEL7 host instead of RHEL6.6, then migration failed to avoid that. Not supported and cause random issues
(In reply to Nikolai Sednev from comment #9) sorry, again can't find relevant in the logs other than lot of noise about network connectivity problems in engine.log Please try to pinpoint the error you see, describe exactly the flow
Flow is as described in description of a bug: Steps to Reproduce: 1.Take guest image and export via iso-uploader. 2.Import template from export domain. 3.Create VM from template and try to run it on RHEL6.6 host. I don't think I can provide more info than this, logs attached and screenshot as well, sorry, but that's my best to describe. If you want to see this happens, please contact me directly and observe on my setup.
(In reply to Nikolai Sednev from comment #12) > Flow is as described in description of a bug: > Steps to Reproduce: > 1.Take guest image and export via iso-uploader. > 2.Import template from export domain. > 3.Create VM from template and try to run it on RHEL6.6 host. > > I don't think I can provide more info than this, logs attached and > screenshot as well, sorry, but that's my best to describe. If you want to > see this happens, please contact me directly and observe on my setup. Did you try upload the image by engine-image-upload ? Since it's a tar image not an ISO file. I can't reproduce this bug either, needinfo Ryan for help.
(In reply to yuliu from comment #13) > (In reply to Nikolai Sednev from comment #12) > > Flow is as described in description of a bug: > > Steps to Reproduce: > > 1.Take guest image and export via iso-uploader. > > 2.Import template from export domain. > > 3.Create VM from template and try to run it on RHEL6.6 host. > > > > I don't think I can provide more info than this, logs attached and > > screenshot as well, sorry, but that's my best to describe. If you want to > > see this happens, please contact me directly and observe on my setup. > > Did you try upload the image by engine-image-upload ? Since it's a tar image > not an ISO file. > > I can't reproduce this bug either, needinfo Ryan for help. I did only as described above, only ISO, upload is OK, import then is fine, VM creation is perfect, but VM start failed.
(In reply to Nikolai Sednev from comment #14) > (In reply to yuliu from comment #13) > > (In reply to Nikolai Sednev from comment #12) > > > Flow is as described in description of a bug: > > > Steps to Reproduce: > > > 1.Take guest image and export via iso-uploader. > > > 2.Import template from export domain. > > > 3.Create VM from template and try to run it on RHEL6.6 host. > > > > > > I don't think I can provide more info than this, logs attached and > > > screenshot as well, sorry, but that's my best to describe. If you want to > > > see this happens, please contact me directly and observe on my setup. > > > > Did you try upload the image by engine-image-upload ? Since it's a tar image > > not an ISO file. > > > > I can't reproduce this bug either, needinfo Ryan for help. > > I did only as described above, only ISO, upload is OK, import then is fine, > VM creation is perfect, but VM start failed. Nikolai, does the VM come up at all? Or is not even the "bios" shown?
According to comment 4 and comment 12 this can only be reproduce on RHEL 6.6. According to comment 4 this can not be reproduce on RHEL 7. So to me this looks like a bug of RHEV on RHEL 6.6, and for me this is not a reason to block the RHEL guest image. We can not make RHEV 3.5 (which is in beta) a blocker for an image with security fixes.
(In reply to Fabian Deutsch from comment #15) > (In reply to Nikolai Sednev from comment #14) > > (In reply to yuliu from comment #13) > > > (In reply to Nikolai Sednev from comment #12) > > > > Flow is as described in description of a bug: > > > > Steps to Reproduce: > > > > 1.Take guest image and export via iso-uploader. > > > > 2.Import template from export domain. > > > > 3.Create VM from template and try to run it on RHEL6.6 host. > > > > > > > > I don't think I can provide more info than this, logs attached and > > > > screenshot as well, sorry, but that's my best to describe. If you want to > > > > see this happens, please contact me directly and observe on my setup. > > > > > > Did you try upload the image by engine-image-upload ? Since it's a tar image > > > not an ISO file. > > > > > > I can't reproduce this bug either, needinfo Ryan for help. > > > > I did only as described above, only ISO, upload is OK, import then is fine, > > VM creation is perfect, but VM start failed. > > Nikolai, does the VM come up at all? Or is not even the "bios" shown? VM not started at all. I didn't saw SPICE coming available for pressing it to see the BIOS.
finally found 2014-10-12 08:47:31,491 ERROR [org.ovirt.engine.core.bll.network.vm.ActivateDeactivateVmNicCommand] (ajp-/127.0.0.1:8702-3) [df52a98] Command org.ovirt.engine.core.bll .network.vm.ActivateDeactivateVmNicCommand throw exception: java.lang.NullPointerException at org.ovirt.engine.core.bll.utils.VmDeviceUtils.updateBootOrderInVmDevice(VmDeviceUtils.java:641) [bll.jar:] in the noise of engine.log
(In reply to Nikolai Sednev from comment #17) > (In reply to Fabian Deutsch from comment #15) > > (In reply to Nikolai Sednev from comment #14) > > > (In reply to yuliu from comment #13) > > > > (In reply to Nikolai Sednev from comment #12) > > > > > Flow is as described in description of a bug: > > > > > Steps to Reproduce: > > > > > 1.Take guest image and export via iso-uploader. > > > > > 2.Import template from export domain. > > > > > 3.Create VM from template and try to run it on RHEL6.6 host. > > > > > > > > > > I don't think I can provide more info than this, logs attached and > > > > > screenshot as well, sorry, but that's my best to describe. If you want to > > > > > see this happens, please contact me directly and observe on my setup. > > > > > > > > Did you try upload the image by engine-image-upload ? Since it's a tar image > > > > not an ISO file. > > > > > > > > I can't reproduce this bug either, needinfo Ryan for help. > > > > > > I did only as described above, only ISO, upload is OK, import then is fine, > > > VM creation is perfect, but VM start failed. > > > > Nikolai, does the VM come up at all? Or is not even the "bios" shown? > > VM not started at all. I didn't saw SPICE coming available for pressing it > to see the BIOS. Okay, then this is very very likely not caused by the image itself.
(In reply to Nikolai Sednev from comment #14) > I did only as described above, only ISO, upload is OK, import then is fine, > VM creation is perfect, but VM start failed. you say VM creation succeeded? Then it's a different thing than what you reported before since the screenshot attached here says the VM creation from template failed.
looking at the log, there are bunch of errors, most of them transient, some for network and some creations failed with "low level Image copy failed, code = 261" tried to reproduce together with Nikolai, we couldn't see it again. so closing, please re-open if it reproduce.