Bug 599116 - ruby QMF bindings can't query agents.
Summary: ruby QMF bindings can't query agents.
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-qmf   
(Show other bugs)
Version: Development
Hardware: All Linux
Target Milestone: ---
: ---
Assignee: Ted Ross
QA Contact: MRG Quality Engineering
Keywords: Regression
Depends On:
Blocks: 529243 564419 609298
TreeView+ depends on / blocked
Reported: 2010-06-02 17:30 UTC by Ian Main
Modified: 2013-05-13 15:11 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 609298 (view as bug list)
Last Closed: 2013-05-13 15:11:00 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
libvirt-list lists libvirt-qpid objects. (1.87 KB, text/plain)
2010-06-02 17:30 UTC, Ian Main
no flags Details

Description Ian Main 2010-06-02 17:30:49 UTC
Created attachment 419106 [details]
libvirt-list lists libvirt-qpid objects.

Description of problem:

I wrote a simple program to query libvirt-qpid some time ago.  This program no longer works with latest release in RHEL6.

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


How reproducible:


Steps to Reproduce:
1. Run qpidd, libvirt-qpid
2. Run libvirt-list.rb, note lack of return.
Actual results:

No objects are found.

Expected results:

libvirt-qpid objects should be found.

Additional info:

libvirt-list.rb is attached.

Comment 2 Ian Main 2010-06-08 16:19:50 UTC
if you are using ruby to query libvirt-qpid, then yes.  libvirt-qpid is working fine as of the last patch.  However, the ruby qmf bindings are not working.

I think this should be high priority but will leave that up to tross.

Comment 3 Jan Sarenik 2010-06-22 10:36:34 UTC
This bug does not have any Target Milestone set.
Is that expected, Ian? This way it will be forgotten soon.
Please set it if you want this bug to be resolved. Thanks.

Comment 5 Ian Main 2010-06-28 20:13:51 UTC
OK, I'm setting this to high in the hopes it will be looked at. :)

Comment 6 Ian Main 2010-06-28 20:20:10 UTC
Well I'd like to see this fixed for rhel6 but am not sure what target milestone should be set to.  I set it to 'next version' for now?

Comment 10 Jan Sarenik 2010-07-20 06:46:59 UTC
Ted, are you working on this for 1.3? This bug prevents me from
running the stress test written by M. Morsi - see branch
jasan at http://ooo.englab.brq.redhat.com/c/movitto-qmf.git/
which contains current changes that make at least the C++ part
work (methods tested with qpid-tool). But the ruby console does
not see the C++ agent so I can not use the test as it is.
It worked previously.

Comment 11 Jan Sarenik 2010-07-27 15:05:07 UTC
Is this still a valid mrg-blocker after today's explanation by Ted that this
is reversed only for RHEL6 so that libvirt-qmf works there?

Comment 12 Ian Main 2010-07-27 15:16:38 UTC
This is the WAY FORWARD(tm).  These bindings are how the python bindings should be done along side the ruby bindings.  This should definitely be a blocker.  This should never have gotten as far behind as it is IMO.

Comment 13 Jan Sarenik 2010-08-04 07:31:58 UTC
What's the status here, please?

Comment 18 Jan Sarenik 2011-03-02 15:22:15 UTC
Is this going into 2.0? What's the progress?

Comment 19 Ted Ross 2011-03-23 12:48:08 UTC
I'm nacking this BZ...  A new Ruby API has been introduced for QMFv2 which does not have the same problem as the existing Ruby API.  There are two possibilities for moving forward:

1) Migrate the test tools to the new API (preferred)
2) Provide old-API support for QMFv2 (I'm not sure there's value in doing this)

Note You need to log in before you can comment on or make changes to this bug.