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.

Bug 1678339

Summary: Provisioning with AWS Compute fails for eu-north-1 region with errors
Product: Red Hat Satellite Reporter: Mihir Lele <mlele>
Component: Compute Resources - EC2Assignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: high Docs Contact:
Priority: urgent    
Version: 6.4CC: ajoseph, bkearney, dvoss, egolov, hmore, mhulan, mlele, mmccune, rakumar, rsunog
Target Milestone: 6.5.2Keywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: tfm-rubygem-fog-aws-1.3.0.2-1 Doc Type: Known Issue
Doc Text:
This region does not exist in the fog library. We will deliver this fix in a future release.
 Story Points: ---
Clone Of:
: 1717699 (view as bug list) Environment:
Last Closed: 2019-08-06 14:37:33 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:
Attachments:
Description Flags
Satellite 6.4 Hotfix RPM none

Description Mihir Lele 2019-02-18 14:48:53 UTC 
Description of problem:

Provisioning with AWS Compute fails  for  eu-north-1 region with error:

=======
Unable to save
Failed to create a compute aws+cr2 (eu-north-1-EC2) instance bill-angert.example.com: Unsupported => The requested configuration is currently not supported. Please check the documentation for supported configurations.
=======

Production logs:

==============

2019-02-18T04:25:36 [I|app|039de] Completed 200 OK in 17ms (Views: 2.9ms | ActiveRecord: 2.6ms)
2019-02-18T04:25:37 [W|app|35283] Unhandled EC2 error
Fog::Compute::AWS::Error: Unsupported => The requested configuration is currently not supported. Please check the documentation for supported configurations.
/opt/theforeman/tfm/root/usr/share/gems/gems/excon-0.58.0/lib/excon/middlewares/expects.rb:7:in `response_call'
/opt/theforeman/tfm/root/usr/share/gems/gems/excon-0.58.0/lib/excon/middlewares/response_parser.rb:9:in `response_call'
/opt/theforeman/tfm/root/usr/share/gems/gems/docker-api-1.28.0/lib/excon/middlewares/hijack.rb:45:in `response_call'
/opt/theforeman/tfm/root/usr/share/gems/gems/excon-0.58.0/lib/excon/connection.rb:389:in `response'
/opt/theforeman/tfm/root/usr/share/gems/gems/excon-0.58.0/lib/excon/connection.rb:253:in `request'
/usr/share/foreman/lib/foreman/http_proxy/excon_connection_extension.rb:13:in `request'
/opt/theforeman/tfm/root/usr/share/gems/gems/fog-xml-0.1.2/lib/fog/xml/sax_parser_connection.rb:35:in `request'
/opt/theforeman/tfm/root/usr/share/gems/gems/fog-xml-0.1.2/lib/fog/xml/connection.rb:7:in `request'
/opt/theforeman/tfm/root/usr/share/gems/gems/fog-aws-1.3.0/lib/fog/aws/compute.rb:541:in `_request'
/opt/theforeman/tfm/root/usr/share/gems/gems/fog-aws-1.3.0/lib/fog/aws/compute.rb:536:in `request'
/opt/theforeman/tfm/root/usr/share/gems/gems/fog-aws-1.3.0/lib/fog/aws/requests/compute/run_instances.rb:139:in `run_instances'
/opt/theforeman/tfm/root/usr/share/gems/gems/fog-aws-1.3.0/lib/fog/aws/models/compute/servers.rb:158:in `save_many'
/opt/theforeman/tfm/root/usr/share/gems/gems/fog-aws-1.3.0/lib/fog/aws/models/compute/server.rb:201:in `save'
/opt/theforeman/tfm/root/usr/share/gems/gems/fog-core-1.45.0/lib/fog/core/collection.rb:50:in `create'
/usr/share/foreman/app/models/compute_resource.rb:195:in `create_vm'
/usr/share/foreman/app/models/compute_resources/foreman/model/ec2.rb:66:in `create_vm'
/usr/share/foreman/app/models/concerns/orchestration/compute.rb:78:in `setCompute'
/usr/share/foreman/app/models/concerns/orchestration.rb:222:in `execute'
/usr/share/foreman/app/models/concerns/orchestration.rb:145:in `block in process'

==============


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


How reproducible: Always for the same region (Stockholm) 


Steps to Reproduce:
1. Add a EC2 compute resource from Stockholm region.
2. Try to provision the host

Actual results:

Provisioning fails

Expected results:

Provisioning works

Additional info:

Provisioning is working for the customer for other regions.
Comment 2 Marek Hulan 2019-02-21 11:43:58 UTC 
BZ 1646156 could potentially help, we need to test if the newer version of fog-aws now supports this region. But the error can also mean that user tries to use instance type that is not supported in that region. Could you try other instance types, e.g. bigger one?
Comment 3 Lukáš Hellebrandt 2019-02-21 12:01:43 UTC 
Related to bug 1664308
Comment 4 Harshad More 2019-03-18 11:45:05 UTC 
(In reply to Marek Hulan from comment #2)
> BZ 1646156 could potentially help, we need to test if the newer version of
> fog-aws now supports this region. But the error can also mean that user
> tries to use instance type that is not supported in that region. Could you
> try other instance types, e.g. bigger one?

----------------
Customer confirmed testing with a bigger instance (I3) worked for him. However, customer is looking for a workaround/patch for T3 instance
Comment 5 Marek Hulan 2019-03-18 12:56:13 UTC 
Thanks for update, I'm afraid this is not something we can solve on our side. It confirms the hypothesis this instance type is not supported in selected region. I didn't find a consumable list of what flavors are available in which regions, fix on our side can be nicer error message explaining what's going on. Can you please update the customer with this? If you agree I'd proceed with the nicer explanation error message.
Comment 11 Mike McCune 2019-04-22 16:51:33 UTC 
Created attachment 1557222 [details]
Satellite 6.4 Hotfix RPM
Comment 12 Mike McCune 2019-04-22 16:53:49 UTC 
** Satellite 6.4.2 Hotfix *** 

1) download attached tfm-rubygem-fog-aws-1.3.0-3.RHBZ1678339.el7sat.noarch.rpm rpm to your Satellite

2) rpm -Uvh tfm-rubygem-fog-aws-1.3.0-3.RHBZ1678339.el7sat.noarch.rpm

3) foreman-maintain service restart

4) resume operations
Comment 16 Lukáš Hellebrandt 2019-07-25 09:18:14 UTC 
Verified with Sat 6.5.2 snap 1.

Used reproducer from OP. CR, Host and VM got created successfully.
Comment 18 errata-xmlrpc 2019-08-06 14:37:33 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/RHBA-2019:2363