Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 842313

Summary: Instance state is misrepresentated with green color and in instance history for a instance in create-failed state
Product: [Retired] CloudForms Cloud Engine Reporter: pushpesh sharma <psharma>
Component: aeolus-conductorAssignee: Jan Provaznik <jprovazn>
Status: CLOSED ERRATA QA Contact: Rehana <aeolus-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.1.0CC: bbandari, dajohnso, dmacpher, morazi, slinaber
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Partially launched applications resulted in a green "running" state on the Monitor page. This bug fix changes the behavior to an "incomplete" state. The Monitor page now displays a yellow "incomplete" state for partially launched applications.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-04 15:15:10 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:
Description Flags
green_signal _for_createFailed
none
history_page
none
instance history
none
monitor
none
monitor after deltacloud service started
none
create_failed
none
history_fixed none

Description pushpesh sharma 2012-07-23 12:42:08 UTC 
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.Build and push any simple image (in my case rhel6.2)
2.Create a deployable from this image
3.Launch overview page is shown all paramter matching 
4.On the aeolus-host stop deltacloud core service
5.Launch the deployable from it,deployment fails and now in create_failed state(as expected).
6.start the deltacloud-core service again
  
Actual results:
1. On monitor page instance is shown with green signal
2.navigate Monitor-->instance-->history last line says state "running" although second last line and instance state in instance tab is "create failed".
3.navigate to Monitor-->instance-->instance-name-link-->history says state "create failed".

Expected results:
1.signal should be "yellow" as used for pending/new or any other but not green.
2.history should be in sync on all pages. 


Additional info:


[root@qeblade29 ~]# rpm -qa|grep aeolus
aeolus-configure-2.7.0-0.20120712224728gitcc8302d.fc16.noarch
rubygem-aeolus-cli-0.6.0-0.20120712224735gite2a391a.fc16.noarch
aeolus-conductor-0.11.0-0.20120713030022git8c99e02.fc16.noarch
aeolus-conductor-daemons-0.11.0-0.20120713030022git8c99e02.fc16.noarch
aeolus-all-0.11.0-0.20120713030022git8c99e02.fc16.noarch
aeolus-conductor-doc-0.11.0-0.20120713030022git8c99e02.fc16.noarch
aeolus-conductor-devel-0.11.0-0.20120713030022git8c99e02.fc16.noarch
rubygem-aeolus-image-0.5.0-1.fc16.noarch
Comment 1 pushpesh sharma 2012-07-23 12:42:56 UTC 
Created attachment 599771 [details]
green_signal _for_createFailed
Comment 2 pushpesh sharma 2012-07-23 12:43:46 UTC 
Created attachment 599773 [details]
history_page
Comment 5 Jan Provaznik 2012-08-27 13:25:57 UTC 
Can you still reproduce this? I wasn't able to reproduce it - for me it works as expected: when an instance launch fails, deployment ends in 'failed' state, not running.
Comment 6 pushpesh sharma 2012-08-28 07:46:11 UTC 
I am still getting the issue on the nightly build.PFA for the problem screenshot.  : -

[root@dell-pe1955-02 ~]# rpm -qa|grep aeolus
aeolus-configure-2.8.0-0.20120827230027gitbdcd549.fc16.noarch
aeolus-conductor-0.13.0-0.20120828030011git202d4f9.fc16.noarch
aeolus-conductor-daemons-0.13.0-0.20120828030011git202d4f9.fc16.noarch
aeolus-all-0.13.0-0.20120828030011git202d4f9.fc16.noarch
aeolus-conductor-doc-0.13.0-0.20120828030011git202d4f9.fc16.noarch
rubygem-aeolus-image-0.6.0-0.20120827230033gite69e319.fc16.noarch
rubygem-aeolus-cli-0.7.0-0.20120827230029gitd64d64f.fc16.noarch
Comment 7 pushpesh sharma 2012-08-28 07:47:14 UTC 
Created attachment 607431 [details]
instance history
Comment 8 pushpesh sharma 2012-08-28 07:47:44 UTC 
Created attachment 607432 [details]
monitor
Comment 9 pushpesh sharma 2012-08-28 07:48:16 UTC 
Created attachment 607433 [details]
monitor after deltacloud service started
Comment 10 Jan Provaznik 2012-08-29 08:08:18 UTC 
a patch for this is waiting for review: https://lists.fedorahosted.org/pipermail/aeolus-devel/2012-August/012339.html
Comment 11 Jan Provaznik 2012-09-04 14:10:05 UTC 
pushed, commit in master: 5e7ae521e39ead9e1796b8b2a940896dd42087a8
Comment 12 Steve Linabery 2012-09-07 21:55:45 UTC 
in build aeolus-conductor-0.13.3-1.el6cf
Comment 14 pushpesh sharma 2012-09-17 12:15:06 UTC 
Verified on :-

[root@dhcp201-113 ~]# rpm -qa|grep aeolus
aeolus-conductor-0.13.7-1.el6cf.noarch
aeolus-all-0.13.7-1.el6cf.noarch
aeolus-conductor-daemons-0.13.7-1.el6cf.noarch
aeolus-configure-2.8.6-1.el6cf.noarch
aeolus-conductor-doc-0.13.7-1.el6cf.noarch
rubygem-aeolus-cli-0.7.1-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch


Instance in create-failed or vanished state and are now color represented  with color "Red".History also seems to be in sync.
Comment 15 pushpesh sharma 2012-09-17 12:15:41 UTC 
Created attachment 613647 [details]
create_failed
Comment 16 pushpesh sharma 2012-09-17 12:16:19 UTC 
Created attachment 613648 [details]
history_fixed
Comment 18 errata-xmlrpc 2012-12-04 15:15:10 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-1516.html