RHEV-H and Satellite

Latest response

Upon attempting to register the RHEV-H 3 beta with Satellite 5.4, I get the following messages.

 

On the RHEV-H:

/var/log/ovirt.log:

---

RHN Config does not exist
cacert: http://lxechostar.osti.gov/pub/RHN-ORG-TRUSTED-SSL-CERT
location: /etc/sysconfig/rhn/RHN-ORG-TRUSTED-SSL-CERT
Downloading Satellite CA cert.....
From: http://lxechostar.osti.gov/pub/RHN-ORG-TRUSTED-SSL-CERT To: /etc/sysconfig/rhn/RHN-ORG-TRUSTED-SSL-CERT
/etc/sysconfig/rhn/RHN-ORG-TRUSTED-SSL-CERT
File already persisted: /etc/sysconfig/rhn/RHN-ORG-TRUSTED-SSL-CERT

/etc/sysconfig/rhn/RHN-ORG-TRUSTED-SSL-CERT Already persisted

Registering to RHN account.....
['/usr/sbin/rhnreg_ks', '--serverUrl', 'http://<FQDN OF MY RHN SATELLITE>', '--sslCACert', '/etc/sysconfig/rhn/RHN-ORG-TRUSTED-SSL-CERT', '--username', '<MY USERNAME>', '--password', 'XXXXXXXX', '--novirtinfo', '--norhnsd', '--nopackages', '--force']

An error has occurred:
Error communicating with server. The message was:
Not Found
See /var/log/up2date for more information

Error registering to RHN account!
---

 

In /var/log/up2date:

---

[Mon Dec 12 21:04:04 2011] up2date A protocol error occurred: Not Found , attempt #1,
[Mon Dec 12 21:04:04 2011] up2date Could not find URL, <FQDN OF MY SATELLITE> /RPC2
[Mon Dec 12 21:04:04 2011] up2date Check server name and/or URL, then retry
[Mon Dec 12 21:04:04 2011] up2date Error communicating with server. The message was:
Not Found
[Mon Dec 12 21:04:04 2011] up2date Error communicating with server. The message was:
Not Found
[Mon Dec 12 21:04:04 2011] up2date
Traceback (most recent call last):
  File "/usr/sbin/rhnreg_ks", line 217, in <module>
    cli.run()
  File "/usr/share/rhn/up2date_client/rhncli.py", line 74, in run
  File "/usr/sbin/rhnreg_ks", line 89, in main
    rhnreg.getCaps()
  File "/usr/share/rhn/up2date_client/rhnreg.py", line 246, in getCaps
  File "/usr/share/rhn/up2date_client/rhnserver.py", line 156, in __get_capabilities
  File "/usr/share/rhn/up2date_client/rhnserver.py", line 50, in __call__
  File "/usr/share/rhn/up2date_client/rpcServer.py", line 279, in doCall
up2date_client.up2dateErrors.CommunicationError: Error communicating with server. The message was:
Not Found
---

JG
Log in to join the conversation

Responses

JG Active Contributor 160 points
15 December 2011 8:17 AM

Noting that there aren't any comments, I believe this is going to prompt me to end my beta participation and go back to RHEV 2.1.  I believe I'll wait a year and review RHEV 3 when it has better documentation and a bit more verbosity in the logs then what I am seeing above.

PM Red Hat Guru 3594 points
15 December 2011 11:25 AM

Hello Jason,

 

1] /var/log/up2date has :

 

[Mon Dec 12 21:04:04 2011] up2date A protocol error occurred: Not Found , attempt #1,

[Mon Dec 12 21:04:04 2011] up2date Could not find URL, <FQDN OF MY SATELLITE> /RPC2

..snip..

up2date_client.up2dateErrors.CommunicationError: Error communicating with server. The message was:
Not Found

 

These indicate there is likely a connectivity issue to the Satellite server. Can you check if the RHEV-H server is able to connect to the Satellite server ?

telnet <satellite-fqdn> 443

telnet <satellite-fqdn> 80

 

2] Also the log has : "up2date Could not find URL, <FQDN OF MY SATELLITE> /RPC2". 

Can you confirm what was the server url which you entered ? It should be entered as "https://<satellite-fqdn>

 

 

~ Paresh

JG Active Contributor 160 points
16 December 2011 11:38 PM

1) It can indeed communicate to Satellite sockets:

 

# telnet <SATELLITE FQDN> 80
Trying <IP OF SATELLITE>...
Connected to <SATELLITE FQDN>.
Escape character is '^]'.
GET
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>400 Bad Request</title>
</head><body>
<h1>Bad Request</h1>
<p>Your browser sent a request that this server could not understand.<br />
</p>
<hr>
<address>Apache Server at <SATELLITE FQDN> Port 80</address>
</body></html>
Connection closed by foreign host.

# telnet <SATELLITE FQDN> 443

Trying <IP OF SATELLITE>...
Connected to <SATELLITE FQDN>.
Escape character is '^]'.
^]
 

So connections do occur.  This means that both name resolution is working, satellite is listening, and there are no network communication problems.

 

2) The URL is indeed what I entered.  However, not that I entered for the URL: https://<FQDN of Satellite> and for the CA: https://<FQDN of Satellite>/pub/RHN-ORG-TRUSTED-SSL-CERT.  The log messages are not reflecting that I added https:// to the fqdn of the RHN Satellite host.

 

Thanks.

 

J

JO Community Member 42 points
15 December 2011 12:55 PM

Jason I have ran into the same issues trying to register a RHEV-H server to the Satellite server 5.4. and I got around this issue by not using the UI on the Concloe of the RHEV-H server and ssh to the host as the user admin and complete the registration there. I have reported this issue to the beta team as well.

JG Active Contributor 160 points
16 December 2011 11:44 PM

Jim,

  I had success by ssh as root and running rhn_register.  If I use the admin account via ssh, that brings up the menu I was already using to register the host whch causes the problems that occur.  I could, however, use F2 after ssh as the admin user to bring up a console to perform the work.  Anyway, this worked, thanks for the advice.

 

J

ka Active Contributor 150 points
11 January 2012 9:52 PM

Hi  Jim,

 

try  editing  /etc/sysconfig/rhn/up2date to  confirm path  of  sslCACert  and  URL of  satellite  server  https://satellite.fqdn/XMLRPC, later  run   persist /etc/sysconfig/rhn/up2date

 

kind  regards,

BM Active Contributor 378 points
12 January 2012 7:51 AM