[SRU] FTBFS logging_user_identity_format's default is using deprecated (now removed) tenant

[Corey Bryant]

[Impact]
python-oslo.context removed a deprecated tenant argument in 4.0.0 [1]. 4.0.0 likely landed in Jammy after python-oslo.log. Now python-oslo.log fails on Jammy rebuilds as seen here: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220506-jammy-jammy.html

[1] https://review.opendev.org/c/openstack/oslo.context/+/815938

[Test Case]
A successful build of the python-oslo.context package will verify this fix.

[Regression Potential]
This is fixing a regression in Jammy. If the version of python3-oslo.context in Jammy is used with the existing python-oslo.log (4.6.1-0ubuntu1), logging_user_identity_format's default will cause a failure as oslo.context has removed the (long deprecated) tenant argument. After this new version of python-oslo.log is available, the regression will be fixed.

[Brian Murray (brian-murray)]

Hello Corey, or anyone else affected,

Accepted python-oslo.log into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python-oslo.log/4.6.1-0ubuntu1.1 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.

[Launchpad Janitor (janitor)]

This bug was fixed in the package python-oslo.log - 4.6.1-0ubuntu1.1

---------------
python-oslo.log (4.6.1-0ubuntu1.1) jammy; urgency=medium

  * d/gbp.conf: Create stable/yoga branch.
  * d/p/use-project-when-logging-the-user-identity.patch: Picked from
    upstream to change the logging_user_identity_format option's default
    the project instead of the tenant (LP: #1976106).

 -- Corey Bryant <email address hidden> Mon, 25 Apr 2022 10:06:27 -0400

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for python-oslo.log 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.