Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1258307 - subscription-manager --type=hypervisor for Satellite 6.1 showing as "host"
Summary: subscription-manager --type=hypervisor for Satellite 6.1 showing as "host"
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Registration
Version: 6.1.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: Tom McKay
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-31 04:21 UTC by Anand Vaddarapu
Modified: 2023-09-14 03:04 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-07 19:51:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Anand Vaddarapu 2015-08-31 04:21:31 UTC
Description of problem:
I have tested to register RHEV's hypervisors thick hypervisor using --type=hypervisor using RHEL6.7's subscription-manager, which didn't work to register the host after the provisioning.  It was registered as a "host", even though I used "hypervisor" as a type.


Actual results:
It was registered as a "host", even though I used "hypervisor" as a type.

Expected results:
My hope that above command would register the hypervisor as "hypervisor" rather than "host".

Comment 3 Barnaby Court 2016-03-04 20:15:49 UTC
Where are you seeing the system listed as type "Host"?

When I look in the database after registration using 
subscription management server: 3.0.0.4-Unknown
subscription management rules: 5.15.2
subscription-manager: 1.15.9-15.el7
python-rhsm: 1.15.4-5.el7

and Sat 6.2 it is properly recorded as type hypervisor.

Comment 4 Tom McKay 2016-03-07 19:51:43 UTC
The term "host" is overused in Sat-6 a lot. Hypervisors are not listed differently than other physical systems. 

If there are specific enhancements that are desired, please reopen this as an RFE with detailed usecase.

Comment 5 Red Hat Bugzilla 2023-09-14 03:04:31 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.