Bug 1212583
Summary: | Ruby app trys to load module and connection is refused | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Eric Rich <erich> |
Component: | ImageStreams | Assignee: | Timothy Williams <tiwillia> |
Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 2.2.0 | CC: | adellape, bleanhar, erich, frank, gpei, jdetiber, jokerman, libra-bugs, libra-onpremise-devel, mmccomas, nwei, vvitek, xtian, yanpzhan |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
The Passenger rubygem previously prespawned on the local 127.0.0.1 IP address. As a result, an error was reported at startup in the Ruby log. This bug fix updates Passenger to connect in prespawn to the proper gear IP address, and as a result prespawn functions properly and no error is reported in the logs at startup.
|
Story Points: | --- |
Clone Of: | 1044980 | Environment: | |
Last Closed: | 2015-07-21 19:12:18 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: | |||
Bug Depends On: | 1044980 | ||
Bug Blocks: |
Comment 1
Eric Rich
2015-04-16 17:34:40 UTC
The issue in ruby 1.8 was a confusing error message but no functionality was technically broken. Is this the same case or is functionality broken in some way? Could reproduce with ruby193-rubygem-passenger-3.0.21-3.el6op.x86_64. This should be the same issue with ruby 1.8. Hardcode '127.0.0.1' could be seen in /opt/rh/ruby193/root/usr/share/gems/gems/passenger-3.0.21/helper-scripts/prespawn 99 class TCPPrespawnLocation < PrespawnLocation 100 def request_port 101 @uri.port 102 end 103 104 def connect 105 TCPSocket.new('127.0.0.1', request_port) 106 end 107 end (In reply to Brenton Leanhardt from comment #4) > The issue in ruby 1.8 was a confusing error message but no functionality was > technically broken. Is this the same case or is functionality broken in > some way? Customer confirmed that this is not something that breaks the application, but is a reporting issue. Verify this bug with ruby193-rubygem-passenger-3.0.21-4.el6op.x86_64 The hardcode has been removed. No error found in ruby-1.8/ruby-1.9 application log. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-1463.html |