[MIR] mitaka neutron 8.3.0 and nova 13.1.2 stable releases
Bug #1633191 reported by
Corey Bryant
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Invalid
|
Undecided
|
Unassigned | ||
Mitaka |
Fix Released
|
Undecided
|
Unassigned | ||
neutron (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
neutron-lbaas (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
nova (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
New stable point releases for neutron and nova:
neutron 8.3.0
neutron-lbaas 8.3.0
nova 13.1.2
[Test Case]
For all stable point releases, we perform regression testing by juju deploying two openstack clouds, one against -proposed and one against -updates, and we then run tempest integration smoke tests[1] to verify those deployed clouds, and evaluate any differences in results.
[1] https:/
[Regression Potential]
Stable point releases from upstream are considered low regression potential.
Changed in neutron (Ubuntu): | |
status: | New → Invalid |
Changed in nova (Ubuntu): | |
status: | New → Invalid |
Changed in neutron-lbaas (Ubuntu): | |
status: | New → Invalid |
no longer affects: | ubuntu |
no longer affects: | Ubuntu Xenial |
Changed in cloud-archive: | |
status: | New → Invalid |
To post a comment you must log in.
Hello Corey, or anyone else affected,
Accepted neutron into xenial-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ neutron/ 2:8.3.0- 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 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, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- 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/ PerformingSRUVe rification . Thank you in advance!