Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1309187

Summary: Should change registration status to RHSM in RHSM page
Product: Red Hat Enterprise Virtualization Manager Reporter: cshao <cshao>
Component: ovirt-nodeAssignee: Ryan Barry <rbarry>
Status: CLOSED DEFERRED QA Contact: cshao <cshao>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5.7CC: dfediuck, fdeutsch, gklein, huiwa, huzhao, leiwang, lsurette, mgoldboi, weiwang, yaniwang, ycui, ykaul
Target Milestone: ovirt-4.0.0-rcKeywords: ZStream
Target Release: 4.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1322785 (view as bug list) Environment:
Last Closed: 2016-06-09 08:17:02 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 1322785    
Attachments:
Description Flags
RHSM.png none

Description cshao 2016-02-17 01:44:57 EST
Created attachment 1127853 [details]
RHSM.png

Description of problem:
Should change registration status to RHSM in RHSM page.

Version-Release number of selected component (if applicable):
rhev-hypervisor7-7.2-20160215.2.
ovirt-node-3.2.3-31.el7.noarch 

How reproducible:
100%

Steps to Reproduce:
1. Install rhev-hypervisor7-7.2-20160215.2.
2. Enter RHSM Registration page
2. Register to RHSM.
3. Focus on registration status.

Actual results:
Registration status show as RHN in RHSM page.

Expected results:
Should change registration status to RHSM in RHSM page.

Additional info:
Comment 1 Mike McCune 2016-03-28 19:24:30 EDT
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune@redhat.com with any questions
Comment 3 Fabian Deutsch 2016-06-09 08:17:02 EDT
This issue will not be fixed with an eventually attached in RHEV 4.0. Instead this bug is getting fixed by the new functionality in Cockpit.