Created attachment 1181193 [details] Stack Trace from fix_auth.rb Description of problem: Importing a large database that requires running the fix_auth script results in a stack trace. Version-Release number of selected component (if applicable): 5.5.5.2 How reproducible: Always on 5.5.5.2 with the tested database Steps to Reproduce: 1. Deploy new 5.5.5.2 appliance 2. Have database deployed 3. Drop deployed database 4. Import new Database 5. Attempt "bundle exec tools/fix_auth.rb --v2 --invalid bogus" 6. View stack trace Actual results: Stack traces in 5s Expected results: Additional info: Workaround is the manually edit tools/fix_auth.rb and comment out line: require File.expand_path('../../config/environment', __FILE__)
This was introduced by https://github.com/ManageIQ/manageiq/pull/8113 to work around a settings bug.
A few scattered thoughts: - the initializer needs to be removed - YAML.load_safe only loads primitives and may help - def const_missing may be a good bet as well - May want to do something similar to MiqQueue.put_or_update which has a development/test only check to block storing objects in db.
Keenan, Is this fixed by https://github.com/ManageIQ/manageiq/commit/6ae22f7ee018f21be20a3aa93b71145b87fb172e#diff-07d6ea8b9ebccc3637e4a0f31d359d48 ?
Nick, Yes. This fixes the bug and has been marked darga/yes. has not been back patched yet - so we can't mark as post
But this is only 5.7, not 5.6z. I'll mark this as POST with PR https://github.com/ManageIQ/manageiq/pull/10166 Then if we get a clone for 5.6.z we can mark that PR as darga/yes.
Verified fixed in 5.7.0.7 - 5.7.0.7-beta1.20161025153249_9376fbd.
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-2017-0012.html