Bug 1322782

Summary: [z-stream clone - 3.6.5] An error in ovirt-node.log related to RHN register
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: ovirt-nodeAssignee: Ryan Barry <rbarry>
Status: CLOSED ERRATA QA Contact: wanghui <huiwa>
Severity: medium Docs Contact:
Priority: low    
Version: 3.6.0CC: cshao, dfediuck, gklein, huiwa, huzhao, leiwang, lsurette, mgoldboi, rbarry, yaniwang, ycui, ykaul
Target Milestone: ovirt-3.6.5Keywords: ZStream
Target Release: 3.6.5   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-node-3.6.1-9.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1290297 Environment:
Last Closed: 2016-04-20 16:24:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1290297    
Bug Blocks:    

Comment 2 wanghui 2016-04-06 02:22:52 UTC 
Test version:
rhev-hypervisor7-7.2-20160330.0

Test steps:
1. TUI install rhev-hypervisor7-7.2-20160330.0
2. Register rhevh to RHN with profile name "test-20160216"
3. Check the ovirt-node.log file.

Test result:
1. It reports as follows.
2016-04-06 02:01:21,647       INFO System test-20160216 successfully registered to SAM

This issue has partial fixed with profile name. But we still encounter the problem that log promote register to SAM instead of RHSM. So change the status to assigned.
Comment 4 wanghui 2016-04-14 08:58:16 UTC 
Test Version:
rhevh-7.2-20160413.0.el7ev
ovirt-node-3.6.1-12.0.el7ev.noarch

Test steps:
1. TUI install rhevh-7.2-20160413.0.el7ev
2. Register rhevh to RHN with profile name "test"
3. Check the ovirt-node.log file.

Test result:
1. It reports as follows.
2016-04-14 08:54:23,639       INFO System test successfully registered to RHSM

This issue is fixed in ovirt-node-3.6.1-12.0.el7ev.noarch.
Comment 7 errata-xmlrpc 2016-04-20 16:24:17 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.

https://rhn.redhat.com/errata/RHBA-2016-0664.html