[SRU] stable point releases for neutron-vpnaas

Bug #1995861 reported by Christian Rohmann
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu Cloud Archive
Fix Released
Undecided
Unassigned
Xena
Fix Released
High
Unassigned
Yoga
Fix Released
High
Unassigned
Zed
Fix Released
Undecided
Unassigned
neutron-vpnaas (Ubuntu)
Fix Released
Undecided
Unassigned
Jammy
Fix Released
High
Unassigned

Bug Description

[Impact]
This release sports mostly bug-fixes and we would like to make
sure all of our supported customers have access to these
improvements. The update contains the following package updates:

neutron-vpnaas 20.0.1 (jammy/yoga)
neutron-vpnaas 19.0.1 (xena)

[Test Case]
The following SRU process was followed:
https://wiki.ubuntu.com/OpenStackUpdates

In order to avoid regression of existing consumers, the OpenStack team
will run their continuous integration test against the packages that
are in -proposed. A successful run of all available tests will be
required before the proposed packages can be let into -updates.

The OpenStack team will be in charge of attaching the output summary
of the executed tests. The OpenStack team members will not mark
‘verification-done’ until this has happened.

[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned tests are attached to this bug.

[Discussion]
Currently the neutron-vpnaas package for Xena, Yoga lack two critical fixes, which both have been merged (just no updated package was provided yet):

 * https://review.opendev.org/c/openstack/neutron-vpnaas/+/823904
 * https://review.opendev.org/c/openstack/neutron-vpnaas/+/840308

without those the VPNaaS is mostly broken when L3 HA is used.

Revision history for this message
Corey Bryant (corey.bryant) wrote :

This patches are in zed but not yet in xena and yoga. I've proposed new point releases for neutron-vpnaas at https://review.opendev.org/c/openstack/releases/+/866784.

Changed in cloud-archive:
status: New → Fix Released
Revision history for this message
Christian Rohmann (christian-rohmann) wrote :

With the fix now merged / released... I am wondering when the new packages will be available via UCA (https://openstack-ci-reports.ubuntu.com/reports/cloud-archive/xena_versions.html / https://openstack-ci-reports.ubuntu.com/reports/cloud-archive/yoga_versions.html ?

Revision history for this message
Corey Bryant (corey.bryant) wrote :
description: updated
Changed in neutron-vpnaas (Ubuntu):
status: New → Fix Released
Changed in neutron-vpnaas (Ubuntu Jammy):
status: New → Triaged
importance: Undecided → High
summary: - [SRU] neutron-vpnaas packages need updates as they are missing two
- critical patches
+ [SRU] stable point releases for neutron-vpnaas
Revision history for this message
Corey Bryant (corey.bryant) wrote : Please test proposed package

Hello Christian, or anyone else affected,

Accepted neutron-vpnaas into xena-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:xena-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-xena-needed to verification-xena-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-xena-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

tags: added: verification-xena-needed
Revision history for this message
Corey Bryant (corey.bryant) wrote :
tags: added: verification-done verification-xena-done
removed: verification-xena-needed
Revision history for this message
Corey Bryant (corey.bryant) wrote :

Nevermind for jammy/yoga.. that still hasn't been accepted into jammy-proposed. I will check with the SRU team now.

tags: removed: verification-done
Revision history for this message
Brian Murray (brian-murray) wrote :

Hello Christian, or anyone else affected,

Accepted neutron-vpnaas into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/neutron-vpnaas/2:20.0.1-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in neutron-vpnaas (Ubuntu Jammy):
status: Triaged → Fix Committed
tags: added: verification-needed verification-needed-jammy
Revision history for this message
Corey Bryant (corey.bryant) wrote :

Hello Christian, or anyone else affected,

Accepted neutron-vpnaas into yoga-proposed. The package will build now and be available in the Ubuntu Cloud Archive in a few hours, and then in the -proposed repository.

Please help us by testing this new package. To enable the -proposed repository:

  sudo add-apt-repository cloud-archive:yoga-proposed
  sudo apt-get update

Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-yoga-needed to verification-yoga-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-yoga-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

tags: added: verification-yoga-needed
Revision history for this message
Corey Bryant (corey.bryant) wrote :

Verified successfully on jammy-yoga:

(unrelated test failure)
======
Totals
======
Ran: 183 tests in 648.2270 sec.
 - Passed: 170
 - Skipped: 12
 - Expected Fail: 0
 - Unexpected Success: 0
 - Failed: 1
Sum of execute time for each test: 1050.9889 sec.

Verified successfully on focal-yoga

======
Totals
======
Ran: 183 tests in 742.3712 sec.
 - Passed: 171
 - Skipped: 12
 - Expected Fail: 0
 - Unexpected Success: 0
 - Failed: 0
Sum of execute time for each test: 891.9525 sec.

tags: added: verification-done verification-done-jammy verification-yoga-done
removed: verification-needed verification-needed-jammy verification-yoga-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package neutron-vpnaas - 2:20.0.1-0ubuntu1

---------------
neutron-vpnaas (2:20.0.1-0ubuntu1) jammy; urgency=medium

  * d/gbp.conf: Create stable/yoga branch.
  * New stable point release for OpenStack Yoga (LP: #1995861).

 -- Corey Bryant <email address hidden> Thu, 15 Dec 2022 08:41:01 -0500

Changed in neutron-vpnaas (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for neutron-vpnaas has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Corey Bryant (corey.bryant) wrote :

The verification of the Stable Release Update for neutron-vpnaas has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Corey Bryant (corey.bryant) wrote :

This bug was fixed in the package neutron-vpnaas - 2:20.0.1-0ubuntu1~cloud0
---------------

 neutron-vpnaas (2:20.0.1-0ubuntu1~cloud0) focal-yoga; urgency=medium
 .
   * New upstream release for the Ubuntu Cloud Archive.
 .
 neutron-vpnaas (2:20.0.1-0ubuntu1) jammy; urgency=medium
 .
   * d/gbp.conf: Create stable/yoga branch.
   * New stable point release for OpenStack Yoga (LP: #1995861).

Revision history for this message
Corey Bryant (corey.bryant) wrote :

The verification of the Stable Release Update for neutron-vpnaas has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Corey Bryant (corey.bryant) wrote :

This bug was fixed in the package neutron-vpnaas - 2:19.0.1-0ubuntu1~cloud0
---------------

 neutron-vpnaas (2:19.0.1-0ubuntu1~cloud0) focal-xena; urgency=medium
 .
   * d/gbp.conf: Create stable/xena branch.
   * New stable point release for OpenStack Xena (LP: #1995861).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.