Bug 857542
| Summary: | RHEV instance stopped but displays 'running' in deployment view | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Aaron Weitekamp <aweiteka> | ||||||||||||||||||||||
| Component: | aeolus-conductor | Assignee: | Jan Provaznik <jprovazn> | ||||||||||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Rehana <aeolus-qa-list> | ||||||||||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||
| Version: | 1.1.0 | CC: | asettle, dajohnso, dmacpher, morazi, rlandy, tzumainn | ||||||||||||||||||||||
| Target Milestone: | beta2 | ||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||||
| OS: | Linux | ||||||||||||||||||||||||
| Whiteboard: | |||||||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||||
| Doc Text: |
Cloud Engine compared "last_pending" time with "last_running" time to distinguish newly created instances from previously running instances. This conflicted with a bug in 0.5.x versions of deltacloud-core, which returned a "pending" state when shutting down an instance. This caused some instances to appear in a "running" state for some views when they were "stopped". This fix changes the behavior to check if 'create' was last queued instance's task. Cloud Engine now displays the instance state correctly in all views.
|
Story Points: | --- | ||||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||||
| Last Closed: | 2012-12-04 15:19:31 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: |
|
||||||||||||||||||||||||
Created attachment 612961 [details]
messages log
Created attachment 612962 [details]
screencap: instances running
Created attachment 612963 [details]
screencap: applications stopped
Created attachment 612964 [details]
screencap: monitor stopped
Created attachment 612965 [details]
screencap: deployment running
Created attachment 612966 [details]
screencap: history running
Created attachment 612977 [details]
aeolus-debug logs
The problem is that we have really old version of deltacloud-core in RHEL, this version has a bug - it returns state 'pending' instead of 'shutting_down' when an instance is being stopped. Pending state should be used only when an instance is being started. And conductor compares last pending/running times to distinguish if an instance is in stopped state after creation or if it was already running before. There are 2 options how to fix this: 1) update deltacloud-core in RHEL 2) if 1) is not possible, create some quickfix on conductor side so that conductor will not use pending time to check if an instance needs to be started. the dc-core issue was tracked here: https://issues.apache.org/jira/browse/DTACLOUD-148 a patch is waiting for review: https://lists.fedorahosted.org/pipermail/aeolus-devel/2012-September/012633.html Pushed to master and 1.1:
commit b2363a25732be9672849bddacccda9cdb9af113a
Author: Jan Provaznik <jprovazn>
Date: Thu Sep 20 14:33:13 2012 -0400
Older dc-core (0.5.x version in RHEL) returns 'pending' state when an instances
is shutting down. Conductor compared last_pending time with last_running time
to distinguish newely created instances. But this comparison doesn't work properly
with the bug in dc-core.
Instead of last_pending time conductor now checks if 'create' was last queued
instance's task.
https://bugzilla.redhat.com/show_bug.cgi?id=857542
Signed-off-by: Tzu-Mainn Chen <tzumainn>
(cherry picked from commit fbf5b95ae1b5c8b014065ea65669fddd89498cf5)
*** Bug 859538 has been marked as a duplicate of this bug. *** Tested rpms: >> rpm -qa |grep aeolus aeolus-configure-2.8.7-1.el6cf.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch rubygem-aeolus-cli-0.7.2-1.el6cf.noarch aeolus-conductor-0.13.14-1.el6cf.noarch aeolus-conductor-daemons-0.13.14-1.el6cf.noarch aeolus-conductor-doc-0.13.14-1.el6cf.noarch aeolus-all-0.13.14-1.el6cf.noarch and >> rpm -qa |grep deltacloud rubygem-deltacloud-client-0.5.0-2.el6.noarch deltacloud-core-vsphere-0.5.0-10.el6_2.noarch deltacloud-core-rhevm-0.5.0-10.el6_2.noarch deltacloud-core-ec2-0.5.0-10.el6_2.noarch deltacloud-core-0.5.0-10.el6_2.noarch I launched an instance to rhevm and the instance was started. I then opened a second browser (chrome one this time) and stopped the rhevm instance in that second browser. The conductor instance opened in the first (FF) browser did pick up the change in state from running -> pending. I needed to refresh the page, but then the instance did show 'stopped' in the deployments/x and details pages ... see attached screenshots. Noting also that this issues has been addressed and verified in Deltacloud 1.0.x versions Marking this BZ as 'verified' since this is not related to page updates and the instance is not recorded as running. Created attachment 617263 [details]
before page refresh - shows pending
Created attachment 617272 [details]
after page refresh - shows stopped
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/RHEA-2012-1516.html |
Created attachment 612960 [details] aeolus.log Description of problem: RHEV instance is stopped but displays running in some views. - Monitor views (conductor/pools): stopped - Deployment Instances view (conductor/deployments/2): running - Deployment History logs: running Version-Release number of selected component (if applicable): CF 1.1 [root@qeblade40 ~]# rpm -qa |grep aeolus aeolus-conductor-daemons-0.13.3-1.el6cf.noarch rubygem-aeolus-image-0.6.0-1.el6cf.noarch aeolus-configure-2.8.3-1.el6cf.noarch aeolus-conductor-0.13.3-1.el6cf.noarch rubygem-aeolus-cli-0.7.1-1.el6cf.noarch aeolus-conductor-doc-0.13.3-1.el6cf.noarch aeolus-all-0.13.3-1.el6cf.noarch How reproducible: Unclear Steps to Reproduce: 1. launch rhevm instance 2. stop instance 3. check UI Actual results: RHEV instance is stopped but says it's running in some UI views Expected results: RHEV instance should report stopped in all UI views