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

[Corey Bryant]

Public bug reported:

[Impact]
python-oslo.context removed a deprecated tenant argument in 4.0.0 [1]. 4.0.0 likely landed in Jammy  after python-castellan. 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]
The only regression potential that I see is for users who are already on Jammy and using the new python3-oslo.context with the existing python-oslo.log 4.6.1-0ubuntu1 as oslo.context has removed the (long deprecated) tenant argument. After this new version of python-oslo.log is avaialble, that regression goes away.

** Affects: python-oslo.log (Ubuntu)
     Importance: Undecided
         Status: New

** Summary changed:

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

-- 
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:
  New

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-castellan. 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]
  The only regression potential that I see is for users who are already on Jammy and using the new python3-oslo.context with the existing python-oslo.log 4.6.1-0ubuntu1 as oslo.context has removed the (long deprecated) tenant argument. After this new version of python-oslo.log is avaialble, that regression goes away.

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