Chapter 3. Release information RHOSO 18.0 These release notes highlight selected updates in some or all of the Red Hat Services on OpenShift (RHOSO) components. Consider these updates when you deploy this release of RHOSO. Each of the notes in this section refers to the Jira issue used to track the update. If the Jira issue security level is public, you can click the link to see the Jira issue. If the security level is restricted, the Jira issue ID does not have a link to the Jira issue. 3.1. Release information RHOSO 18.0.4 3.1.1. Advisory list This release of Red Hat OpenStack Services on OpenShift (RHOSO) includes the following advisories: RHBA-2025:0435 Release of components for RHOSO 18.0.4 RHBA-2025:0436 Release of containers for RHOSO 18.0.4 RHBA-2025:0437 Control plane Operators for RHOSO 18.0.4 RHBA-2025:0438 Data plane Operators for RHOSO 18.0.4 RHSA-2025:0439 Moderate: Red Hat OpenStack Platform 18.0.4 (openstack-ironic) security update 3.1.2. Compute 3.1.2.1. Bug fixes This part describes bugs fixed in Red Hat OpenStack Services on OpenShift 18.0 that have a significant impact on users. Boot instances from images with hardware architecture properties Before this update, you could not boot an instance from an image that had hw_architecture or hw_emulation_architecture properties. With this update, you can boot instances from images that have hw_architecture and hw_emulation_architecture properties. Jira:OSPRH-6215 3.1.2.2. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Instances with ephemeral storage on NFS share stop working after Compute service restart Compute service (nova) instances with ephemeral storage on NFS shares stop working as soon as the containerized Compute agent service restarts on the hypervisor host. That happens because of changed permissions of /var/lib/nova/ instances. Workaround: Manually restore permissions to the original values and avoid the service restarts. Jira:OSPRH-10729 Cold migration fails for server with swap in flavor for shared storage like NFS. When the Compute service (nova) is enabled with shared storage, for example, NFS, cold migration fails if the instance uses the FLAVOR_SWAP flavor. Jira:OSPRH-12784 Compute service power management feature disabled by default The Compute service (nova) power management feature is disabled by default. You can enable it with the following nova-compute configuration: The default cpu_power_management_strategy cpu_state is currently unsupported. Restarting nova-compute causes all dedicated PCPUs on that host to be powered down, including ones used by instances. If the cpu_state strategy is used, those instances' CPUs will become unpinned. Jira:OSPRH-10772 3.1.3. Data plane 3.1.3.1. Bug fixes This part describes bugs fixed in Red Hat OpenStack Services on OpenShift 18.0 that have a significant impact on users. Documentation: Specify a pool to register nodes if you have multiple Red Hat subscriptions Before this update, there was an optional command missing to specify a pool when you registered nodes for your RHOSO deployment in the procedures for creating the OpenStackDataPlaneNodeSet CR with pre-provisoned nodes or unprovisioned nodes. The missing command could cause a registration error when deploying the data plane or Compute nodes in RHOSO if you had multiple Red Hat subscriptions. With this update, the optional command to specify a pool if you have multiple Red Hat subscriptions is included in these procedures. Jira:OSPRH-12956 Ansible task writes the registries.conf file successfully in disconnected deployments Before this update, the registries.conf file failed in disconnected deployments because the Ansible task attempted to use the template module and the raw string input as the src . With this update, the Ansible task writes the registries.conf file successfully because it uses the ansible.builtin.copy module with the content parameter. Jira:OSPRH-11475 iscsi-starter.service disabled on EDPM nodes after a reboot Before this update, the iscsi.service started after a reboot of EDPM nodes that run an instance with an iSCSI-backed volume, even though iscsi.service was not enabled in edpm-ansible . This issue occurred because the iscsi-starter.service was enabled in the EDPM node's image. With this update, the iscsi-starter.service is disabled on EDPM nodes to prevent the issue. Jira:OSPRH-12372 3.1.4. Hardware Provisioning 3.1.4.1. Bug fixes This part describes bugs fixed in Red Hat OpenStack Services on OpenShift 18.0 that have a significant impact on users. New default_network_interface parameter for Bare Metal service (ironic) Before this update, if the Bare Metal service network_interface was not configured during ControlPlane deployment, RHOSO configured it as a no-op. With this update, RHOSO set the default_network_interface parameter to a default value under customServiceConfig / [DEFAULT] Jira:OSPRH-10697 3.1.5. Networking 3.1.5.1. Bug fixes This part describes bugs fixed in Red Hat OpenStack Services on OpenShift 18.0 that have a significant impact on users. Adds support of dynamic routing without DVR Previously, you could not use dynamic routing on the data plane with Free Range Routing (FRR) and Border Gateway Protocol (BGP) unless you also used distributed virtual routing (DVR). Now you can use dynamic routing without enabling DVR. Jira:OSPRH-8429 Documentation: Set replicas: 3 for ovndbcluster fields Previously, CR examples throughout the RHOSO documentation did not consistently represent that to support OVN database high availability, you must set replicas: 3 in the ovndbcluster-nb and ovndbcluster-sb fields for every control plane CR that includes the OVN spec. With this update, all CR examples now include the replicas requirement. The following example shows an excerpt from the CR example with the added section: Jira:OSPRH-12462 Update to latest RHOSP 17.1 version before adopting When performing adoption of a source environment which is older than RHOSP 17.1.4, the workloads experience a prolonged network connectivity disruption. Make sure to update the source environment at least to RHOSP 17.1.4 before adopting. Jira:OSPRH-10283 Corrected default value for createDefaultLbMgmtNetwork and manageLbMgmtNetworks when availability zones are defined Before this update, createDefaultLbMgmtNetwork and manageLbMgmtNetworks were incorrectly set to false when availability zones were defined. With this update, createDefaultLbMgmtNetwork and manageLbMgmtNetworks are set to true when availability zones are defined. Jira:OSPRH-11092 3.1.5.2. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. octavia-operator does not enable anti affinity The Load-balancing service (octavia) does not currently configure anti-affinity settings in the Compute service (nova) to prevent Amphora VMs from being scheduled to the same Compute node. Workaround: Add the relevant setting to the Load-balancing service by using the customServiceConfig parameter, as shown in the following example: Example Jira:OSPRH-10705 Legacy tripleo Networking services (neutron) after adoption After the edpm_tripleo_cleanup task, there are still legacy tripleo Networking service (neutron) services. These services are stopped after adoption, so the RHOSO services are not affected. Workaround: Perform the following steps to remove the legacy services manually: Check tripleo neutron services list: systemctl list-unit-files --type service Remove tripleo services from /etc/systemd/system/ Jira:OSPRH-11323 Adoption not supported with Load-balancing service (octavia) agents on networker nodes Adoption of deployments that have Load-balancing service agents deployed on networker nodes is currently not supported. Jira:OSPRH-10771 Packets silently dropped when external MTU is greater than internal MTU RHOSO does not fragment north-south packets as expected when the external MTU is greater than the internal MTU. Instead, if the ingress packets are dropped with no notification. Also, fragmentation does not work on east/west traffic between tenant networks. Until these issues are resolved, ensure that the external MTU settings are less than or equal to internal MTU settings, and that all MTU settings on east/west paths are equal. Procedure: Set ovn_emit_need_to_frag to true . Set global_physnet_mtu to a size that is at least 58 bytes larger than the external network MTU, to accommodate the geneve tunnel encapsulation overhead. Set physical_network_mtus value pairs to describe the MTU of each physical network. Ensure that the MTU setting on on every device on the external network is less than the internal MTU setting. To apply the changes to an existing router, delete the router and re-create it. Example For example, suppose that the external network datacentre MTU is 1500. Enter the following neutron settings in your OpenStackControlPlane CR: Ensure that the MTU setting on on every device on the external network is less than the internal MTU setting. Ensure that all tenant networks that use the OVN router have the same MTU. To apply the changes to an existing router, delete the router and re-create it. Jira:OSPRH-12695 3.1.6. Network Functions Virtualization 3.1.6.1. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Do not use virtual functions (VF) for the RHOSO control plane interface This RHOSO release does not support the use of VFs for the RHOSO control plane interface. Jira:OSPRH-8882 Verify that the os-net-config provider is ifcfg for any production deployment Red Hat does not currently support NMstate as the os-net-config provider . Ensure that you have the setting edpm_network_config_nmstate: false , which is the default. This ensures that your environment uses the ifcfg provider. Jira:OSPRH-11309 3.1.7. Control plane 3.1.7.1. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Control plane temporarily unavailable during minor update During the minor update to 18.0 Feature Release 1, the RHOSO control plane temporarily becomes unavailable. API requests might fail with HTTP error codes, such as error 500. Alternatively, the API requests might succeed but the underlying life cycle operation fails. For example, a virtual machine (VM) created with the openstack server create command during the minor update never reaches the ACTIVE state. The control plane outage is temporary and automatically recovers after the minor update is finished. The control plane outage does not affect the already running workload. Jira:OSPRH-10790 3.1.8. Security and hardening 3.1.8.1. Bug fixes This part describes bugs fixed in Red Hat OpenStack Services on OpenShift 18.0 that have a significant impact on users. Custom configuration support for Key Manager (barbican) services Before this update, there was an issue in common_types.go , preventing the customServiceConfig field in the custom resource definition (CRD) for the Key Manager service from being applied correctly. With this update, the issue has been resolved, allowing custom configuration to be correctly generated and applied. Jira:OSPRH-10935 3.1.9. Storage 3.1.9.1. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. extraMounts propagation to instance does not work when uniquePodNames is true When uniquePodNames is true , every Cinder pod (and in general each component and service) is prefixed by a pseudo-random string. This affects the per-instance propagation, because the legacy method, based on strings.TrimPrefix , is not valid anymore. In a DCN deployment, propagate secrets to pods by matching the instance AZ name. Example 1 results in pods with names that match az0 getting the secret ceph-conf-az-0, pods with names that match az1 getting the secret ceph-conf-az-0, and so on. Example 1 works for Glance pods but only works for Cinder pods if uniquePodNames is false . Workaround: Set uniquePodNames to false as shown in Example 2, until this issue is resolved. The uniquePodNames setting is only required if the storage back end uses NFS. Example 1 Example 2 Jira:OSPRH-11240 3.2. Release information RHOSO 18.0.3 3.2.1. Advisory list This release of Red Hat OpenStack Services on OpenShift (RHOSO) includes the following advisories: RHBA-2024:9480 Release of components for RHOSO 18.0.3 (Feature Release 1) RHSA-2024:9481 Moderate: Red Hat OpenStack Platform 18.0.3 (python-django) security update RHBA-2024:9482 Release of containers for RHOSO 18.0.3 (Feature Release 1) RHBA-2024:9483 Data plane Operators for RHOSO 18.0.3 (Feature Release 1) RHBA-2024:9484 Release of operators for RHOSO 18.0.3 (Feature Release 1) RHSA-2024:9485 Important: Control plane Operators for RHOSO 18.0.3 (Feature Release 1) security update RHBA-2024:9486 Control plane Operators for RHOSO 18.0.3 (Feature Release 1) 3.2.2. Observability 3.2.2.1. New features This part describes new features and major enhancements introduced in Red Hat OpenStack Services on OpenShift 18.0. RabbitMQ metrics now in Prometheus. With this update, RabbitMQ metrics are collected and stored in Prometheus. A new dashboard for displaying these metrics was added. Jira:OSPRH-7610 Autoscaling improvements Autoscaling has been updated to use the server_group metadata. This improves the stability of the autoscaling feature. For more information, see Autoscaling for instances Jira:OSPRH-9202 3.2.2.2. Technology Previews This part provides a list of all Technology Previews available in Red Hat OpenStack Services on OpenShift 18.0. For information on the scope of support for Technology Preview features, see Technology Preview Features - Scope of Support . VM power usage monitoring (Technology Preview) With the integration of the kepler component, youi can expose the power usage of VM instances in a dashboard. Jira:OSPRH-10006 3.2.3. Compute 3.2.3.1. New features This part describes new features and major enhancements introduced in Red Hat OpenStack Services on OpenShift 18.0. vGPUs enablement This update introduces enhancements for mdev and vGPU. Jira:OSPRH-63 3.2.3.2. Bug fixes This part describes bugs fixed in Red Hat OpenStack Services on OpenShift 18.0 that have a significant impact on users. NUMA resource tracking works correctly With this release, a bug that causes NUMA resource tracking issues has been fixed. Previously, Libvirt reported all powered down CPUs on NUMA node 0 instead of on the correct NUMA node. Now, Nova caches the correct CPU topology before powering down any CPUs, fixing the resource tracking issues. Jira:OSPRH-8712 3.2.3.3. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Setting hw-architecture or architecture on Image service (glance) image does not work as expected In RHOSO 18.0, the image metadata prefilter is enabled by default. RHOSO does not support emulation of non-native architectures. As part of the introduction of emulation support upstream, the image metadata prefilter was enhanced to support the scheduling of instances based on the declared VM architecture, for example, hw_architecture=x86_64 . When nova was enhanced to support emulating non-native architecture by using image properties, a bug was introduced, because the native architecture was not reported as a trait by the virt driver. Therefore, by default, support for setting hw_architecture or architecture on an image was rendered inoperable. Workaround: To mitigate this bug, perform one of the following tasks: Unset the architecture / hw_architecture image property. RHOSO supports only one architecture, x86_64. There is no valid use case that requires this to be set for an RHOSO cloud, so all hosts will be x86_64. Disable the image metadata prefilter in the CustomServiceConfig section of the nova scheduler: Jira:OSPRH-6215 Instances with ephemeral storage on NFS share stop working after Compute service restart Compute service (nova) instances with ephemeral storage on NFS shares stop working as soon as the containerized Compute agent service restarts on the hypervisor host. That happens because of changed permissions of /var/lib/nova/instances. Workaround: Manually restore permissions to the original values and avoid the service restarts. Jira:OSPRH-10729 Compute service power management feature disabled by default The Compute service (nova) power management feature is disabled by default. You can enable it with the following nova-compute configuration: The default cpu_power_management_strategy cpu_state is currently unsupported. Restarting nova-compute causes all dedicated PCPUs on that host to be powered down, including ones used by instances. if the cpu_state strategy is used, those instances' CPUs will become unpinned. Jira:OSPRH-10772 3.2.4. Data plane 3.2.4.1. New features This part describes new features and major enhancements introduced in Red Hat OpenStack Services on OpenShift 18.0. OpenStackAnsibleEE custom resource replaced with functionality in openstack-operator Enhancement: The OpenStackAnsibleEE custom resource has been removed along with the openstack-ansibleee-operator. This functionality has been integrated into the openstack-operator to allow the direct creation of Kubernetes jobs without the unnecessary abstraction provided by the additional operator and associated custom resource. Reason: The additional abstraction was unnecessary. This change reduces the amount of code that we need to maintain, along with reducing the number of CRD's and operators running in the cluster. Result: Users can expect that there will no longer be any OpenStackAnsibleEE resources created when they deploy dataplane nodes. Instead, they will just see Kubernetes Jobs. Existing OpenStackAnsibleEE resources will remain in the cluster for posterity, or if users no longer require them for historical reference, they can be deleted. Documentation is provided to cleanup unnecessary resources and operators. Jira:OSPRH-7650 3.2.5. Networking 3.2.5.1. New features This part describes new features and major enhancements introduced in Red Hat OpenStack Services on OpenShift 18.0. Dynamic routing on data plane with FRR and BGP This update introduces support of Free Range Routing (FRR) border gateway protocol (BGP) to provide dynamic routing capabilities on the RHOSO data plane. Limitations: If you use dynamic routing, you must also use distributed virtual routing (DVR). If you use dynamic routing, you also use dedicated networker nodes. You can not use dynamic routing in an IPv6 deployment or a deployment that uses the Load-balancing service (octavia). Jira:OSPRH-9298 3.2.5.2. Technology Previews This part provides a list of all Technology Previews available in Red Hat OpenStack Services on OpenShift 18.0. For information on the scope of support for Technology Preview features, see Technology Preview Features - Scope of Support . Custom ML2 mechanism driver and SDN back end support (Technology Preview) This update introduces a Technology Preview of the ability to integrate the Networking service (neutron) with a custom ML2 mechanism driver and software defined networking (SDN) back end components, instead of the default OVN mechanism driver and back end components. Jira:OSPRH-3678 3.2.5.3. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Update to latest RHOSP 17.1 version before adopting When performing adoption of a source environment which is older than RHOSP 17.1.4, the workloads experience a prolonged network connectivity disruption. Make sure to update the source environment at least to RHOSP 17.1.4 before adopting. Jira:OSPRH-10283 octavia-operator does not enable anti affinity The Load-balancing service (octavia) does not currently configure anti-affinity settings in Nova to prevent amphora VMs from being scheduled to the same compute node. Workaround: Add the relevant setting to octavia through customConfig, as shown in the following example: Example Jira:OSPRH-10705 Adoption not supported with Load-balancing service (octavia) agents on networker nodes Adoption of deployments that have Load-balancing service agents deployed on networker nodes is currently not supported. Jira:OSPRH-10771 createDefaultLbMgmtNetwork and manageLbMgmtNetworks set to false when availability zones are defined When setting a list of availability zones in the Octavia CR (in spec.lbMgmtNetwork.availabilityZones ), the default values of the spec.lbMgmtNetwork.createDefaultLbMgmtNetwork and spec.lbMgmtNetwork.manageLbMgmtNetworks settings are incorrectly reset to false . Workaround: When setting availabilityZones to a non-empty list in spec.lbMgmtNetwork , explicity set createDefaultLbMgmtNetwork and manageLbMgmtNetworks to `true . Jira:OSPRH-11092 Adoption of combined Controller/Networker nodes not verified Red Hat has not verified a process for adoption of a RHOSP 17.1 environment where Controller and Networker roles are composed together on Controller nodes. If your RHOSP 17.1 environment does use combined Controller/Networker roles on the Controller nodes, the documented adoption process will not produce the expected results. Adoption of RHOSP 17.1 environments that use dedicated Networker nodes has been verified to work as documented. Jira:OSPRH-11301 Legacy tripleo Networking services (neutron) after adoption After edpm_tripleo_cleanup task, there are still legacy tripleo Networking service (neutron) services. These services are stopped after adoption, so the RHOSO services are not affected. Workaround: Perform the following steps to remove the legacy services manually: Jira:OSPRH-11323 3.2.6. Network Functions Virtualization 3.2.6.1. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Do not use virtual functions (VF) for the RHOSO control plane interface This RHOSO release does not support use of VFs for the RHOSO control plane interface. Jira:OSPRH-8882 Verify that the os-net-config provider `ifcfg`for any production deployment Red Hat does not currently support NMstate as the os-net-config provider . Ensure that you have the setting edpm_network_config_nmstate: false , which is the default. This ensures that your environment uses the ifcfg provider. Jira:OSPRH-11309 3.2.7. Control plane 3.2.7.1. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Control plane temporarily unavailable during minor update During the minor update to 18.0 Feature Release 1, the Red Hat OpenStack Platform control plane temporarily becomes unavailable. API requests might fail with HTTP error codes, such as error 500. Alternatively, the API requests might succeed but the underlying life cycle operation fails. For example, a virtual machine (VM) created with the openstack server create command during the minor update never reaches the ACTIVE state. The control plane outage is temporary and automatically recovers after the minor update is finished. The control plane outage does not affect the already running workload. Jira:OSPRH-10790 3.2.8. High availability 3.2.8.1. Technology Previews This part provides a list of all Technology Previews available in Red Hat OpenStack Services on OpenShift 18.0. For information on the scope of support for Technology Preview features, see Technology Preview Features - Scope of Support . Instance high availability RHOSO 18.0.3 (Feature Release 1) introduces a technology preview of instance high availability (instance HA). With instance HA, RHOSO can automatically evacuate and re-create instances on a different Compute node when a Compute node fails. To use the instance HA technology preview in a test environment, see https://access.redhat.com/articles/7094761 . Do not use this technology preview in a production environment. Jira:OSPRH-9902 3.2.8.2. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Possible database error before adoption You might see a database error for system table mysql.proc if you run mysqlcheck before adopting the OSP database. This error message is harmless and results from a system table's redo log that was not replicated correctly when the galera cluster was bootstrapped. Workaround: You can remove the error by repairing the mysql.proc system table: Example command Example output The table and its redo log are fixed and replicated across all galera nodes. Re-run the mysqlcheck and continue the adoption procedure. Jira:OSPRH-10783 3.2.9. Storage 3.2.9.1. New features This part describes new features and major enhancements introduced in Red Hat OpenStack Services on OpenShift 18.0. Decommission a manilaShare back end You can now decommission a manilaShare back end from RHOSO. When you delete a manila-share , a clean-up job runs to clean up the service list for the Shared File Systems service (manila). The output of the openstack share pool list command does not reflect storage pool changes. To update and display the latest statistics, you must restart the scheduler service. Perform the restart during scheduled downtime because it causes a minor disruption. Jira:OSPRH-1099 Rebuilding volume-backed server This release adds the support to rebuild a volume-backed server with the same or different image. Jira:OSPRH-1391 Migrate director-deployed Ceph cluster to external Ceph cluster With this update, after adoption from RHOSP 17.1 to a RHOSO 18.0 data plane, you can migrate a Director deployed Ceph cluster and turn it into an external Ceph cluster. The Ceph daemons deployed on the Controller nodes are migrated to a set of target nodes. Jira:OSPRH-8369 Shared File Systems service (manila) support for VAST Data Platform The Shared File Systems service now includes a storage driver to support VAST Data Platform. The driver allows provisioning and management of NFS shares and point-in-time backups through snapshots. Jira:OSPRH-8821 Block Storage service (cinder) volume deletion With this release, the Block Storage service RBD driver takes advantage of recent Ceph developments to allow RBD volumes to meet normal volume deletion expectations. In releases, when the Block Storage service used an RBD (Ceph) volume back end, it was not always possible to delete a volume. Jira:OSPRH-9477 3.2.9.2. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. extraMounts propagation to instance does not work when uniquePodNames is true When uniquePodNames is true , every Cinder Pod (and in general each component and service) is prefixed by a pseudo-random string. This affects the per-instance propagation, because the legacy method, based on strings.TrimPrefix , is not valid anymore. In a DCN deployment, Red Hat recommends propagating secrets to pods by matching the instance AZ name. Example 1 results in pods whose names match az0 getting the secret ceph-conf-az-0, pods whose names match az1 getting the secret ceph-conf-az-0, and so on. Example 1 works for Glance pods but only works for Cinder pods if uniquePodNames is false . Workaround: Set uniquePodNames to false as shown in Example 2, until this bug is resolved. The uniquePodNames setting is only needed if the storage backend uses NFS. Example 1 Example 2 Jira:OSPRH-11240 3.2.10. Upgrades and updates 3.2.10.1. New features This part describes new features and major enhancements introduced in Red Hat OpenStack Services on OpenShift 18.0. os-diff tool identifies differences between source 17.1 and adopted RHOSO environments RHOSO ships the os-diff tool , which can help the operator find differences between the source OSP 17.1 environment configuration and the adopted RHOSO environment configuration. Jira:OSPRH-1490 Baremetal adoption You can now adopt baremetal OSP 17.1 environments into RHOSO environments. Jira:OSPRH-2428 Adoption roll-back You can now roll back a failed adoption of a RHOSP 17.1 control plane. Jira:OSPRH-7817 3.2.10.2. Bug fixes This part describes bugs fixed in Red Hat OpenStack Services on OpenShift 18.0 that have a significant impact on users. Erroneous error messages no longer generated Previously, the Keystone services and endpoints clean up step in the adoption procedure generated false errors when some services weren't deployed in the source cloud. The false errors are not generated anymore. Jira:OSPRH-10174 3.3. Release information RHOSO 18.0.2 3.3.1. Advisory list This release of Red Hat OpenStack Services on OpenShift (RHOSO) includes the following advisories: RHBA-2024:8151 Release of containers for RHOSO 18.0.2 RHBA-2024:8152 Release of components for RHOSO 18.0.2 RHBA-2024:8153 Control plane Operators for RHOSO 18.02 RHBA-2024:8154 Data plane Operators for RHOSO 18.0.2 RHBA-2024:8155 Release of components for RHOSO 18.0.2 3.3.2. Compute 3.3.2.1. Bug fixes This part describes bugs fixed in Red Hat OpenStack Services on OpenShift 18.0 that have a significant impact on users. Fix for instances created before OpenStack Victoria In OpenStack Victoria, the instance_numa_topology object was extended to enable mix cpus (pinned and unpinned cpus) in the same instance. Object conversion code was added to handle upgrades but did not account for flavors that have either hw:mem_page_size or hw:numa_nodes set with hw:cpu_policy not set to dedicated As a result instances created before the victoria release could not be started after an upgrade to victoria. With this update, non-pinned numa instances can be managed after an FFU from 16.2. Jira:OSPRH-10183 3.3.2.2. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Setting hw-architecture or architecture on Image service (glance) image does not work as expected In RHOSO 18.0, the image metadata prefilter is enabled by default. RHOSO does not support emulation of non-native architectures. As part of the introduction of emulation support upstream, the image metadata prefilter was enhanced to support the scheduling of instances based on the declared VM architecture, for example, hw_architecture=x86_64 . When nova was enhanced to support emulating non-native architecture by using image properties, a bug was introduced, because the native architecture was not reported as a trait by the virt driver. Therefore, by default, support for setting hw_architecture or architecture on an image was rendered inoperable. Workaround: To mitigate this bug, perform one of the following tasks: Unset the architecture / hw_architecture image property. RHOSO supports only one architecture, x86_64. There is no valid use case that requires this to be set for an RHOSO cloud, so all hosts will be x86_64. Disable the image metadata prefilter in the CustomServiceConfig section of the nova scheduler: Jira:OSPRH-6215 Compute service power management feature disabled by default The Compute service (nova) power management feature is disabled by default. You can enable it with the following nova-compute configuration: The default cpu_power_management_strategy cpu_state is not supported at the moment due to a bug that causes NUMA resource tracking issues, as all disabled CPUs are reported on NUMA node 0 instead of on the correct NUMA node. Jira:OSPRH-8712 QEMU process failure A paused instance that uses local storage cannot be live migrated more than once. The second migration causes the QEMU process to crash and nova puts the instance to ERROR state. Workaround : if feasible, unpause the instance temporarily, then pause it again before the second live migration. It is not always feasible to unpause an instance. For example, suppose the instance uses a multi-attach cinder volume, and pause is used to limit the access to that volume to a single instance while the other is kept in paused state. In this case, unpausing the instance is not a feasible workaround. Jira:OSPRH-8699 3.3.3. Data plane 3.3.3.1. Bug fixes This part describes bugs fixed in Red Hat OpenStack Services on OpenShift 18.0 that have a significant impact on users. The value for edpm_kernel_hugepages is reliably set on the kernel command line. Before this update, the value for edpm_kernel_hugepages could be missing from the kernel commandline due to an an error in an ansible role that configures it. With this update, this problem is resolved, and no work arounds are required. Jira:OSPRH-10007 3.3.4. Networking 3.3.4.1. Bug fixes This part describes bugs fixed in Red Hat OpenStack Services on OpenShift 18.0 that have a significant impact on users. Metadata rate-limiting feature This update fixes a bug that prevented successful use of metadata rate-limiting. Metadata rate limiting is now available. Jira:OSPRH-9569 3.3.4.2. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Router deletion problem and workaround After an update to RHOSO 18.0.2, you cannot delete a pre-existing router as expected. The following error is displayed in the CLI: Also, the Neutron API logs include the following exception message: Workaround: Manually create a database register. In a SQL CLI: Jira:OSPRH-10537 3.3.5. Network Functions Virtualization 3.3.5.1. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Do not use virtual functions (VF) for the RHOSO control plane interface This RHOSO release does not support use of VFs for the RHOSO control plane interface. Jira:OSPRH-8882 3.3.6. Storage 3.3.6.1. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. OpenStack command output does not account for storage pool changes in the Shared File Systems service (manila) The openstack share pool list command output does not account for storage pool changes, for example, changes to pool characteristics on back end storage systems, or removal of existing pools from the deployment. Provisioning operations are not affected by this issue. Workaround: Restart the scheduler service to reflect the latest statistics. Perform the restart during scheduled downtime because it causes a minor disruption. Jira:OSPRH-1099 3.4. Release information RHOSO 18.0.1 3.4.1. Advisory list This release of Red Hat OpenStack Services on OpenShift (RHOSO) includes the following advisories: RHBA-2024:6773 Release of containers for RHOSO 18.0.1 RHBA-2024:6774 Release of components for RHOSO 18.0.1 RHBA-2024:6775 Moderate: Red Hat OpenStack Platform 18.0 (python-webob) security update RHBA-2024:6776 Control plane Operators for RHOSO 18.0.1 RHBA-2024:6777 Data plane Operators for RHOSO 18.0.1 RHBA-2024:6778 Data plane Operators for RHOSO 18.0.1 3.4.2. Compute 3.4.2.1. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Setting hw-architecture or architecture on Image service (glance) image does not work as expected In RHOSO 18.0, the image metadata prefilter is enabled by default. RHOSO does not support emulation of non-native architectures. As part of the introduction of emulation support upstream, the image metadata prefilter was enhanced to support the scheduling of instances based on the declared VM architecture, for example, hw_architecture=x86_64 . When nova was enhanced to support emulating non-native architecture by using image properties, a bug was introduced, because the native architecture was not reported as a trait by the virt driver. Therefore, by default, support for setting hw_architecture or architecture on an image was rendered inoperable. Workaround: To mitigate this bug, perform one of the following tasks: Unset the architecture / hw_architecture image property. RHOSO supports only one architecture, x86_64. There is no valid use case that requires this to be set for an RHOSO cloud, so all hosts will be x86_64. Disable the image metadata prefilter in the CustomServiceConfig section of the nova scheduler: Jira:OSPRH-6215 Compute service power management feature disabled by default The Compute service (nova) power management feature is disabled by default. You can enable it with the following nova-compute configuration: The default cpu_power_management_strategy cpu_state is not supported at the moment due to a bug that causes NUMA resource tracking issues, as all disabled CPUs are reported on NUMA node 0 instead of on the correct NUMA node. Jira:OSPRH-8712 QEMU process failure A paused instance that uses local storage cannot be live migrated more than once. The second migration causes the QEMU process to crash and nova puts the instance to ERROR state. Workaround : if feasible, unpause the instance temporarily, then pause it again before the second live migration. It is not always feasible to unpause an instance. For example, suppose the instance uses a multi-attach cinder volume, and pause is used to limit the access to that volume to a single instance while the other is kept in paused state. In this case, unpausing the instance is not a feasible workaround. Jira:OSPRH-8699 3.4.3. Data plane 3.4.3.1. Bug fixes This part describes bugs fixed in Red Hat OpenStack Services on OpenShift 18.0 that have a significant impact on users. Using the download-cache service no longer prevents Podman from pulling images for data plane deployment Before this bug fix, if you included download-cache service in spec.services of the OpenStackDataPlaneNodeSet , a bug prevented Podman from pulling container images that are required by the data plane deployment. With this bug fix, you can include download-cache service in spec.services of the OpenStackDataPlaneNodeSet and doing so does not prevent Podman from pulling the required container images. Jira:OSPRH-9500 3.4.3.2. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Set edpm_kernel_args variable if you configure the Ansible variable edpm_kernel_hugepages To configure the Ansible variable edpm_kernel_hugepages in the ansibleVars section of an OpenStackDataPlaneNodeSet CR, you must also set the edpm_kernel_args variable. If you do not need to configure edpm_kernel_args with a particular value, then set it to an empty string: Jira:OSPRH-10007 3.4.4. Networking 3.4.4.1. New features This part describes new features and major enhancements introduced in Red Hat OpenStack Services on OpenShift 18.0. Support for security group logging on Compute nodes With this update, when security group logging is enabled, RHOSO writes logs to the data plane node that hosts the project instance. In the /var/log/messages file, each log entry contains the string, acl_log . Jira:OSPRH-9248 3.4.4.2. Bug fixes This part describes bugs fixed in Red Hat OpenStack Services on OpenShift 18.0 that have a significant impact on users. Fixed delay between the oc patch command and update of OVN databases Before this update, custom configuration settings applied with the oc patch command did not affect the Networking service (neutron) OVN databases until 10 minutes passed. This update eliminates the delay. Jira:OSPRH-9035 MAC_Binding aging functionality added back in RHOSO 18.0.1 The MAC_Binding aging functionality that was added in OSP 17.1.2 was missing from 18.0 GA. This update to RHOSO 18.0.1 adds it back. Jira:OSPRH-8716 3.4.4.3. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Delayed OVN database update after oc patch command Any custom configuration settings applied with the oc patch command do not affect the Networking service OVN databases until 10 minutes have passed. Workaround: After you replace old pods by using the oc patch command, use the oc delete pod command to delete the new neutron pods. The pod deletion forces a new configuration to be set without the delay issue. Jira:OSPRH-7998 Metadata rate-limiting feature Metadata rate-limiting is not available in RHOSO 18.0.1. A fix is in progress. Jira:OSPRH-9569 3.4.5. Network Functions Virtualization 3.4.5.1. Bug fixes This part describes bugs fixed in Red Hat OpenStack Services on OpenShift 18.0 that have a significant impact on users. DPDK bonds are now validated in os-net-config Previously, when OVS or DPDK bonds were configured with a single port, no error was reported despite the ovs bridge not being in the right state. With this update os-net-config reports an error if the bond has a single interface. Jira:OSPRH-9307 3.4.5.2. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Do not use virtual functions (VF) for the RHOSO control plane interface This RHOSO release does not support use of VFs for the RHOSO control plane interface. Jira:OSPRH-8882 3.4.6. Storage 3.4.6.1. Bug fixes This part describes bugs fixed in Red Hat OpenStack Services on OpenShift 18.0 that have a significant impact on users. Image import no longer remains in importing state after conversion with ISO image format Before this update, when you used image conversion with the ISO image format, the image import operation remained in an "importing" state. Now the image import operation does not remain in an "importing" state. Jira:OSPRH-8580 3.5. Release information RHOSO 18.0 GA 3.5.1. Advisory list This release of Red Hat OpenStack Services on OpenShift (RHOSO) includes the following advisories: RHEA-2024:5245 Release of components for RHOSO 18.0 RHEA-2024:5246 Release of containers for RHOSO 18.0 RHEA-2024:5247 Data plane Operators for RHOSO 18.0 RHEA-2024:5248 Control plane Operators for RHOSO 18.0 RHEA-2024:5249 Release of components for RHOSO 18.0 3.5.2. Observability 3.5.2.1. New features This part describes new features and major enhancements introduced in Red Hat OpenStack Services on OpenShift 18.0. Deploy metric storage with Telemetry Operator The Telemetry Operator now supports deploying and operating Prometheus by using the cluster-observability-operator through a MonitoringStack resource. Jira:OSPRH-1896 Expanded interaction with metrics and alarms You can now use the openstack metric and openstack alarm commands in the OpenStack CLI to interact with metrics and alarms. These commands are useful for troubleshooting. Jira:OSPRH-2892 Ceilometer uses TCP publisher to expose data for Prometheus Ceilometer can now use the TCP publisher to publish metric data to sg-core, which exposes them for scraping by Prometheus. Jira:OSPRH-2957 Prometheus replaces Gnocchi for metrics storage and metrics-based autoscaling In RHOSO 18.0, Prometheus replaces Gnocchi for metrics and metrics-based autoscaling. Jira:OSPRH-3057 Compute node log collection RHOSO uses the Cluster Logging Operator ( cluster-logging-operator ) to collect and centrally store logs from OpenStack Compute nodes. Jira:OSPRH-802 Graphing dashboards for OpenStack metrics The Red Hat OpenShift Container Platform (RHOCP) console UI now provides graphing dashboards for OpenStack Metrics. Jira:OSPRH-824 3.5.3. Compute 3.5.3.1. New features This part describes new features and major enhancements introduced in Red Hat OpenStack Services on OpenShift 18.0. The compute service now supports native Secure RBAC In osp 17.1 secure role-based access control was implemented using custom policy. In RHOSO-18.0.0 this is implemented using nova native support for SRBAC. As a result all OpenStack deployments support the ADMIN, MEMBER and READER roles by default. Jira:OSPRH-1505 Setting the hostname of the Compute service (nova) instance by using the Compute service API microversions 2.90 and 2.94 This enhancement enables you to set the hostname of the Compute service (nova) instance by using the Compute service API microversions 2.90 and 2.94 that are now included in the 18.0 release of RHOSO. API microversion 2.90 enables you to specify an optional hostname when creating, updating, or rebuilding an instance. This is a short name (without periods), and it appears in the metadata available to the guest OS, either through the metadata API or on the configuration drive. If installed and configured in the guest, cloud-init uses this optional hostname to set the guest hostname. API microversion 2.94 extends microversion 2.90 by enabling you to specify fully qualified domain names (FQDN) wherever you specify the hostname. When using an FQDN as the instance hostname, you must set the [api]dhcp_domain configuration option to the empty string in order for the correct FQDN to appear in the hostname field in the metadata API. Jira:OSPRH-17 Manage dedicated CPU power state You can now configure the nova-compute service to manage dedicated CPU power state by setting [libvirt]cpu_power_management to True. This feature requires the Compute service to be set with [compute]cpu_dedicated_set. With that setting, all dedicated CPUs are powered down until they are used by an instance. They are powered up when an instance using them is booted. If power management is configured but [compute]cpu_dedicated_set isn't set, then the compute service will not start. By default, the power strategy offlines CPUs when powering down and onlines the CPUs on powering up, but another strategy is possible. Set [libvirt]cpu_power_management_strategy=governor to instead use governors, and use [libvirt]cpu_power_governor_low [libvirt]cpu_power_governor_high to direct which governors to use in online and offline mode (performance and powersave). Jira:OSPRH-18 Evacuate to STOPPED with v2.95 Starting with the v2.95 micro version, any evacuated instance will be stopped at the destination. Operators can still continue using the behaviour by selecting a microversion below v2.95. Prior to v2.95, if the VM was active prior to the evacuation, it was restored to the active state following a failed evacuation. If the workload encountered I/O corruption as a result of the hypervisor outage, this could potentially make recovery effort harder or cause further issues if the workload was a clustered application that tolerated the failure of a single VM. For this reason, it is considered safer to always evacuate to Stopped and allow the tenant to decide how to recover the VM. Jira:OSPRH-184 Compute service hostname change If you start the Compute service (nova) and your Compute host detects a name change, you must know the reason for the change of the host names. When you resolve the issue, you must restart the Compute service. Jira:OSPRH-20 Create a neutron port without an IP address if the port requires only L2 network connectivity You can now create an instance with a non-deferred port that has no fixed IP address if the network back end has L2 connectivity. In releases of RHOSP, all neutron ports were required to have a IP address. The IP address assignment could be immediate (default) or deferred for L3 routed networks. In RHOSO 18.0, that requirement has been removed. You can now create a neutron port without an IP address if the port requires only L2 network connectivity. To use this feature, set ip_allocation = 'none' on the neutron port before passing it to nova to use when creating a VM instance or attaching the port to an existing instance. Jira:OSPRH-57 New enlightenments to the libvirt XML for Windows guests in RHOSO 18.0.0 This update adds the following enlightenments to the libvirt XML for Windows guests: vpindex runtime synic reset frequencies tlbflush ipi This adds to the list of existing enlightenments: relaxed vapic spinlocks retries vendor_id spoofing Jira:OSPRH-58 New default for managing instances on NUMA nodes In RHOSP 17.1.4, the default was to pack instances on NUMA nodes. In RHOSO 18.0, the default has been changed to balance instances across NUMA nodes. To change the default, and pack instances on NUMA nodes, set in both the scheduler and compute node nova.conf Jira:OSPRH-59 Rebuild a volume-backed instance with a different image This update adds the ability to rebuild a volume-backed instance from a different image. Before this update, you could only rebuild a volume-backed instance from the original image in the boot volume. Now you can rebuild the instance after you have reimaged the boot volume on the cinder side. This feature requires API microversion 2.93 or later. Jira:OSPRH-66 Archive 'task_log' database records This enhancement adds the --task-log option to the nova-manage db archive_deleted_rows CLI. When you use the --task-log option, the task_log table records get archived while archiving the database. This option is the default in the nova-operator database purge cron job. Previously, there was no method to delete the task_log table without manual database modification. You can use the --task-log option with the --before option for records that are older than a specified <date> . The updated_at field is compared to the specifed <date> to determine the age of a task_log record for archival. If you configure nova-compute with [DEFAULT]instance_usage_audit = True , the task_log database table maintains an audit log of --task-log use. Jira:OSPRH-68 Support for virtual IOMMU device The Libvirt driver can add a virtual IOMMU device to guests. This capability applies to x86 hosts that use the Q35 machine type. To enable the capability, provide the hw:viommu_model extra spec or equivalent image metadata property hw_viommu_model .The following values are supported: intel , smmuv3 , virtio , auto . The default value is auto , which automatically selects virtio . Note Due to the possible overhead introduced with vIOMMU, enable this capability only for required workloads. Jira:OSPRH-69 More options for the server unshelve command With this update, new options are added to the server unshelve command in RHOSO 18.0.0. The --host option allows adminstirators to specify a destination host. The --no-availability-zone option allows administrators to specify the availability zone. Both options require the server to be in the SHELVED_OFFLOADED state and the Compute API version to be 2.91 or greater. Jira:OSPRH-74 Support for the bochs libvirt video model This release adds the ability to use the bochs libvirt video model. The bochs libvirt video model is a legacy-free video model that is best suited for UEFI guests. In some cases, it can be usable for BIOS guests, such as when the guest does not depend on direct VGA hardware access. Jira:OSPRH-76 Schedule archival and purge of deleted rows from Compute service (nova) cells The nova-operator now schedules a periodic job for each Compute service (nova) cell to archive and purge the deleted rows from the cell database. The frequency of the job and the age of the database rows to archive and purge can be fine tuned in the {{OpenStackControlPlane.spec.nova.template.cellTemplates[].dbPurge}} structure for each cell in the cellTemplates. Jira:OSPRH-86 3.5.3.2. Bug fixes This part describes bugs fixed in Red Hat OpenStack Services on OpenShift 18.0 that have a significant impact on users. Migrating paused instance no longer generates error messages Before this update, live migration of a paused instance with live_migration_permit_post_copy=True in nova.conf caused the libvirt driver to erroneously generate error messages similar to [1]. Now the error message is not generated when you live migrate a paused instance with live_migration_permit_post_copy=True. [1] Error message example: "Live Migration failure: argument unsupported: post-copy migration is not supported with non-live or paused migration: libvirt.libvirtError: argument unsupported: post-copy migration is not supported with non-live or paused migration." Jira:OSPRH-41 No network block device (NBD) live migration with TLS enabled In RHOSO 18.0 Beta, a bug prevents you from using network block device (NBD) to live migrate storage between Compute nodes with TLS enabled. See https://issues.redhat.com/browse/OSPRH-6931 . This has now been resolved and live migration with TLS enabled is supported with local storage. Jira:OSPRH-6740 Cannot delete instance when cpu_power_managment is set to true in the rhos-18.0.0 beta release, a known issue was discovered preventing the deletion of an instance shortly after it was created if power management was enabled. This has now been fixed in the rhoso-18.0.0 release Jira:OSPRH-7103 3.5.3.3. Technology Previews This part provides a list of all Technology Previews available in Red Hat OpenStack Services on OpenShift 18.0. For information on the scope of support for Technology Preview features, see Example . Technology preview of PCI device tracking in Placement service RHOSO 18.0.0 introduces a technology preview of the ability to track PCI devices in the OpenStack Placement service. Tracking PCI devices in the Placement service enables you to use granular quotas on PCI devices when combined with the Unified Limits Technology Preview. PCI tracking in the Placement service is disabled by default and is limited to flavor-based PCI passthrough. Support for the Networking service (neutron) SRIOV ports is not implemented, but is required before this feature is fully supported. Jira:OSPRH-19 Use of Identity service (Keystone) unified limits in the Compute service (nova) This RHOSO release supports Identity service unified limits in the Compute service. Unified limits centralize management of resource quota limits in the Identity service (Keystone) and enable flexibility for users to manage quota limits for any Compute service resource being tracked in the Placement service. Jira:OSPRH-70 3.5.3.4. Removed functionality This part provides an overview of functionality that has been removed in Red Hat OpenStack Services on OpenShift 18.0. Removed functionality is no longer supported in this product and is not recommended for new deployments. Keypair generation removed from RHOSO 18 Keypair generation was deprecated in RHOSP 17 and has been removed from RHOSO 18. Now you need to precreate the keypair by the SSH command line tool ssh-keygen and then pass the public key to the nova API. Jira:OSPRH-67 i440fx PC machine type no longer tested or supported In RHOSP 17, the i440fx PC machine type, pc-i440fx, was deprecated and Q35 became the default machine type for x86_64. In RHOSP 18, the i440fx PC machine type is no longer tested or supported. The i440fx PC machine type is still available for use under a support exception for legacy applications that cannot function with the Q35 machine type. If you have such a workload, contact Red Hat support to request a support exception. With the removal of support for the i440fx PC machine type from RHOSP, you cannot use pc-i440fx to certify VNFs or third-party integrations. You must use the Q35 machine type. Jira:OSPRH-7373 Unsupported: vDPA and Hardware offload OVS are unsupported Hardware offload OVS consists of processing network traffic in hardware with the kernel swtichdev and tcflower protocols. vDPA extends Hardware offload OVS by providing a vendor-neutral virtio net interface to the guest, decoupling the workload from the specifics fo the host hardware instead of presenting a vendor-specific virtual function. Both Hardware offload OVS and vDPA are unsupported in RHOSO 18.0 with no upgrade path available for existing users. At this time there is no plan to reintroduce this functionality or continue to invest in new features related to vdpa or hardware offloaded ovs. If you have a business requirement for these removed features, please reach out to Red Hat support or your partner and Technical Account Manager so that Red Hat can reassess the demand for these features for a future RHOSO release. Jira:OSPRH-7829 3.5.3.5. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Setting hw-architecture or architecture on Image service (glance) image does not work as expected In RHOSO 18.0, the image metadata prefilter is enabled by default. RHOSO does not support emulation of non-native architectures. As part of the introduction of emulation support upstream, the image metadata prefilter was enhanced to support the scheduling of instances based on the declared VM architecture, for example hw_architecture=x86_64 . When nova was enhanced to support emulating non-native architecture via image properties, a bug was introduced, because the native architecture was not reported as a trait by the virt driver. Therefore, by default, support for setting hw_architecture or architecture on an image was rendered inoperable. To mitigate this bug, you have two choices: Unset the architecture / hw_architecture image property. RHOSO supports only one architecture, x86_64. There is no valid use case that requires this to be set for an RHOSO cloud, so all hosts will be x86_64. Disable the image metadata prefilter in the CustomServiceConfig section of the nova scheduler: Jira:OSPRH-6215 QEMU process failure A paused instance that uses local storage cannot be live migrated more than once. The second migration causes the QEMU process to crash and nova puts the instance to ERROR state. Workaround : if feasible, unpause the instance temporarily then pause it again before the second live migration. It is not always feasible to unpause an instance. For example, suppose the instance uses a multi-attach cinder volume, and pause is used to limit the access to that volume to a single instance while the other is kept in paused state. In this case, unpausing the instance is not a feasible workaround. Jira:OSPRH-8699 Compute service power management feature disabled by default The Compute service (nova) power management feature is disabled by default. You can enable it with the following nova-compute configuration. The default cpu_power_management_strategy cpu_state is not supported at the moment due to a bug that causes NUMA resource tracking issues, as all disable CPUs are reported on NUMA node 0 instead of on the correct NUMA node. Jira:OSPRH-8712 3.5.4. Data plane 3.5.4.1. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Using the download-cache service prevents Podman from pulling images for data plane deployment Do not list the download-cache service in spec.services of the OpenStackDataPlaneNodeSet . If you list download-cache in OpenStackDataPlaneNodeSet , Podman can not pull the container images required by the data plane deployment. Workaround: Omit the download-cache service from the default services list in OpenStackDataPlaneNodeSet . Jira:OSPRH-9500 3.5.5. Hardware Provisioning 3.5.5.1. Bug fixes This part describes bugs fixed in Red Hat OpenStack Services on OpenShift 18.0 that have a significant impact on users. Increased EFI partition size Before RHOSP 17.1.4, the EFI partition size of an overcloud node was 16MB. With this update, the image used for provisioned EDPM nodes now has an EFI partition size of 200MB to align with RHEL and to accommodate firmware upgrades. Jira:OSPRH-6691 3.5.6. Networking 3.5.6.1. New features This part describes new features and major enhancements introduced in Red Hat OpenStack Services on OpenShift 18.0. Octavia Operator availability zones The Octavia Management network created and managed by the Octavia operator requires that the OpenStack routers and networks are scheduled on the OVN controller on the OpenShift worker nodes. If the OpenStack Networking Service (neutron) is configured with non-default availability zones, the OVN controller pod on the OpenShift worker and Octavia must be configured with the same availability zone. Example: Jira:OSPRH-6901 3.5.6.2. Bug fixes This part describes bugs fixed in Red Hat OpenStack Services on OpenShift 18.0 that have a significant impact on users. OVN pod no longer goes into loop due to NIC Mapping When using a large number of NIC mappings, OVN could go into a creation loop. This is now fixed Jira:OSPRH-7480 3.5.6.3. Technology Previews This part provides a list of all Technology Previews available in Red Hat OpenStack Services on OpenShift 18.0. For information on the scope of support for Technology Preview features, see Technology Preview Features - Scope of Support . QoS minimum bandwidth policy (technology preview) In RHOSO 18.0.0, a technology preview is available for the Networking service (neutron) for QoS minimum bandwidth for placement reporting and scheduling. Jira:OSPRH-507 Load-balancing service (Octavia) support of multiple VIP addresses This update adds a technology preview of support for multiple VIP addresses allocated from the same Neutron network for the Load-balancing service. You can now specify additional subnet_id/ip_address pairs for the same VIP port. This makes it possible to configure the Load-balancing service with both IPv4 and IPv6 exposed to both public and private subnets. Jira:OSPRH-2154 3.5.6.4. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Delayed OVN database update after oc patch command Any custom configuration settings applied with 'oc patch ... ' command do not affect neutron ovn databases until 10 minutes have passed. Workaround: After you replace old pods using the oc patch ... command, delete the new neutron pod(s) manually using oc delete pod ... command. The pod deletion forces a new configuration to be set without the delay issue. Jira:OSPRH-7998 MAC_Binding aging functionality missing in RHOSO 18.0.0 The MAC_Binding aging functionality that was added in OSP 17.1.2 is missing from 18.0 GA. A fix is in progress. Jira:OSPRH-8716 10-minute delay between 'oc patch`command and update of OVN databases Custom configuration settings applied with the 'oc patch' command do not affect the Networking service (neutron) OVN databases until 10 minutes have passed. Workaround: After the old Networking service pods are replaced new pods after an 'oc patch' command operation, delete the new Networking service pods manually using the 'oc delete pod' command. This deletion forces a new configuration to be set without the delay issue. Jira:OSPRH-9035 Metadata rate-limiting feature Metadata rate-limiting is not available in RHOSO 18.0.0. A fix is in progress. Jira:OSPRH-9569 3.5.7. Network Functions Virtualization 3.5.7.1. New features This part describes new features and major enhancements introduced in Red Hat OpenStack Services on OpenShift 18.0. AMD CPU powersave profiles A power save profile, cpu-partitioning-powersave, was introduced in Red Hat Enterprise Linux 9 (RHEL 9), and made available in Red Hat OpenStack Platform (RHOSP) 17.1.3. This TuneD profile is the base building block for saving power in NFV environments. RHOSO 18.0 adds cpu-partitioning-powersave support for AMD CPUs. Jira:OSPRH-2268 3.5.7.2. Bug fixes This part describes bugs fixed in Red Hat OpenStack Services on OpenShift 18.0 that have a significant impact on users. Physical function (PF) MAC address now matches between VM instances and SR-IOV physical functions (PFs) This update fixes a bug that caused a PF MAC address mismatch between VM instances and SR-IOV PFs (Networking service ports with vnic-type set to direct-physical ). In the RHOSO 18.0 Beta release, a bug in the Compute service (nova) prevented the MAC address of SR-IOV PFs from being updated correctly when attached to a VM instance. Now the MAC address of the PF is set on the corresponding neutron port. Jira:OSPRH-7085 3.5.7.3. Technology Previews This part provides a list of all Technology Previews available in Red Hat OpenStack Services on OpenShift 18.0. For information on the scope of support for Technology Preview features, see Example . In RHOSO 18.0, a technology preview is available for the nmstate provider back-end in os-net-config . This technology preview of nmstate and NIC hardware offload has known issues that make it unsuitable for production use. For production, use the openstack-network-scripts package rather than nmstate and NetworkManager. There is a production-ready native nmstate mode you can select during installation, but network configuration, which must be provided in nmstate format, is not backwards-compatible with templates from TripleO. It also lacks certain features that os-net-config provides, such as NIC name mapping or DSCP configuration. Jira:OSPRH-2273 Data Center Bridge (DCB)-based QoS settings technology preview Specific to port/interface, DCB-based QoS settings are now available as a technology preview as part of the os-net-config tool's network configuration template. For more information, see this knowledge base article: https://access.redhat.com/articles/7062865 Jira:OSPRH-2889 3.5.7.4. Deprecated functionality This part provides an overview of functionality that has been deprecated in Red Hat OpenStack Services on OpenShift 18.0. Deprecated functionality will likely not be supported in future major releases of this product and is not recommended for new deployments. TimeMaster service is deprecated in RHOSO 18.0 In RHOSO 18.0, support for the TimeMaster service is deprecated. Bug fixes and support are provided through the end of the RHOSO 18.0 lifecycle, but no new feature enhancements will be made. Jira:OSPRH-8244 3.5.7.5. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Do not use virtual functions (VF) for the RHOSO control plane interface This RHOSO release does not support use of VFs for the RHOSO control plane interface. Jira:OSPRH-8882 Bonds require minimum of two interfaces If you configure an OVS or DPDK bond, always configure at least two interfaces. Bonds with only a single interface do not function as expected. Jira:OSPRH-9307 3.5.8. High availability 3.5.8.1. New features This part describes new features and major enhancements introduced in Red Hat OpenStack Services on OpenShift 18.0. Password rotation This update introduces the ability to generate and rotate OpenStack database passwords. Jira:OSPRH-92 3.5.9. Storage 3.5.9.1. New features This part describes new features and major enhancements introduced in Red Hat OpenStack Services on OpenShift 18.0. Shared File Systems support for scaleable CephFS-NFS The Shared File Systems service (manila) now supports a scaleable CephFS-NFS service. In earlier releases of Red Hat OpenStack Platform, only active/passive high-availability that was orchestrated with Director, using Pacemaker/Corosync, was supported. With this release, deployers can create active/active clusters of CephFS-NFS and integrate these clusters with the Shared File Systems service for improved scalability and high availability for NFS workloads. Jira:OSPRH-1024 Block Storage service (cinder) volume deletion With this release, the Block Storage service RBD driver takes advantage of recent Ceph developments to allow RBD volumes to meet normal volume deletion expectations. In releases, when the Block Storage service used an RBD (Ceph) volume back end, it was not always possible to delete a volume. Jira:OSPRH-1777 project_id in API URLs now optional You are no longer required to include project_id in Block Storage service (cinder) API URLs. Jira:OSPRH-1787 Dell PowerStore storage systems driver A new share driver has been added to support Dell PowerStore storage systems with the Shared File Systems service (Manila) service. Jira:OSPRH-4425 Dell PowerFlex storage systems driver A new share driver has been added to support Dell PowerFlex storage systems with the Shared File Systems service (Manila) service. Jira:OSPRH-4426 openstack-must-gather SOS report support You can now collect diagnostic information about your RHOSO deployment using the openstack-must-gather. You can retrieve SOS reports for both the RHOCP control plane and RHOSO data plane nodes using a single command, and options are available to dump specific information related to a particular deployed service. Jira:OSPRH-866 3.5.9.2. Bug fixes This part describes bugs fixed in Red Hat OpenStack Services on OpenShift 18.0 that have a significant impact on users. Key Manager service configuration fix enables Image service image signing and verification With this fix, the Image service (glance) is automatically configured to interact with the Key Manager service (barbican), and you can now perform encrypted image signing and verification. Jira:OSPRH-7155 Fixed faulty share creation in the NetApp ONTAP driver when using SVM scoped accounts Due to a faulty kerberos enablement check upon shares creation, the NetApp ONTAP driver failed to create shares when configured with SVM scoped accounts. A fix has been committed to openstack-manila and shares creation should work smoothly. Jira:OSPRH-8044 3.5.9.3. Technology Previews This part provides a list of all Technology Previews available in Red Hat OpenStack Services on OpenShift 18.0. For information on the scope of support for Technology Preview features, see Technology Preview Features - Scope of Support . Deployment and scale of Object Storage service This feature allows for the deployment and scale of Object Storage service (swift) data on data plane nodes. This release of the feature is a technology preview. Jira:OSPRH-1307 3.5.9.4. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. RGW does not pass certain Tempest object storage metadata tests Red Hat OpenStack Services on OpenShift 18.0 supports Red Hat Ceph Storage 7. Red Hat Ceph Storage 7 RGW does not pass certain Tempest object storage metadata tests as tracked by the following Jiras: https://issues.redhat.com/browse/RHCEPH-6708 https://issues.redhat.com/browse/RHCEPH-9119 https://issues.redhat.com/browse/RHCEPH-9122 https://issues.redhat.com/browse/RHCEPH-4654 Jira:OSPRH-7464 Image import remains in importing state after conversion with ISO image format When you use image conversion with the ISO image format, the image import operation remains in an "importing" state. Example: Replace <iso_image> with the name of your image. Replace <my_file.iso> with the file name for your image. Jira:OSPRH-8580 3.5.10. Dashboard 3.5.10.1. New features This part describes new features and major enhancements introduced in Red Hat OpenStack Services on OpenShift 18.0. Hypervisor status now includes vCPU and pCPU information Before this update, pCPU usage was excluded from the hypervisor status in the Dashboard service (horizon) even if the cpu_dedicated_set configuration option was set in the nova.conf file. This enhancement uses the Placement API to display information about vCPUs and pCPUs. You can view vCPU and pCPU usage diagrams under the Resource Providers Summary and find more information on vCPUs and pCPUs on the new Resource provider tab at the Hypervisors panel. Jira:OSPRH-1516 With this update, you can now customize the OpenStack Dashboard (horizon) container. The customization can be performed by using the extra mounts feature to add or change files inside of the Dashboard container. Jira:OSPRH-5644 TLS everywhere in RHOSO Dashboard Operator With this update, the RHOSO Dashboard (horizon) Operator automatically configures TLS-related configuration settings. These settings include certificates and response headers when appropriate, including the secure cookies and HSTS headers for serving over HTTPS. Jira:OSPRH-5882 3.5.10.2. Bug fixes This part describes bugs fixed in Red Hat OpenStack Services on OpenShift 18.0 that have a significant impact on users. Host spoofing protective measure Before this update, the hosts configuration option was not populated with the minimum hosts necessary to protect against host spoofing. With this update, the hosts configuration option is now correctly populated. Jira:OSPRH-5832 Dashboard service operators now include HSTS header Before this update, HSTS was only enabled in Django through the Dashboard service (horizon) application. However, user HTTPS sessions were going through the OpenShift route, where HSTS was disabled. With this update, HSTS is enabled on the OpenShift route. Jira:OSPRH-7367 3.6. Release information RHOSO 18.0 Beta 3.6.1. Advisory list This release of Red Hat OpenStack Services on OpenShift (RHOSO) includes the following advisories: RHEA-2024:3646 RHOSO 18.0 Beta container images, data plane 1.0 Beta RHEA-2024:3647 RHOSO 18.0 Beta container images, control plane 1.0 Beta RHEA-2024:3648 RHOSO 18.0 Beta service container images RHEA-2024:3649 RHOSO 18.0 Beta packages 3.6.2. Compute 3.6.2.1. New features This part describes new features and major enhancements introduced in Red Hat OpenStack Services on OpenShift 18.0. You can schedule archival and purge of deleted rows from Compute service (nova) cells The nova-operator now schedules a periodic job for each Compute service (nova) cell to archive and purge the deleted rows from the cell database. The frequency of the job and the age of the database rows to archive and purge can be fine tuned in the {{OpenStackControlPlane.spec.nova.template.cellTemplates[].dbPurge}} structure for each cell in the cellTemplates. Jira:OSPRH-86 3.6.2.2. Deprecated functionality This part provides an overview of functionality that has been deprecated in Red Hat OpenStack Services on OpenShift 18.0. Deprecated functionality will likely not be supported in future major releases of this product and is not recommended for new deployments. i440fx PC machine type no longer tested or supported In RHOSP 17, the i440fx PC machine type, pc-i440fx, was deprecated and Q35 became the default machine type for x86_64. In RHOSP 18, the i440fx PC machine type is no longer tested or supported. The i440fx PC machine type is still available for use under a support exception for legacy applications that cannot function with the Q35 machine type. If you have such a workload, contact Red Hat support to request a support exception. With the removal of support for the i440fx PC machine type from RHOSP, you cannot use pc-i440fx to certify VNFs or third-party integrations. You must use the Q35 machine type. Jira:OSPRH-7373 3.6.2.3. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. No network block device (NBD) live migration with TLS enabled In RHOSO 18.0 Beta, a bug prevents you from using network block device (NBD) to live migrate storage between Compute nodes with TLS enabled. See https://issues.redhat.com/browse/OSPRH-6931 . This issue only affects storage migration when TLS is enabled. You can live migrate storage with TLS not enabled. Jira:OSPRH-6740 Do not mix NUMA and non-NUMA instances on same Compute host Instances without a NUMA topology should not coexist with NUMA instances on the same host. Jira:OSPRH-83 Cannot delete instance when cpu_power_managment is set to true When an instance is first started and the host core state is changed there is a short time period where it cannot be updated again. during this period instance deletion can fail. if this happens a second delete attempt should succeed after a short delay of a few seconds. Jira:OSPRH-7103 3.6.3. Networking 3.6.3.1. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. OVN pod goes into loop due to NIC Mapping When using a large number of NIC mappings, OVN might go into a creation loop. Jira:OSPRH-7480 3.6.4. Network Functions Virtualization 3.6.4.1. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Listing physical function (PF) ports using neutron might show the wrong MAC Lists of PF ports might show the wrong MAC. Jira:OSPRH-7085 3.6.5. Storage 3.6.5.1. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Image uploads might fail if a multipathing path for Block Storage service (cinder) volumes is offline If you use multipath for Block storage service volumes, and you have configured the Block Storage service as the back end for the Image service (glance), image uploads might fail if one of the paths goes offline. Jira:OSPRH-7393 RGW does not pass certain Tempest object storage metadata tests Red Hat OpenStack Services on OpenShift 18.0 supports Red Hat Ceph Storage 7. Red Hat Ceph Storage 7 RGW does not pass certain Tempest object storage metadata tests as tracked by the following Jiras: https://issues.redhat.com/browse/RHCEPH-6708 https://issues.redhat.com/browse/RHCEPH-9119 https://issues.redhat.com/browse/RHCEPH-9122 https://issues.redhat.com/browse/RHCEPH-4654 Jira:OSPRH-7464 Missing Barbican configuration in the Image service (glance) The Image service is not automatically configured to interact with Key Manager (barbican), and encrypted image signing and verification fails due to the missing configuration. Jira:OSPRH-7155 3.6.6. Release delivery 3.6.6.1. Removed functionality This part provides an overview of functionality that has been removed in Red Hat OpenStack Services on OpenShift 18.0. Removed functionality is no longer supported in this product and is not recommended for new deployments. Removal of snmp and snmpd The snmp service and snmpd daemon are removed in RHOSO 18.0. Jira:OSPRH-2960 3.6.7. Integration test suite 3.6.7.1. Known issues This part describes known issues in Red Hat OpenStack Services on OpenShift 18.0. Tempest test-operator does not work with LVMS storage class When the test-operator is used to run Tempest, it requests a "ReadWriteMany" PersistentVolumeClaim (PVC) which the LVMS storage class does not support. This causes the tempest-test pod to become stuck in the pending state. Workaround : Use the test-operator with a storage class supporting ReadWriteMany PVCs. The test-operator should work with a ReadWriteOnce PVC so the fixed version will no longer request a ReadWriteMany PVC. Jira:OSPRH-7062

Commands:
[libvirt] cpu_power_management = true cpu_power_management_strategy = governor
ovn: template: ovnDBCluster: ovndbcluster-nb: replicas: 3 <<---------- dbType: NB storageRequest: 10G networkAttachment: internalapi ovndbcluster-sb: replcas: 3 <<---------- dbType: SB storageRequest: 10G networkAttachment: internalapi ovnNorthd: {}
names will be dependent on the deployment patch -n openstack openstackcontrolplane openstack-galera-network-isolation --type=merge --patch ' spec: octavia: template: octaviaHousekeeping: customServiceConfig: | [nova] enable_anti_affinity = true octaviaWorker: customServiceConfig: | [nova] enable_anti_affinity = true octaviaHealthManager: customServiceConfig: | [nova] enable_anti_affinity = true '
neutron: enabled: true : template: : customServiceConfig: | [DEFAULT] global_physnet_mtu=1558 [ml2] physical_network_mtus = ["datacentre:1500"] [ovn] ovn_emit_need_to_frag = true
apiVersion: core.openstack.org/v1beta1 kind: OpenStackControlPlane spec: extraMounts: - extraVol: - extraVolType: Ceph mounts: - mountPath: /etc/ceph name: ceph0 readOnly: true propagation: - az0 volumes: - name: ceph0 projected: sources: - secret: name: ceph-conf-az-0 - extraVolType: Ceph mounts: - mountPath: /etc/ceph name: ceph1 readOnly: true propagation: - az1 volumes: - name: ceph1 projected: sources: - secret: name: ceph-conf-az-1
apiVersion: core.openstack.org/v1beta1 kind: OpenStackControlPlane <...> spec: cinder: uniquePodNames: false # workaround https://issues.redhat.com/browse/OSPRH-11240 enabled: true apiOverride: <...>
[scheduler] image_metadata_prefilter=false
[libvirt] cpu_power_management = true cpu_power_management_strategy = governor
names will be dependent on the deployment patch -n openstack openstackcontrolplane openstack-galera-network-isolation --type=merge --patch ' spec: octavia: template: octaviaHousekeeping: customServiceConfig: | [nova] enable_anti_affinity = true octaviaWorker: customServiceConfig: | [nova] enable_anti_affinity = true octaviaHealthManager: customServiceConfig: | [nova] enable_anti_affinity = true '
- Check tripleo neutron services list: systemctl list-unit-files --type service - Remove tripleo services from: /etc/systemd/system/
[...] mysql.plugin OK mysql.proc Needs upgrade mysql.procs_priv OK [...]
run mariadb-client USD{MARIADB_CLIENT_ANNOTATIONS} -q --image USD{MARIADB_IMAGE} -i --rm --restart=Never -- mysql -h USDSOURCE_MARIADB_IP -u root -p"USDSOURCE_DB_ROOT_PASSWORD" -e "repair table mysql.proc;"
+------------+--------+----------+---------------------------------+ | Table | Op | Msg_type | Msg_text | +------------+--------+----------+---------------------------------+ | mysql.proc | repair | info | Running zerofill on moved table | | mysql.proc | repair | status | OK | +------------+--------+----------+---------------------------------+
apiVersion: core.openstack.org/v1beta1 kind: OpenStackControlPlane spec: extraMounts: - extraVol: - extraVolType: Ceph mounts: - mountPath: /etc/ceph name: ceph0 readOnly: true propagation: - az0 volumes: - name: ceph0 projected: sources: - secret: name: ceph-conf-az-0 - extraVolType: Ceph mounts: - mountPath: /etc/ceph name: ceph1 readOnly: true propagation: - az1 volumes: - name: ceph1 projected: sources: - secret: name: ceph-conf-az-1
apiVersion: core.openstack.org/v1beta1 kind: OpenStackControlPlane <...> spec: cinder: uniquePodNames: false # workaround https://issues.redhat.com/browse/OSPRH-11240 enabled: true apiOverride: <...>
[scheduler] image_metadata_prefilter=false
[libvirt] cpu_power_management = true cpu_power_management_strategy = governor
Internal Server Error: The server has either erred or is incapable of performing the requested operation.
Could not find a service provider that supports distributed=False and ha=False
use ovs_neutron; insert into providerresourceassociations (provider_name, resource_id) values ("ovn", "<router_id>");
[scheduler] image_metadata_prefilter=false
[libvirt] cpu_power_management = true cpu_power_management_strategy = governor
edpm_kernel_args: ""
[compute] packing_host_numa_cells_allocation_strategy = True
[scheduler] image_metadata_prefilter=false
[libvirt] cpu_power_management = true cpu_power_management_strategy = governor
ovn: template: ovnController: external-ids: availability-zones: - zone1 octavia: template: lbMgmtNetwork: availabilityZones: zone1
*Workaround:* If your deployment supports uploading images in ISO format, you can use the `image-create` command to upload ISO images as shown in the following example (instead of using image conversion with the `image-create-via-import` command).
glance image-create --name <iso_image> --disk-format iso --container-format bare --file <my_file.iso>