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.
I'm testing the EC2 Compute Resources in Satellite 6.2. However, I try to add my EC2 account details and click Load Regions. It fails to load the regions and returns the following error:
"AuthFailure => AWS was not able to validate the provided access credentials"
production.log shows the following:
2016-04-29 05:07:59 [app] [I] Started PUT "/compute_resources/test_connection" for 192.168.125.1 at 2016-04-29 05:07:59 +1000
2016-04-29 05:07:59 [app] [I] Processing by ComputeResourcesController#test_connection as */*
2016-04-29 05:07:59 [app] [I] Parameters: {"utf8"=>"✓", "authenticity_token"=>"tSKnqYsuUAcjsA5Zz7+7A6oGaIbDc/nLHnm50Zt/iYU=", "compute_resource"=>{"name"=>"EC2", "provider"=>"EC2", "description"=>"", "user"=>"AKIAIXCHKTHSDRW7JFWA", "password"=>"[FILTERED]", "location_ids"=>[""], "organization_ids"=>["", "3"]}, "fakepassword"=>"[FILTERED]", "cr_id"=>"null"}
2016-04-29 05:07:59 [app] [I] CR_ID IS null
2016-04-29 05:08:10 [app] [I] Rendered compute_resources/form/_ec2.html.erb (5482.1ms)
2016-04-29 05:08:10 [app] [I] Rendered taxonomies/_loc_org_tabs.html.erb (29.8ms)
2016-04-29 05:08:10 [app] [I] Rendered compute_resources/_form.html.erb (5531.8ms)
2016-04-29 05:08:10 [app] [I] Completed 200 OK in 11318ms (Views: 5529.0ms | ActiveRecord: 17.4ms)
Version-Release number of selected component (if applicable):
foreman-ec2.noarch.1.11.0.17-1.el7sat
How reproducible:
Always
Steps to Reproduce:
1. Add EC2 provider in UI
2. Click "Load Regions"
Actual results:
Error appears
Expected results:
No error appears, region list should appear
Additional info:
foreman-ec2 didn't seem to be install with a default Satellite 6.2 Beta installation, so I installed this package separately.
I should also note, I tested out my AWS key pair with the aws command line tool and they seem to work fine. I've tried multiple times re-entering my AWS key pair and it doesn't seem to work. I'm pretty sure this isn't a PEBKAC error.
Found out what was causing it. My Satellite Server's time was off by two hours, which screwed up the authentication. After installing and configuring ntpd, the authentication worked!
I'm testing the EC2 Compute Resources in Satellite 6.2. However, I try to add my EC2 account details and click Load Regions. It fails to load the regions and returns the following error: "AuthFailure => AWS was not able to validate the provided access credentials" production.log shows the following: 2016-04-29 05:07:59 [app] [I] Started PUT "/compute_resources/test_connection" for 192.168.125.1 at 2016-04-29 05:07:59 +1000 2016-04-29 05:07:59 [app] [I] Processing by ComputeResourcesController#test_connection as */* 2016-04-29 05:07:59 [app] [I] Parameters: {"utf8"=>"✓", "authenticity_token"=>"tSKnqYsuUAcjsA5Zz7+7A6oGaIbDc/nLHnm50Zt/iYU=", "compute_resource"=>{"name"=>"EC2", "provider"=>"EC2", "description"=>"", "user"=>"AKIAIXCHKTHSDRW7JFWA", "password"=>"[FILTERED]", "location_ids"=>[""], "organization_ids"=>["", "3"]}, "fakepassword"=>"[FILTERED]", "cr_id"=>"null"} 2016-04-29 05:07:59 [app] [I] CR_ID IS null 2016-04-29 05:08:10 [app] [I] Rendered compute_resources/form/_ec2.html.erb (5482.1ms) 2016-04-29 05:08:10 [app] [I] Rendered taxonomies/_loc_org_tabs.html.erb (29.8ms) 2016-04-29 05:08:10 [app] [I] Rendered compute_resources/_form.html.erb (5531.8ms) 2016-04-29 05:08:10 [app] [I] Completed 200 OK in 11318ms (Views: 5529.0ms | ActiveRecord: 17.4ms) Version-Release number of selected component (if applicable): foreman-ec2.noarch.1.11.0.17-1.el7sat How reproducible: Always Steps to Reproduce: 1. Add EC2 provider in UI 2. Click "Load Regions" Actual results: Error appears Expected results: No error appears, region list should appear Additional info: foreman-ec2 didn't seem to be install with a default Satellite 6.2 Beta installation, so I installed this package separately.