Bug 705716 - Port for qpidd should also be listed under "Network and Firewall Requirements" section
Summary: Port for qpidd should also be listed under "Network and Firewall Requirements...
Keywords:
Status: CLOSED DUPLICATE of bug 704587
Alias: None
Product: Red Hat Update Infrastructure for Cloud Providers
Classification: Red Hat
Component: Documentation
Version: 2.0
Hardware: powerpc
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Lana Brindley
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-18 08:45 UTC by Sachin Ghai
Modified: 2016-02-18 06:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-18 13:26:06 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Sachin Ghai 2011-05-18 08:45:44 UTC
Description of problem:
Port for qpid daemon should be open by firewall rules. These ports should also be listed under the "Network and Firewall Requirements" section

Following ports should be open on RHUA, CDS and client:

Port 5672 for non-ssl and 
Port 5674 for SSL message bus connections.


Version-Release number of selected component (if applicable):
http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Update_Infrastructure/2.0/pdf/Installation_Guide/Red_Hat_Update_Infrastructure-2.0-Installation_Guide-en-US.pdf

How reproducible:


Steps to Reproduce:
=> Chapter2 Installation Requirements
=> Under Network and Firewall Requirements section:

  
Actual results:


Expected results:

Following ports should be open on RHUA, CDS and client:

Port 5672 for non-ssl and 
Port 5674 for SSL message bus connections. 



Additional info:

Comment 1 Sachin Ghai 2011-05-18 08:48:51 UTC
I'm copying to Jeff and Jason on this defect to know their views.

Comment 2 Jay Dobies 2011-05-18 13:26:06 UTC
Great pickup Sachin. It's already been filed in the Installer docs bugs: 704587

*** This bug has been marked as a duplicate of bug 704587 ***


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