Bug 1828428 - Controller AWS S3 Connectivity Test requires port 80, should use https and 443
Summary: Controller AWS S3 Connectivity Test requires port 80, should use https and 443
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Migration Tooling
Version: 4.3.z
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.4.0
Assignee: Sam Lucidi
QA Contact: Xin jiang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-27 17:15 UTC by Erik Nelson
Modified: 2020-05-28 11:10 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-28 11:09:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2020:2326 0 None None None 2020-05-28 11:10:21 UTC

Description Erik Nelson 2020-04-27 17:15:50 UTC
Description of problem:
The controller's S3 connectivity check requires port 80 and uses http. It should prefer https and port 443.

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

How reproducible:
Always

Steps to Reproduce:
1. Add replication repo

Actual results:
Requires port 80 open in proxy/firewall

Expected results:
Customer should not be required to open port 80

Comment 5 Sergio 2020-05-12 17:03:46 UTC
Verified using CAM 1.2 stage


The problem can be triggered by using a proxied environment and configuring a http proxy that does not work. (http_proxy variable in MigrationController resource). It does not break the validation anymore.

Comment 7 errata-xmlrpc 2020-05-28 11:09:56 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/RHEA-2020:2326


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