Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1431815 - appliance_console_cli allows configuration that is not supported
appliance_console_cli allows configuration that is not supported
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance (Show other bugs)
5.6.0
Unspecified Unspecified
medium Severity medium
: GA
: 5.9.0
Assigned To: Gregg Tanzillo
luke couzens
black
:
Depends On:
Blocks: 1542093
  Show dependency treegraph
 
Reported: 2017-03-13 15:38 EDT by Thom Carlin
Modified: 2018-03-01 08:11 EST (History)
8 users (show)

See Also:
Fixed In Version: 5.9.0.3
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-03-01 08:11:02 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:0380 normal SHIPPED_LIVE Moderate: Red Hat CloudForms security, bug fix, and enhancement update 2018-03-01 13:37:12 EST

  None (edit)
Description Thom Carlin 2017-03-13 15:38:13 EDT
Description of problem:

QCI 1.1 is passing --internal without --dbdisk.  This should not be allowed since it caused problems with miq_postgres_upgrade.sh

Version-Release number of selected component (if applicable):

5.6

How reproducible:

100%

Steps to Reproduce:
1. Setup appliance using appliance_console_cli with --internal but *not* --dbdisk
2. appliance_console
3. Examine output

Actual results:

Local Database Server:   not initialized
CFME Server:             running
CFME Database:           localhost
Database/Region:         vmdb_production / 1

Expected results:

Error message during appliance_console_cli

Additional info:

https://bugzilla.redhat.com/show_bug.cgi?id=1387672#c4 stated we shouldn't allow this configuration
Comment 2 Eric Lavarde 2017-09-28 03:40:07 EDT
I'm seeing a similar behaviour with -p: the DB password is actually mandatory to fulfil the configuration but the CLI doesn't check the parameter at the beginning and fails with an obscure error during the configuration (at a stage where recovering isn't possible anymore).

In summary, the tool should properly validate all parameters before starting any modification to the system.
Comment 6 CFME Bot 2017-10-13 15:28:46 EDT
New commit detected on ManageIQ/manageiq-gems-pending/master:
https://github.com/ManageIQ/manageiq-gems-pending/commit/7ae42c0221436d03a94620ce58cfabc97363f797

commit 7ae42c0221436d03a94620ce58cfabc97363f797
Author:     Bo Yao <icerove@gmail.com>
AuthorDate: Wed Oct 4 15:10:16 2017 -0400
Commit:     Bo Yao <icerove@gmail.com>
CommitDate: Fri Oct 6 11:34:51 2017 -0400

    check and only allow to create database in a mount point
    https://bugzilla.redhat.com/show_bug.cgi?id=1431815
    https://bugzilla.redhat.com/show_bug.cgi?id=1425153

 .../appliance_console/internal_database_configuration.rb    | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)
Comment 7 CFME Bot 2017-10-13 15:48:09 EDT
New commit detected on ManageIQ/manageiq-gems-pending/master:
https://github.com/ManageIQ/manageiq-gems-pending/commit/b74866760004f4b2b30dd75620192ed3e91e2014

commit b74866760004f4b2b30dd75620192ed3e91e2014
Author:     Bo Yao <icerove@gmail.com>
AuthorDate: Wed Oct 4 16:52:21 2017 -0400
Commit:     Bo Yao <icerove@gmail.com>
CommitDate: Fri Oct 13 15:38:58 2017 -0400

    must give password to set db in cli
    https://bugzilla.redhat.com/show_bug.cgi?id=1431815

 lib/gems/pending/appliance_console/cli.rb | 5 +++++
 1 file changed, 5 insertions(+)
Comment 8 luke couzens 2017-10-24 10:35:55 EDT
Verified in 5.9.0.3
Comment 12 errata-xmlrpc 2018-03-01 08:11:02 EST
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://access.redhat.com/errata/RHSA-2018:0380

Note You need to log in before you can comment on or make changes to this bug.