Hide Forgot
Description of problem: ================================= kudos to jlaska for pointing this out... If I build/push a rhevm image, it will successfully deploy from the catalog entry page which prompts for specific realm. This is not the case if I try to deploy a second time using the catalog drop down on the Monitor tab pool. It throws an error which seems to indicate it has no clue which realm the image needs to go to Error: frontend: Unhandled exception or status code (Storage Domain cannot be accessed. ) Version-Release number of selected component (if applicable): aeolus-all-0.7.0-4.el6.noarch aeolus-conductor-0.7.0-4.el6.noarch aeolus-conductor-daemons-0.7.0-4.el6.noarch aeolus-conductor-doc-0.7.0-4.el6.noarch aeolus-configure-2.4.0-3.el6.noarch rubygem-aeolus-cli-0.2.0-3.el6.noarch rubygem-aeolus-image-0.2.0-1.el6.noarch Steps to Reproduce: 1. fresh install 2. configure for rhevm 3. add rhevm realm 4. aeolus-cli build/push rhevm image 5. create a catalog 6. add a catalog entry pointing at image id from step 4 7. launch image from catalog entry page 8. prompts for realm and name, point at rhevm realm 9. see image successfully launches 10. click on monitor tab 11. click catalog drop down to launch catalog 12. launch instance confirm page appears without prompting for realm 13. click launch, launch fails with above error
After *much* discussion, we are wondering if you have the latest Deltacloud version which maps RHEV-M datacenters to providers, rather than the entire rhev-m installation to a provider. This is a recent change to the RHEV-M deltacloud driver, but if it is in place and your providers are mapped correctly (i.e. you have a provider named "rhev-m-datacenter-xyz"), you should *never* hit a condition where you launch a deployable and it fails because the image is not available in rhev-m. Ping Michal Fojtik for more information on this. Thanks...
According to Hugh's comment switching this ticket back to QA - could you please retest if it's still broken?
Steps to Reproduce: 1. fresh install 2. configure for rhevm 3. add rhevm realm 4. aeolus-cli build/push rhevm image 5. create a catalog 6. add a catalog entry pointing at image id from step 4 7. launch image from catalog entry page 8. prompts for realm and name, point at rhevm realm 9. see image successfully launches 10. click on monitor tab 11. click catalog drop down to launch catalog 12. launch instance confirm page appears without prompting for realm 13. click launch, launch fails with above error In the above steps , error was coming because of absence of realm drop down while launching from catalog. Launch from catalog in Monitor page now prompts for realm. In the attached screenshot , realm field can be seen. ================================================== verified in rpm -qa|grep aeolus aeolus-conductor-daemons-0.8.0-0.20111222233342gitd98cb57.el6.noarch rubygem-aeolus-image-0.3.0-0.20111222173411gitc13b654.el6.noarch rubygem-aeolus-cli-0.3.0-0.20111222173356git3cd6277.el6.noarch aeolus-all-0.8.0-0.20111222233342gitd98cb57.el6.noarch aeolus-conductor-0.8.0-0.20111222233342gitd98cb57.el6.noarch aeolus-configure-2.5.0-0.20120104154940git196b80d.el6.noarch aeolus-conductor-doc-0.8.0-0.20111222233342gitd98cb57.el6.noarch
Created attachment 551126 [details] realm
bugs in verified or on_qa moving off tracker
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