Hide Forgot
Description of problem: =============================== Some confusion about realms comes from creating a realm under a provider. In the context of rhevm, you then add a "realm" mapping to a specific rhevm cluster at which point deploying images to this realm should work. If you go back to the provider and click on the realm tab, it shows a single realm is associated with the provider and clicking on it shows that the realm is mapped to a rhevm (cluster) "realm". The confusing part is that when viewing the realm, there is no mapping back to the provider. If a end user then adds one, deployments fail. See this screenshot, it shows a realm is associated with this provider
Created attachment 532593 [details] provider showing associated realm
Created attachment 532594 [details] realm not showing provider mapping
adding to ce-sprint-next
adding to ce-sprint
removing ce-sprint-next tracker
Created patch: https://fedorahosted.org/pipermail/aeolus-devel/2012-January/008091.html
I'm not sure this approach really makes sense. I think the real solution here is simply to not show the 'new realm' option when looking at a provider realm, since provider realms themselves come from the provider -- we can't touch them. "New Realm" is an admin action that creates a new conductor (i.e. front-end vs. back-end or provider) realm, and from here the admin can link the new realm to various back-end providers or provider realms. So linking from a back-end provider realm page to the 'new realm' creation form and automatically creating a new front-end conductor provider that maps to the provider you were looking at before seems confusing at best, or possibly just plain wrong. I think the right answer here is simply to not show 'new realm' when looking at a provider realm, since provider realms aren't editable by conductor users -- they're set by the provider.
Makes sense (now); updated patch which simply removes the button https://fedorahosted.org/pipermail/aeolus-devel/2012-January/008096.html
Pushed with commit: ed663f5e69ec1a4d034661b58afe8b57d14518f1
aeolus-conductor-0.8.0-8.el6.src.rpm 1f32b4f142e5efab976ff296090e761831305092
Created attachment 556967 [details] new_realm_removed
As mentioned in comment 9 , " New Realm " button is removed from Provider section Verified in rpm -qa|grep aeolus aeolus-conductor-0.8.0-9.el6.noarch aeolus-conductor-doc-0.8.0-9.el6.noarch rubygem-aeolus-image-0.3.0-3.el6.noarch rubygem-aeolus-cli-0.3.0-5.el6.noarch aeolus-all-0.8.0-9.el6.noarch aeolus-configure-2.5.0-6.el6.noarch aeolus-conductor-daemons-0.8.0-9.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-0583.html