RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
There is a regression in MariaDB (which occurs in 10.5.13 build) which has a negative impact on Openstack, the related upstream bugs are:
https://jira.mariadb.org/browse/MDEV-27132
https://jira.mariadb.org/browse/MDEV-27510

The regression is fixed in 10.5.14.

The way how Openstack is impacted:
The nova placement service fails to schedule a Virtual machine because It believes all the compute nodes ran out of available resources (VCPUs to be specific). The record in the DB is wrong and does not match the reality,. Based on this discussion:
https://serverfault.com/questions/1064579/openstack-only-building-one-vm-per-machine-in-cluster-then-runs-out-of-resource It seems to be caused by the MariaDB regression which start with following bug:
https://jira.mariadb.org/browse/MDEV-25714

We retested Openstack with a scratch build og 10.5.1 + mentioned patches and The problem was not reproduced anymore.

Version-Release number of selected component (if applicable):
mariadb-10.5.13-2.el9.x86_64
OSP17.0

How reproducible:
Always

Steps to Reproduce:
1. The reproducer is within the Openstack environment where higher number of running tests will caused nova placement to stop scheduling new VMs on compute nodes due to wrong record in the DB of available capabilities

Merged into the CentOS Stream 9:
  https://gitlab.com/redhat/centos-stream/rpms/mariadb/-/commits/c9s