Bug 1511216
Summary: | Satellite is not able to connect to AWS zone us-east-2 | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Brian Coca <brcoca> |
Component: | Compute Resources - EC2 | Assignee: | satellite6-bugs <satellite6-bugs> |
Status: | CLOSED ERRATA | QA Contact: | Sanket Jagtap <sjagtap> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.2.12 | CC: | bbuckingham, dlobatog, ehelms, pcreech, sjagtap |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-02-21 16:42:43 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Brian Coca
2017-11-08 22:43:02 UTC
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 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 |