Bug 786167

Summary: ruby QMFv1 console uses puts
Product: Red Hat Enterprise MRG Reporter: Matthew Farrellee <matt>
Component: qpid-qmfAssignee: Darryl L. Pierce <dpierce>
Status: CLOSED ERRATA QA Contact: Irina Boverman <iboverma>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.0CC: iboverma, jross, lzhaldyb, mcressma, tross
Target Milestone: 3.0   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qpid-qmf-0.22-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-24 15:03:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Matthew Farrellee 2012-01-31 16:01:33 UTC
Description of problem:

QMFv1 ruby console library is writing to stdout.


Version-Release number of selected component (if applicable):

ruby-qpid-qmf-0.14-2.el5


How reproducible:

100%


Steps to Reproduce:
1. Use a cli ruby console, see "Console Connection Established..."

  
Actual results:


Expected results:

No stdout from library.


Additional info:

There are 11 instances of this...

$ grep puts /usr/lib/ruby/site_ruby/1.8/qmf.rb
            puts "Event Exception: #{ex}"
              puts ex.backtrace
          puts "Exception caught in callback: #{ex}"
            puts ex.backtrace
      puts "Console Connection Established..."
      puts "Console Connection Lost"
      puts "Console Session Lost"
      puts "Unexpected RECV Event" if not @operational
      puts "Agent Connection Established..."
      puts "Agent Connection Lost"
      puts "Agent Session Lost"

Comment 1 Darryl L. Pierce 2012-04-23 18:48:06 UTC
There is a fix posted upstream.

Comment 5 Darryl L. Pierce 2012-10-11 19:49:16 UTC
This fix is pushed into the upstream project now.

Comment 8 errata-xmlrpc 2014-09-24 15:03:53 UTC
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.

http://rhn.redhat.com/errata/RHEA-2014-1296.html