Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionLukáš Hellebrandt
2018-06-21 10:09:14 UTC
Created attachment 1453396[details]
foreman-tail
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(?).
Traceback attached.
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
How reproducible:
Deterministic
Steps to Reproduce:
1. Infrastructure -> Compute Resources -> Create
2. Select provider EC2, fill in some random values
3. Submit
Actual results:
Error message, traceback, resource not created
Expected results:
Error message about invalid values, nothing about oVirt.
Comment 11Lukáš Hellebrandt
2019-01-08 10:46:15 UTC
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.
https://access.redhat.com/errata/RHSA-2019:1222
Created attachment 1453396 [details] foreman-tail 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(?). Traceback attached. 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 How reproducible: Deterministic Steps to Reproduce: 1. Infrastructure -> Compute Resources -> Create 2. Select provider EC2, fill in some random values 3. Submit Actual results: Error message, traceback, resource not created Expected results: Error message about invalid values, nothing about oVirt.