Bug 1488631 - (OSP11 backport) fail to use jump with tripleo::firewall::rule
Summary: (OSP11 backport) fail to use jump with tripleo::firewall::rule
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-tripleo
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z3
: 11.0 (Ocata)
Assignee: Emilien Macchi
QA Contact: Gurenko Alex
URL:
Whiteboard:
Depends On: 1488492
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-05 22:30 UTC by Emilien Macchi
Modified: 2020-12-14 09:52 UTC (History)
11 users (show)

Fixed In Version: puppet-tripleo-6.5.0-9.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1488492
Environment:
Last Closed: 2017-10-31 17:37:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1669763 0 None None None 2017-09-05 22:30:44 UTC
OpenStack gerrit 501013 0 None None None 2017-09-05 22:39:44 UTC
Red Hat Product Errata RHBA-2017:3098 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 11.0 director Bug Fix Advisory 2017-10-31 21:33:28 UTC

Description Emilien Macchi 2017-09-05 22:30:44 UTC 
+++ This bug was initially created as a clone of Bug #1488492 +++

Description of problem:
Unable to use jump following https://forge.puppet.com/puppetlabs/firewall

Version-Release number of selected component (if applicable):
puppet-tripleo-5.6.1-2.el7ost.noarch

How reproducible:

try to deploy this rule : 
       '410 allow marking':
          port: 10051
          proto: tcp
          source: 10.0.0.8
          extra: {
            table: mangle,
            jump: dscp,
            set_dscp: 12
          } 

It's fail cause action is by default ACCEPT.

Bug lanchpad : https://bugs.launchpad.net/tripleo/+bug/1669763
Comment 5 errata-xmlrpc 2017-10-31 17:37:35 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://access.redhat.com/errata/RHBA-2017:3098
Note You need to log in before you can comment on or make changes to this bug.