Bug 772902

Summary:	Register to RHN by run command "ovirt-config-rhn" failed.
Product:	Red Hat Enterprise Linux 6	Reporter:	cshao <cshao>
Component:	ovirt-node	Assignee:	Joey Boggs <jboggs>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	6.2	CC:	acathrow, bsarathy, cpelland, gouyang, jboggs, leiwang, mburns, moli, ovirt-maint, sgordon, ycui
Target Milestone:	rc	Keywords:	ZStream
Target Release:	6.2
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ovirt-node-2.2.1-1.el6	Doc Type:	Bug Fix
Doc Text:	Previously, registering to Red Hat Network during autoinstall would fail. This was due to the wrong Red Hat Network registration command being called. This update corrects this logic, ensuring that the correct Red Hat Network registration command is called.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-07-19 14:17:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	773676

Description cshao 2012-01-10 09:54:38 UTC

Description of problem:
Register to RHN by run command "ovirt-config-rhn" failed.

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.2-20120106.0.el6_2

How reproducible:
100%

Steps to Reproduce:
1. Install RHEV-H.
2. Run command "/usr/libexec/ovirt-config-rhn".
3. Register to public RHN
4. check the system on rhn (https://rhn.redhat.com). 

  
Actual results:
1. Register RHN failed, no current system in RHN.
2. The word "successful" spell wrong in log <<Jan 10 06:19:16 System  sucessfuly registered >>. 

========================================================
[root@cshao-test libexec]# ./ovirt-config-rhn 
1) Register to public RHN
2) Register to RHN Satellite
3) Register to Subscription Asset Manager
4) Return to the Hypervisor Configuration Menu
Choose an option: 1

Enter RHN account username: qa

Enter password for RHN account: 
Enter profile name for this system (optional): 

Enter HTTP proxy in host:port format, e.g. proxy.example.com:3128 (leave blank if not required): 
 File persisted

Successfully persisted /etc/rhsm/rhsm.conf

Jan 10 06:18:59 Registering to RHN account.....
The system has been registered with id: 660c3abe-a5c4-41da-b18f-bae05a7a7995 
Installed Product Current Status:
 File persisted

Successfully persisted /etc/pki/consumer/cert.pem
 File persisted

Successfully persisted /etc/pki/consumer/key.pem
Cannot persist: /var/lib/rhsm/productid.js
 File persisted

Successfully persisted /var/lib/rhsm/cache/installed_products.json
 File persisted

Successfully persisted /var/lib/rhsm/facts/facts.json

Jan 10 06:19:16 System  sucessfuly registered 


Expected results:
1. Register to RHN by run ovirt-config-rhn can successful.
2. No spelling  mistakes.

Additional info:
1. Register to RHN by TUI no such issue.
2. No log is recorded to ovirt.log file after run command "ovirt-config-rhn".

Comment 2 Mike Burns 2012-01-10 13:43:51 UTC

This is not a valid scenario.  The user should never be running ovirt-config-rhn directly.  That being said, it does need to be investigated since ovirt-config-rhn is used during autoinstall.

Comment 5 Mike Burns 2012-01-12 17:39:20 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Registering to RHN during autoinstall would fail due to a bug that send RHN registrations using the wrong method.  This patch fixes the logic to send RHN registrations correctly

Comment 6 Stephen Gordon 2012-01-12 19:37:46 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-Registering to RHN during autoinstall would fail due to a bug that send RHN registrations using the wrong method.  This patch fixes the logic to send RHN registrations correctly+Previously, registering to RHN during autoinstall would fail. This was due to the wrong RHN registration command being called. This patch changes this logic, calling the correct RHN registration command.

Comment 8 cshao 2012-02-20 09:43:51 UTC

Block by bug 791122, I will verify it after fix bz 791122.

Comment 10 Stephen Gordon 2012-03-27 21:25:59 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-Previously, registering to RHN during autoinstall would fail. This was due to the wrong RHN registration command being called. This patch changes this logic, calling the correct RHN registration command.+Previously, registering to Red Hat Network during autoinstall would fail. This was due to the wrong Red Hat Network registration command being called. This update corrects this logic, calling the correct Red Hat Network registration command.

Comment 11 Stephen Gordon 2012-05-28 16:32:56 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-Previously, registering to Red Hat Network during autoinstall would fail. This was due to the wrong Red Hat Network registration command being called. This update corrects this logic, calling the correct Red Hat Network registration command.+Previously, registering to Red Hat Network during autoinstall would fail. This was due to the wrong Red Hat Network registration command being called. This update corrects this logic, ensuring that the correct Red Hat Network registration command is called.

Comment 13 errata-xmlrpc 2012-07-19 14:17:37 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.

http://rhn.redhat.com/errata/RHBA-2012-0741.html