42074a6725
Currently, 'icmp', 'ipv6-icmp' and 'icmpv6' can be specified as an IPv6 ICMP protocol value. This can lead to duplicate entries in the DB for doing exactly the same thing. Change to always be 'ipv6-icmp' so this doesn't happen. Existing rules using one of the old values will now be returned with 'ipv6-icmp' as the protocol value. Depends-on: https://review.opendev.org/660206 Depends-on: https://review.opendev.org/660387 Change-Id: I7cd146691dce1a690e1d2c309dfd54b4a0032f76 Partial-Bug: #1582500
15 lines
593 B
YAML
15 lines
593 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
Existing IPv6 ICMP security group rules created by using legacy protocol
|
|
names ``icmpv6`` and ``icmp`` will now be returned as ``ipv6-icmp`` in
|
|
an API GET call.
|
|
fixes:
|
|
- |
|
|
Security group rule code has been changed to better detect duplicate
|
|
rules by standardizing on ``ipv6-icmp`` as the protocol field value
|
|
for IPv6 ICMP rules. The legacy names ``icmpv6`` and ``icmp`` can still
|
|
be used in API POST calls, but API GET calls will return ``ipv6-icmp``.
|
|
Partial fix for bug
|
|
`1582500 <https://bugs.launchpad.net/neutron/+bug/1582500>`_.
|