Bug 1250098
Summary: | Fleecing on openstack instance: job timed out because snapshot creation never completes. | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Aziza Karol <akarol> | ||||
Component: | SmartState Analysis | Assignee: | Rich Oliveri <roliveri> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Satyajit Bulage <sbulage> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 5.5.0 | CC: | jhardy, obarenbo, sbulage | ||||
Target Milestone: | GA | ||||||
Target Release: | cfme-future | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | upstream:smartstate:retest:openstack | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2017-08-21 13:02:56 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: | |||||||
Attachments: |
|
Github link -https://github.com/ManageIQ/manageiq/issues/3666 The fact that the snapshot creation never completes would indicate some sort of back end problem. Can this be reproduced in other OpenStack environments? Hello Rich, SmartState Analysis(fleecing) is working fine on RHOS-7 provider. Appliance Version:5.8 Please let me know if any other information needed. Thanks, Satyajit Bulage. This bug has been open for more than a year and is assigned to an older release of CloudForms. If you would like to keep this Bugzilla open and if the issue is still present in the latest version of the product, please file a new Bugzilla which will be added and assigned to the latest release of CloudForms. |
Created attachment 1059105 [details] err Description of problem: Version-Release number of selected component (if applicable): master.20150804081122_7775a99 How reproducible: 100% Steps to Reproduce: 1.Add Rhos cloud provider 2.perform smart state analysis on rhos instance 3.Navigate to configure->task Actual results: job timed out after 328.288434042 seconds of inactivity. Inactivity threshold [3000 seconds] is displayed in task. see attached screenshot Expected results: smart state analysis on rhos instance should be successful Additional info: