Bug 743395

Summary: stopping rhevm deployment causes 6+ days added to total uptime
Product: [Retired] CloudForms Cloud Engine Reporter: Dave Johnson <dajohnso>
Component: aeolus-conductorAssignee: Jozef Zigmund <jzigmund>
Status: CLOSED ERRATA QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, dajohnso, deltacloud-maint, dgao, jzigmund, slinaber, ssachdev, whayutin
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-15 22:10:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
screenshot
none
rhev_inst
none
rhev_time none

Description Dave Johnson 2011-10-04 19:14:17 UTC
Created attachment 526309 [details]
screenshot

Description of problem:
==============================
Once a rhevm deployment is stopped, the total uptime changes to 6 days 23+ hours no matter how long the instance was online.  This appears on the pool score cards.

Version-Release number of selected component (if applicable):
===============================================================
aeolus-all-0.4.0-0.20111003184622git65a7d19.fc15.noarch
aeolus-conductor-0.4.0-0.20111003184622git65a7d19.fc15.noarch
aeolus-conductor-daemons-0.4.0-0.20111003184622git65a7d19.fc15.noarch
aeolus-conductor-doc-0.4.0-0.20111003184622git65a7d19.fc15.noarch
aeolus-configure-2.0.2-4.20110930103205gitaf78594.fc15.noarch
deltacloud-core-0.5.0-0.1.1317167702git.noarch
deltacloud-core-ec2-0.5.0-0.1.1317167702git.noarch
deltacloud-core-rhevm-0.5.0-0.1.1317167702git.noarch
deltacloud-core-vsphere-0.5.0-0.1.1317167702git.noarch
imagefactory-0.6.2_11_g7b94a4a-1.fc15.noarch
iwhd-0.98.15.z3-2.fc15.x86_64
oz-0.7.0-2.fc15.noarch
rubygem-aeolus-cli-0.1.0-3.20111003133323git9451323.fc15.noarch
rubygem-aeolus-image-0.1.0-3.20111003170706git8f23238.fc15.noarch
rubygem-deltacloud-client-0.4.0-3.fc15.noarch
rubygem-imagefactory-console-0.5.0-4.20110824113238gitd9debef.fc15.noarch

Steps to Reproduce:
=================================
1.  deploy a rhevm image through a cloud engine deployment
2.  allow it to transition to running
3.  click on the pool to see uptime
4.  stop the instance/image/deployment
5.  click on the pool to see the uptime (6 days 23 hours...)

Comment 2 Dave Johnson 2011-11-03 14:00:36 UTC
good 2 go in aeolus-conductor-0.5.0-1.fc15.noarch

Comment 3 Dave Johnson 2011-12-07 15:24:36 UTC
This issue seems to have come back.  Seen with the following rpms
   aeolus-all-0.7.0-4.el6.noarch
   aeolus-conductor-0.7.0-4.el6.noarch
   aeolus-conductor-daemons-0.7.0-4.el6.noarch
   aeolus-conductor-doc-0.7.0-4.el6.noarch
   aeolus-configure-2.4.0-3.el6.noarch
   rubygem-aeolus-cli-0.2.0-3.el6.noarch
   rubygem-aeolus-image-0.2.0-1.el6.noarch

Comment 4 wes hayutin 2012-01-12 16:34:56 UTC
adding to ce-sprint

Comment 5 wes hayutin 2012-01-12 16:41:16 UTC
removing ce-sprint-next tracker

Comment 6 Shveta 2012-01-13 15:11:21 UTC
Created attachment 555080 [details]
rhev_inst

Comment 7 Shveta 2012-01-13 15:12:59 UTC
Created attachment 555081 [details]
rhev_time

Comment 8 Jozef Zigmund 2012-01-24 13:15:44 UTC
Bug was fixed. Please verify it. Bugfix's commit # dba3a9e3266e3a6f049600a6a645e5a26498f6d9 in axiom/1.0-staging repo.

Comment 9 Steve Linabery 2012-01-25 00:09:28 UTC
49a0120  dba3a9e in aeolus-conductor-0.8.0-11.el6

Comment 11 Dave Johnson 2012-02-02 15:25:16 UTC
good 2 go with

aeolus-all-0.8.0-17.el6.noarch
aeolus-conductor-0.8.0-17.el6.noarch
aeolus-conductor-daemons-0.8.0-17.el6.noarch
aeolus-conductor-doc-0.8.0-17.el6.noarch

Comment 12 errata-xmlrpc 2012-05-15 22:10:28 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.

http://rhn.redhat.com/errata/RHEA-2012-0583.html