Created attachment 1453396 [details]
Description of problem:
When creating a compute resource of type EC2 (with some made up values), I click submit and get the error message:
Oops, we're sorry but something went wrong uninitialized constant ComputeResourcesController::OVIRT Did you mean? Ovirt
However, EC2 shouldn't have anything to do with oVirt(?).
This is a regression against 6.3.
The resource is not created after this.
Version-Release number of selected component (if applicable):
Sat 6.4, tested with snap 8
Steps to Reproduce:
1. Infrastructure -> Compute Resources -> Create
2. Select provider EC2, fill in some random values
Error message, traceback, resource not created
Error message about invalid values, nothing about oVirt.
Created redmine issue https://projects.theforeman.org/issues/24053 from this bug
Upstream bug assigned to email@example.com
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/24053 has been resolved.
Verified with EC2 and OpenStack on Sat 6.5 snap 10.
Loading regions with incorrect credentials now results in a pop up box saying "Unable to save: AuthFailure => AWS was not able to validate the provided access credentials".
Submitting with incorrect credentials now results in traceback: "Fog::Compute::AWS::Error: AuthFailure => AWS was not able to validate the provided access credentials" and a pop up box saying "Error while trying to create resource: AuthFailure => AWS was not able to validate the provided access credentials".
The same with correct credentials completes the action successfully.
Similarly for OpenStack.
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.