[SRU] python-os-brick stable point releases
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Invalid
|
Undecided
|
Unassigned | ||
Xena |
Fix Released
|
High
|
Unassigned | ||
Yoga |
Fix Released
|
High
|
Unassigned | ||
python-os-brick (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 users have access to these improvements.
While python-os-brick is not covered under the OpenStack stable release exception I would like to see if these would be covered by the Ubuntu SRU "New upstream microrelease" exception.
The update contains the following package updates:
* python-os-brick 5.2.2 (Yoga/Jammy)
* python-os-brick 5.0.3 (Xena)
[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]
Thew new versions of os-brick are defined by opentack's upper-constraints which are the versions that get tested by the upstream gate: https:/
Following are the delta of fixes between the current versions in Ubuntu/UCA and the new versions that we would like to pick up:
# Yoga (Jammy)
os-brick$ git-pretty 5.2.0..5.2.2
- [743002c] RBD: Fix disconnect_volume for encrypted volumes
- [0bd5dc9] Fix encryption symlink issues
- [0f6b3d4] Update TOX_CONSTRAINTS
- [008c8e6] Update .gitreview for stable/yoga
# Xena
os-brick$ git-pretty 5.0.2..5.0.3
- [3aa5d29] RBD: Fix disconnect_volume for encrypted volumes
- [b31b109] Fix encryption symlink issues
[Discussion]
It is important to note that upstream has:
1) a reliable and credible test suite for assuring the quality of every commit or release,
2) the tests are covering both functionality and API/ABI stability
The upstream policy for testing is described a bit here: https:/
(specifically see the paragraphs starting with "Patches lacking unit tests are unlikely to be approved." and "If your patch has a -1 from Zuul.."). Pep8, unit, and functional (tempest) tests are run during the gate for each patch. For example, looking at the following upstream review: https:/
It is also import to note that the ubuntu package has:
1) unit tests run during package build to cover all architectures
Additionally, the OpenStack team will run their continuous integration test against the packages that are in -proposed (a juju deployed openstack with tempest functional tests executed to validate the cloud). A successful run of all available tests will be required before the proposed packages can be let into -updates.
Related branches
- Ubuntu OpenStack uploaders: Pending requested
-
Diff: 53 lines (+26/-1)2 files modifieddebian/changelog (+7/-0)
debian/control (+19/-1)
- Ubuntu OpenStack uploaders: Pending requested
-
Diff: 46 lines (+22/-2)2 files modifieddebian/changelog (+4/-2)
debian/control (+18/-0)
CVE References
Changed in python-os-brick (Ubuntu): | |
status: | New → Invalid |
Changed in python-os-brick (Ubuntu Jammy): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in cloud-archive: | |
status: | New → Invalid |
Hello Corey, or anyone else affected,
Accepted python-os-brick 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/ PerformingSRUVe rification . Thank you in advance!