[SRU] yoga stable releases
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Invalid
|
Undecided
|
Unassigned | ||
Yoga |
Fix Released
|
High
|
Unassigned | ||
cinder (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
High
|
Unassigned | ||
designate (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
High
|
Unassigned | ||
heat (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
High
|
Unassigned | ||
manila (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
High
|
Unassigned | ||
nova (Ubuntu) |
Invalid
|
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:
cinder 20.2.0
designate 14.0.2
heat 18.0.1
manila 14.1.0
nova 25.1.1
[Test Case]
The following SRU process was followed:
https:/
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
Related branches
- Ubuntu OpenStack uploaders: Pending requested
-
Diff: 14 lines (+6/-0)1 file modifieddebian/changelog (+6/-0)
- Ubuntu OpenStack uploaders: Pending requested
-
Diff: 38 lines (+19/-0)2 files modifieddebian/changelog (+7/-0)
debian/control (+12/-0)
- Ubuntu OpenStack uploaders: Pending requested
-
Diff: 44 lines (+17/-1)2 files modifieddebian/changelog (+7/-0)
debian/control (+10/-1)
- Ubuntu OpenStack uploaders: Pending requested
-
Diff: 14 lines (+6/-0)1 file modifieddebian/changelog (+6/-0)
CVE References
Changed in cloud-archive: | |
status: | New → Invalid |
Changed in cinder (Ubuntu): | |
status: | New → Invalid |
Changed in designate (Ubuntu): | |
status: | New → Invalid |
Changed in heat (Ubuntu): | |
status: | New → Invalid |
Changed in manila (Ubuntu): | |
status: | New → Invalid |
Changed in nova (Ubuntu): | |
status: | New → Invalid |
Changed in cinder (Ubuntu Jammy): | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in designate (Ubuntu Jammy): | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in heat (Ubuntu Jammy): | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in manila (Ubuntu Jammy): | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in nova (Ubuntu Jammy): | |
importance: | Undecided → High |
status: | New → Triaged |
Hello Corey, or anyone else affected,
Accepted manila into jammy-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ manila/ 1:14.1. 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 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/ PerformingSRUVe rification . 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.