Bug 1412118 - RHEVH register to satellite 5.7 failed.
Summary: RHEVH register to satellite 5.7 failed.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-node
Version: 3.6.9
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Douglas Schilling Landgraf
QA Contact: Wei Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-11 10:01 UTC by Wei Wang
Modified: 2017-01-12 14:56 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-12 14:56:46 UTC
oVirt Team: Node
Target Upstream Version:


Attachments (Terms of Use)
log files (487.27 KB, application/x-gzip)
2017-01-11 10:01 UTC, Wei Wang
no flags Details
my_sat5.7_log (420.64 KB, application/x-gzip)
2017-01-12 03:29 UTC, Wei Wang
no flags Details
mmello_sat62_log (418.74 KB, application/x-gzip)
2017-01-12 03:31 UTC, Wei Wang
no flags Details

Description Wei Wang 2017-01-11 10:01:05 UTC
Created attachment 1239398 [details]
log files

Description of problem:
RHEVH register to satellite 5.7 failed.

Version-Release number of selected component (if applicable):
rhevh-7.3-20170110.1.el7ev.iso
ovirt-node-3.6.1-40.0.el7ev.noarch
satellite 5.7


How reproducible:
100%


Steps to Reproduce:
1. Clean install RHEVH
2. Input below information:
username: admin
password: xxxxxx
type: satellite
URL: https://example57.redhat.com
CA URL: https://example57.redhat.com/pub/RHN-ORG-TRUSTED-SSL-CERT
3. Register to satellite

Actual results:
An error occurred while applying the changes: │
│Error registering to RHN account

Expected results:
RHEVH register to satellite 5.7 successfully.


Additional info:
Check the config-file:
1. There is no RHN-ORG-TRUSTED-SSL-CERT file under /usr/share/rhn folder in rhevh
2. "serverURL" is configured wrong in /etc/sysconfig/rhn/up2date

Comment 1 Ryan Barry 2017-01-11 13:14:26 UTC
Does this work with the previous build?

Comment 3 Marcelo Moreira de Mello 2017-01-11 14:54:03 UTC
  Hello Wei, 

    Thanks for reporting this.  I'm going to check this today with Douglas and I'll report the results here. 

 Best,
mmello

Comment 4 Douglas Schilling Landgraf 2017-01-11 18:52:51 UTC
I see from logs:

2017-01-11 09:28:08,510      ERROR Failed to call: /usr/sbin/rhnreg_ks --novirtinfo --norhnsd --nopackages --force --password XXXXXXXX --username admin --serverUrl https://satellite57jan3.redhat.com/XMLRPC --sslCACert /etc/sysconfig/rhn/RHN-ORG-TRUSTED-SSL-CERT
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/ovirt/node/setup/rhn/rhn_model.py", line 263, in commit
    process.check_call(Vars.argbuilder.get_commandlist())
  File "/usr/lib/python2.7/site-packages/ovirt/node/utils/process.py", line 139, in check_call
    return int(subprocess.check_call(*args, **kwargs))
  File "/usr/lib64/python2.7/subprocess.py", line 542, in check_call
    raise CalledProcessError(retcode, cmd)

Wei Wang,

I am unable to access satellite57jan3.redhat.com, is it down?

Comment 8 Wei Wang 2017-01-12 02:01:07 UTC
Thanks mmello! I will retest with the environment you gave and give the report about satellite 5.7 here today.

Comment 10 Wei Wang 2017-01-12 03:29:10 UTC
Created attachment 1239758 [details]
my_sat5.7_log

Comment 11 Wei Wang 2017-01-12 03:31:50 UTC
Created attachment 1239759 [details]
mmello_sat62_log

Comment 15 Douglas Schilling Landgraf 2017-01-12 14:56:46 UTC
Closing as the sat57 got all available subscriptions for the requested channel have been exhausted. 

Error Class Code: 70
Error Class Info: 
     All available subscriptions for the requested channel have been exhausted.
     Please contact a Red Hat Satellite Sales associate.
Explanation: 
     An error has occurred while processing your request. If this problem
     persists please consult the Red Hat Customer Portal Knowledge Base
     landing page on common registration Error Class Codes at
     https://access.redhat.com/solutions/17036 for a possible resolution.
     If you choose to open a support case in the Red Hat Customer Portal,
     please be sure to include details of what you were trying to do when
     this error occurred and specifics on how to reproduce this problem.


There is KCS about it:
https://access.redhat.com/solutions/18134


Thanks!


Note You need to log in before you can comment on or make changes to this bug.