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:
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?
Upstream PR created: https://github.com/ManageIQ/manageiq/pull/10705
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(-)
Fixed upstream by Jason. Thanks.
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