[Bug 1888693] Re: [SRU] networking-arista version re-alignment

[Aurelien Lourot]

** Description changed:

  [Impact]
  The versions of networking-arista in Ubuntu releases are not aligned to the associated OpenStack Release:
  
  bionic: Queens - 2018.1.16
  focal: Ussuri - no release tag but stable/ussuri branch exists
  groovy: Victoria - snapshot required
  
  and for the UCA
  
  bionic/stein: 2019.1.9
  bionic/train: 2019.2.3
  bionic/ussuri: 2019.2.3 (this is still the latest tagged release)
  
  [Test Case]
- TBC by Aurelien
+ charm-neutron-api-plugin-arista's Zaza tests: https://opendev.org/openstack/charm-neutron-api-plugin-arista/src/branch/master/src/tests
+ 
+ These tests deploy OpenStack with networking-arista for all supported
+ Ubuntu series and OpenStack releases, and validate that when
+ creating/deleting Neutron networks, they also appear/disappear on the
+ associated Arista test fixture.
  
  [Regression Potential]
  This update essentially only includes the following updates:
-  - [df37db8] Reduce info level logging output
-  - [5ea0b08] Fix handling of ERROR ports and '' device_id
-  - [5843ba4] Test routes are not deleted on sync
+  - [df37db8] Reduce info level logging output
+  - [5ea0b08] Fix handling of ERROR ports and '' device_id
+  - [5843ba4] Test routes are not deleted on sync
  
  df37db8 shouldn't have much of an effect, of course an error in any of the logs could result in an unhandled python exception occurring
  5ea0b08 changes logic around when ports get deleted, it looks correct but a regression in this code could result in a network port getting deleted when it shouldn't have
  5843ba4 is only updating tests

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1888693

Title:
  [SRU] networking-arista version re-alignment

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive queens series:
  Won't Fix
Status in Ubuntu Cloud Archive stein series:
  Triaged
Status in Ubuntu Cloud Archive train series:
  Triaged
Status in Ubuntu Cloud Archive ussuri series:
  Triaged
Status in Ubuntu Cloud Archive victoria series:
  Fix Released
Status in networking-arista package in Ubuntu:
  Fix Released
Status in networking-arista source package in Bionic:
  Won't Fix
Status in networking-arista source package in Focal:
  Triaged
Status in networking-arista source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  The versions of networking-arista in Ubuntu releases are not aligned to the associated OpenStack Release:

  bionic: Queens - 2018.1.16
  focal: Ussuri - no release tag but stable/ussuri branch exists
  groovy: Victoria - snapshot required

  and for the UCA

  bionic/stein: 2019.1.9
  bionic/train: 2019.2.3
  bionic/ussuri: 2019.2.3 (this is still the latest tagged release)

  [Test Case]
  charm-neutron-api-plugin-arista's Zaza tests: https://opendev.org/openstack/charm-neutron-api-plugin-arista/src/branch/master/src/tests

  These tests deploy OpenStack with networking-arista for all supported
  Ubuntu series and OpenStack releases, and validate that when
  creating/deleting Neutron networks, they also appear/disappear on the
  associated Arista test fixture.

  [Regression Potential]
  This update essentially only includes the following updates:
   - [df37db8] Reduce info level logging output
   - [5ea0b08] Fix handling of ERROR ports and '' device_id
   - [5843ba4] Test routes are not deleted on sync

  df37db8 shouldn't have much of an effect, of course an error in any of the logs could result in an unhandled python exception occurring
  5ea0b08 changes logic around when ports get deleted, it looks correct but a regression in this code could result in a network port getting deleted when it shouldn't have
  5843ba4 is only updating tests

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1888693/+subscriptions