Linux Archive

Linux Archive (http://www.linux-archive.org/)
-   Fedora/Linux Management Tools (http://www.linux-archive.org/fedora-linux-management-tools/)
-   -   cobbler-1.0.1-2 - build problem using koan (http://www.linux-archive.org/fedora-linux-management-tools/116789-cobbler-1-0-1-2-build-problem-using-koan.html)

Tom Brown 07-01-2008 10:20 AM

cobbler-1.0.1-2 - build problem using koan
 
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.


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

Adam Rosenwald 07-01-2008 10:52 AM

cobbler-1.0.1-2 - build problem using koan
 
Tom,



Please provide the following info:


What does /tftpboot/pxelinux.cfg/xxxxxxx look like (where
xxxxxxxx corresponds to your system)?

Is xinetd (or standalone tftpd) running?

What does the host entry (corresponding to your system) in
/etc/dhcpd.conf look like?

Is dhcpd running?

Are you 100% positive that there is an ethernet link on eth0 and
not on some other NIC? (you may want to try setting ksdevice=link in
your tftp boot file)?
Do you observe dhcp-related noise on the cobbler server (tcpdump,
etc.) indicating that the provisioned system is communicating
properly?* Are there any f/w's, vlan issues (you may need a dhcp helper
address if your system is on a separate vlan than the cobbler server),
etc. that might interfere with the boot process?
Can you provide a more detailed list of what shows up on the
console during the boot process?

Regards,



*- A.



Tom Brown 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.




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="" class="moz-txt-link-freetext" href="http://cobbler.server/cblr/links/RHEL4-u5-i386">http://cobbler.server/cblr/links/RHEL4-u5-i386


# Network information


network --bootproto=static --device=eth0 --
--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









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

Tom Brown 07-01-2008 10:55 AM

cobbler-1.0.1-2 - build problem using koan
 
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.


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?



i should perhaps point out that i i have manage_dhcp=0 in the
configuration so DHCP should not come into the equation. Also i have
since removed the cobbler server hostname and replaced it with an IP
incase this made a difference, it hasnt.


Using a different tty on the install process just before it asks me
about which ethernet card to use i can see it say 'getting kickstart
file' - If i boot the client i am trying to install back into its OS and
then wget on the kickstart URL it downloads fine.


still stuck....

thanks

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

Tom Brown 07-01-2008 10:58 AM

cobbler-1.0.1-2 - build problem using koan
 
Tom,

Please provide the following info:

* What does /tftpboot/pxelinux.cfg/xxxxxxx look like (where
xxxxxxxx corresponds to your system)?
o Is xinetd (or standalone tftpd) running?
* What does the host entry (corresponding to your system) in
/etc/dhcpd.conf look like?
o Is dhcpd running?
* Are you 100% positive that there is an ethernet link on eth0 and
not on some other NIC? (you may want to try setting
ksdevice=link in your tftp boot file)?
* Do you observe dhcp-related noise on the cobbler server
(tcpdump, etc.) indicating that the provisioned system is
communicating properly? Are there any f/w's, vlan issues (you
may need a dhcp helper address if your system is on a separate
vlan than the cobbler server), etc. that might interfere with
the boot process?
* Can you provide a more detailed list of what shows up on the
console during the boot process?



thanks but i am NOT using DHCP - this is rebuilding a current OS. As the
install should happen over http is TFTP required? I imagine not


thanks

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

Tom Brown 07-01-2008 11:18 AM

cobbler-1.0.1-2 - build problem using koan
 
* What does /tftpboot/pxelinux.cfg/xxxxxxx look like (where
xxxxxxxx corresponds to your system)?
o Is xinetd (or standalone tftpd) running?
* What does the host entry (corresponding to your system) in
/etc/dhcpd.conf look like?
o Is dhcpd running?
* Are you 100% positive that there is an ethernet link on eth0 and
not on some other NIC? (you may want to try setting
ksdevice=link in your tftp boot file)?
* Do you observe dhcp-related noise on the cobbler server
(tcpdump, etc.) indicating that the provisioned system is
communicating properly? Are there any f/w's, vlan issues (you
may need a dhcp helper address if your system is on a separate
vlan than the cobbler server), etc. that might interfere with
the boot process?
* Can you provide a more detailed list of what shows up on the
console during the boot process?



in addition to not using DHCP the box that i am trying to get cobbler
running already provisions machines using kickstart over http using a
bit of a home brew system. I am trying to get rid of this system and use
cobbler like we do in other environments so from a network level there
should be no issues getting the install tree over http as it already
does that and i can get the kickstart etc over http to the client with a
wget and it looks correct so i am a little stumped.


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

Adam Rosenwald 07-01-2008 11:20 AM

cobbler-1.0.1-2 - build problem using koan
 
Tom Brown wrote:


Tom,




Please provide the following info:




*** * What does /tftpboot/pxelinux.cfg/xxxxxxx look like (where


***** xxxxxxxx corresponds to your system)?


********* o Is xinetd (or standalone tftpd) running?


*** * What does the host entry (corresponding to your system) in


***** /etc/dhcpd.conf look like?


********* o Is dhcpd running?


*** * Are you 100% positive that there is an ethernet link on eth0 and


***** not on some other NIC? (you may want to try setting


***** ksdevice=link in your tftp boot file)?


*** * Do you observe dhcp-related noise on the cobbler server


***** (tcpdump, etc.) indicating that the provisioned system is


***** communicating properly?* Are there any f/w's, vlan issues (you


***** may need a dhcp helper address if your system is on a separate


***** vlan than the cobbler server), etc. that might interfere with


***** the boot process?


*** * Can you provide a more detailed list of what shows up on the


***** console during the boot process?







thanks but i am NOT using DHCP - this is rebuilding a current OS. As
the install should happen over http is TFTP required? I imagine not



Yes.* DHCP is needed, since your system hasn't been assigned an IP
address and can only identify itself by MAC.* The network portion of
your kickstart file will ensure that a static IP will be assigned to
eth0 only AFTER the kickstart file has been downloaded.




Set 'manage_dhcp=1' in /etc/cobbler/settings (or
/var/lib/cobbler/settings if using an older version of cobbler).


In the dhcp template file (/etc/cobbler/dhcp.template) ensure
that you have configured a stanza for the subnet corresponding to that
of your provisioned system.

E.g.





...


subnet 10.x.x.x netmask 255.255.254.0 {

**** option routers********* 10.x.x.253;

**** option subnet-mask***** 255.255.254.0;

**** filename*************** "/pxelinux.0";

**** next-server************ $next_server;

}
...



Just be sure there are no 'range dynamic-bootp',
'default-lease-time', or 'max-lease-time' statements, since you are
probably concerned about dynamic IP assignments in a prod environment.



When provisioning your system with cobbler, specify both
a MAC address and an IP address, so that the host stanza in
/etc/dhcpd.conf is unique and not dependent upon dynamic options.

Give it a whirl and reply with any updates. :)



*- A.



thanks




_______________________________________________


et-mgmt-tools mailing list


et-mgmt-tools@redhat.com


https://www.redhat.com/mailman/listinfo/et-mgmt-tools









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

Tom Brown 07-01-2008 11:27 AM

cobbler-1.0.1-2 - build problem using koan
 
Yes. DHCP is needed, since your system hasn't been assigned an IP
address and can only identify itself by MAC. The network portion of
your kickstart file will ensure that a static IP will be assigned to
eth0 only AFTER the kickstart file has been downloaded.


* Set 'manage_dhcp=1' in /etc/cobbler/settings (or
/var/lib/cobbler/settings if using an older version of cobbler).
* In the dhcp template file (/etc/cobbler/dhcp.template) ensure
that you have configured a stanza for the subnet corresponding
to that of your provisioned system.
o E.g.
+ ...
+ subnet 10.x.x.x netmask 255.255.254.0 {
option routers 10.x.x.253;
option subnet-mask 255.255.254.0;
filename "/pxelinux.0";
next-server $next_server;
}
+ ...
o Just be sure there are no 'range dynamic-bootp',
'default-lease-time', or 'max-lease-time' statements,
since you are probably concerned about dynamic IP
assignments in a prod environment.
* When provisioning your system with cobbler, specify *both* a MAC
address *and* an IP address, so that the host stanza in
/etc/dhcpd.conf is unique and not dependent upon dynamic options.

Give it a whirl and reply with any updates. :)




OK thanks for the update i am a bit confused though as i thought that
using koan i could _reinstall_ a system without the need for DHCP and
PXE - The simple fact is that right now i cant use DHCP in this specific
network and so using koan to rebuild, and thats the key i think i am
rebuilding a current running OS not bare metal, to contact the cobbler
server.


Koan contacts the cobbler server and i thought, and it seems correct,
that it builds a minimal boot kernel, this boots with IP info and then
the kickstart is downloaded negating the need for DHCP. I do similar
things in another network to rebuild people's VM's running on laptops
etc that are not covered in my DHCP setup and they rebuild fine, the
only issue is that this is a new server and o cant seem to figure out
whats wrong.


i'd like to know if i've had a misconception about koan all this time ;)

thanks

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

Adam Rosenwald 07-01-2008 11:34 AM

cobbler-1.0.1-2 - build problem using koan
 
Tom Brown wrote:




* What does /tftpboot/pxelinux.cfg/xxxxxxx look like (where
xxxxxxxx corresponds to your system)?
o Is xinetd (or standalone tftpd) running?
* What does the host entry (corresponding to your system) in
/etc/dhcpd.conf look like?
o Is dhcpd running?
* Are you 100% positive that there is an ethernet link on eth0 and
not on some other NIC? (you may want to try setting
ksdevice=link in your tftp boot file)?
* Do you observe dhcp-related noise on the cobbler server
(tcpdump, etc.) indicating that the provisioned system is
communicating properly? Are there any f/w's, vlan issues (you
may need a dhcp helper address if your system is on a separate
vlan than the cobbler server), etc. that might interfere with
the boot process?
* Can you provide a more detailed list of what shows up on the
console during the boot process?



in addition to not using DHCP the box that i am trying to get cobbler
running already provisions machines using kickstart over http using a
bit of a home brew system. I am trying to get rid of this system and
use cobbler like we do in other environments so from a network level
there should be no issues getting the install tree over http as it
already does that and i can get the kickstart etc over http to the
client with a wget and it looks correct so i am a little stumped.
Please explain how your home brew system talks to booting systems. When
your provisioned systems boot, how do they communicate with the server
hosting the kickstart files?

As I understand it, at network boot time, they need to have IP
addresses, netmasks assigned to them. PXE starts by the NIC(s)
broadcasting its MAC address. Some daemon on the LAN segment (typically
dhcp) will respond to the broadcast by assigning the NIC an IP address
and subnet mask.


Unless you have an ability to assign IPs/netmasks to NICs through BIOS
(which I've never seen and which would be a pain to do for a 'lot' of
servers) or have some other mechanism (i.e. other than DHCP) which
assigns IPs/netmasks by responding to MAC broadcasts, you will have to
use DHCP somewhere during a network install.


-A.


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



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

Tom Brown 07-01-2008 11:41 AM

cobbler-1.0.1-2 - build problem using koan
 
Please explain how your home brew system talks to booting systems.
When your provisioned systems boot, how do they communicate with the
server hosting the kickstart files?
As I understand it, at network boot time, they need to have IP
addresses, netmasks assigned to them. PXE starts by the NIC(s)
broadcasting its MAC address. Some daemon on the LAN segment
(typically dhcp) will respond to the broadcast by assigning the NIC an
IP address and subnet mask.


Unless you have an ability to assign IPs/netmasks to NICs through BIOS
(which I've never seen and which would be a pain to do for a 'lot' of
servers) or have some other mechanism (i.e. other than DHCP) which
assigns IPs/netmasks by responding to MAC broadcasts, you will have to
use DHCP somewhere during a network install.




i will try and explain as best i can as i did not write the system - but
basically what i believes happens is that a minimal boot kernel boots
that is generated on the client machines before a reboot is issued.
Within this boot kernel is the network info that allows the box to have
network info before it then downloads its kickstart file etc. This is
how i thought koan worked as i can rebuild machines using a different
cobbler server and in a different network that the cobbler server knows
nothing about, i mean it knows nothing about these other networks from a
DHCP point of view.


I can of course see why my goal will not work on a bare metal system but
i thought that on a system that has a running OS koan could be used to
rebuild it to the profile as per assigned by the cobbler server. When
rebuilds occur using koan i did not think DHCP or PXE came into it.


thanks

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

Adam Rosenwald 07-01-2008 11:43 AM

cobbler-1.0.1-2 - build problem using koan
 
Tom Brown wrote:


Yes.* DHCP is needed, since your system
hasn't been assigned an IP address and can only identify itself by
MAC.* The network portion of your kickstart file will ensure that a
static IP will be assigned to eth0 only AFTER the kickstart file has
been downloaded.




*** * Set 'manage_dhcp=1' in /etc/cobbler/settings (or


***** /var/lib/cobbler/settings if using an older version of cobbler).


*** * In the dhcp template file (/etc/cobbler/dhcp.template) ensure


***** that you have configured a stanza for the subnet corresponding


***** to that of your provisioned system.


********* o E.g.


*************** + ...


*************** + subnet 10.x.x.x netmask 255.255.254.0 {


********************** option routers********* 10.x.x.253;


********************** option subnet-mask***** 255.255.254.0;


********************** filename*************** "/pxelinux.0";


********************** next-server************ $next_server;


***************** }


*************** + ...


********* o Just be sure there are no 'range dynamic-bootp',


*********** 'default-lease-time', or 'max-lease-time' statements,


*********** since you are probably concerned about dynamic IP


*********** assignments in a prod environment.


*** * When provisioning your system with cobbler, specify *both* a MAC


***** address *and* an IP address, so that the host stanza in


***** /etc/dhcpd.conf is unique and not dependent upon dynamic options.




Give it a whirl and reply with any updates. :)









OK thanks for the update i am a bit confused though as i thought that
using koan i could _reinstall_ a system without the need for DHCP and
PXE - The simple fact is that right now i cant use DHCP in this
specific network and so using koan to rebuild, and thats the key i
think i am rebuilding a current running OS not bare metal, to contact
the cobbler server.




Koan contacts the cobbler server and i thought, and it seems correct,
that it builds a minimal boot kernel, this boots with IP info and then
the kickstart is downloaded negating the need for DHCP. I do similar
things in another network to rebuild people's VM's running on laptops
etc that are not covered in my DHCP setup and they rebuild fine, the
only issue is that this is a new server and o cant seem to figure out
whats wrong.




i'd like to know if i've had a misconception about koan all this time
;)




thanks



OK.* Something is definitely missing here.* Notice how (http://www.redhat.com/magazine/024oct06/features/kickstart/)
GRUB contains options for setting the IP address, netmask, and gateway
for the system you intend to boot.* These arguments are not
set in your grub configuration.* As to why they are not, either
you didn't specify them during your cobbler system provisioning OR
there is some kind of a bug in koan's 'reprovision' logic.* Likely the
former.* Please double check that you specified



cobbler .... --ip=X --subnet=Y --gateway=Z ...



in your provision command.



-A.



_______________________________________________


et-mgmt-tools mailing list


et-mgmt-tools@redhat.com


https://www.redhat.com/mailman/listinfo/et-mgmt-tools









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


All times are GMT. The time now is 03:47 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.