Bug 799272
| Summary: | Stopping a stopped deployment says : "You must select one or more applications. " | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Shveta <ssachdev> | ||||||||||
| Component: | aeolus-conductor | Assignee: | Tomas Hrcka <thrcka> | ||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | pushpesh sharma <psharma> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 1.0.0 | CC: | akarol, bbandari, deltacloud-maint, hbrock, psharma, ssachdev | ||||||||||
| 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-08-30 17:14:44 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
It shouldn't be possible to trigger the stop action by clicking on a stopped application. I am not able to replicate this bug. From which view you have invoked the stop action? If from table view did you select any application? Noticed it now , Actual bug is this : 1) Try to launch an instance whose name is already taken. 2) It shows validation while launching "Name already taken" 3) But at the same time a stopped instance gets listed in the monitor page In the attached screenshot, observe more than one instance with name RHEL6-2-configserver-ec2. Stop action on such instances shows message "you must select one or more instances" Created attachment 567646 [details]
duplicate names
I am not able to replicate this bug anymore. Set to modified. need QE to try and reproduce. Behaviour described in the steps to reproduce as well as in comment#3 is not observed in the latest build.so marking this as verified as it is not reproducible in the latest build. PFA for the screen shots [root@dhcp201-169 ~]# rpm -qa|grep aeolus aeolus-configure-2.5.2-1.el6.noarch aeolus-conductor-0.8.7-1.el6.noarch rubygem-aeolus-cli-0.3.1-1.el6.noarch aeolus-conductor-doc-0.8.7-1.el6.noarch aeolus-all-0.8.7-1.el6.noarch aeolus-conductor-daemons-0.8.7-1.el6.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch Created attachment 577970 [details]
stopping stopped instance verified
Created attachment 577971 [details]
name already taken verified
|
Created attachment 567032 [details] stop_instance Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Launched few applications, some of them show stopped status 2. stop action on "Stopped" application says , "You must select one or more applications. " 3. Actual results: Expected results: Additional info: rpm -qa|grep aeolus aeolus-conductor-doc-0.8.0-39.el6.noarch rubygem-aeolus-cli-0.3.0-12.el6.noarch aeolus-all-0.8.0-39.el6.noarch aeolus-conductor-0.8.0-39.el6.noarch rubygem-aeolus-image-0.3.0-11.el6.noarch aeolus-configure-2.5.0-16.el6.noarch aeolus-conductor-daemons-0.8.0-39.el6.noarch