Description of problem: After performing the configuration in the item "8) Configure Database > 1) Create Internal Database". The database is created correctly but after this the CloudForms is not initialized correctly. Apparently because the region was not created. In version 4.1 at the time of creation of the database the region was also created and the CloudForms initialized. Workaround: In order for the CloudForms to be properly initialized, it is necessary to reinitiate the Operating System. After this go to "appliance_console > 8) Configure Database > 4) Reset Configured Database. At this point the region is created correctly and the database is erased. Then use option "19) Start EVM Server Process" so that CloudForms is initialized correctly. Version-Release number of selected component (if applicable): cfme-rhos-5.7.1.3-1.x86_64.qcow2 ( CFME 4.2) How reproducible: Go to the appliance_console > 8) Configure Database > 1) Create Internal Database" after this in the main menu choose 19) Start EVM Server Process. The CloudForms is not initialized correctly. Actual results: CloudForms initialization error. Expected results: Proper start of CloudForms.
I cannot get this reproduced with cfme-5.7.2.1-1.el7cf or cfme-5.8.0.10-beta1.1.nightly.1.el7cf I'll take a look at your specific 5.7.1.3-1 Anyway this doesn't seem to be a problem in later versions. So it perhaps doesn't need blocker+ flag.
Is it possible that this was filed on a version without the improved prompt (https://github.com/ManageIQ/manageiq-gems-pending/pull/27)?
I would venture to say that we can close this as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1412742 either way.
Nod. I think we can definitely close this one. Assuming the original reproducer involved configuring db and then resetting with dedicated database this is clear duplicate. Thanks. *** This bug has been marked as a duplicate of bug 1412742 ***
*** Bug 1435341 has been marked as a duplicate of this bug. ***