Bug 1331416

Summary: preupg prints error messages when stdin is redirected from pipe
Product: Red Hat Enterprise Linux 6 Reporter: Tereza Cerna <tcerna>
Component: preupgrade-assistantAssignee: Michal Bocek <mbocek>
Status: CLOSED CURRENTRELEASE QA Contact: Tereza Cerna <tcerna>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.8CC: amahdal, phracek, pstodulk, ttomecek
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: preupgrade-assistant-2.6.1-1.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-01 15:35:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Tereza Cerna 2016-04-28 13:23:10 UTC 
Preupgrade print message "Inappropriate ioctl for device" to stderr when output is redirect to file.

# preupg <<<y >preupg.out 2>preupg.err

# tail preupg.err
stty: standard input: Inappropriate ioctl for device
stty: standard input: Inappropriate ioctl for device
stty: standard input: Inappropriate ioctl for device
stty: standard input: Inappropriate ioctl for device
stty: standard input: Inappropriate ioctl for device
stty: standard input: Inappropriate ioctl for device
stty: standard input: Inappropriate ioctl for device
stty: standard input: Inappropriate ioctl for device
stty: standard input: Inappropriate ioctl for device
stty: standard input: Inappropriate ioctl for device

# rpm -q preupgrade-assistant
preupgrade-assistant-2.1.6-3.el6.noarch
Comment 2 Alois Mahdal 2016-08-03 22:46:32 UTC 
*** Bug 1363911 has been marked as a duplicate of this bug. ***
Comment 3 Alois Mahdal 2016-08-04 00:12:53 UTC 
Turns out this is caused by the STDIN redirection, not the STDOUT; i.e.

    preupg --force >out 2>err

works fine, but

    preupg <<<y

suffers from this.
Comment 5 Michal Bocek 2019-07-01 15:35:04 UTC 
Closing this bugzilla as the component is under a maintenance mode in which the maintainers are going to fix only critical bugs. If you consider the bugzilla critical, feel free to reopen the bug with an explanation.
Comment 6 Petr Stodulka 2019-07-01 15:45:40 UTC 
This is already fixed in latest build.