No more comments?
On Tue, Mar 9, 2010 at 08:56, Jonas Bygdén <jonaslis...@gmail.com> wrote:
>
>
> On Mon, Mar 8, 2010 at 22:12, Scott Henson <shen...@redhat.com> wrote:
>
>> Excerpts from Jonas Bygdén's message of Mon Mar 08 15:59:11 -0500 2010:
>> > No, then you totally misunderstood me.
>> >
>> > I *most definitely do not* want the profile kickstart file, but I don't
>> > understand why I get that instead of the system one.
>> >
>> > With older cobbler version (don't remember right now which version was
>> in
>> > Spacewalk 0.6) I just created the systems and the kickstartfile was the
>> > default for that system. Now it seems that it's the profile one I get
>> > instead.
>> >
>> > Why? How do I get the system to kickstart using it's own file? And if
>> the
>> > default in 2.0 is changed, where's that documented? Is there at all any
>> > in-depth documentation on the cobbler architecture and how cobbler works
>> > with Spacewalk (which template is used where, how to edit templates,
>> where
>> > do I add snippets in a template etc.)?
>>
>> My confusion comes from the fact that the behavior that you expect is
>> the behavior that cobbler should be exhibiting. A few questions might
>> help to clarify things.
>>
>
> So, cobbler is supposed to give me the profile kickstart file instead of
> the system file in 2.0?
>
>
>> 1. Are you doing bare metal host provisioning or virt provisioning?
>>
>
> My tests now are with virtual hosts.
>
> 2. If you are doing virt, can you show me the koan command that you
>> are using?
>>
>
> I'm not using koan, I don't know what koan does, I've never used koan, it's
> been working fine without koan for a year - up until the upgrade to
> Spacewalk 0.8 (and hence cobbler 2.0). Do I need koan? I haven't before.
>
>
>> 3. If bare metal, are you doing PXE or koan --replace-self?
>>
>> I'd like to get a look at the cobbler system record as well. Also,
>>
>
> r...@spacewalk # cobbler system report --name=xenlinux21
> Name : xenLinux21
> Comment :
> Gateway : 192.168.33.1
> Hostname : xenLinux21.domain.net
> Image :
> Kernel Options : {}
> Kernel Options (Post Install) : {}
> Kickstart : <<inherit>>
> Kickstart Metadata : {}
> Management Classes : []
> Name Servers : []
> Name Servers Search Path : []
> Netboot Enabled : True
> Owners : ['admin']
> Power Management Address :
> Power ID :
> Power Password :
> Power Management Type : ipmitool
> Power Username :
> Profile : centos5-x86_64-xen:1:SpacewalkPublicCert
> Red Hat Management Key : 1-domain_common,<<inherit>>
> Red Hat Management Server : <<inherit>>
> Server Override : <<inherit>>
> Template Files : {}
> Virt Auto Boot : <<inherit>>
> Virt CPUs : <<inherit>>
> Virt File Size(GB) : <<inherit>>
> Virt Path : <<inherit>>
> Virt RAM (MB) : <<inherit>>
> Virt Type : <<inherit>>
> Interface ===== : eth0
> Bonding Mode :
> Bonding Master :
> Bonding Opts :
> DHCP Tag :
> DNS Name :
> IP Address : 192.168.33.100
> MAC Address : 00:16:3e:57:22:66
> Static : True
> Static Routes : []
> Subnet :
> Virt Bridge :
>
>
>
>> you can use cobbler system getks <system> to figure out what cobbler
>> thinks the kickstart should be. A look at your httpd access logs
>> should also show you what kickstart your system is going after.
>>
>
> I can provide you with anything you need from my system to help me. Can you
> be specific?
>
> I can tell you though (and Leon in the next mail) that both of these
> commands give me the exact same kickstartfile (containing the code from the
> 'post_install_network_config'-snippet).
>
> cobbler system getks --name=xenlinux21
>
> wget http://spacewalk/cblr/svc/op/ks/system/xenlinux21
>
>
> The above information would help us determine why things are getting
>> the wrong data.
>> --
>> Scott Henson
>> Red Hat CIS Operator
>> WVU Alum BSAE/BSME
>>
>
> /Jonas
>
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
