Bug 1235351
| Summary: | RHEV-H hypervisor is not showing the local disk | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
| Component: | ovirt-node | Assignee: | Ryan Barry <rbarry> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.5.0 | CC: | cshao, ecohen, fdeutsch, gchakkar, lbopf, leiwang, lsurette, nashok, pdwyer, rbarry, virt-bugs, ycui, ylavi |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | 3.5.4 | Flags: | fdeutsch:
Triaged+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | node | ||
| Fixed In Version: | ovirt-node-3.2.3-13.el7 ovirt-node-3.2.3-13.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, when Red Hat Enterprise Virtualization Hypervisor was installed on a host with multiple disks, some disks did not appear in the installation dialog. Now, all disks are detected, and appear during the installation.
|
Story Points: | --- |
| Clone Of: | 1203176 | Environment: | |
| Last Closed: | 2015-09-03 17:55:16 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: | 1203176 | ||
| Bug Blocks: | |||
|
Comment 3
Fabian Deutsch
2015-07-08 13:12:06 UTC
Verified this bug on rhev-hypervisor6-6.7-20150717.0.el6ev(ovirt-node-3.2.3-11.el6) and rhev-hypervisor-7-7.1-20150717.0.el7ev(ovirt-node-3.2.3-11.el7.noarch). Test env. Emulex FC HBA and with _15_ luns with 2 paths and _one_ local disk on IBM 3560M4(this bug depends on how much luns but not related hardware.) Steps: 1. TUI install rhevh. 2. Navigate to rhevh boot disk selection and installation disk selection pages These 15 luns and local disks can be detected now. 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-1733.html |