Bug 851217
Summary: | wallaby shell should detect if there are more wallaby agents on broker | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Lubos Trilety <ltrilety> |
Component: | wallaby-utils | Assignee: | Will Benton <willb> |
Status: | CLOSED ERRATA | QA Contact: | Lubos Trilety <ltrilety> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.2 | CC: | iboverma, matt, willb |
Target Milestone: | 2.3 | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | wallaby-0.16.1-1 | Doc Type: | Bug Fix |
Doc Text: |
Cause: There should be only one Wallaby agent running on the qpid broker, but in some rare cases it may be possible for two Wallaby agents to start on the same broker.
Consequence: Running wallaby shell commands could have unpredictable results if more than one Wallaby agent is on the broker.
Fix: The wallaby shell now ensures that only one Wallaby agent is running on the specified broker as part of its startup.
Result: The aforementioned unpredictable behavior will be avoided.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-03-06 18:45:33 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Lubos Trilety
2012-08-23 14:08:21 UTC
tested with:
wallaby-utils-0.16.1-2
tested on:
RHEL6 i386,x86_64
RHEL5 i386,x86_64
wallaby shell correctly detect if there is more than one wallaby agent connected
# wallaby -H host1 list-nodes
Console Connection Established...
fatal: there is more than one Wallaby agent running on the specified broker (lt-rhel5_64-old:5672); only one may run at a time
Agents found:
pid 10150 on host1
pid 24612 on host2
pid 14393 on host3
pid 23114 on host4
>>> verified
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/RHSA-2013-0564.html |