Bug 1368234

Summary:	Request to restore diagnostic functionality critical to support (ie, current appliance settings) removed in the CFME 4.1
Product:	Red Hat CloudForms Management Engine	Reporter:	Thomas Hennessy <thenness>
Component:	Appliance	Assignee:	Jason Frey <jfrey>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Oleksii Tsuman <otsuman>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	5.6.0	CC:	abellott, benglish, cpelland, jdeubel, jfrey, jhardy, jocarter, myoder, obarenbo, simaishi, slukasik
Target Milestone:	GA	Keywords:	TestOnly, ZStream
Target Release:	5.7.0
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	5.7.0.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1370209 (view as bug list)		Environment:
Last Closed:	2017-01-11 20:18:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1370209

Description Thomas Hennessy 2016-08-18 18:29:16 UTC

Description of problem: there is no longer any file/repository/anything collected either by batch log collections or UI initiated log collections which provides any insight into the current (ie, at log collection) configuration of any appliance running CFME.


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


How reproducible:


Steps to Reproduce:
1. go to any running CFME 4.1 appliance and change any settings and save
2. collect logs from that appliance using the mechanism of your choice.
3. where in prior releases the current settings could be obtained from the /var/www/miq/vmdb/config/vmdb.yml.db file, or the vmdb.yml file, there is no longer any such repository. from a debugging perspective one no longer knows what should be running on any appliance. 
game.
set.
match.

if you don't know what the appliance should be doing (ie, is configured to do), how can you tell when it isn't working?

Actual results:


Expected results:


Additional info:

Comment 2 Šimon Lukašík 2016-08-22 13:17:05 UTC

The ondisk configuration was removed as part of config redesign https://github.com/ManageIQ/manageiq/pull/7432

Users can generate the config in rails console by running 

   File.write('/tmp/vmdb.yml', VMDB::Config.get_file)

Perhaps we can make a rake task for doing that. Or we can integrate with favorite support method to grab the configs. Do we have some blessed method?

Comment 3 Jason Frey 2016-08-23 18:02:51 UTC

Upstream PR created: https://github.com/ManageIQ/manageiq/pull/10705

Comment 4 CFME Bot 2016-08-24 11:05:52 UTC

New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/1510ac05e4c4e40f55d28c48ce8f9e743734664f

commit 1510ac05e4c4e40f55d28c48ce8f9e743734664f
Author:     Jason Frey <jfrey>
AuthorDate: Tue Aug 23 13:43:37 2016 -0400
Commit:     Jason Frey <jfrey>
CommitDate: Tue Aug 23 14:10:33 2016 -0400

    Restore the dumping of settings to the log dir for diagnostic purposes.
    
    This commit hooks the initialization and reload of the Settings constant
    to also dump it to the log directory.
    
    Previously, support used the config/vmdb.yml.db for diagnostic purposes
    as it contained the last known setttings for a particular appliance.
    Since this file no longer exists with the config revamp, and
    config/settings.yml and friends only contain the "template" values, there
    is no way for support to know what settings an appliance is configured
    with.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1368234

 lib/patches/config_patch.rb    |  6 +++---
 lib/vmdb/settings.rb           | 10 ++++++++++
 spec/lib/vmdb/settings_spec.rb | 38 ++++++++++++++++++++++++++++++++++++++
 3 files changed, 51 insertions(+), 3 deletions(-)

Comment 5 Šimon Lukašík 2016-08-25 07:03:19 UTC

Fixed upstream by Jason. Thanks.

Comment 7 Oleksii Tsuman 2016-10-06 14:37:29 UTC

verified in  5.7.0.3.20160927165516_075d0f3

Logs with configuration and other logs for debug(/var/www/miq/vmdb/*) is present in ftp after log collection. /var/www/miq/vmdb/config/vmdb.yml.db now called /var/www/miq/vmdb/config/settings.yml

In logs archive file located in config/settings.yml