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 1307036 - [RFE] Auto attach VDC subscription to ESXi hypervisor
Summary: [RFE] Auto attach VDC subscription to ESXi hypervisor
Keywords:
Status: CLOSED DUPLICATE of bug 1308544
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Registration
Version: 6.1.6
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: 1296845 1353215
TreeView+ depends on / blocked
 
Reported: 2016-02-12 14:20 UTC by Marcel Gazdík
Modified: 2023-09-07 18:44 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-15 16:27:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1308544 0 high CLOSED [RFE] Allow automatic assignment of subscriptions to hypervisors discovered by "virt-who" 2023-10-06 17:31:43 UTC
Red Hat Bugzilla 1353697 0 high CLOSED [RFE] virt-who should register automatically all hypervisor hosts in a cluster if there are RHEL VM inside 2023-10-06 17:32:58 UTC
Red Hat Bugzilla 1401106 0 medium CLOSED [RFE] Subscription-Intent: Allow a user to express the intent of how a subscription should be used, using a rules based ... 2023-10-06 17:34:56 UTC

Internal Links: 1308544 1353697 1401106

Description Marcel Gazdík 2016-02-12 14:20:37 UTC 
Description of problem:
  Support for auto attach functionality for ESXi hypervisors in virt-who environment. The VDC subscription must be attached manually to each hypervisor
reported by the virt-who. This is turning into very difficult task in environments with hundreds of hypervisors.

Version-Release number of selected component (if applicable):
Satellite 6.X


Actual results:
  Each ESXi HV has to be subscribed manually.

Expected results:
  VDC subscription will be attached automatically

Additional info:
  Current workaround is using API which is very slow.
Comment 2 Tom McKay 2016-02-12 16:13:44 UTC 
The following behavior is expected to work...

1. Don't assign a VDC to a hypervisor
2. Guest registers and then subscribes with --auto-attach
3. If the guest...
   a) ...has not been reported by virt-who yet, it will get a temporary guest subscription
   b) ...has been reported by virt-who, it will trigger an auto-attach on they parent hypervisor (which will grab a VDC) and then guest will get permanent guest subscription

If this is not acceptable or causing problems, please expand on the issues involved for this RFE.
Comment 3 Evgeni Golov 2016-02-12 16:28:37 UTC 
Hi Tom,

is there any way to select which VDC pool will be used?

We have different subs in the account that allow guests:
* Unlimited guests (1-2 sockets)
* Unlimited guests (4 sockets)
* Unlimited guests (8 sockets)
* Same as above but for 1 guest

Additionally we have them in multiple batches, bought at different times, expiring at different times.

As far as I know virt-who will not report socket-count for ESXi hypervisors.
Will 3b) then just grab any available 1-2 sockets, unlimited guests sub?

Regards
Evgeni
Comment 7 Preetesh Sharma 2016-06-20 03:22:12 UTC 
Customer is requesting for an workaround on this issue.

Is below workaround applicable to this problem ?
https://github.com/RedHatSatellite/katello-attach-subscription

Also kindly empathize that #comment 3.
Comment 9 Preetesh Sharma 2016-06-23 11:15:45 UTC 
Customer has also requested for the possibility to select the subscription based on (regexp)regular expression or some other method? 
preferred list: 
1) regexp on VCenter cluster name 
2) regexp on ESXi Host name"

So that they can filer based on the *Cluster* name (not hostname) in the VCenter.

Preetesh
Comment 10 Evgeni Golov 2016-06-24 07:24:55 UTC 
(In reply to Preetesh Sharma from comment #9)
> Customer has also requested for the possibility to select the subscription
> based on (regexp)regular expression or some other method? 
> preferred list: 
> 1) regexp on VCenter cluster name 

That data is not available at the moment :(

> 2) regexp on ESXi Host name"

That works in katello-attache-subscription today, but yeah would be great if that would be inside Satellite.
Comment 11 Bryan Kearney 2017-06-15 16:27:34 UTC 

*** This bug has been marked as a duplicate of bug 1308544 ***
Note You need to log in before you can comment on or make changes to this bug.