Bug 484673 - unable to install without TTY
unable to install without TTY
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Installer (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jan Pazdziora
Jan Hutař
Depends On:
Blocks: 456985
  Show dependency treegraph
Reported: 2009-02-09 09:04 EST by Jan Hutař
Modified: 2009-09-10 16:32 EDT (History)
1 user (show)

See Also:
Fixed In Version: sat530
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-09-10 16:32:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jan Hutař 2009-02-09 09:04:19 EST
Description of problem:
I'm unable to install 20090206.1 RHEL-5 Satellite using RHTS script (I was able to install 5.2.0 Satellite) - installer wants TTY. I can fix the test to provide it, but automated installation (with answers file) should not enforce it.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. /mnt/redhat/devel/candidate-trees/Satellite-5.3.0-RHEL5-re20090206.1/i386/i386//install.pl --answer-file=/mnt/tests/CoreOS/RHN-Satellite/Inter-Satellite-Sync/Sanity/general/answers.txt --non-interactive --disconnected --run-updater

Actual results:
* Enabling Monitoring.
sudo: sorry, you must have a tty to run sudo
RHN::Exception: There was a problem updating your configuration.  See the webserver error log for details.
  RHN::SatInstall /usr/lib/perl5/vendor_perl/5.8.8/RHN/SatInstall.pm 117 RHN::Exception::throw
  main /usr/bin/spacewalk-setup 1194 RHN::SatInstall::write_config
  main /usr/bin/spacewalk-setup 132 main::setup_monitoring

Expected results:
Installation works

Additional info:
RHTS test in question:
Logs for i386 system:
Comment 1 Brandon Perkins 2009-02-10 12:28:27 EST
Approved.  It appears the problem is with:

  RHN::SatInstall->write_config({ monitoringDOTscout_shared_key => $scout_shared

being used instead of standard write_config used elsewhere in /usr/bin/spacewalk-setup.  *Theoretically* just changing the 'RHN::SatInstall->write_config' to 'write_config' may solve the problem.  But then we have the next question, of why do we have a local write_config and another write_config function in RHN/SatInstall.pm.

Regardless, Cliff and I both think it should be fixed as we don't want to have QA doing workarounds in the installation automation efforts.
Comment 2 Jan Pazdziora 2009-02-10 13:00:45 EST
In fact, I changed that write_config invocation today in Spacewalk, independently from this bugzilla. So this problem should not appear anymore because that sudo will not be run.

However: we should really make sure that the sudoers is sane upon installation. So: why didn't sudo work in this situation? Was it the first time non-tty installation was tried?
Comment 3 Clifford Perry 2009-02-10 15:32:18 EST
Assume the fairly new RHTS automated installer path high lighted this issue. 


Care to move to modified Jan? :)
Comment 4 Jan Pazdziora 2009-02-11 02:41:06 EST
Modified in Spacewalk, commit fac483b1bb84aaa57bb15227418293f7da74da71.
Comment 6 Jan Hutař 2009-03-30 09:35:59 EDT
VERIFIED with Satellite-5.3.0-RHEL5-re20090327.0-x86_64

* Enabling Monitoring.
* Configuring apache SSL virtual host.
Comment 7 Jan Hutař 2009-08-17 02:51:46 EDT
Installed Satellite multiple times without this issue.
Comment 8 Brandon Perkins 2009-09-10 16:32:46 EDT
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.


Note You need to log in before you can comment on or make changes to this bug.