Red Hat Bugzilla – Bug 506698
Handle backward/forward compatibility for QMF
Last modified: 2011-08-12 12:02:12 EDT
Description of problem:
In the next version, the QMF protocol will have undergone some changes and will have a new magic number in the header. It's possible that components (agents, brokers, and consoles) will not all be upgraded at the same time.
It is important that the different versions work as well with each other as is possible.
In the 929717 (and later) packages, the broker provides dual support in that it allows both QMFv1 and QMFv2 operations to occur and the Python console concurrently supports both v1 and v2 agents. A v1-only console will not be able to manage a v2 agent.
QMF compatibility matrix
MRG | 1.2 | 1.3 | <-- agent
1.2 | OK | n/a |
1.3 | OK | OK |
Only 1.3 (QMF2 capable) broker was used in testing.
Condor with its QMF plugins (which use QMF1 in MRG 1.2
version of Condor) was run with QMF_BROKER_HOST set to
host running MRG 1.3 broker. Also sesame was run against
the same broker.
Then Python QMF console qpid-tool was from both hosts.
1.2 QMF console could see only 1.2 agents, i.e. it could
not see the MRG 1.3 broker's internal agents at all as
they use QMF2 already.
1.3 QMF console was able to see all the agents when asked
for schema, but QMF1 agent objects can not be seen using
"list" (except for "schema") without running 1.2 qpid-tool
RHEL4 1.2 packages:
RHEL4 1.3 packages:
There is a new bug 506698 covering appearance of QMFv1 agent
objects. But as far as I can work around it (by running MRG 1.2
qpid-tool and triggering appearance of those objects this way),
I prove this bug to be verified with strings attached.
MRG 1.2 packages:
MRG 1.3 packages (installed on different host):
Verified on both RHEL4 and RHEL5, i386 and x86_64.
Correction, the new one is bug 640640.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
This update handles backward/forward compatibility for QMF and its components.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.