Bug 859821

Summary: Segmentation faults during the installation of RHEV-H
Product: Red Hat Enterprise Linux 6 Reporter: Anush Shetty <ashetty>
Component: ovirt-nodeAssignee: Mike Burns <mburns>
Status: CLOSED WORKSFORME QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4CC: acathrow, bsarathy, cshao, fdeutsch, gouyang, grajaiya, hadong, jboggs, leiwang, mburns, ovirt-maint, vbellur, ycui
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-11 13:18:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot of the segfault none

Description Anush Shetty 2012-09-24 06:29:54 UTC
Description of problem: During the installation of RHEV-H, we encountered segmentation faults.


Version-Release number of selected component (if applicable): 
rhev-hypervisor6-6.3-20120920.0.rhev31.auto33.el6.iso



How reproducible: Not consistent still filing since this was detected the second time.


Steps to Reproduce:
1. Install RHEV-H from ISO
2.
3.
  
Actual results:

Segmentation fault

Expected results:

Installation should proceed without any issues.


Additional info:

Comment 1 Anush Shetty 2012-09-24 06:30:24 UTC
Created attachment 616380 [details]
Screenshot of the segfault

Comment 3 Fabian Deutsch 2012-09-24 07:02:24 UTC
Did you maybe note some squashfs errors during boot?

Comment 4 Anush Shetty 2012-09-24 08:19:00 UTC
Nope, didn't notice any.

Comment 5 Mike Burns 2012-10-04 19:12:39 UTC
any hint on where it was?  what type of hardware?  what options were used?  log files?

Comment 6 Anush Shetty 2012-10-11 12:41:02 UTC
Tried this with installation of rhev-hypervisor6-6.3-20121010.2.auto55.el6.iso and was not able to reproduce the issue.

We shall get necessary details if we hit this issue again.

Comment 7 Mike Burns 2012-10-11 13:18:56 UTC
Closing since it can't be reproduced.  Please reopen if the issue is seen again.