Red Hat Bugzilla – Bug 506405
automated installation - cobbler is asking about services
Last modified: 2009-09-10 14:16:18 EDT
Description of problem:
There should be way how to automate tftp/xinetd enablement. While running unatended Satellite install, Cobbler is asking me and I do not know a way how to automate the answer (well, I could do `echo "y" | ./install.pl ...`, but that did not seem to be a good way how to do it).
q = "Cobbler requires tftp and xinetd services be turned on for PXE provisioning functionality. Enable these services"
if ask_yes_no(q, 'y'):
system("chkconfig tftp on")
system('chkconfig xinetd on')
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. # ./install.pl
* Setting up Cobbler..
Cobbler requires tftp and xinetd services be turned on for PXE provisioning functionality. Enable these services [y/n]:
* Setting up Cobbler..
** Enabling tftp and xinetd services as per answers.txt config option xyz.
This is currently a blocker for a Satellite RHTS automation.
Should be resolved in the next push. http://git.fedorahosted.org/git/?p=spacewalk.git;a=commit;h=f2dfc55fb40254c6bffbccac796b4ceb08dd2abc
you can now add a "enable-tftp=y" or "enable-tftp=n" flag in your answers file to fix this.. On the other hand if you specify the --non-interactive install and do not specify a value for enable-tftp it will assume the user wants the service enabled and not prompt.
- enable-tftp=y in answers file does enable tftp on install
- enable-tftp=n in answers file does not enable tftp on install
- no enable-tftp in answers file and --non-interactive does enable tftp on install
When using --enable-tftp option for the install.pl script, Cobbler doesn't stop the installation with a question whether to enable tftp and xinetd.
--enable-tftp=yes (tftp will be correctly enabled via xinetd)
--enable-tftp=no (tftp wont' be enabled via via xinetd)
When not using --enable-tftp option with an answer file, Cobbler doesn't stop the installation and services are correctly enabled.
Stage validated -> RELEASE_PENDING.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.