Bug 965923

Summary: All rhc commands are failed on windows with "unsupported signal SIGPIPE (ArgumentError)"
Product: OpenShift Online Reporter: joycezhang <jinzhang>
Component: ocAssignee: Jordan Liggitt <jliggitt>
Status: CLOSED CURRENTRELEASE QA Contact: libra bugs <libra-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 2.xCC: jliggitt, xtian
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-11 04:07:57 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:
Embargoed:

Description joycezhang 2013-05-22 04:08:40 UTC
Description of problem:
If trying to use rhc commands on win7/win8, it would be failed as below:


C:\Users\openshift>rhc
C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/rhc-1.9.3/bin/rhc:15:in `trap': unsuppor
ted signal SIGPIPE (ArgumentError)
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/rhc-1.9.3/bin/rhc:15:in `<t
op (required)>'
        from C:/Ruby200-x64/bin/rhc:23:in `load'
        from C:/Ruby200-x64/bin/rhc:23:in `<main>'

C:\Users\openshift>rhc
C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/rhc-1.9.3/bin/rhc:15:in `trap': unsuppor
ted signal SIGPIPE (ArgumentError)
        from C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/rhc-1.9.3/bin/rhc:15:in `<t
op (required)>'
        from C:/Ruby200-x64/bin/rhc:23:in `load'
        from C:/Ruby200-x64/bin/rhc:23:in `<main>'



Version-Release number of selected component (if applicable):
rhc-1.9.3.gem

How reproducible:
always

Steps to Reproduce:
1.Install rhc client on Win7/win8, and run some rhc commands



Actual results:
It's failed for all rhc commands.


Expected results:
All rhc commands can work well.

Additional info:
Ruby version is as below:
C:\Users\openshift>ruby -v
ruby 2.0.0p0 (2013-02-24) [x64-mingw32]

Comment 1 Xiaoli Tian 2013-05-24 03:27:31 UTC
Comment out the following line could work around this problem.

 C:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/rhc-1.9.3/bin/rhc:15

Comment 2 Jordan Liggitt 2013-05-28 14:50:06 UTC
Filter list of trapped signals by the ones Signal can process

Comment 3 Jordan Liggitt 2013-05-28 15:27:30 UTC
Marked as merge in https://github.com/openshift/rhc/pull/391

Comment 4 openshift-github-bot 2013-05-28 17:33:34 UTC
Commit pushed to master at https://github.com/openshift/rhc

https://github.com/openshift/rhc/commit/73c2b6dd06f1117b1d6065da47aea3cd7c674895
Fix bug 965923 - only trap supported signals

Comment 5 joycezhang 2013-05-29 02:25:30 UTC
This bug is not fixed with rhc-1.9.5, a different error is returned as below:

$ rhc
c:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/rhc-1.9.5/bin/rhc:16:in `trap': tried to
 create Proc object without a block (ArgumentError)
        from c:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/rhc-1.9.5/bin/rhc:16:in `<t
op (required)>'
        from c:/Ruby200-x64/bin/rhc:23:in `load'
        from c:/Ruby200-x64/bin/rhc:23:in `<main>'


It's required to comment out c:/Ruby200-x64/lib/ruby/gems/2.0.0/gems/rhc-1.9.5/bin/rhc:16 to work around.

Comment 6 joycezhang 2013-05-29 08:44:47 UTC
Pasted the signal list keys for the used windows client for the reference as below:
$ irb
DL is deprecated, please use Fiddle
irb(main):001:0> Signal.list.keys
=> ["EXIT", "INT", "ILL", "ABRT", "FPE", "KILL", "SEGV", "TERM"]
irb(main):002:0>

Comment 7 Jordan Liggitt 2013-05-29 12:57:58 UTC
Marked as merge in https://github.com/openshift/rhc/pull/393

Comment 8 openshift-github-bot 2013-05-29 14:05:42 UTC
Commit pushed to master at https://github.com/openshift/rhc

https://github.com/openshift/rhc/commit/b7daac827dc2febe2f534c860fb319cca91b22a2
Fix bug 965923 - only trap PIPE if supported

Comment 9 joycezhang 2013-05-30 02:54:05 UTC
Fixed with rhc-1.9.6.gem on Windows, no error shown when using rhc commands with this version. Thanks.