FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora/Linux Management Tools

 
 
LinkBack Thread Tools
 
Old 07-01-2008, 02:05 PM
"Stephen John Smoogen"
 
Default cobbler-1.0.1-2 - build problem using koan

On Tue, Jul 1, 2008 at 4:20 AM, Tom Brown <tom@ng23.net> wrote:
> Hi
>
> I cant use DHCP yet in my prd environment but i can use koan so i can have
> cobbler rebuild existing hosts.
>
> I have setup a cobbler server and added a test system to that but i
> encounter an issue when i try and build using koan in that after the client
> reboots and boots the 'kick' kernel it seems unable to get the kickstart as
> it starts to ask me which ethernet card to use and also then tries to do a
> DHCP request.
>

Which OS are you trying to replace it with? There are a couple of
possible items:

1) The ethernet card is not detected easily.. or you have multiple
cards and it could not contact the cobbler server so it tried to probe
for other ethernet systems. Our Dell 2950's have this problem.. on
installation eth0 is eth1 and vice versa.

> If i hit the URL that generates the kickstart it seems fine and the network
> part looks like this apart from the xxxxxx and the 'cobbler.server' hostname
>
> # Use network installation
> url --url=http://cobbler.server/cblr/links/RHEL4-u5-i386
> # Network information
> network --bootproto=static --device=eth0 --onboot=on --ip=10.xxx.xxx.19
> --netmask=255.255.254.0 --gateway=10.xxx.xxx.253
> --nameserver=10.xxx.xxx.117 --hostname=xxxxxxxx
>
> In the grub config on the client before i reboot i see this
>
> title kick1214906905
> root (hd0,0)
> kernel /vmlinuz ro root=LABEL=/
> ks=http://cobbler.server/cblr/svc/op/ks/system/xxxxxxxx
> initrd /initrd.img
>
> and the 'cobbler.server' can be resolved from the client using the correct
> nameserver -
>
> Does anyone have any ideas whats going on as i am stuck?
>
> thanks
>
>
> _______________________________________________
> et-mgmt-tools mailing list
> et-mgmt-tools@redhat.com
> https://www.redhat.com/mailman/listinfo/et-mgmt-tools
>



--
Stephen J Smoogen. -- BSD/GNU/Linux
How far that little candle throws his beams! So shines a good deed
in a naughty world. = Shakespeare. "The Merchant of Venice"

_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 07-01-2008, 02:23 PM
Tom Brown
 
Default cobbler-1.0.1-2 - build problem using koan

Which OS are you trying to replace it with? There are a couple of
possible items:

1) The ethernet card is not detected easily.. or you have multiple
cards and it could not contact the cobbler server so it tried to probe
for other ethernet systems. Our Dell 2950's have this problem.. on
installation eth0 is eth1 and vice versa.




thanks - i have resolved this by using a non broken version of koan and
adding ksopts to the cobbler creation line


thanks

_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 07-01-2008, 02:44 PM
Michael DeHaan
 
Default cobbler-1.0.1-2 - build problem using koan

In the grub config on the client before i reboot i see this

title kick1214906905
root (hd0,0)
kernel /vmlinuz ro root=LABEL=/
ks=http://cobbler.server/cblr/svc/op/ks/system/xxxxxxxx

initrd /initrd.img



Hi Tom,

The latest stable version of koan is 1.0.1, cobbler is 1.0.2. You
should upgrade as this includes the fix for the above problem with the
missing kernel options.


You should be pulling from EPEL testing or the Fedora repos, if you have
access to neither, see http://cobbler.et.redhat.com/download.


--Michael

_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 07-01-2008, 02:54 PM
Michael DeHaan
 
Default cobbler-1.0.1-2 - build problem using koan

Michael DeHaan wrote:





In the grub config on the client before i reboot i see this

title kick1214906905
root (hd0,0)
kernel /vmlinuz ro root=LABEL=/
ks=http://cobbler.server/cblr/svc/op/ks/system/xxxxxxxx

initrd /initrd.img



Hi Tom,

The latest stable version of koan is 1.0.1, cobbler is 1.0.2. You
should upgrade as this includes the fix for the above problem with the
missing kernel options.


You should be pulling from EPEL testing or the Fedora repos, if you
have access to neither, see http://cobbler.et.redhat.com/download.


--Michael

_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools


I don't know how to expand threads, apparently

Glad this is already resolved.


_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 07-01-2008, 02:59 PM
Tom Brown
 
Default cobbler-1.0.1-2 - build problem using koan

I don't know how to expand threads, apparently

Glad this is already resolved.





it is yes thanks - although any opinion in inheriting those values from
cobbler into koan?



_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 07-01-2008, 03:10 PM
Michael DeHaan
 
Default cobbler-1.0.1-2 - build problem using koan

Tom Brown wrote:




I don't know how to expand threads, apparently

Glad this is already resolved.





it is yes thanks - although any opinion in inheriting those values
from cobbler into koan?



_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools


Hmm, I'm not sure I understand the question. All kernel options given
to cobbler settings, distros, profiles, and systems end up used by koan.


Can you elaborate?

--Michael


_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 07-01-2008, 03:13 PM
Tom Brown
 
Default cobbler-1.0.1-2 - build problem using koan

Hmm, I'm not sure I understand the question. All kernel options
given to cobbler settings, distros, profiles, and systems end up used
by koan.


Can you elaborate?




on a rebuild IP, mask and gateway info thats in cobbler does not get
pulled by koan and inserted onto the grub command line unless you
specify the --kopts when you provision a system or hand it to koan at
the rebuild time.


Rather than having to add --kopts to cobbler during provision cant the
values already given be used?


thanks


_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 07-01-2008, 03:29 PM
Michael DeHaan
 
Default cobbler-1.0.1-2 - build problem using koan

Tom Brown wrote:




Hmm, I'm not sure I understand the question. All kernel options
given to cobbler settings, distros, profiles, and systems end up used
by koan.


Can you elaborate?




on a rebuild IP, mask and gateway info thats in cobbler does not get
pulled by koan and inserted onto the grub command line unless you
specify the --kopts when you provision a system or hand it to koan at
the rebuild time.


If you have those variables stored on the system object's --kopts, you
just invoke koan as:


koan --server=cobbler.example.org --replace-self --system=this_system_name

If the mac address is in Cobbler, it's smart enough to auto-find the
system, so you can just do:


koan --server=cobbler.example.org --replace-self

I think what you're saying is if the network parameters are not in
--kopts, but are stored on the interface, they don't show up in --kopts.

This is true.

Before we used to have a parameter to auto-discover the network details
from the local system and append them to the kernel options line to
eliminate DHCP, however due to some python version incompatibilies we
had to remove that feature. If that is interesting, this is something
that we could work on cleaning up and adding back.


Another option would be to add in support for just using the IP info in
cobbler and adding /that/ to --kopts implicitly.


Perhaps this would look like:

koan --server=cobbler.example.org --replace-self --use-static-interface=0

All of these problems of course go away when you have DHCP

--Michael

_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 07-01-2008, 03:34 PM
Tom Brown
 
Default cobbler-1.0.1-2 - build problem using koan

If you have those variables stored on the system object's --kopts, you
just invoke koan as:


koan --server=cobbler.example.org --replace-self
--system=this_system_name


If the mac address is in Cobbler, it's smart enough to auto-find the
system, so you can just do:


koan --server=cobbler.example.org --replace-self

I think what you're saying is if the network parameters are not in
--kopts, but are stored on the interface, they don't show up in --kopts.

This is true.

Before we used to have a parameter to auto-discover the network
details from the local system and append them to the kernel options
line to eliminate DHCP, however due to some python version
incompatibilies we had to remove that feature. If that is
interesting, this is something that we could work on cleaning up and
adding back.


Another option would be to add in support for just using the IP info
in cobbler and adding /that/ to --kopts implicitly.


Perhaps this would look like:

koan --server=cobbler.example.org --replace-self --use-static-interface=0

All of these problems of course go away when you have DHCP



you have hit the nail on the head and also why this used to 'work' but
seemed to stop working for me when i installed another cobbler server in
a network where DHCP is a big no-no (but thats another thing i'm working
an angle on )


the feature of auto-appending the network details was nice to have but
personally using the IP info available to cobbler and just adding that
implicitly to -kopts would be the way to go, thats how i have solved
this issue for me by adding a bit to a script but it would be nice if it
did this by default.


IMHO

_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 
Old 07-01-2008, 03:47 PM
Adam Rosenwald
 
Default cobbler-1.0.1-2 - build problem using koan

Michael DeHaan wrote:

Tom Brown wrote:




Hmm, I'm not sure I understand the question. All kernel options
given to cobbler settings, distros, profiles, and systems end up
used by koan.


Can you elaborate?




on a rebuild IP, mask and gateway info thats in cobbler does not get
pulled by koan and inserted onto the grub command line unless you
specify the --kopts when you provision a system or hand it to koan at
the rebuild time.


If you have those variables stored on the system object's --kopts, you
just invoke koan as:


koan --server=cobbler.example.org --replace-self
--system=this_system_name


If the mac address is in Cobbler, it's smart enough to auto-find the
system, so you can just do:


koan --server=cobbler.example.org --replace-self

I think what you're saying is if the network parameters are not in
--kopts, but are stored on the interface, they don't show up in --kopts.

This is true.

Before we used to have a parameter to auto-discover the network
details from the local system and append them to the kernel options
line to eliminate DHCP, however due to some python version
incompatibilies we had to remove that feature. If that is
interesting, this is something that we could work on cleaning up and
adding back.


Another option would be to add in support for just using the IP info
in cobbler and adding /that/ to --kopts implicitly.


Perhaps this would look like:

koan --server=cobbler.example.org --replace-self --use-static-interface=0

All of these problems of course go away when you have DHCP

--Michael

_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools



What about auto-discovery of IP, netmask, gateway when explicitly
performing a koan --replace-self operation? The discovered values can
then be appended to and/or override the koan kopts string. This seems
like the most logical approach, given that this is needed only when not
using dhcp.


-A.

_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
 

Thread Tools




All times are GMT. The time now is 10:01 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org