Bug 454411 - On s390x, stty: standard input: Bad file descriptor
On s390x, stty: standard input: Bad file descriptor
Status: CLOSED CURRENTRELEASE
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Installer (Show other bugs)
520
All Linux
low Severity low
: ---
: ---
Assigned To: Jan Pazdziora
Steve Salevan
:
Depends On:
Blocks: 446866
  Show dependency treegraph
 
Reported: 2008-07-08 07:38 EDT by Jan Pazdziora
Modified: 2008-11-05 13:41 EST (History)
2 users (show)

See Also:
Fixed In Version: sat520
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-11-05 13:41:05 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan Pazdziora 2008-07-08 07:38:02 EDT
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:
Comment 1 Milan Zázrivec 2008-07-09 10:25:15 EDT
Sending        install/stage2.pl
Transmitting file data .
Committed revision 174908.
Comment 2 Michael Mráka 2008-07-24 05:33:21 EDT
Ported to RELEASE-5.2, r175400.
Comment 3 Brad Buckingham 2008-08-13 12:52:29 EDT
Mass move to ON_QA.
Comment 4 Steve Salevan 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 5 wes hayutin 2008-10-23 15:45:35 EDT
release pendin
* Activating Satellite.
Where is your satellite certificate file? /root/cert.cert
** Loading Satellite Certificate.
** Verifying certificate locally.
** Activating Satellite.
* Enabling Monitoring.
* Creating SSL certificates.
CA certificate password? 
Re-enter CA certificate password? 
Organization? Red Hat
Organization Unit [rhndev4.z900.redhat.com]? RHEN
Email Address [whayutin@redhat.com]? 
City? Raleigh
State? NC
Country code (Examples: "US", "JP", "IN", or type "?" to see a list)? US
** SSL: Generating CA certificate.
** SSL: Deploying CA certificate.
** SSL: Generating server certificate.
** SSL: Storing SSL certificates.
* Deploying configuration files.
* Update configuration in database.
* Restarting services.
Installation complete.
Visit https://rhndev4.z900.redhat.com to create the satellite administrator account.
[root@rhndev4 iso]#
Comment 6 Brandon Perkins 2008-11-05 13:41:05 EST
5.2.0 Satellite is now GA, bugs Closed for Current Release.

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