Description of problem: This bug is intended to track updating the installation guide to document the new required argument. The existing (1.0) installation guide [1] documents the following Cloud Engine configuration procedure in section "3.2. Configuring CloudForms Cloud Engine" > # aeolus-conductor As of CloudEngine 1.0.1, the admin user account will not be created unless the following arguments are supplied. > # aeolus-conductor -p admin [1] https://docs.redhat.com/docs/en-US/CloudForms/1.0/html/Installation_Guide/sect-Installation_Guide-Configuring_Cloudforms_Cloud_Engine.html Version-Release number of selected component (if applicable): * aeolus-configure-2.5.7-1.el6_3.noarch * aeolus-conductor-0.8.28-1.el6_3.noarch
Edited the section with "admin" user information. Link: http://documentation-stage.bne.redhat.com/docs/en-US/CloudForms/1.0/html-single/Installation_Guide/#sect-Installation_Guide-Configuring_Cloudforms_Cloud_Engine Regards, Shikha
This bug now depends on BZ# 824526 due to the fact that the admin profile has been removed. From the upstream: The default admin user will be created as part of the conductor manifest, and this will be indicated by creation of a file in /var/lib/aeolus-configure. This will ensure the admin user does not get created by configure after multiple configure invocations. The expectation is for administrative users to be managed via the web UI (or API), not via configure.
Have reverted this back to the original text and have brewed a new version of the book (CloudForms-Installation_Guide-1.0-web-en-US-1-53.el6eng). Since nothing has changed nor requires fixing, closing this with a NOTABUG.