Bug 1525375
Summary: | [Engine 4.1] Failed to start VM with direct lun on both 4.1 and 4.2 host | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [oVirt] vdsm | Reporter: | Israel Pinto <ipinto> | ||||||||
Component: | General | Assignee: | Eyal Shenitzky <eshenitz> | ||||||||
Status: | CLOSED NOTABUG | QA Contact: | Israel Pinto <ipinto> | ||||||||
Severity: | high | Docs Contact: | |||||||||
Priority: | high | ||||||||||
Version: | 4.19.41 | CC: | amureini, bugs, ipinto, mavital, mzamazal, nsoffer, ylavi | ||||||||
Target Milestone: | ovirt-4.2.1 | Flags: | rule-engine:
ovirt-4.2?
ylavi: planning_ack+ ipinto: devel_ack? ipinto: testing_ack? |
||||||||
Target Release: | --- | ||||||||||
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: | 2018-01-02 09:21:18 UTC | Type: | Bug | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
Israel Pinto
2017-12-13 08:36:21 UTC
Created attachment 1367175 [details]
logs(engine,vdsm - both hosts)
Created attachment 1367176 [details]
Events - vm is up
Created attachment 1367177 [details]
Events - Failed to start VM
I couldn't reproduce the bug with the steps above on my setup. I created a VM and attached an iSCSI disk to it. In step 5. the VM had automatically and successfully migrated to the 4.2 host, so I put that host to maintenance to perform step 5. with failure. Even then the VM starts successfully in step 7., on any of the hosts. Considering the weird errors reported from libvirt in bug 1524941, I'd suggest double checking that there is no problem outside oVirt, e.g. with storage. Dropping blocker flag according to https://lists.ovirt.org/pipermail/devel/2017-December/032213.html (In reply to Sandro Bonazzola from comment #5) > Dropping blocker flag according to > https://lists.ovirt.org/pipermail/devel/2017-December/032213.html Pushing out to 4.2.1 accordingly. (In reply to Milan Zamazal from comment #4) > I couldn't reproduce the bug with the steps above on my setup. I created a > VM and attached an iSCSI disk to it. In step 5. the VM had automatically and > successfully migrated to the 4.2 host, so I put that host to maintenance to > perform step 5. with failure. Even then the VM starts successfully in step > 7., on any of the hosts. > > Considering the weird errors reported from libvirt in bug 1524941, I'd > suggest double checking that there is no problem outside oVirt, e.g. with > storage. Can you please check? Closing this BZ after check with storage DEV, There was problem with the storage settings that cause this problem. |