[Spacewalk-list] Re-registering clients causing problem with client-type identification

[Michal Bruncko]

Hello again,

I will try to formulate my question another way: how the client is 
detecting that if it is the virtual guest or standalone station? As I 
can see from VM properties within Spacewalk, this system contain 
virtualization and UUID fields. From which system resource is this 
information provided from client to server?

I remember that I had similar problem once I've used 1.2 or 1.3 version 
of Spacewalk satellite.

thanks

michal

On 31. 3. 2013 20:37, Michal Bruncko wrote:
> Hello list,
>
> I am in following situation:
> - I've successfully installed and using spacewalk 1.9 with ~20 clients 
> for some time
> - I've decided to rename one of spacewalk client (paravirtualized 
> guest on XenServer) following way:
>  -- delete system entry from Spacewalk server (using classic system 
> deletion)
>  -- rename hostname (editing /etc/sysconfig/network, /etc/hosts file) 
> followed with restart
>  -- and try to re-register with spacewalk using "--foce" parameter to 
> rhnreg_ks
>
> But now, I see the client as the classic (non para-virtualized) system 
> (rhn-icon-system.gif). So I have decided to do the following:
> - remove all sapcewalk client packages from client
> - remove /etc/sysconfig/rhn and /usr/share/rhn directories
> - remove system entry again from Spacewalk server
> - reboot client and completely reinstall spacewalk client packages on 
> client
> - register client without use of "--force" parameter
>
> but the situation remains same.
>
> Questions:
> - why the client system is threaded as normal system from Spacewalk 
> server point of view? when I registered client client system at first 
> time, it was identified correctly as "paravirtualized" host
> - is there any chance to fix this?
>
> Additional info:
> - I am using spacewalk 1.9 on server and on client as well
> - Used CentOS 6.4 (x86_64) as operating system on both server and client
> - Client is virtual machine hosted on XenServer 6.1
>
> thanks for any help
>

-- 
Ing. Michal Bruncko, PhD., CCNP
IT systems and network administrator
Coupled school of business and services Ruzomberok
Slovak Republic