Opening ports from cloud side helped Login to AWS NETWORK & SECURITY -> Security Groups -> Select correspodning Security group -> Add required ports from cloud side too. Not just instances. Required ports: https://github.com/SatelliteQE/automation-tools/blob/master/automation_tools/__init__.py#L336 Good to update documentation. Thanks to Kedar for his help.
Hi Pradeep, did the changes applied with comment #2 solve the issue being observed? Is any action needed on the bug?
This solves/ Thanks . I feel this should be updated in documentation part.
Hi Pradeep, when you mention documentation, are you referring to the Satellite 6 Installation Guide? Asking to ensure that we align the bug correctly. Thanks!
(In reply to Brad Buckingham from comment #5) > Hi Pradeep, when you mention documentation, are you referring to the > Satellite 6 Installation Guide? yes. I am referring to Satellite 6 Installation Guide
Moving to the default assignee to be re-triaged as the schedule allows.
Hello The tables have been updated and can be found in the "Ports and Firewalls Requirements" section[1]. I specifically added the second sentence in this paragraph to remind readers that the System Administrator needs to ensure communications are possible in a cloud environment: "The tables indicate the destination port and the direction of network traffic, use this information to configure any network-based firewalls. Note that some cloud solutions need to be specifically configured to allow communications between machines as they isolate machines similarly to network-based firewalls." Please let us know if any further improvement is required Thank you [1] https://access.redhat.com/documentation/en/red-hat-satellite/6.2-beta/installation-guide/chapter-2-preparing-your-environment-for-installation#ports_prerequisites