Hide Forgot
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:
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
Michal, is this a Deltacloud issue, or a deltacloud vs. deltacloud-client mismatch?
@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?
Created attachment 565633 [details] mock.log I've uploaded the mock.log
Created attachment 567707 [details] vsphere instance running
Created attachment 567708 [details] Stop selected question
Created attachment 567709 [details] stop request queued
Created attachment 567710 [details] vsphere instance stopped
Created attachment 567711 [details] delete selected question
Created attachment 567712 [details] vsphere instance gone from deployments list
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
Created attachment 567716 [details] stop invalid
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.
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.
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
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