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.
Bug 1511216 - Satellite is not able to connect to AWS zone us-east-2
Summary: Satellite is not able to connect to AWS zone us-east-2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - EC2
Version: 6.2.12
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Sanket Jagtap
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-08 22:43 UTC by Brian Coca
Modified: 2021-06-10 13:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:42:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 17781 0 'Normal' 'Closed' '"us-east-2" (Ohio region) not in foreman-ec2 compute resource' 2019-12-04 16:47:47 UTC

Description Brian Coca 2017-11-08 22:43:02 UTC 
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
Comment 2 Daniel Lobato Garcia 2017-11-13 08:18:46 UTC 
Connecting redmine issue http://projects.theforeman.org/issues/17781 from this bug
Comment 3 Daniel Lobato Garcia 2017-11-13 08:19:57 UTC 
Hooked up to upstream issue & moved to POST.
Comment 4 Sanket Jagtap 2017-12-07 11:16:04 UTC 
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
Comment 5 Bryan Kearney 2018-02-21 16:40:21 UTC 
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
Comment 6 Bryan Kearney 2018-02-21 16:42:43 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.