Bug 796857

Summary: Application that is reporting at running reports error when stopping
Product: [Retired] CloudForms Cloud Engine Reporter: Steve Reichard <sreichar>
Component: deltacloud-coreAssignee: Michal Fojtik <mfojtik>
Status: CLOSED ERRATA QA Contact: Ronelle Landy <rlandy>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, deltacloud-maint, hbrock, rananda, scollier, ssachdev, whayutin
Target Milestone: rcKeywords: Triaged
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 20:33:05 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
video
none
mock.log
none
vsphere instance running
none
Stop selected question
none
stop request queued
none
vsphere instance stopped
none
delete selected question
none
vsphere instance gone from deployments list
none
stop invalid none

Description Steve Reichard 2012-02-23 19:09:12 UTC
Created attachment 565358 [details]
video

Description of problem:

Watch attached video.  You see I get an error trying to stop an Application that says it is running.  I then go and delete the running app.

When I check my vsphere client, the VM did not appear to be running or exist.




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


[root@cf-cloudforms9 imagefactory]# /pub/scripts/post_install_configuration_scripts/cf-versionsRed Hat Enterprise Linux Server release 6.2 (Santiago)
Linux cf-cloudforms9.cloud.lab.eng.bos.redhat.com 2.6.32-220.4.2.el6.x86_64 #1 SMP Mon Feb 6 16:39:28 EST 2012 x86_64 x86_64 x86_64 GNU/Linux
postgresql-8.4.9-1.el6_1.1.x86_64
mongodb-1.8.2-3.el6.x86_64
euca2ools-1.3.1-4.el6_0.noarch
ruby-1.8.7.352-5.el6_2.x86_64
rubygems-1.8.10-1.el6.noarch
deltacloud-core-0.5.0-5.el6.noarch
rubygem-deltacloud-client-0.5.0-2.el6.noarch
package libdeltacloud is not installed
hail-0.8-0.2.gf9c5b967.el6_0.x86_64
puppet-2.6.11-1.el6_1.noarch
aeolus-configure-2.5.0-14.el6.noarch
iwhd-1.2-3.el6.x86_64
imagefactory-1.0.0rc5-1.el6.noarch
aeolus-conductor-daemons-0.8.0-28.el6.noarch
aeolus-conductor-0.8.0-28.el6.noarch
[root@cf-cloudforms9 imagefactory]# 



How reproducible:

Unknown at this time

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 wes hayutin 2012-02-24 03:25:50 UTC
nuts and bolts of this bug.. once stop or delete are executed for a particular application or instance.. ignore further attempts to stop or delete

Comment 2 Hugh Brock 2012-02-24 15:33:28 UTC
Michal, is this a Deltacloud issue, or a deltacloud vs. deltacloud-client mismatch?

Comment 3 Michal Fojtik 2012-02-24 15:44:34 UTC
@Hugh: I need more details. 
@Steve: Do you have logs from /var/log/deltacloud-core/* ? Worth to check if there is no error.

Can someone explain me how to repro this bug using just Deltacloud? Like start an instance, then stop it?

Comment 4 Steve Reichard 2012-02-24 15:56:00 UTC
Created attachment 565633 [details]
mock.log

I've uploaded the mock.log

Comment 5 Ronelle Landy 2012-03-05 18:32:30 UTC
Created attachment 567707 [details]
vsphere instance running

Comment 6 Ronelle Landy 2012-03-05 18:33:20 UTC
Created attachment 567708 [details]
Stop selected question

Comment 7 Ronelle Landy 2012-03-05 18:34:39 UTC
Created attachment 567709 [details]
stop request queued

Comment 8 Ronelle Landy 2012-03-05 18:35:19 UTC
Created attachment 567710 [details]
vsphere instance stopped

Comment 9 Ronelle Landy 2012-03-05 18:36:12 UTC
Created attachment 567711 [details]
delete selected question

Comment 10 Ronelle Landy 2012-03-05 18:36:54 UTC
Created attachment 567712 [details]
vsphere instance gone from deployments list

Comment 11 Ronelle Landy 2012-03-05 18:53:19 UTC
Using the versions of deltacloud and conductor copied below, I was able to:

 -  build, push, and launch an image in vsphere
 - see conductor report that the instance is running (see screenshot: vsphere instance running)
 - stop the instance (see screenshots; Stop selected question, stop request queued, vsphere instance stopped)
 - then delete the stopped instance (see screenshot: delete selected question)
 - see that the instance was no longer reported in the deployments list (see srceenshot: vsphere instance gone from deployments list).

If I deployed a second instance, stopped it and then tried to stop it again (after conductor reported that my stop action had been queued), I got "stop is an invalid action." error  - see screenshot stop invalid

rpm -qa |grep aeolus
rubygem-aeolus-cli-0.3.0-12.el6.noarch
aeolus-conductor-0.8.0-39.el6.noarch
aeolus-conductor-daemons-0.8.0-39.el6.noarch
aeolus-configure-2.5.0-16.el6.noarch
aeolus-conductor-doc-0.8.0-39.el6.noarch
aeolus-all-0.8.0-39.el6.noarch
rubygem-aeolus-image-0.3.0-11.el6.noarch


rpm -qa |grep deltacloud
deltacloud-core-rhevm-0.5.0-5.el6.noarch
deltacloud-core-0.5.0-5.el6.noarch
rubygem-deltacloud-client-0.5.0-2.el6.noarch
deltacloud-core-ec2-0.5.0-5.el6.noarch
deltacloud-core-vsphere-0.5.0-5.el6.noarch

Comment 12 Ronelle Landy 2012-03-05 18:54:19 UTC
Created attachment 567716 [details]
stop invalid

Comment 13 Ronelle Landy 2012-03-05 19:21:00 UTC
The image used in the examples and screenshots included open-vm-tools:

 -  open-vm-tools-8.8.0-4.el6.x86_64.rpm       
 -  open-vm-toolsd-8.8.0-4.el6.x86_64.rpm  

Did the image used in the bug report include open-vm-tools and if so, what version?

If there was anything particular about that image, please leave those details.

Comment 14 Michal Fojtik 2012-03-06 13:36:53 UTC
The error message produced by Conductor is correct. You can't stop the 'stopping' instance once again in VSphere. The action is not valid. I would suggest to change the error message to something like: 'Instance is already being stopped' or something similar.

Personally I vote for closing this bug as NOTABUG and open a new bug for Conductor to deal with this error message.

Comment 16 Ronelle Landy 2012-03-06 16:05:20 UTC
Considering testing done and documented in Comment 11 and screenshots above, marking this BZ as VERIFIED for conductor version:

rubygem-aeolus-cli-0.3.0-12.el6.noarch
aeolus-conductor-0.8.0-39.el6.noarch
aeolus-conductor-daemons-0.8.0-39.el6.noarch
aeolus-configure-2.5.0-16.el6.noarch
aeolus-conductor-doc-0.8.0-39.el6.noarch
aeolus-all-0.8.0-39.el6.noarch
rubygem-aeolus-image-0.3.0-11.el6.noarch

Comment 17 errata-xmlrpc 2012-05-15 20:33:05 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-0587.html