Bug 1625377

Summary: appliance_console not logging to appliance_console.log
Product: Red Hat CloudForms Management Engine Reporter: Tasos Papaioannou <tpapaioa>
Component: ApplianceAssignee: Brandon Dunne <bdunne>
Status: CLOSED CURRENTRELEASE QA Contact: Devidas Gaikwad <dgaikwad>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.9.2CC: abellott, bdunne, dmetzger, mshriver, nansari, obarenbo, simaishi, yrudman
Target Milestone: GAKeywords: TestOnly, ZStream
Target Release: 5.11.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: 5.11.0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1678340 (view as bug list) Environment:
Last Closed: 2019-12-13 15:01:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1678340    

Description Tasos Papaioannou 2018-09-04 19:06:48 UTC 
Description of problem:

If an error occurs while configuring the database via appliance_console, the user is told to 'See /var/www/miq/vmdb/log/appliance_console.log for details.', but nothing gets logged to that file.

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

Verified on 5.9.2, 5.9.3, 5.9.4, and 5.10.0.
On 5.8.5, nothing gets logged to appliance_console.log either, but the 'See /var/www/miq/vmdb/log/appliance_console.log for details.' message isn't presented.

How reproducible:

100%

Steps to Reproduce:

For example, select "5) Configure Database" > "3) Join Region in External Database", then specify an invalid database name:

****
Activating the configuration using the following settings...
Host:     XXX.XXX.XXX.XXX
Username: root
Database: bad_db
Port:     5432

Validated failed with error - FATAL:  database "bad_db" does not exist
.
See /var/www/miq/vmdb/log/appliance_console.log for details.

Press any key to continue.
Configuration failed

Press any key to continue.
****

Actual results:

Nothing is logged to /var/www/miq/vmdb/log/appliance_console.log (the file might not even exist at this point).

Expected results:

Error information gets logged to appliance_console.log.

Additional info:
Comment 2 CFME Bot 2018-12-12 18:53:48 UTC 
https://github.com/ManageIQ/manageiq-appliance_console/pull/76
Comment 3 CFME Bot 2018-12-12 19:10:01 UTC 
New commit detected on ManageIQ/manageiq-appliance_console/master:

https://github.com/ManageIQ/manageiq-appliance_console/commit/5b7c706116e67aea4b80c227b6a4ee04adf036bf
commit 5b7c706116e67aea4b80c227b6a4ee04adf036bf
Author:     Yuri Rudman <yrudman>
AuthorDate: Wed Dec 12 11:53:48 2018 -0500
Commit:     Yuri Rudman <yrudman>
CommitDate: Wed Dec 12 11:53:48 2018 -0500

    fix logging when configure db
    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1625377

 lib/manageiq/appliance_console/database_configuration.rb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Comment 4 Yuri Rudman 2019-02-07 15:59:10 UTC 
changing BZ status back to "ON_DEV" since latest manageiq-appliance_console gem was not released yet
Comment 6 Brandon Dunne 2019-02-14 20:13:19 UTC 
https://github.com/ManageIQ/manageiq-appliance/pull/227
Comment 7 CFME Bot 2019-02-18 14:46:30 UTC 
New commit detected on ManageIQ/manageiq-appliance/master:

https://github.com/ManageIQ/manageiq-appliance/commit/8131d15d1a76dca313473340e1e3f1dc764cd61e
commit 8131d15d1a76dca313473340e1e3f1dc764cd61e
Author:     Brandon Dunne <brandondunne>
AuthorDate: Thu Feb 14 15:00:59 2019 -0500
Commit:     Brandon Dunne <brandondunne>
CommitDate: Thu Feb 14 15:00:59 2019 -0500

    Update to a minimum of manageiq-appliance_console v3.3.1

    https://bugzilla.redhat.com/show_bug.cgi?id=1648986
    https://bugzilla.redhat.com/show_bug.cgi?id=1625377

 manageiq-appliance-dependencies.rb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Comment 10 Satyajit Bulage 2019-05-08 10:47:25 UTC 
Verified Version: 5.11.0.3.20190507174347_a77bd90