Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1432566 - [RFE] Configure the fiewall on the overcloud nodes to make ceph-ansible to succeed
[RFE] Configure the fiewall on the overcloud nodes to make ceph-ansible to su...
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates (Show other bugs)
12.0 (Pike)
Unspecified Unspecified
high Severity high
: Upstream M2
: 12.0 (Pike)
Assigned To: Giulio Fidente
Yogev Rabl
: FutureFeature, Triaged
Depends On: 1432576
Blocks: 1442136 1386911
  Show dependency treegraph
 
Reported: 2017-03-15 13:03 EDT by Giulio Fidente
Modified: 2018-02-05 14:04 EST (History)
9 users (show)

See Also:
Fixed In Version: openstack-tripleo-heat-templates-7.0.0-0.20170628002128.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-12-13 16:17:04 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
OpenStack gerrit 467682 None None None 2017-06-28 09:06 EDT
Red Hat Product Errata RHEA-2017:3462 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-15 20:43:25 EST

  None (edit)
Description Giulio Fidente 2017-03-15 13:03:03 EDT
We need to figure how to configure the firewall on the overcloud nodes before the Ceph deployment is initiated via ceph-ansible. This could be done using a service in Director but only if we're able to trigger the puppet run before or together with the Ceph deployment.

Alternatively, we might try to add in ceph-ansible some logic to open the needed firewall ports.
Comment 3 Yogev Rabl 2017-09-28 08:48:44 EDT
verified
Comment 6 errata-xmlrpc 2017-12-13 16:17:04 EST
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-2017:3462

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