| 2020-04-27 17:55:57 |
Corey Bryant |
bug |
|
|
added bug |
| 2020-04-27 17:56:12 |
Corey Bryant |
nominated for series |
|
cloud-archive/rocky |
|
| 2020-04-27 17:56:12 |
Corey Bryant |
bug task added |
|
cloud-archive/rocky |
|
| 2020-04-27 17:56:34 |
Corey Bryant |
cloud-archive/rocky: status |
New |
Triaged |
|
| 2020-04-27 17:56:36 |
Corey Bryant |
cloud-archive/rocky: importance |
Undecided |
High |
|
| 2020-04-27 17:56:39 |
Corey Bryant |
cloud-archive: status |
New |
Invalid |
|
| 2020-05-01 20:12:55 |
Corey Bryant |
cloud-archive/rocky: status |
Triaged |
Fix Committed |
|
| 2020-05-01 20:12:56 |
Corey Bryant |
tags |
|
verification-rocky-needed |
|
| 2020-05-05 17:11:44 |
Corey Bryant |
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:
ceilometer 11.1.0
horizon 14.1.0
[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]
n/a |
[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:
ceilometer 11.1.0
horizon 14.1.0
neutron 13.0.7
[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]
n/a |
|
| 2020-05-05 17:20:14 |
Corey Bryant |
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:
ceilometer 11.1.0
horizon 14.1.0
neutron 13.0.7
[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]
n/a |
[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:
ceilometer 11.1.0
horizon 14.1.0
neutron 13.0.7
nova 18.3.0
cinder 13.0.9
keystone 14.2.0
[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]
n/a |
|
| 2020-05-28 14:15:12 |
James Page |
tags |
verification-rocky-needed |
verification-rocky-done |
|
| 2020-05-28 14:16:03 |
James Page |
cloud-archive/rocky: status |
Fix Committed |
Fix Released |
|
