Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 970015 - [RFE] The profile name should be displayed in Red Hat Network page
Summary: [RFE] The profile name should be displayed in Red Hat Network page
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Joey Boggs
QA Contact: Virtualization Bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2013-06-03 10:28 UTC by wanghui
Modified: 2014-06-24 20:49 UTC (History)
14 users (show)

Fixed In Version: ovirt-node-3.0.1-10.el6
Doc Type: Enhancement
Doc Text:
Previously the profile name was not displayed in the Red Hat Network page. As the profile name is used to find the hypervisor in Red Hat Network, it would be beneficial to the user to have the profile name displayed. The profile name is now displayed in TUI as a reminder.
Clone Of:
Last Closed: 2014-01-21 19:35:11 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0033 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2014-01-22 00:14:30 UTC

Description wanghui 2013-06-03 10:28:56 UTC
Description of problem:
The profile name should be better to display in Red Hat Network page once it been configured successfully. Because you will using the profile name to find the Rhev-hypervisor in Red Hat Network, so it should be better to display it as a reminder.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Clear install Rhev-hypervisor.
2. Register to RHN/Satellite/Subscription Asset Manager with valid Profile Name.
3. Check the Profile Name in TUI.

Actual results:
After step3, the Profile Name is blank.

Expected results:
After step3, it is better to display the profile name.

Additional info:

Comment 1 RHEL Program Management 2013-10-14 03:26:49 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 5 Cheryn Tan 2014-01-08 05:36:49 UTC
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

Thank you for your help.

Comment 6 wanghui 2014-01-08 09:14:50 UTC
Test version:

Test steps:
1. Clear install Rhev-hypervisor.
2. Register to RHN/Satellite/Subscription Asset Manager with valid Profile Name.
3. Check the Profile Name in TUI.

Test result:
1. After step3, it displays the profile name in TUI.

So this bug is fixed in rhevh-6.5-20131220.0.iso. Change the status from ON_QA to VERIFIED.

Comment 8 errata-xmlrpc 2014-01-21 19:35:11 UTC
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.


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