Deleting csnat port fails due to no fixed ips
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Invalid
|
High
|
Miguel Lavalle |
Bug Description
This code [1] ends up emitting an "IndexError: list index out of range" exception that ends up with a trace like this [2]. Essentially, there are no fixed ips on the port. Not sure yet how it got in to this state. This failure is linked to various tempest failures in gate-tempest-
tempest.
tempest.
[1] https:/
[2] http://
[3] http://
Changed in neutron: | |
assignee: | nobody → Carl Baldwin (carl-baldwin) |
Changed in neutron: | |
assignee: | Kevin Benton (kevinbenton) → Carl Baldwin (carl-baldwin) |
Changed in neutron: | |
assignee: | Carl Baldwin (carl-baldwin) → Kevin Benton (kevinbenton) |
Changed in neutron: | |
assignee: | Carl Baldwin (carl-baldwin) → Miguel Lavalle (minsel) |
tags: | added: neutron-proactive-backport-potential |
Kevin mentioned that he suspects that the code that handles multiple ipv6 addresses on a single csnat port may be the culprit. It is difficult to follow and complicates things. It was added in this patch [1].
Each ipv4 subnet gets its own port, so why not the ipv6 ones?
[1] https:/ /review. openstack. org/#/c/ 225319