Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
1. Proposed title of this feature request
- Accurate marking of subscribed hypervisors, regardless of platform
2. Who is the customer behind the request?
Account: name and acct # <- please include both
- Shawn DeLuca - 5366814
TAM customer: no
SRM customer: no
Strategic: yes
3. What is the nature and description of the request?
- Please have ESX hypervisors accurately depict whether or not they are subscribed, both with the indicator button and in the hypervisor details.
4. Why does the customer need this? (List the business requirements here)
- When analyzing a potentially long list of hypervisors to find a few that are not subscribed, especially when one is attempting to true up one's subscription count, it becomes burdensome to have to go into the subscription details of each hypervisor and force it to show you what it's actual status is.
5. How would the customer like to achieve this? (List the functional requirements here)
- The indicator should be green or red depending upon whether or not the hypervisor is subscribed or not.
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
- We would download the patch, and then remove and add subscriptions to hypervisors to determine if the changes worked.
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
- No
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
- Sooner would be better
9. Is the sales team involved in this request and do they have any additional input?
- No
10. List any affected packages or components.
- N/A
11. Would the customer be able to assist in testing this functionality if implemented?
- Possibly.