Description of problem: Could not create AzureRM compute resource with error: "Oops, we're sorry but something went wrong uninitialized constant ForemanAzureRM::AzureSDKAdapter". This was due to a minor "autoloading" functionality used, that works fine in development but fails in production. Hence, raised a PR to replace it with "eagerloading". How reproducible: Steps to Reproduce: 1.Go to compute resources 2.Create Compute Resource 3.Fill in azurerm credentials required. 4.Click on Submit. Actual results: "Oops, we're sorry but something went wrong uninitialized constant ForemanAzureRM::AzureSDKAdapter" Expected results: Compute Resource created successfully. Additional info: The PR has been merged in upstream. https://github.com/theforeman/foreman_azure_rm/pull/46
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28355 has been resolved.
ON_QA Verified @Satellite 6.7.0 snap 4.0
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-2020:1454