Hide Forgot
Description of problem: ============================= Seems like we should create a default catalog for the user just like we have a default pool. From my understanding, a catalog is basically a folder. Why not have a default one to begin with? If the user creates a new image through the web ui new image "wizard" which has them make a deployable, the process de-rails if they haven't created a catalog. Seems like a default would only serve to help users get started.
Propose that we add this via either aeolus-configure or seeding the database.
*** Bug 773051 has been marked as a duplicate of this bug. ***
needs to be hooked into the default pool
Patch posted to list
Pushed commit ae989f63458fee07ff8c5747d572d7f75afd4fd0
ae989f6 in aeolus-conductor-0.8.0-12
default catalog added. verified on: rpm -qa | grep aeolus aeolus-conductor-0.8.0-16.el6.noarch rubygem-aeolus-cli-0.3.0-7.el6.noarch aeolus-conductor-daemons-0.8.0-16.el6.noarch aeolus-conductor-doc-0.8.0-16.el6.noarch aeolus-all-0.8.0-16.el6.noarch aeolus-configure-2.5.0-11.el6.noarch rubygem-aeolus-image-0.3.0-6.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