Bug 1142528

Summary: open ceph ports on HA controller
Product: Red Hat OpenStack Reporter: Crag Wolfe <cwolfe>
Component: openstack-foreman-installerAssignee: Crag Wolfe <cwolfe>
Status: CLOSED ERRATA QA Contact: Leonid Natapov <lnatapov>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.0 (RHEL 7)CC: mburns, morazi, rhos-maint, slong, yeylon
Target Milestone: z2Keywords: ZStream
Target Release: Installer   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-foreman-installer-2.0.29-1.el6ost Doc Type: Bug Fix
Doc Text:
Previously, the firewall deployed by the RHEL-OSP installer on the HA controllers blocked Ceph monitor traffic, and any existing Ceph cluster would fail to maintain quorum after the HA Controller was deployed. With this update, the HA controller puppet manifests open up the port 6789 if using Ceph as a backend, and any pre-existing Ceph cluster continues to operate after the HA controller is deployed.
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-04 17:02:40 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:

Description Crag Wolfe 2014-09-17 01:04:44 UTC
After running puppet on HA controllers where a ceph cluster was already installed, the following issues occur:

# ceph -s
2014-09-16 08:19:00.842695 7f41084ef700  0 -- :/1025773 >> 192.168.7.62:6789/0 pipe(0x7f4104024400 sd=3 :0 s=1 pgs=0 cs=0 l=1 c=0x7f4104024670).fault
*and*
# rados -p images ls
<nothing>
simply hangs

The issues go away when the firewall is made less restrictive.

Comment 7 Leonid Natapov 2014-11-03 12:05:22 UTC
openstack-foreman-installer-2.0.31-1.el6ost

[root@macf04da2732fb1 ~]# iptables -nL | grep 6789
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            multiport dports 6789 /* 001 ceph mon incoming */

Comment 9 errata-xmlrpc 2014-11-04 17:02:40 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://rhn.redhat.com/errata/RHBA-2014-1800.html