Back to bug 1393487

Who When What Removed Added
Marius Cornea 2016-11-09 16:29:06 UTC Target Release --- 10.0 (Newton)
Target Milestone --- ga
Sean Cohen 2016-11-09 16:52:17 UTC CC scohen
Sean Cohen 2016-11-09 16:52:52 UTC Assignee athomas tbarron
QA Contact ohochman dschoenb
Tom Barron 2016-11-09 19:22:23 UTC CC tbarron
Link ID OpenStack gerrit 395769
Tom Barron 2016-11-09 19:23:42 UTC Link ID Launchpad 1640568
Tom Barron 2016-11-09 19:24:09 UTC Status NEW POST
Jon Schlueter 2016-11-10 05:31:45 UTC CC jschluet
Component rhel-osp-director openstack-tripleo-heat-templates
Target Milestone ga rc
Tom Barron 2016-11-10 13:11:46 UTC Link ID OpenStack gerrit 396183
Jon Schlueter 2016-11-10 14:51:50 UTC Keywords Triaged
Jon Schlueter 2016-11-11 13:44:56 UTC Link ID OpenStack gerrit 395769
Jon Schlueter 2016-11-14 15:50:56 UTC Status POST MODIFIED
Fixed In Version openstack-tripleo-heat-templates-5.0.0-1.7.el7ost
errata-xmlrpc 2016-11-14 17:40:55 UTC Status MODIFIED ON_QA
Paul Grist 2016-11-14 20:57:30 UTC CC pgrist
Tom Barron 2016-11-17 17:00:43 UTC Doc Text Cause: Firewall updates not set specifically when deploying manila-api service via OSPd.

Consequence: When manila api service is moved off of controllers to its own role, its endpoints become unreachable as they are blocked by default firewall rules.

Fix: Explicitly update firewall rules to open manila-api ports when deploying manila-api service via OSPd.

Result: Manila endpoints are now reachable even when manila api service has been moved to its own role off of controller nodes.
Doc Type If docs needed, set a value Bug Fix
Dan Macpherson 2016-11-23 03:49:52 UTC CC dmacpher
Doc Text Cause: Firewall updates not set specifically when deploying manila-api service via OSPd.

Consequence: When manila api service is moved off of controllers to its own role, its endpoints become unreachable as they are blocked by default firewall rules.

Fix: Explicitly update firewall rules to open manila-api ports when deploying manila-api service via OSPd.

Result: Manila endpoints are now reachable even when manila api service has been moved to its own role off of controller nodes.
OpenStack Platform director did not update firewall when deploying OpenStack File Share API (manila-api). If you moved the manila-api service off controllers to its own role, the default firewall rules blocked the endpoints. This fix explicitly updates the firewall rules to open ports for the manila-api when deployed with director. You can now reach the endpoints even when manila-api is on a role separate from the controller nodes.
Dan Macpherson 2016-11-23 03:53:50 UTC Doc Text OpenStack Platform director did not update firewall when deploying OpenStack File Share API (manila-api). If you moved the manila-api service off controllers to its own role, the default firewall rules blocked the endpoints. This fix explicitly updates the firewall rules to open ports for the manila-api when deployed with director. You can now reach the endpoints even when manila-api is on a role separate from the controller nodes. OpenStack Platform director did not update firewall when deploying OpenStack File Share API (manila-api). If you moved the manila-api service off controllers to its own role, the default firewall rules blocked the endpoints. This fix updates the manila-api firewall rules in the overcloud Heat template collection. You can now reach the endpoints even when manila-api is on a role separate from the controller nodes.
Dustin Schoenbrun 2016-11-23 21:08:18 UTC Status ON_QA VERIFIED
errata-xmlrpc 2016-12-14 14:17:09 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-12-14 16:31:17 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-12-14 11:31:17 UTC

Back to bug 1393487