[Yahoo-eng-team] [Bug 1816927] Re: Deployments with high churn are susceptible to false positives with token validation

** Changed in: openstack-ansible Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1816927 Title: Deployments with high ch

[Yahoo-eng-team] [Bug 1822676] Re: novnc no longer sets token inside cookie

** Changed in: openstack-ansible Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1822676 Title: novnc no longer sets token insi

[Yahoo-eng-team] [Bug 1777446] Re: "Using MigrationKeyManager to provide support for legacy fixed_key encryption: DuplicateOptError: duplicate option: fixed_key" warnings all over n-api logs in barbic

This bug report does not appear related to openstack-ansible ** Changed in: openstack-ansible Status: Confirmed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net

[Yahoo-eng-team] [Bug 1918292] [NEW] rescuing a boot from volume instance failed with "no bootable device" when hw_rescue_bus=scsi

Public bug reported: I spent some time understanding how to rescue instances which are boot- from-volume. After finding a setup which would rescue instances properly with hw_rescue_device=disk and hw_rescue_bus=usb, switching the rescue bus to hw_rescue_bus=scsi resulted in an Ubuntu Focal instan

[Yahoo-eng-team] [Bug 1918288] [NEW] rescue of boot from volume image fails when --image is not specified

Public bug reported: >From an environment where all storage is on ceph, it was not possible to omit the --image parameter when rescuing a boot-from-volume instance as suggested near the end of this doc: https://docs.openstack.org/nova/latest/user/rescue.html The doc implies that omitting --image

[Yahoo-eng-team] [Bug 1844157] [NEW] keystone-manage db_sync --check misbehaves, version 15.1.0

Public bug reported: We are seeing a difference in behaviour in keystone-manage between version 15.0.0 and 15.1.0. The newer version always has a return code of zero, which means that in openstack-ansible we never initialise the keystone db - that process is driven by parsing the return code. He