Red Hat Bugzilla – Bug 805001
Deployment is created even if match is not found
Last modified: 2012-12-13 14:48:48 EST
Steps to Reproduce: 1. prepare a deployment launch (go to "/deployments/launch_time_params" but don't press "launch" button yet) 2. in another tab make some change which causes that deployment's instances won't be launchable on any provider account (for example make a provider unavailable, remove account from pool family, delete realm mapping or hwp...) 3. finish deployment launch from first step -> deployment is created, but all instances have state set to "new" (or "create_failed" depending if https://bugzilla.redhat.com/show_bug.cgi?id=796528 is applied) Deployment should not be created if a match is not found, a user should stay on "/deployments/launch_time_params" (and an error message should be displayed).
This BZ was fixed meantime, switching to QA for checking.
Testing the following rpms: >> rpm -qa |grep aeolus aeolus-configure-2.8.6-1.el6cf.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch rubygem-aeolus-cli-0.7.1-1.el6cf.noarch aeolus-conductor-0.13.8-1.el6cf.noarch aeolus-conductor-daemons-0.13.8-1.el6cf.noarch aeolus-conductor-doc-0.13.8-1.el6cf.noarch aeolus-all-0.13.8-1.el6cf.noarch It's a mixed result ... If I follow the reproduction steps above ... prepare the deployment lauch, on a second tab open to conductor, I remove the realm mapping, and then click the 'Launch' button (with , the Realm assigned to 'Auto-select'), the instance launches successfully and goes to a 'New' state. (see attached screenshot Auto-selectLaunch.png) If I follow the same set of steps but, instead if using 'Auto-select' for the realm, I select *any* realm listed in the Realm drop down, I get an error when clicking the 'Launch' button and conductor stays on the launch_time_params page. (see attached screenshot SpecifiedRealmLaunch.png)
Created attachment 615043 [details] Auto-select Realm
Created attachment 615044 [details] Launch with specifed realm selected
Behavior in both cases is correct - remove realm mapping was one of examples how to achieve "match not found error". When using "auto-select" realm mapping is not applied. In second case - if none of listed realms works it probably means that after removing the realm mapping there is not suitable provider account for which some realm mapping exists and where all deployment's images are pushed to.
So considering the explanation in Comment 5 above (thanks for that answer, Jan Provaznik), I'm marking this BZ as 'verified' for the case in which the Realm mapping is considered, conductor throws the 'Match not found' error and does not launch the instance.