Description of problem: Currently when trying to create a security rule specifying ports for the protocol 112 we have an error: ~~~ #openstack security group rule create 058b5d6c-3329-4c66-b7cd-0f85c73ec5fe --protocol 112 --egress --dst-port 1:65535 Error while executing command: BadRequestException: Unknown error, {"NeutronError": {"message": "Invalid protocol 112 for port range, only supported for TCP, UDP, UDPLITE, SCTP and DCCP.", "type": "SecurityGroupInvalidProtocolForPortRange", "detail": ""}} ~~~ This error would be more understandable if make it explicit that the issue is that this protocol doesn't need to have a port specified to it, something like this: ~~~ Invalid port range specified for protocol 112. Port ranges are only supported for TCP, UDP, UDPLITE, SCTP and DCCP. ~~~ Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Create a security group 2. Create a security group rule with protocol 112 and specifying a port range Actual results: ~~~ Error while executing command: BadRequestException: Unknown error, {"NeutronError": {"message": "Invalid protocol 112 for port range, only supported for TCP, UDP, UDPLITE, SCTP and DCCP.", "type": "SecurityGroupInvalidProtocolForPortRange", "detail": ""}} ~~~ Expected results: A more understandable error message: ~~~ Invalid port range specified for protocol 112. Port ranges are only supported for TCP, UDP, UDPLITE, SCTP and DCCP. ~~~ Additional info:
This bugzilla can be close due to these upstream patches: https://review.openstack.org/#/c/636174/ https://bugs.launchpad.net/neutron/+bug/1815478
Change has been merged upstream in all stable branches. Will create downstream cherry-picks.
Hello, Do we have any estimation for the downstream release? I know we don't have exact dates for that, but at least some estimation?
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-2019:1744