+++ This bug was initially created as a clone of Bug #1187233 +++ Description of problem: While installing CFME I wanted to set a DB region (option 7 on CLI config menu), minor typo: "Enter the Enter a database region number : : " Attaching print screen One more thing (newbie to CFME) going over CLI figured I should change region. Tried to change but it yelled back at me no database... So I figured it's my fault as I hadn't setup a DB yet. IMHO if this should be done once a DB is created I'd switch CLI menu order first create DB (#8->7) only then change region (#7->8). Version-Release number of selected component (if applicable): 5.3.1.10 Appliance over RHOS 6 How reproducible: Not sure, BTW if I waited for cli timeout and selected 7 again it happens over and over same typo, not a fluke. Steps to Reproduce: 1. On CLI selected #7 for Setup Database Region, typo on screen 2. 3. Actual results: "Enter the Enter a database region number : : " Expected results: "Enter a database region number : " Additional info: --- Additional comment from Keenan Brock on 2015-01-29 13:19:54 EST --- @tsherfi thanks submitted, hope you'll see it get merged very soon --- Additional comment from CFME Bot on 2015-01-29 16:25:52 EST --- New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/0d7e3fd4317100f4956127d68092788f998dad82 commit 0d7e3fd4317100f4956127d68092788f998dad82 Author: Keenan Brock <kbrock> AuthorDate: Thu Jan 29 13:15:38 2015 -0500 Commit: Keenan Brock <kbrock> CommitDate: Thu Jan 29 13:17:19 2015 -0500 Fix Typo for database region number https://bugzilla.redhat.com/show_bug.cgi?id=1187233 lib/appliance_console.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- Additional comment from Keenan Brock on 2015-01-30 10:58:48 EST --- Posted to 5.4
Posted to 5.3.z
Typo removed in "Setup Database Region" CLI menu.screenshot attached. verified: 5.3.3.1.20150210145146_14d1c48
Created attachment 990355 [details] typo removed
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. https://rhn.redhat.com/errata/RHBA-2015-0261.html