Created attachment 1092613 [details] rhn_issue.tar.gz Description of problem: RHN status always show success even if the registration was failed. And the same issue with Satellite/SAM. Version-Release number of selected component (if applicable): rhev-hypervisor7-7.2-20151104.0 ovirt-node-3.6.0-0.20.20151103git3d3779a.el7ev.noarch subscription-manager-1.15.9-15.el7.x86_64 python-rhsm-1.15.4-5.el7.x86_64 vdsm-4.17.10.1-0.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. Install RHEV-H 7.2 2. Go to "RHN Registration" page, register to RHN/Satellite/SAM with incorrect info. 3. Check RHN status in TUI. Actual results: RHN status always show success even if the registration was failed Expected results: RHN can show correct status. Additional info:
Created attachment 1092616 [details] failed
Created attachment 1092617 [details] always show success
*** Bug 1282698 has been marked as a duplicate of this bug. ***
Test version: rhev-hypervisor7-7.2-20151210.1 ovirt-node-3.6.0-0.24.20151209gitc0fa931.el7ev.noarch Test steps: 1. Install RHEV-H 7.2 latest build 2. Go to "RHN Registration" page, register to RHN with incorrect info. 3. Check RHN status in TUI. Actual results: 1. pop-up: registration failed 2. But in TUI, Registration Status still show as "RHN" The current status shouldn't show as RHN due to the failed registration. So I have to assigned this bug.
Test version: RHEV-H 7.2-20151221.1.el7ev ovirt-node-3.6.0-0.24.20151209gitc0fa931.el7ev.noarch Got the same issue with #c5, so I have tp assigned this bug again. Test steps: 1. Install RHEV-H 7.2 latest build 2. Go to "RHN Registration" page, register to RHN with incorrect info. 3. Check RHN status in TUI. Actual results: 1. pop-up: registration failed 2. But in TUI, Registration Status still show as "RHN" The current status shouldn't show as RHN due to the failed registration.
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. https://rhn.redhat.com/errata/RHBA-2016-0378.html