| 2020-09-23 19:26:06 |
Flavio Fernandes |
bug |
|
|
added bug |
| 2020-09-23 19:26:16 |
Flavio Fernandes |
networking-ovn: assignee |
|
Flavio Fernandes (ffernand) |
|
| 2020-09-23 19:27:12 |
Flavio Fernandes |
description |
Currently, the port_update api in networking_ovn does not seem to
retain values in the external_ids that it may not care about.
That is not proper behavior as external ids in the lsp may be
storing data used by another entity in neutron, such as
ovn-octavia-provider.
Pseudo example:
1- create neutron port (which creates lsp in ovn)
2- add a new value to lsp's external_ids
3- invoke neutron: port_update
4- check an verify that after port update the key/value pair added in step 2 is still present
Ref code to networking-ovn port_update:
https://github.com/openstack/networking-ovn/blob/51e4351309c1f38c2ed353e6547c60ae9d5d50f5/networking_ovn/common/ovn_client.py#L456 |
Currently, the update_port api in networking_ovn does not seem to
retain values in the external_ids that it may not care about.
That is not proper behavior as external ids in the lsp may be
storing data used by another entity in neutron, such as
ovn-octavia-provider.
Pseudo example:
1- create neutron port (which creates lsp in ovn)
2- add a new value to lsp's external_ids
3- invoke neutron: port_update
4- check an verify that after port update the key/value pair added in step 2 is still present
Ref code to networking-ovn port_update:
https://github.com/openstack/networking-ovn/blob/51e4351309c1f38c2ed353e6547c60ae9d5d50f5/networking_ovn/common/ovn_client.py#L456 |
|
| 2020-09-23 19:27:31 |
Flavio Fernandes |
description |
Currently, the update_port api in networking_ovn does not seem to
retain values in the external_ids that it may not care about.
That is not proper behavior as external ids in the lsp may be
storing data used by another entity in neutron, such as
ovn-octavia-provider.
Pseudo example:
1- create neutron port (which creates lsp in ovn)
2- add a new value to lsp's external_ids
3- invoke neutron: port_update
4- check an verify that after port update the key/value pair added in step 2 is still present
Ref code to networking-ovn port_update:
https://github.com/openstack/networking-ovn/blob/51e4351309c1f38c2ed353e6547c60ae9d5d50f5/networking_ovn/common/ovn_client.py#L456 |
Currently, the update_port api in networking_ovn does not seem to
retain values in the external_ids that it may not know about.
That is not proper behavior as external ids in the lsp may be
storing data used by another entity in neutron, such as
ovn-octavia-provider.
Pseudo example:
1- create neutron port (which creates lsp in ovn)
2- add a new value to lsp's external_ids
3- invoke neutron: port_update
4- check an verify that after port update the key/value pair added in step 2 is still present
Ref code to networking-ovn port_update:
https://github.com/openstack/networking-ovn/blob/51e4351309c1f38c2ed353e6547c60ae9d5d50f5/networking_ovn/common/ovn_client.py#L456 |
|
| 2020-09-23 20:50:56 |
Brian Haley |
networking-ovn: status |
New |
Confirmed |
|
| 2020-09-23 20:51:15 |
Brian Haley |
affects |
networking-ovn |
neutron |
|
| 2020-09-23 20:51:31 |
Brian Haley |
tags |
|
ovn |
|
| 2020-09-23 20:51:37 |
Brian Haley |
neutron: importance |
Undecided |
High |
|
| 2020-09-24 12:22:15 |
OpenStack Infra |
neutron: status |
Confirmed |
In Progress |
|
| 2020-09-29 16:54:09 |
OpenStack Infra |
neutron: status |
In Progress |
Fix Released |
|
| 2020-10-05 14:08:07 |
OpenStack Infra |
tags |
ovn |
in-stable-victoria ovn |
|
| 2020-10-06 06:37:05 |
OpenStack Infra |
tags |
in-stable-victoria ovn |
in-stable-ussuri in-stable-victoria ovn |
|
| 2020-10-08 11:39:58 |
Bernard Cafarelli |
tags |
in-stable-ussuri in-stable-victoria ovn |
in-stable-ussuri in-stable-victoria neutron-proactive-backport-potential ovn |
|
