Bug 466747

Summary: On s390x, stty: standard input: Bad file descriptor
Product: Red Hat Satellite 5 Reporter: Milan Zázrivec <mzazrivec>
Component: InstallerAssignee: Milan Zázrivec <mzazrivec>
Status: CLOSED CURRENTRELEASE QA Contact: John Matthews <jmatthew>
Severity: low Docs Contact:
Priority: low    
Version: 530CC: bperkins, jmatthew, mzazrivec, psklenar
Target Milestone: ---Keywords: Regression, Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: sat530 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-10 20:29:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 456985, 462714    

Description Milan Zázrivec 2008-10-13 12:28:32 UTC
This bug reappeared in Satellite-5.3.0-RHEL5-re20080922.0
Seemingly the fix for the problem did not make it into spacewalk
and therefore Vader builds.

+++ This bug was initially created as a clone of Bug #454411 +++

Description of problem:

When running install of Satellite on s390x, I get

** Activating Satellite.
* Enabling Monitoring.
* Creating SSL certificates.
CA certificate password? stty: standard input: Bad file descriptor
stty: standard input: Bad file descriptor

Those stty messages do not seem correct, and the password is shown.

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

Satellite-5.2.0-RHEL4-re20080704.0

How reproducible:

Tried once.

Steps to Reproduce:
1. Run ./install.pl --disconnected
  
Actual results:

** Activating Satellite.
* Enabling Monitoring.
* Creating SSL certificates.
CA certificate password? stty: standard input: Bad file descriptor
stty: standard input: Bad file descriptor

and password is shown as it is typed.

Expected results:

** Activating Satellite.
* Enabling Monitoring.
* Creating SSL certificates.
CA certificate password?
Re-enter CA certificate password?

No warning and no password shown.

Additional info:

--- Additional comment from mzazrivec on 2008-07-09 10:25:15 EDT ---

Sending        install/stage2.pl
Transmitting file data .
Committed revision 174908.

--- Additional comment from mmraka on 2008-07-24 05:33:21 EDT ---

Ported to RELEASE-5.2, r175400.

--- Additional comment from bbuckingham on 2008-08-13 12:52:29 EDT ---

Mass move to ON_QA.

--- Additional comment from ssalevan on 2008-09-02 11:58:34 EDT ---

Checked against RHEL4/5 s390x 520 ISOs; error message not seen and password not echoed to terminal.  Moving to VERIFIED.

Comment 1 Milan Zázrivec 2008-10-14 12:39:27 UTC
status -> modified
spacewalk git commit: 3627e5750dd7d780bf36e1955b0704fab96c56a7

Comment 2 Milan Zázrivec 2009-01-06 09:14:00 UTC
This error still shows in Satellite-5.3.0-RHEL5-re20081223.1

Comment 4 Milan Zázrivec 2009-03-24 11:14:45 UTC
spacewalk.git master: c7d6fc215e9874b3defc6f8f83b428002b9f6e0e

Comment 5 Milan Zázrivec 2009-04-09 13:07:52 UTC
Fix present in spacewalk-setup-0.5.27-2 or Satellite-5.3.0-RHEL5-re20090403.2.

Comment 6 John Matthews 2009-06-26 21:25:08 UTC
Installed ISO Satellite-5.3.0-RHEL5-re20090625.0-s390x-embedded-oracle.iso

I entered the CA cert password, it worked as expected.

VERIFIED

Comment 8 Petr Sklenar 2009-09-02 14:08:50 UTC
I didnt see any stty error:
tried: Satellite-5.3.0-RHEL4-re20090820.1/tree-s390x/

* Creating SSL certificates.
CA certificate password? 
Re-enter CA certificate password? 
Organization? redhat

Comment 9 Brandon Perkins 2009-09-10 20:29:09 UTC
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.

http://rhn.redhat.com/errata/RHEA-2009-1434.html

Comment 10 Jan Pazdziora 2013-04-15 12:05:34 UTC
*** Bug 510754 has been marked as a duplicate of this bug. ***