Bug 1222138 - Timeout issues with fleecing on OpenStack
Summary: Timeout issues with fleecing on OpenStack
Keywords:
Status: CLOSED ERRATA
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.4.0
Assignee: Rich Oliveri
QA Contact: Ramesh A
URL:
Whiteboard:
Depends On: 1219998
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-15 21:01 UTC by Oleg Barenboim
Modified: 2015-06-16 13:02 UTC (History)
9 users (show)

Fixed In Version: 5.4.0.2
Doc Type: Bug Fix
Doc Text:
Clone Of: 1219998
Environment:
Last Closed: 2015-06-16 13:02:34 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
rhos fleecing error (70.15 KB, image/png)
2015-05-18 16:05 UTC, Ramesh A
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:1100 0 normal SHIPPED_LIVE CFME 5.4.0 bug fixes, and enhancement update 2015-06-16 16:28:42 UTC

Comment 1 John Prause 2015-05-15 21:09:45 UTC
Seems we need a cherry-pick back for 5.4.z

Comment 3 Ramesh A 2015-05-18 16:00:05 UTC
Still reproducible in 5.4.0.1.20150512111354_4368716.

Fleeced two instance with the following details
1. Instance created with cirros image with 20Gb of storage - Fleecing result: passed
2. EVM instance with 40Gb of storage -Fleecing result: Failed with timeout exception. 

Refer the log file and screenshot for further details.

*Note*:
Had a discussing with Thom and he said after applying the job.rb patch, he is not able to see any timed out exception in the appliance.  However I did not see this patch being cherry picked in the above mentioned build.  Hence moving it back to ON_DEV status.


evm.log:
========
[----] E, [2015-05-18T11:04:24.492791 #4915:f2bea8] ERROR -- : action-abort: job aborting, job timed out after 360.2952184 seconds of inactivity.  Inactivity threshold [300 seconds]
[----] E, [2015-05-18T11:08:18.050753 #4911:f3fea8] ERROR -- : Q-task_id([4bef2b1a-fd6e-11e4-9b8c-0050569674e2]) MIQ(scan-call_snapshot_create Failed to create evm snapshot with EMS. Error: []: [execution expired]
[----] E, [2015-05-18T11:08:18.138159 #4911:f3fea8] ERROR -- : Q-task_id([4bef2b1a-fd6e-11e4-9b8c-0050569674e2]) action-abort: job aborting, Failed to create evm snapshot with EMS. Error: []: [execution expired]


policy.log:
===========
[----] I, [2015-05-18T10:58:08.773660 #4915:f2bea8]  INFO -- : MIQ(policy-enforce_policy): Event: [request_vm_scan], To: [s_appl_downstream-54z_150506_7b3qy6zE]
[----] I, [2015-05-18T10:58:18.078242 #4911:f3fea8]  INFO -- : Q-task_id([4bef2b1a-fd6e-11e4-9b8c-0050569674e2]) MIQ(policy-enforce_policy): Event: [vm_scan_start], To: [s_appl_downstream-54z_150506_7b3qy6zE]
[----] I, [2015-05-18T10:58:18.117344 #4911:f3fea8]  INFO -- : Q-task_id([4bef2b1a-fd6e-11e4-9b8c-0050569674e2]) MIQ(policy-enforce_policy): Resolving policy [ramesh]...
[----] I, [2015-05-18T10:58:18.445895 #4911:f3fea8]  INFO -- : Q-task_id([4bef2b1a-fd6e-11e4-9b8c-0050569674e2]) MIQ(action-invoke) Invoking action [Generate log message] for successful policy [ramesh], event: [VM Analysis Start], entity name: [s_appl_downstream-54z_150506_7b3qy6zE], entity type: [VmOpenstack], sequence: [1], synchronous? [true]
[----] I, [2015-05-18T10:58:18.446267 #4911:f3fea8]  INFO -- : Q-task_id([4bef2b1a-fd6e-11e4-9b8c-0050569674e2]) MIQ(action-log): Policy success: policy: [ramesh], event: [VM Analysis Start], entity name: [s_appl_downstream-54z_150506_7b3qy6zE], entity type: [VmOpenstack]
[----] I, [2015-05-18T10:58:18.446538 #4911:f3fea8]  INFO -- : Q-task_id([4bef2b1a-fd6e-11e4-9b8c-0050569674e2]) MIQ(action-invoke) Invoking action [ramesh-analysis-profile] for successful policy [ramesh], event: [VM Analysis Start], entity name: [s_appl_downstream-54z_150506_7b3qy6zE], entity type: [VmOpenstack], sequence: [2], synchronous? [true]
[----] I, [2015-05-18T10:58:18.448610 #4911:f3fea8]  INFO -- : Q-task_id([4bef2b1a-fd6e-11e4-9b8c-0050569674e2]) MIQ(action_assign_scan_profile): Action [ramesh-analysis-profile], using analysis profile: [default]
[----] I, [2015-05-18T10:59:48.822501 #4915:f2bea8]  INFO -- : MIQ(policy-enforce_policy): Event: [vm_template], To: [EvmSnapshot]
[----] I, [2015-05-18T11:04:24.456165 #4915:f2bea8]  INFO -- : MIQ(policy-enforce_policy): Event: [vm_scan_abort], To: [s_appl_downstream-54z_150506_7b3qy6zE]
[----] I, [2015-05-18T11:08:18.108806 #4911:f3fea8]  INFO -- : Q-task_id([4bef2b1a-fd6e-11e4-9b8c-0050569674e2]) MIQ(policy-enforce_policy): Event: [vm_scan_abort], To: [s_appl_downstream-54z_150506_7b3qy6zE]

Comment 4 Ramesh A 2015-05-18 16:05:26 UTC
Created attachment 1026763 [details]
rhos fleecing error

Comment 5 Oleg Barenboim 2015-05-18 16:52:08 UTC
Ramesh - it only got merged on Friday late afternoon - so it would not be in the 5.4.0.1 build.  But it should be in the 5.4.0.2 build.

Comment 7 Ramesh A 2015-05-22 12:18:45 UTC
Good to go.  Verified and working fine in 5.4.0.2.20150519003830_673f996

Comment 9 errata-xmlrpc 2015-06-16 13:02:34 UTC
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.

https://rhn.redhat.com/errata/RHBA-2015-1100.html


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