On Mon, Mar 22, 2010 at 7:29 PM, Jonas Bygdén <[email protected]> wrote:
> On 2010-03-22 14:45, Tom Brown wrote:
>
> Exactly! So, why doesn't it use that when kickstarting? Where's the
> determination made? It can't be the 'Kickstart'-variable, since all my
> systems have the value '<<inherit>>' here, and only some of the systems have
> the problem of getting the profile-ks instead of the system-ks.
>
>
> then what is 'different' about those systems?
>
> They use a different profile (for xen, since they are virtual), that much
> I've figured out. This is the output of 'cobbler profile report' on two
> profiles, the first one causes the system to be installed with the
> profile-ks, and the second one causes the system to be installed with it's
> own system-ks:
>
> r...@spacewalk # cobbler profile report
> --name=centos5-x86_64-xen:1:SpacewalkPublicCert
> Name : centos5-x86_64-xen:1:SpacewalkPublicCert
> Comment :
> DHCP Tag : default
> Distribution :
> CentOs-5.3-x86_64-xen:xen:1:Spacewalk-Public-Cert
> Enable PXE Menu? : 1
> Kernel Options : {}
> Kernel Options (Post Install) : {}
> Kickstart :
> /var/lib/rhn/kickstarts/wizard/centos53-x86_64-xen--1.cfg
> Kickstart Metadata : {'org': 1}
> Management Classes : []
> Name Servers : []
> Name Servers Search Path : []
> Owners : ['admin']
> Parent Profile :
> Red Hat Management Key :
> 1-e864f76fe07e3fef07dbf9457fb6bdf2,1-company_common
> Red Hat Management Server : <<inherit>>
> Repos : []
> Server Override : <<inherit>>
> Template Files : {}
> Virt Auto Boot : 1
> Virt Bridge : xenbr0
> Virt CPUs : 1
> Virt File Size(GB) : 3
> Virt Path :
> Virt RAM (MB) : 512
> Virt Type : xenpv
>
> r...@spacewalk # cobbler profile report
> --name=centos5-x86_64:1:SpacewalkPublicCert
> Name : centos5-x86_64:1:SpacewalkPublicCert
> Comment :
> DHCP Tag : default
> Distribution : CentOs-5.3-x86_64:1:Spacewalk-Public-Cert
> Enable PXE Menu? : 1
> Kernel Options : {}
> Kernel Options (Post Install) : {}
> Kickstart :
> /var/lib/rhn/kickstarts/wizard/centos5-x86_64--1.cfg
> Kickstart Metadata : {'org': 1}
> Management Classes : []
> Name Servers : []
> Name Servers Search Path : []
> Owners : ['admin']
> Parent Profile :
> Red Hat Management Key :
> 1-f7ec311e3f8aba149a205c9f7e58f2b9,1-company_common
> Red Hat Management Server : <<inherit>>
> Repos : []
> Server Override : <<inherit>>
> Template Files : {}
> Virt Auto Boot : 1
> Virt Bridge : xenbr0
> Virt CPUs : 1
> Virt File Size(GB) : 3
> Virt Path :
> Virt RAM (MB) : 512
> Virt Type : qemu
>
> Both of these profile-ks contains the 'post_install_network_config'-snippet,
> but for some reason I get the profile-ks for the systems using the first
> profile and the system-ks for the systems using the second one.
>
> /Jonas
>
Sorry looks like I really missed something. The logic for
inclusion/exclusion of the post_install_network_config is part of the
post_install_network_config snippet itself.
The first line in the post_install_network_config snippet tries to
determine if the kickstart is generated for a profile or a system.
#if $getVar("system_name","") != "" (see
http://git.fedoraproject.org/git/cobbler/?p=cobbler;a=blob;f=snippets/post_install_network_config;h=83640122bdab9e6158ff5cf1aaf0e3dcf2a3dc88;hb=HEAD)
In case it is a system the network configuration snippet is included
and not for profile.
So your kickstart setting "<<inherit>>" is correct.
Based on the info you provided it looks like the above mentioned "if
condition" is failing for you for system which are not getting the
snippet. Just a pointer for you to debug,
How this is related to spacewalk i am not sure as i have no experience
of spacewalk or xen with cobbler.
This is all i can guess at the moment
- Chandan
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
