Bug 564419
| Summary: | QMF Console hangs when querying for objects | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Robert Rati <rrati> | ||||||
| Component: | qpid-qmf | Assignee: | Ted Ross <tross> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Jeff Needle <jneedle> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | Development | CC: | gsim, iboverma, jross, tross | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-03-05 15:55:39 UTC | Type: | --- | ||||||
| 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: | 599116 | ||||||||
| Bug Blocks: | |||||||||
| Attachments: |
|
||||||||
|
Description
Robert Rati
2010-02-12 17:18:05 UTC
Fixed upstream at revision 909548. Created attachment 399312 [details] stress tests patch Source of the tests is http://github.com/movitto/qmf/ but this patch is needed to make it work on RHEL5 without rubygems. Libvirt-devel is also not needed. Reproduced on qmf-0.7.908272-1.el5.x86_64.rpm qmf-devel-0.7.908272-1.el5.x86_64.rpm ruby-qmf-0.7.908272-1.el5.x86_64.rpm qpid-cpp-server-0.7.908272-1.el5.x86_64.rpm qpid-cpp-client-0.7.908272-1.el5.x86_64.rpm qpid-cpp-client-devel-0.7.908272-1.el5.x86_64.rpm On the mentioned versions, only "src/stress_agent -n 82" runs without a hang of the console.rb client. On latest candidate packages (0.7.916826-2.el5) the client (console.rb) is not hanging, but writes this in the log: ------------------- Console Connection Established... Searching for objects of class testobject in packages com.redhat.stress_agent Got 1 objects Object Retreived #<Qmf::ConsoleObject:0x2b38f3f52f10> Generated password t2bwCHHJVGMKc from ANoQBSAW-t2j1tVpA ------------------- Whereas in buggy version it at least gets 500 objects (that's the number supplied to stress_agent via -n parameter): ------------------- Console Connection Established... Searching for objects of class testobject in packages com.redhat.stress_agent Got 500 objects Object Retreived #<Qmf::ConsoleObject:0x2b17edacded0> ...SNIP... ------------------- Is this behavior correct? Hmm, something is wrong. I have just tested it with 0.7.909548-1 packages (fixed) and they get all 500 objects without hanging. So there is probably a regression somewhere after that. The output on 909548 looks like this: Console Connection Established... Searching for objects of class testobject in packages com.redhat.stress_agent Got 500 objects Object Retreived #<Qmf::ConsoleObject:0x2ab34b6336b0> Object Retreived #<Qmf::ConsoleObject:0x2ab34b6328c8> ...SNIP... (another 498 lines like this follow) Generated password ktR3VusHFoPco from SZJDqoKq-ZbUFRGF0 Generated password jMsCvRW9BNklA from SZJDqoKq-ZbUFRGF0 ...SNIP... (another 498 lines like the two above follow) This bug depends on bug 599116 for I am currently unable to see the C++ agent (stress_test) in ruby console. This bug is not a TestBlocker itself. The C++ sources are already compilable with latest modification I did yesterday and the resulting binary does its job (tested with qpid-tool's "call"). See branch jasan at http://ooo.englab.brq.redhat.com/c/movitto-qmf.git/ Created attachment 434763 [details] Current tests The attached test uses sources from jasan branch in git repo http://ooo.englab.brq.redhat.com/c/movitto-qmf.git/ commit aa83599285033ca9dabf556b2f4cf2aa1d1a67ad. Verified on RHEL6 x86_64, will be re-used on RHEL5 later. qpid-cpp-client-devel-0.7.946106-5.el6.x86_64 This is not going to be fixed in 1.3. I've moved the target to 1.3.1. Ted, is this still an issue? This bug is in code that is being deprecated. There has been no activity for a long time. I'm closing the bug. |