Bug 1264049 - TUI/Auto clean install RHEV-H failed on single path iscsi
Summary: TUI/Auto clean install RHEV-H failed on single path iscsi
Keywords:
Status: CLOSED DUPLICATE of bug 1265209
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-node
Version: 3.5.6
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ovirt-3.6.0-rc3
: 3.5.6
Assignee: Fabian Deutsch
QA Contact: cshao
URL:
Whiteboard: node
Depends On: 1259831 1271118
Blocks: 1264358
TreeView+ depends on / blocked
 
Reported: 2015-09-17 11:59 UTC by cshao
Modified: 2016-02-10 19:18 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-16 12:11:04 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
rdsosreport.txt (85.42 KB, text/plain)
2015-09-18 05:05 UTC, cshao 		no flags Details
kernel panic (47.71 KB, image/png)
2015-10-13 11:11 UTC, cshao 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.