Emerging Technologies Management Tools ()

problems with koan...

ok,

after has been resolved the problems with fedora core 6 in my laptop
(compaq r3000), running xen and SELinux disabled, i try to run the koan in
my laptop.

The scenario as follows:

my cobbler server is 136.145.116.114. I set up the next on it:

# cobbler distro add --name="test1" --kernel=/boot/vmlinuz-2.6.18...
--initrd=/boot/initrd-2.6.18...

# cobbler profile add --name="test1-profile" --distro="test1"
--kickstart=/root/anaconda-ks.cfg.virtual --virt-name="cobblertest"
--virt-file-size=3 --virt-ram=250

when run koan in my laptop, as follows:
# koan --virt --profile=test1-profile --server=136.145.116.114

i got the next output:

- processing profile: test1-profile
- fetching configuration for profile: test1-profile
- url=http://136.145.116.114/cobbler/profiles/test1-profile
- {'kickstart':
'http://136.145.116.114/cobbler_track/kickstarts/test1-profile/ks.cfg',
'name': 'test1-profile', 'virt_ram': 250, 'repos': '', 'kernel_options':
'lang ksdevice=eth0  text syslog=136.145.116.114:25150 devfs=nomount
ramdisk_size=16438 syslog=136.145.116.114:25150', 'virt_name':

(Continue reading)

headers

Michael DeHaan | 8 Feb 15:27

Re: problems with koan...

John.Sanabria@... wrote:
> ok,
>
> after has been resolved the problems with fedora core 6 in my laptop
> (compaq r3000), running xen and SELinux disabled, i try to run the koan in
> my laptop.
>
> The scenario as follows:
>
> my cobbler server is 136.145.116.114. I set up the next on it:
>
> # cobbler distro add --name="test1" --kernel=/boot/vmlinuz-2.6.18...
> --initrd=/boot/initrd-2.6.18...
>
> # cobbler profile add --name="test1-profile" --distro="test1"
> --kickstart=/root/anaconda-ks.cfg.virtual --virt-name="cobblertest"
> --virt-file-size=3 --virt-ram=250
>
> when run koan in my laptop, as follows:
> # koan --virt --profile=test1-profile --server=136.145.116.114
>
> i got the next output:
>
> - processing profile: test1-profile
> - fetching configuration for profile: test1-profile
> - url=http://136.145.116.114/cobbler/profiles/test1-profile
> - {'kickstart':
> 'http://136.145.116.114/cobbler_track/kickstarts/test1-profile/ks.cfg',
> 'name': 'test1-profile', 'virt_ram': 250, 'repos': '', 'kernel_options':
> 'lang ksdevice=eth0  text syslog=136.145.116.114:25150 devfs=nomount

(Continue reading)

headers

John.Sanabria | 8 Feb 16:21

Re: Re: problems with koan...


>
> There was a bug based on koan ignoring the RAM setting from cobbler,
> though that was fixed a few releases ago.
> Can you give me the output of "cobbler profile report" as well as "rpm
> -q cobbler" and "rpm -q koan" ?
>

At 136.145.116.114 and remote site the output is:

[root <at> dhcp-crl-116-78 ~]# rpm -q cobbler
cobbler-0.3.9-1.fc6
[root <at> dhcp-crl-116-78 ~]# rpm -q koan
koan-0.2.5-1.fc6

> Thanks,
>

you're welcome

                    (`'`'`'`'`)
                     |       |
                     |       |
                     |       |
    -----..        (()----   |
   |        ||     (_        |
   |        ||       |       |
   |        ||       |       |
   |        ||       /\   ..--
   '--------''   /\  ||-''    \

(Continue reading)

headers

Michael DeHaan | 8 Feb 16:35

Re: Re: problems with koan...

John.Sanabria@... wrote:
>> There was a bug based on koan ignoring the RAM setting from cobbler,
>> though that was fixed a few releases ago.
>> Can you give me the output of "cobbler profile report" as well as "rpm
>> -q cobbler" and "rpm -q koan" ?
>>
>>     
>
> At 136.145.116.114 and remote site the output is:
>
> [root <at> dhcp-crl-116-78 ~]# rpm -q cobbler
> cobbler-0.3.9-1.fc6
> [root <at> dhcp-crl-116-78 ~]# rpm -q koan
> koan-0.2.5-1.fc6

John,

Those are up to date, which is good.

What may have happened, and this is very likely, is that you did not run 
"cobbler sync" after making the profile change on the boot server, so 
koan is requesting the old configuration still.   I would bet that if 
you run "cobbler sync" on the server and then run koan again on the 
remote it should work fine.

(Note that the new version of cobbler - 0.4.0, not yet released, will 
not require running sync after these operations).

--Michael

(Continue reading)