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

[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.

** Changed in: python-oslo.log (Ubuntu Jammy)
       Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to python-oslo.log in Ubuntu.
https://bugs.launchpad.net/bugs/1976106

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

Status in python-oslo.log package in Ubuntu:
  Fix Released
Status in python-oslo.log source package in Jammy:
  Fix Committed

Bug description:
  [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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-oslo.log/+bug/1976106/+subscriptions