Description of problem: recreate: 1. create catalog 2. create catalog entry 3. navigate to catalog entry list @ https://hp-bl480c-01.rhts.eng.bos.redhat.com/conductor/catalogs/1 Second column lists deployment URL, 1. click on deployment URL .. get redirected to deployment details IMHO the deployment name should redirect to details, URL should redirect to the deployment xml 2. click on deployment details click on URL link there.. properties page is reopened, same if you open in new tab. If you open the url by cutting and pasting the deployment URL is displayed. [root@hp-bl480c-01 ce]# rpm -qa | grep aeolus aeolus-conductor-devel-0.5.0-0.20111017201942git2810f1b.fc15.noarch aeolus-conductor-doc-0.5.0-0.20111017201942git2810f1b.fc15.noarch rubygem-aeolus-cli-0.1.0-3.20111003133323git9451323.fc15.noarch aeolus-conductor-0.5.0-0.20111017201942git2810f1b.fc15.noarch aeolus-conductor-daemons-0.5.0-0.20111017201942git2810f1b.fc15.noarch aeolus-configure-2.2.0-1.20111007151942git26136f2.fc15.noarch aeolus-all-0.5.0-0.20111017201942git2810f1b.fc15.noarch rubygem-aeolus-image-0.1.0-3.20111003170706git8f23238.fc15.noarch
This is caused by a missing /usr/share/aeolus-conductor/app/util/deployable-rng.xml. The aeolus-conductor-in.spec file needs to be updated to install this file.
f5c4fc61d3d5ef04d9c5a950c29181f9f7589c6f conductor git repo
Deployment URL's is redirected to template xml. when clicked on catalog entry name,property page is displayed. clicking on URL link in property page is redirected to deployable xml. [root@nec-em11 ~]# rpm -qa | grep aeolus aeolus-conductor-doc-0.5.0-0.20111018184108gitf5c4fc6.fc15.noarch aeolus-all-0.5.0-0.20111018184108gitf5c4fc6.fc15.noarch rubygem-aeolus-cli-0.1.0-3.20111003133323git9451323.fc15.noarch aeolus-configure-2.2.0-1.20111007151942git26136f2.fc15.noarch aeolus-conductor-0.5.0-0.20111018184108gitf5c4fc6.fc15.noarch aeolus-conductor-daemons-0.5.0-0.20111018184108gitf5c4fc6.fc15.noarch rubygem-aeolus-image-0.1.0-3.20111003170706git8f23238.fc15.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