Mike,
You ever just have one of those days? LOL, some of the easiest problems to solve are
right under your nose sometimes. Since I am doing --nobase install (super super thin
install for our computer low latency nodes) my install was missing wget!
We should maybe stick some logic in there where it tries a few different tools instead of
just wget, just a thought. (I know it sounds bizzare but our systems dont have any wget
or curl on them)
Thx,
Chris
________________________________________
From: cobbler-bounces(a)lists.fedorahosted.org [cobbler-bounces(a)lists.fedorahosted.org] On
Behalf Of Michael DeHaan [mdehaan(a)redhat.com]
Sent: Friday, October 31, 2008 9:19 AM
To: cobbler mailing list
Subject: Re: pxe_just_once not working
Christopher Johnston wrote:
a) $kickstart_done is there
root@xenguest01:/etc/cobbler# cobbler profile report --name=Fedora-9-x86_64 | grep
kickstart
kickstart : /etc/cobbler/f9_template.ks
root@xenguest01:/etc/cobbler# tail -5 /etc/cobbler/f9_template.ks
%post
$yum_config_stanza
SNIPPET::post_install_kernel_options
$kickstart_done
%end
b) macs and IPs are there
root@xenguest01:/etc/cobbler# cobbler system report --name=core001.lax02.mtt | egrep
'profile|mac|address|hostname|gateway|subnet'
profile : Fedora-9-x86_64
mac address : xx:xx:xx:xx:xx
ip address : x.x.x.x
hostname : core001
gateway : x.x.x.x
subnet : 255.255.255.0
c) yea noticed this, it will just tell the host during its PXE to boot off the local
disk.
________________________________________
From: cobbler-bounces(a)lists.fedorahosted.org [cobbler-bounces(a)lists.fedorahosted.org] On
Behalf Of Michael DeHaan [mdehaan(a)redhat.com]
Sent: Friday, October 31, 2008 8:11 AM
To: cobbler mailing list
Subject: Re: pxe_just_once not working
Christopher Johnston wrote:
> All,
>
> I am running cobbler-1.2.8-1 and I am having some issues getting the pxe_just_once
feature working. We have a scenario where the kickstart completes and the build process
continues to go through a loop. This is mostly because we keep PXE enabled as a default on
a large portion of our systems, but I thought the pxe_just_once flag will allow cobbler to
disable the the system by removing the pxe links in /tftpboot when the system makes a
final call out to cobbler to tell it has completed?
>
> See below..
>
> Its enabled and cobblerd is restarted/running:
> root@xenguest01:/# grep pxe_just_once /etc/cobbler/settings
> pxe_just_once: 1
> root@xenguest01:/#
>
> Host is set to netboot itself on next boot:
> root@xenguest01:/# cobbler system report --name=client | grep netboot
> netboot enabled? : True
> root@xenguest01:/#
>
> .
> .
> .
> Kickstart completes
> .
> .
> .
>
> Host remains with the netboot flag still enabled, shouldnt this have disabled
itself?
> root@xenguest01:/# cobbler system report --name=core001.lax02.mtt | grep netboot
> netboot enabled? : True
> root@xenguest01:/#
>
> $kickstart_done is specified in the %post section of the kickstart template:
> root@xenguest01:/etc/cobbler# grep done fedora9_template.ks
> $kickstart_done
> root@xenguest01:/etc/cobbler#
>
> Thanks,
>
> - Chris
>
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
>
https://fedorahosted.org/mailman/listinfo/cobbler
>
>
A couple of thoughts:
(A)
You're probably just missing the $kickstart_done template line in the
%post of your kickstart file.
(B)
The PXE boot loop prevention requires that the MAC (or IP) address of
the system be stored in Cobbler, so if you are PXE'ing from the default
profile or the PXE menu, it will not be available. If you do a full
"cobbler system report --name=core001.lax02.mtt", what do you see?
(C)
FYI -- Starting in 1.2.0, the code in question does not remove the
per-system config file in /tftpboot/pxelinux.cfg but instead replaces it
with a configuration file that says "boot the local disk". So if you're
expecting to see that file removed, it should not be, but the contents
of what is written to /tftpboot/pxelinux.cfg/{encoded-mac-address}
should change when you toggle the netboot flag (or cobbler toggles it
automatically).
--Michael
Ok thanks ... please check the following:
(0)
"cobbler check" is clean and cobblerd is running.
(1)
Run "cobbler system getks --name=core001.lax02.mtt"
Let's see the "%post" section to make sure the URLs look correct. Verify
the URLs are reachable from the installed machine's network.
(2)
If you visit the URLs mentioned in post, what do you see?
(3)
Anything in /var/log/cobbler/cobbler.log or /var/log/httpd/error.log
that looks like a Cobbler error/traceback?
--Michael
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler