Security Group empty protocol defaults to TCP

[German Eichberger]

When leaving the protocol field blank for security group it defaults to TCP. In previous versions (e.g. Liberty) this allowed *any* protocol by leaving it blank.

[Reedip (reedip-banerjee-deactivatedaccount)]

Are you using curl/shade/OSC/neutron client?
Some example would be great :)

[Brian Haley (brian-haley)]

German - this looks like it's intended behavior, the help message in the openstack client actually says the default is TCP:

  --protocol <protocol>
                        IP protocol (ah, dccp, egp, esp, gre, icmp, igmp,
                        ipv6-encap, ipv6-frag, ipv6-icmp, ipv6-nonxt,
                        ipv6-opts, ipv6-route, ospf, pgm, rsvp, sctp, tcp,
                        udp, udplite, vrrp and integer representations
                        [0-255]; default: tcp)

But I'm not sure I agree that was a good choice, especially given it was not discussed, and not even in the commit message of the change that did it.

I'll propose a change for it and see what happens.

[Brian Haley (brian-haley)]

The change BTW was https://review.openstack.org/#/c/307908

[Brian Haley (brian-haley)]

https://review.openstack.org/#/c/518954/ is the fix for this German it's just stuck in limbo.

[Rudolf Vriend (rudolf-vriend-deactivatedaccount)]

The issue is actually that currently it is not possible to specify 'Any' (or None) as protocol by omitting the --protocol argument (since it defaults to tcp).

But that is definitely required, since it is a very valid setup (required to have a decent default security group rule)

[Brian Haley (brian-haley)]

https://review.opendev.org/#/c/518954/ has merged, changing the default back to protocol 'any'.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/python-openstackclient 4.0.0 release.