Hide Forgot
Description of problem: recreate: 1. create a realm for vsphere 2. create a realm for rhevm 3. create a third realm that maps both providers 1. have a template built and pushed to both rhevm and vshpere 2. launch the deployable w/ the third realm.. in #3 results.. unhandled exception expected result either the image is launched w/ the provider w/ the higher priority or a proper error message why its not.. see screenshots
Created attachment 552194 [details] ss1
Created attachment 552195 [details] ss2
[root@qeblade32 yum.repos.d]# rpm -qa | grep aeolus aeolus-configure-2.5.0-3.el6.noarch rubygem-aeolus-image-0.3.0-2.el6.noarch aeolus-conductor-0.8.0-5.el6.noarch rubygem-aeolus-cli-0.3.0-3.el6.noarch aeolus-conductor-doc-0.8.0-5.el6.noarch aeolus-conductor-daemons-0.8.0-5.el6.noarch aeolus-all-0.8.0-5.el6.noarch
In this case.. vsphere had a priority=1, rhevm =2
adding to ce-sprint
removing ce-sprint-next tracker
Do you still have the logs available? The exception text looks like it points to a bug in the code ("undefined method 'empty?' for nil:NilClass") -- we have something that's nil that we expect to be an array -- the log would make it a lot easier to pinpoint. /var/log/aeolus-conductor/rails.log would be the likely place to see a corresponding stacktrace.
Also, it looks like this and 773410 are reporting essentially the same setup. The only difference is that here you're creating two additional realms (that you're not using at launch). With the latest comment on 773410 indicating that it's not repeatable, I'm wondering about this one as well.
will try to recreate
I was unable to reproduce the same. The instance came to running state (instance_running.jpg) Screen shot attached: 1. Image pushed to multiple providers.png 2. rhevm priority.png 3. vsphere priority.png 4. multi-provider cluster.png additional info: [root@ibm-ls21-04 ~]# rpm -qa | grep aeolus aeolus-conductor-daemons-0.8.0-35.el6.noarch aeolus-conductor-0.8.0-35.el6.noarch aeolus-configure-2.5.0-15.el6.noarch aeolus-conductor-doc-0.8.0-35.el6.noarch rubygem-aeolus-cli-0.3.0-10.el6.noarch aeolus-all-0.8.0-35.el6.noarch rubygem-aeolus-image-0.3.0-9.el6.noarch
Created attachment 565514 [details] imagepushed to multiple providers
Created attachment 565515 [details] rhevm priority
Created attachment 565517 [details] vsphere priority
Created attachment 565519 [details] multi-provider cluster
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-0583.html