Bug 1156112
| Summary: | [rhevh 6.6] Can't install RHEVH successful on physical machine- Error Exception display. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ | ||||||
| Component: | ovirt-node | Assignee: | Fabian Deutsch <fdeutsch> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | urgent | ||||||||
| Version: | 3.5.0 | CC: | cshao, dfediuck, dougsland, ecohen, fdeutsch, gklein, gouyang, hadong, huiwa, iheim, juwu, leiwang, lsurette, rbarry, rhev-integ, sherold, ycui | ||||||
| Target Milestone: | --- | Keywords: | AutomationBlocker, Regression, TestBlocker, ZStream | ||||||
| Target Release: | 3.4.5 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | node | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | 1150377 | Environment: | |||||||
| Last Closed: | 2015-02-04 22:08:26 UTC | Type: | --- | ||||||
| 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: | 1150377 | ||||||||
| Bug Blocks: | 1133612 | ||||||||
| Attachments: |
|
||||||||
Created attachment 950906 [details]
attached ovirt-node.log from /var/log/ of rhev-hypervisor6-6.6-20141024.1.iso
I've run through this more than 20 times today without a reproducer.
If you encounter it again, please post the output of /proc/mounts and "find /liveos -exec ls -l {} \;"
I have report a new "bug 1158044 - [rhevh 6.6] Can't reinstall RHEVH successful on physical machine-Grub Installation Failed ." to track 20% reproduce issue. so this bug could be verified in rhev-hypervisor6-6.6-20141027.0.iso Julie, we need to note in the release notes - prominently - that this build can have installation problems on some hardware. We must also note that edit-node (tool) should not be used yet, with 6.6 based images, because the resulting images will also have trouble to boot. (In reply to Fabian Deutsch from comment #16) > Julie, > > we need to note in the release notes - prominently - that this build can > have installation problems on some hardware. > We must also note that edit-node (tool) should not be used yet, with 6.6 > based images, because the resulting images will also have trouble to boot. I understand 3.4.4 has been pushed back to Nov 25. Can you confirm again what you would like to include in for the errata doc text and release notes? Please add the doc text in the doc text field, and the 'requires_doc_text' flag will automatically be set to '?'. The 'requires_release_note' flag needs to be set manually and that's what you have done. Please confirm the request and provide doc text. 'this build can have installation problems on some hardware.' Can you clarify on this and let me know what problems and what kind of hardware? Many thanks, Julie (In reply to Julie from comment #17) > (In reply to Fabian Deutsch from comment #16) > > Julie, > > > > we need to note in the release notes - prominently - that this build can > > have installation problems on some hardware. > > We must also note that edit-node (tool) should not be used yet, with 6.6 > > based images, because the resulting images will also have trouble to boot. > > I understand 3.4.4 has been pushed back to Nov 25. Can you confirm again > what you would like to include in for the errata doc text and release notes? > Please add the doc text in the doc text field, and the 'requires_doc_text' > flag will automatically be set to '?'. The 'requires_release_note' flag > needs to be set manually and that's what you have done. Please confirm the > request and provide doc text. > 'this build can have installation problems on some hardware.' Can you > clarify on this and let me know what problems and what kind of hardware? Hey Julie, contrary to what I wrote in comment 16 we don't need that release note (and doctext anymore, because the cause for this bug has been found. 3.4.4 was released. moving to async release 3.4.4-1, only for RHEV-H Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-0128.html |
Created attachment 950905 [details] attached ovirt.log from /tmp of rhev-hypervisor6-6.6-20141024.1.iso