conntrack v1.4.4 (conntrack-tools): `0' unsupported protocol
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Brian Haley |
Bug Description
Hi,
In neutron-
From the code it seem to be related to a port update.
Does it has something to do with the fact than during security group rule creation sometime we could set a number[1] ?
2019-03-18 17:15:45.700 7 ERROR neutron.
Try `conntrack -h' or 'conntrack --help' for more information.
2019-03-18 17:15:45.701 7 ERROR neutron.
Try `conntrack -h' or 'conntrack --help' for more information.
2019-03-18 17:15:45.701 7 ERROR neutron.
2019-03-18 17:15:45.701 7 ERROR neutron.
2019-03-18 17:15:45.701 7 ERROR neutron.
2019-03-18 17:15:45.701 7 ERROR neutron.
2019-03-18 17:15:45.701 7 ERROR neutron.
2019-03-18 17:15:45.701 7 ERROR neutron.
2019-03-18 17:15:45.701 7 ERROR neutron.
2019-03-18 17:15:45.701 7 ERROR neutron.
2019-03-18 17:15:45.701 7 ERROR neutron.
This happens on Rocky version.
Changed in neutron: | |
importance: | Undecided → High |
status: | New → Confirmed |
So did you just run 'openstack security group rule create --ingress --protocol 0 default' and then delete the rule? Looks like there might be a bug in conntrack-tools I need to chase down.