This is an FYI post for anyone else who might have run into this issue.
After upgrading to v1.4.x all servers that I provisioned still reported in
build mode. I could not cancel the build, nor could I update the build as
being complete by running the "wget -q -O /dev/null --no=check-certificate
http://<foreman_url>" command. After much trolling the internet and
looking for bug reports, I came across the following posts:
http://projects.theforeman.org/issues/2792
http://projects.theforeman.org/issues/4008
These posts report the exact symptom I was seeing, when the default
PXELinux template is renamed or deleted, build status updates fail within
foreman. The posts provide the fix, but when I attempted to implement the
suggested fix of implementing the required template called "PXELinux
Localboot Default" it still did not work… after many frustrations I built
a temporary system and installed foreman to see that I actually needed to
name the template "PXELinux default local boot" in order to get everything
to work. The content of the template is as suggested:
DEFAULT menu
PROMPT 0
MENU TITLE PXE Menu
TIMEOUT 200
TOTALTIMEOUT 6000
ONTIMEOUT local
LABEL local
MENU LABEL (local)
MENU DEFAULT
LOCALBOOT 0
Anyway, hopefully this will some folks headaches if you encounter this
error. Long term, hopefully this bug will be fixed soon enough and this
post will be rendered moot.
Adam
Also, you should add this note at the top of the template to at least,
forewarn that its a special template:
<%#
king: PXELinux
name: Community PXE Localboot
%>
<%# This template has special name (do not change it) and it is used for
booting already provisioned hosts. %>
···
On Tuesday, March 11, 2014 10:42:15 AM UTC-4, Adam Carlson wrote:
This is an FYI post for anyone else who might have run into this issue.
After upgrading to v1.4.x all servers that I provisioned still reported in
build mode. I could not cancel the build, nor could I update the build as
being complete by running the “wget -q -O /dev/null --no=check-certificate
http://<foreman_url>” command. After much trolling the internet and
looking for bug reports, I came across the following posts:
Bug #2792: If you delete "PXE Localboot Default" cancel build fails - Foreman
Bug #4008: Disable 'build mode' unsuccessful - Foreman
These posts report the exact symptom I was seeing, when the default
PXELinux template is renamed or deleted, build status updates fail within
foreman. The posts provide the fix, but when I attempted to implement the
suggested fix of implementing the required template called “PXELinux
Localboot Default” it still did not work… after many frustrations I built
a temporary system and installed foreman to see that I actually needed to
name the template “PXELinux default local boot” in order to get everything
to work. The content of the template is as suggested:
DEFAULT menu
PROMPT 0
MENU TITLE PXE Menu
TIMEOUT 200
TOTALTIMEOUT 6000
ONTIMEOUT local
LABEL local
MENU LABEL (local)
MENU DEFAULT
LOCALBOOT 0
Anyway, hopefully this will some folks headaches if you encounter this
error. Long term, hopefully this bug will be fixed soon enough and this
post will be rendered moot.
Adam
These comments should be present in new Foreman 1.4 installations, but
probably not if you've upgraded (since we won't overwrite templates).
···
--
Dominic Cleal
Red Hat Engineering
On 11/03/14 14:55, Adam Carlson wrote:
Also, you should add this note at the top of the template to at least,
forewarn that its a special template:
<%#
king: PXELinux
name: Community PXE Localboot
%>
<%# This template has special name (do not change it) and it is used for
booting already provisioned hosts. %>
On Tuesday, March 11, 2014 10:42:15 AM UTC-4, Adam Carlson wrote:
This is an FYI post for anyone else who might have run into this issue.
After upgrading to v1.4.x all servers that I provisioned still
reported in build mode. I could not cancel the build, nor could I
update the build as being complete by running the "wget -q -O
/dev/null --no=check-certificate http://<foreman_url>" command.
After much trolling the internet and looking for bug reports, I came
across the following posts:
http://projects.theforeman.org/issues/2792
<http://projects.theforeman.org/issues/2792>
http://projects.theforeman.org/issues/4008
<http://projects.theforeman.org/issues/4008>
These posts report the exact symptom I was seeing, when the default
PXELinux template is renamed or deleted, build status updates fail
within foreman. The posts provide the fix, but when I attempted to
implement the suggested fix of implementing the required template
called "PXELinux Localboot Default" it still did not work... after
many frustrations I built a temporary system and installed foreman
to see that I actually needed to name the template "PXELinux default
local boot" in order to get everything to work. The content of the
template is as suggested:
DEFAULT menu
PROMPT 0
MENU TITLE PXE Menu
TIMEOUT 200
TOTALTIMEOUT 6000
ONTIMEOUT local
LABEL local
MENU LABEL (local)
MENU DEFAULT
LOCALBOOT 0
Anyway, hopefully this will some folks headaches if you encounter
this error. Long term, hopefully this bug will be fixed soon enough
and this post will be rendered moot.
Adam
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com
mailto:foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
mailto:foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
