[Spacewalk-list] Indentifying host type

Gerhardus.Geldenhuis at gta-travel.com Gerhardus.Geldenhuis at gta-travel.com
Tue Jan 6 10:55:20 UTC 2009


> -----Original Message-----
> From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-
> bounces at redhat.com] On Behalf Of Brian Kosick
> Sent: 05 January 2009 19:45
> To: spacewalk-list at redhat.com
> Subject: Re: [Spacewalk-list] Indentifying host type
> 
> That's caused by haldaemon not running...
> 
> service haldeamon start
> 
> HAL depends on messagebus so if it fails to start, do this...
> 
> service messagebus restart
> service haldaemon restart
> 
> You should be OK...   Other than that, I'm relatively new to spacewalk
> and rhnreg_ks as well and I can't answer the rest of your question...

Indeed! Many thanks.


> 
> Brian
> 
> 
> On Mon, 2009-01-05 at 07:17 -0700, Gerhardus.Geldenhuis at gta-travel.com
> wrote:
> > Hi
> > Can anyone comment on how the registration process using rhnreg_ks
> > determines the system type. Eg how does it know whether the machine
> you
> > are registering is a Virtual Guest, Virtual Host or a non-Virtual
> > system.
> >
> > We have some Citrix xen servers:
> > cat /etc/redhat-release
> > XenServer release 4.1.0-7843p (xenenterprise)
> >
> > that is not picked up as Virtual Host servers when we register them
> in
> > spacewalk and instead are just registered as "Non-Virtual System"
> >
> > I do get the following error when registering:
> > Error reading hardware information: dbus_bindings.DBusException
> > Error reading DMI information: dbus_bindings.DBusException
> >
> > But I get that for other machines too when registering, and this
> error
> > has not prevented spacewalk from correctly indentifying whether the
> > machine is a xen guest or a physical server and thus I believe it is
> not
> > related.
> >
> > Regards

I remembered that I went through some effort to get xen guests
registered and listed under the correct xen host(created using virsh)
while using Satellite and redhat.

Do that I had to do:
yum install rhn-kickstart-virtualization

I did that but I get the following error message:

rhnreg_ks --serverUrl=http://LONGRHN01A.gta.travel.lcl/XMLRPC
--activationkey=1-basic --username=admin --force
libvir: Xen Daemon error : internal error failed to connect to xend
libvir: Xen Daemon error : internal error failed to connect to xend
An error has occurred:
exceptions.AttributeError
See /var/log/up2date for more information

Traceback (most recent call last):
  File "/usr/sbin/rhnreg_ks", line 267, in ?
    cli.run()
  File "/usr/share/rhn/up2date_client/rhncli.py", line 65, in run
    sys.exit(self.main() or 0)
  File "/usr/sbin/rhnreg_ks", line 176, in main
    rhnreg.sendVirtInfo(systemId)
  File "/usr/share/rhn/up2date_client/rhnreg.py", line 648, in
sendVirtInfo
    support.refresh()
  File "/usr/share/rhn/virtualization/support.py", line 71, in refresh
    domain_list = domains.values()
exceptions.AttributeError: 'list' object has no attribute 'values'


I am assuming that the appropriate libraries that this python code is
expecting is not in place. I someone able to make some suggestions as to
what libraries are required for the python code to pick up all the
necessary info.

Regards

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________




More information about the Spacewalk-list mailing list