Bug 1278358
| Summary: | Should add --type=hypervisor when register RHEVH to RHN | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | wanghui <huiwa> |
| Component: | ovirt-node | Assignee: | Fabian Deutsch <fdeutsch> |
| Status: | CLOSED ERRATA | QA Contact: | wanghui <huiwa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.5.6 | CC: | bmcclain, bugs, cshao, cwu, gklein, huiwa, huzhao, leiwang, lsurette, rbarry, yaniwang, ycui, ykaul |
| Target Milestone: | ovirt-3.6.1 | ||
| Target Release: | 3.6.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-node-3.6.0-0.22.20151126git72acbb2.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-03-09 14:42:32 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: | |||
|
Comment 1
Red Hat Bugzilla Rules Engine
2015-11-05 10:38:33 UTC
I would also suggest that a bug be opened against the RHSM portal, since RHEV-H has its own product key (there was an earlier bug about this), and RHSM should be able to figure this out on its own based on that. Test version: rhev-hypervisor7-7.2-20151201.2.el7ev ovirt-node-3.6.0-0.23.20151201git5eed7af.el7ev.noarch Test steps: 1. Install rhev-hypervisor7-7.2-20151201.2.el7ev 2. Enable network 3. Register to RHN 4. Check in RHN 5. Check the log file Test result: 1. After step4, we can find registered rhevh in hypervisor type. 2. The output in log file about the registration is as follows. 2015-12-07 05:31:51,667 INFO /usr/sbin/subscription-manager register --force --type hypervisor --password XXXXXXXX --username qa So this issue is fixed in ovirt-node-3.6.0-0.23.20151201git5eed7af.el7ev.noarch. Change the status to verified. 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-2016-0378.html |