Red Hat Bugzilla – Bug 1016348
Shown "None" for RHN configuration Transaction title
Last modified: 2014-07-18 11:49:00 EDT
Created attachment 809046 [details]
Description of problem:
Clean install rhev-hypervisor6-6.5-20130930.0.auto1927.el6.iso and setup network.
Then configure RHN in RHN Registration page. Check that it showed "None" for RHN configuration Transaction title.
(Seen RHN Transaction.png)
Similar problems was met when configuring Satellite and SAM
Version-Release number of selected component (if applicable):
Steps to Reproduce:
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:
Thanks in advance.
Shown "Satellite" for RHN configuration Transaction title when register Satellite
Shown "SAM" for RHN configuration Transaction title when register SAM.
But met the follow issue:
Shown "Satellite" for RHN configuration Transaction title when register RHN for the first time,
and it will show "RHN" for RHN configuration Transaction title when register RHN for the seconed time.
For the low issue, i have report another bug 1043422 to track it.
Change this bug into "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.