As a workaround, maybe you can try putting using firewall-update <id> --admin-state-up <false/true> after it goes into error state to recover after making the rule change.
James > On Nov 6, 2015, at 5:27 AM, Erdősi Péter <f...@niif.hu> wrote: > > Hy guys! > > We facing a problem with FWaaS on Kilo release. > The problem is the same with this > (https://review.openstack.org/#/c/190336/), but as I see, the patch only > included to Liberty release. > > Are there any possibility to backport that to Kilo, or we must upgrade, > to get FWaaS up and running? > > Thanks, > Peter > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack@lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
