[Spacewalk-list] Spacewalk 2.7 - OpenVZ Debian containers

[Robert Paschedag]

Am 15. Februar 2018 20:40:19 MEZ schrieb Ben Myatt <ben at myattzone.org.uk>:
>Hi,
>
>I don’t believe this is the case as the containers only have 1 IP
>address and the newer ones being on Debian 9, the ifconfig setup should
>be the latest. 
>
>I will double check though.
>
>Kind Regards
>Ben Myatt
>
>> On 15 Feb 2018, at 18:18, Robert Paschedag <robert.paschedag at web.de>
>wrote:
>> 
>> Am 15. Februar 2018 18:54:06 MEZ schrieb Ben Myatt
><ben at myattzone.org.uk>:
>>> Hi,
>>> 
>>> I am trying to register a Debian 9 client with spacewalk 2.7. The
>>> client is configured as a container on a CentOS 7 host, running
>openvz,
>>> virtuozzo kernel 2.6.32-042stab127.2. It has also been tested with a
>>> newer kernel version of 3.10.0-693.11.6.vz7.42.5.
>>> 
>>> I can get CentOS containers registered but cannot get any Debian
>>> machines to register properly. 
>>> The error I get is :Error reading network interface information:
><type
>>> 'exceptions.IOError’>” and in the up2date log file it reads the
>>> following "[Mon Feb 12 12:55:30 2018] up2date Warning: haldaemon or
>>> messagebus service not running. Cannot probe hardware and DMI
>>> information.”
>>> This does actually register it with the server but I does not allow
>a
>>> base channel to be set.
>>> 
>>> All Debian machines that aren’t containers are fine.
>>> 
>>> Do you have any info on this?
>>> 
>>> 
>>> Kind Regards
>>> Ben Myatt
>>> 
>>> 
>>> _______________________________________________
>>> Spacewalk-list mailing list
>>> Spacewalk-list at redhat.com
>>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>> 
>> Please check if you have old style ifconfig "aliases" defined (e.g.
>eth0:0). This causes that message. Had that also on several servers.
>> 
>> Robert

Maybe you could check, if you get the same error if you run rhn-profile-sync on the Debian system.

Robert