Bug #3128
noVNC not working properly in Ruby 1.8.7
| Status: | Closed | Start date: | 08/03/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Jaime Melis | % Done: | 0% | |
| Category: | Sunstone | |||
| Target version: | Release 4.8 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 4.6, OpenNebula 4.8 |
Description
This affects CentOS 6 for instance.
In OpenNebulaVNC.rb we close the stdin and reopen stderr and stdout to the log. However in Ruby 1.8.7 after this snippet is executed
$stdin.close $stdout.reopen(VNC_LOG, "a") $stderr.reopen(VNC_LOG, "a")
STDOUT occupies fd0 and STDERR fd1, meaning that child process will find stderr closed.
Associated revisions
Bug #3128: noVNC not working properly in Ruby 1.8.7
Bug #3128: noVNC not working properly in Ruby 1.8.7
(cherry picked from commit 01d308c171a1f9b7b4d921ca69cdf2e7d3c0f283)
Bug #3128: noVNC not working properly in Ruby 1.8.7
(cherry picked from commit 01d308c171a1f9b7b4d921ca69cdf2e7d3c0f283)
History
#1
Updated by Jaime Melis almost 7 years ago
- Status changed from Assigned to Closed
- Resolution set to fixed
Fixed by reordering the order of reopen and close. Patch applied to 4.6 branch as well.