Description of problem: Satellite is not able to connect to AWS zone us-east-2 It fails with: Oops, we're sorry but something went wrong Unknown region "us-east-2" Version-Release number of selected component (if applicable): satellite-6.2.12-5.0.el6sat.noarch More specifically: tfm-rubygem-fog-aws-0.7.4-3.el6sat.noarch This issue was resolved upstream: http://projects.theforeman.org/issues/17781 https://github.com/theforeman/foreman-packaging/pull/1461 How reproducible: 100% Steps to Reproduce: 1.Create a key that is able to access all zones 2.Add us-east-2 zone as a compute resource Actual results: Oops, we're sorry but something went wrong Unknown region "us-east-2" Expected results: Adding us-east-2 as a compute resource Additional info: This issue was resolved upstream: http://projects.theforeman.org/issues/17781 https://github.com/theforeman/foreman-packaging/pull/1461
Connecting redmine issue http://projects.theforeman.org/issues/17781 from this bug
Hooked up to upstream issue & moved to POST.
Build:Satellite 6.3.0 snap 27 hammer> compute-resource list ---|---------|--------- ID | NAME | PROVIDER ---|---------|--------- 2 | aws | EC2 1 | libvirt | Libvirt ---|---------|--------- hammer> compute-resource info --id 2 Id: 2 Name: aws Provider: EC2 Url: us-east-2 Description: User: Locations: Default Location Organizations: Default Organization Created at: 2017/12/07 11:11:09 Updated at: 2017/12/07 11:11:09 Region: us-east-2 Also test connection returned positve
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-2018:0336