Bug 1228750 - Fleecing a RHOS4 instance throws "Cannot grant exclusive access to queue"
Summary: Fleecing a RHOS4 instance throws "Cannot grant exclusive access to queue"
Keywords:
Status: CLOSED DUPLICATE of bug 1224389
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: SmartState Analysis
Version: 5.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: 5.5.0
Assignee: Rich Oliveri
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-05 15:06 UTC by Thom Carlin
Modified: 2015-11-11 20:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-05 15:15:03 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Thom Carlin 2015-06-05 15:06:19 UTC
Description of problem:

When fleecing an instance, receive errors in evm.log

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

5.4.0.4.20150528174021_88cc76c

How reproducible:

100%

Steps to Reproduce:
1. Define a RHOS provider
2. Fleece an instance
3.

Actual results:

No SmartState Analysis, errors in log

Expected results:

Successful SmartState Analysis, no errors

Additional info:

evm.log excerpt:
[----] E, [2015-06-05T11:02:50.265050 #4556:3515de4] ERROR -- : MIQ(EventCatcherOpenstack) EMS [10.8.58.49] as [admin] Event Monitor Thread aborted because [resource-locked: resource-locked: Cannot gr
ant exclusive access to queue miq-<ip_address>-nova (qpid/broker/SessionAdapter.cpp:332)]
[----] E, [2015-06-05T11:02:50.265167 #4556:3515de4] ERROR -- : [MessagingError]: resource-locked: resource-locked: Cannot grant exclusive access to queue miq-<ip_address>-nova (qpid/broker/SessionAdapt
er.cpp:332)  Method:[rescue in block in start_event_monitor]
[----] E, [2015-06-05T11:02:50.265261 #4556:3515de4] ERROR -- : /opt/rh/ruby200/root/usr/share/gems/gems/qpid_messaging-0.20.2/lib/qpid_messaging/receiver.rb:137:in `getAvailable'
/opt/rh/ruby200/root/usr/share/gems/gems/qpid_messaging-0.20.2/lib/qpid_messaging/receiver.rb:137:in `available'
/var/www/miq/lib/openstack/amqp/openstack_qpid_receiver.rb:44:in `get_notifications'
/var/www/miq/lib/openstack/amqp/openstack_qpid_event_monitor.rb:73:in `block in each_batch'
/var/www/miq/lib/openstack/amqp/openstack_qpid_event_monitor.rb:72:in `each'
/var/www/miq/lib/openstack/amqp/openstack_qpid_event_monitor.rb:72:in `each_batch'
/var/www/miq/vmdb/lib/workers/mixins/event_catcher_openstack_mixin.rb:40:in `monitor_events'
/var/www/miq/vmdb/lib/workers/event_catcher.rb:99:in `block in start_event_monitor'
/var/www/miq/vmdb/lib/extensions/ar_thread.rb:11:in `block in new_with_release'

Comment 2 Greg Blomquist 2015-06-05 15:15:03 UTC

*** This bug has been marked as a duplicate of bug 1224389 ***


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