Bug 1264049

Summary: TUI/Auto clean install RHEV-H failed on single path iscsi
Product: Red Hat Enterprise Virtualization Manager Reporter: cshao <cshao>
Component: ovirt-nodeAssignee: Fabian Deutsch <fdeutsch>
Status: CLOSED DUPLICATE QA Contact: cshao <cshao>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 3.5.6CC: amureini, cwu, ecohen, fdeutsch, gklein, huiwa, huzhao, leiwang, lsurette, mgoldboi, yaniwang, ycui
Target Milestone: ovirt-3.6.0-rc3Keywords: TestBlocker, TestOnly
Target Release: 3.5.6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: node
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-16 12:11:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1259831, 1271118    
Bug Blocks: 1264358    
Attachments:
Description Flags
rdsosreport.txt
none
kernel panic none

Comment 5 cshao 2015-09-18 05:05:55 UTC
Created attachment 1074676 [details]
rdsosreport.txt

Comment 6 Fabian Deutsch 2015-09-18 14:59:44 UTC
Likely a symptom of bug 1259831

Comment 7 cshao 2015-09-22 08:31:21 UTC
I can reproduce this issue with RHEV-H 7.1 for RHEV 3.5.5 rhev-hypervisor-7-7.1-20150917.0 (ovirt-node-3.2.3-23.el7.noarch) build.

Comment 8 cshao 2015-10-13 07:44:25 UTC
Still can reproduce this issue with rhev-hypervisor7-7.2-20151009.0 (ovirt-node-3.3.0-0.13.20151008git03eefb5.el7ev.noarch).

Comment 11 Fabian Deutsch 2015-10-13 09:48:42 UTC
Allon, I'm quite sure it's not that bug - or a regression of that one, because we already include device-mapper-multipath-0.4.9-85.el7 which fixes this issue.

Comment 12 Allon Mureinik 2015-10-13 09:51:01 UTC
(In reply to Fabian Deutsch from comment #11)
> Allon, I'm quite sure it's not that bug - or a regression of that one,
> because we already include device-mapper-multipath-0.4.9-85.el7 which fixes
> this issue.

I don't understand the question.
Are you referring to bug 1271118?

Comment 14 Fabian Deutsch 2015-10-13 09:54:50 UTC
Yes, I was referring to the fact that this bug also appears despite the fact that the fix for bug 1271118 is already in the tested build.

Comment 16 cshao 2015-10-13 11:11:35 UTC
Created attachment 1082349 [details]
kernel panic

Comment 17 cshao 2015-10-15 11:12:40 UTC
Update:

For the original issue, I tested with the incorrect nic name, so it will jump to dractu mode, actually we have reported the dracut issue(1265209).

For correct nic name on single path iscsi machine, it will cause kernel panic, we are still investigation on it, will give update later.

Comment 18 cshao 2015-10-16 12:08:28 UTC
(In reply to shaochen from comment #17)
> Update:
> 
> For the original issue, I tested with the incorrect nic name, so it will
> jump to dractu mode, actually we have reported the dracut issue(1265209).
> 
> For correct nic name on single path iscsi machine, it will cause kernel
> panic, we are still investigation on it, will give update later.

Bug 1272434 can trace the kernel panic issue.

Comment 19 cshao 2015-10-16 12:11:04 UTC
Close this bug according #c17 & 18.

*** This bug has been marked as a duplicate of bug 1265209 ***