> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-openstack/5.8/support/release-notes-openstack.md). # Managed OpenStack Release Notes ## Release Summary The Platform9 Managed OpenStack (PMO) version 5.8 release is now generally available. This release brings enhancements such as Rocky 9.1 Operating System support, Software TPM disk persistence and more. Enhancements & Updates `Added` Rocky 9.1 Operating System support for PMO KVM. `Added` Software TPM disk persistence after instance hard reboot. `Added` Ability to run RabbitMQ broker external to the Platform9 control plane for scaling benefits. `Added` API to query versions for all OpenStack Components using ** endpoint. `Enhanced` Reduced Keystone token catalog size by limiting to region scope for all service endpoints. `Enhanced` Upgraded memcached on the control plane to latest version for optimal slab rebalancing support. ## Bug Fixes `Fixed` an issue with instance hard reboot when SElinux is in permissive mode on the underlying hypervisor. `Fixed` an issue with Designate service where pool update was failing earlier if it had duplicate masters among all targets. `Fixed` an issue with Nova and Cinder services when using Ceph storage backend. `Fixed` an issue with Nova when scheduling an instance that previously belonged to a server group that has been deleted. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.platform9.com/managed-openstack/5.8/support/release-notes-openstack.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.