THanks for the comments, Jeremy, from the link above, it says:
https://opendev.org/openstack/keystone/commit/7653847a04e56555b8d172a3d5c76a95533cdec7
```
The keystone token model was refactored in the Rocky release. This
commit only backports the test so that we have test coverage against
the bug and proves there wasn't a regression in Queens. As such, the
code changes to token_model.py (where the bug was introduced) are not
applicable to Pike.
```
so I think the reason you can cherry pick
THanks for the comments, Jeremy, from the link above, it says:
https:/ /opendev. org/openstack/ keystone/ commit/ 7653847a04e5655 5b8d172a3d5c76a 95533cdec7
```
The keystone token model was refactored in the Rocky release. This
commit only backports the test so that we have test coverage against
the bug and proves there wasn't a regression in Queens. As such, the
code changes to token_model.py (where the bug was introduced) are not
applicable to Pike.
```
so I think the reason you can cherry pick