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 1333558 - AWS Compute Resource Issue: Issue with the eu-central-1 zone (Frankfurt zone)
Summary: AWS Compute Resource Issue: Issue with the eu-central-1 zone (Frankfurt zone)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - EC2
Version: 6.1.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-05 20:50 UTC by Calvin Hartwell
Modified: 2019-09-26 18:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-22 15:29:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
compute resource aws issue screenshots (88.61 KB, image/png)
2016-05-05 20:50 UTC, Calvin Hartwell
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 8859 0 Normal New Foreman does not display case specific hostnames 2020-03-31 11:12:57 UTC

Description Calvin Hartwell 2016-05-05 20:50:54 UTC
Created attachment 1154386 [details]
compute resource aws issue screenshots

Description of problem:

Assume that user/customer already has an AWS account and can provision AWS virtual machines themselves through the AWS web gui. Now they want to setup satellite 6 to provision images in AWS. 

The issue is that they cannot provision at all to the Frankfurt Zone/Region (EU central AWS Datacenter). 

Assume the customer has created their user account, permissions and groups on AWS before hand and have the correct Access Key and Secret Access Key for the user. 

The customer then attempts to setup a compute resource for AWS. They can test the connection OK, but submitting the compute resource fails (see screenshots). 

If you pick another datacenter, such as eu-west-1, it will succeed and you can provision. However, if you attempt to change the Region on the compute resource from eu-west-1 to eu-central-1 it will succeed, but break the compute resource in numerous ways. 

For example, if you attempt to associate it to virtual machines, it will cause a 500 error. If you attempt to provision with this modified compute resource, the Virtual Machine tab will give a 500 error. 

* Please see the screenshots. 

* The issue may also be present in the upstream FOG library.  


Version-Release number of selected component (if applicable):

Satellite 6.1.7

How reproducible:

Tested on 6.1.7 but probably affects 6.1.8 and 6.2 beta


Steps to Reproduce:
1.Install and setup Satellite 6, setup AWS account (including user, groups, etc)
 
2. Setup compute resource for AWS, set zone to eu-central-1 (Frankfurt)

3. Attempt to save it, it breaks. 

Actual results:

Cannot provision AWS instances in Frankfurt/eu-central-1 zone (compute resource issue). 


Expected results:

AWS provisioning should work + Compute resource should work in eu-central-1 zone. 

Additional info:

Comment 2 Calvin Hartwell 2016-05-06 16:42:36 UTC
I can confirm this bug still exists in 6.1.8, I will also test it on 6.2.0 over the weekend. Apparently Cloudforms also had the SAME BUG, but they have already fixed it (they also use the Fog Library for managing AWS).

Comment 3 Brad Buckingham 2016-06-07 09:41:41 UTC
Hi Calvin, do you happen to have a reference to the Cloudforms bug that resolved the issue?  The version of fog may help as well.

Comment 6 Bryan Kearney 2016-07-26 18:58:36 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 7 Daniel Lobato Garcia 2017-11-22 15:25:31 UTC
Connecting redmine issue http://projects.theforeman.org/issues/8859 from this bug

Comment 8 Daniel Lobato Garcia 2017-11-22 15:29:19 UTC
Fixed via fog update in the attached issue


Note You need to log in before you can comment on or make changes to this bug.