Chapter 2. Release information RHOSO 18.0

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:

Control plane temporarily unavailable during minor update

During minor updates, 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 instance 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.

IPv6 export locations cannot be used with Shared File Systems service shares that have a CephFS-NFS back end

An issue with Red Hat Ceph Storage prevents the use of IPv6 export locations with Shared File Systems service (manila) shares that have a CephFS-NFS back end. Workaround: Currently, there is no workaround.

Enhanced os-vif OVS plugin improves network performance on OVS interfaces

Previously, a bug fix was made to OVS that changed the application of the kernel’s default QOS policy to OVS ports. This fix was applied to 17.1 but not to 18.0. As a result, a regression in the network configuration for OVS interfaces negatively impacted network performance of Openstack instances when using kernel OVS. With this update, the os-vif OVS plugin has been enhanced to improve network performance on OVS interfaces by using the linux-noop QOS policy by default. This can still be overridden by neutron QOS policies. To apply the update, restart or move the instance to recreate the port with a hard reboot, perform a detach followed by an attach operation, or perform a live migrate operation.

Compute instance with ISO image boots correctly

Previously, a Compute instance with an ISO image booted via a block device instead of CD-ROM. This prevented the RHEL Kickstart installation from initiating from the CD-ROM. With this bug fix, Compute boots the instance from the ISO image correctly and via CD-ROM.

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:

OpenStack Operator checks namespace field for upgrade of Operators

This update fixes an issue where upgrades from OpenStack Operator version 1.0.6 or earlier sometimes failed when OpenShift Lifecycle Manager (OLM) Operator resources contained data with no namespace field defined.

Control plane temporarily unavailable during minor update

During minor updates, 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 instance 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.

Multipart image upload with S3 back end

Before this update, you had to use the image import workflow to upload multipart images if you had an S3 back end for the Image service (glance). With this update, you can set s3_store_large_object_size to 0 to force multipart upload when you create an image in the S3 back end from a Block Storage service (cinder) volume.

IPv6 export locations cannot be used with Shared File Systems service shares that have a CephFS-NFS back end

An issue with Red Hat Ceph Storage prevents the use of IPv6 export locations with Shared File Systems service (manila) shares that have a CephFS-NFS back end. Workaround: Currently, there is no workaround.

Volume migration operations are technology preview

Volume migration operations that are a part of the zone migration strategy are provided as a technology preview only, and should not be used in production.

The Telemetry service collects telemetry related to RHOSO database services

This enhancement implements a new exporter that enables observability of the MariaDB databases that run within RHOSO.

Compute metrics are available to Prometheus for telemetry data collection and storage

Telemetry data for Compute nodes is now collected directly from Prometheus rather than transiting the internal message bus, enabling storage of Compute node telemetry in the telemetry storage system.

Collection of telemetry data no longer disrupted by DNS search domains

This update fixes an issue where DNS search domains (dns_search_domains) shorter than 8 characters that appeared alphabetically before the control plane DNS domain caused disruption in the collection of telemetry data.

Enablement of Nova notifications in RHOSO

This update adds support for configuring a dedicated notifications message bus in the nova-operator. By setting the notificationsBusInstance in the Nova custom resource (CR), operators can specify an external RabbitMQ for emitting versioned and unversioned notifications.

Support for data plane adoption of the source cloud with multiple nova cells

The cloud operator can now adopt an existing 17.1 multi-cell nova deployment with a common network from TripleO management to the new installer for RHOSO.

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:

Improved logging and error handling for cross-controller packet loss

Before this update, cross-controller packet loss could impact request handling by the python-networking-baremetal agent and prevent physical network mapping updates from occurring in the Networking service (neutron) for bare-metal nodes. With this update, there is additional logging and error handling so that the python-networking-baremetal provided service exits and the container can automatically restart if packet loss occurs. Physical network mappings for bare-metal nodes continue to to be updated if network interruptions for Controller nodes occur.

Workflow operations persist through interruptions in connectivity

This update solves an issue in the Bare Metal Provisioning service (ironic) that caused the deployment process to loop and time out because of interruptions in connectivity while the deployment agent was starting. The issue occurred because only one attempt was made to evaluate if a RAM drive was recently booted. When this issue occurred, the bare metal nodes would fail to clean, deploy, or perform other workflow actions.

Adoption of combined Networker/Controller nodes

Adoption of RHOSP 17.1 environments that use combined Controller/Networker nodes are verified to work as documented in Adopting a Red Hat OpenStack Platform 17.1 deployment.

North/south fragmentation fix

Before this update, OpenStack did not fragment north-south packets as expected when the external maximum transmission unit (MTU) was less than the internal MTU, which resulted in packets being dropped silently. With this update, fragmentation happens as expected, and packets are not dropped silently.

Fix improves BGP recovery time

Before this update, disabling Bidirectional Forwarding Detection (BFD) in Free Range Routing (FRR) on RHEL 9.4 could cause traffic disruptions during error recovery.

DNS as a service

With this technology preview, you can test the management of DNS records, names, and zones using the DNS service (designate). For more information, see Configuring DNS as a service.

Load-balancing service (octavia) support for DCN

With this technology preview, you can test creating load balancers in availability zones (AZs) to increase traffic throughput, reduce latency, and enhance security. For more information, see Creating availability zones for load balancing of network traffic at the edge.

Create Load-balancing service resources for a specific project

Load-balancing service (octavia) resources are created by default within a project (tenant) service. RHOSO 18.0.10 (Feature Release 3) introduces a technology preview of a new TenantName parameter for the Octavia Operator, which restricts the use of the resource to a specific project. RHOSO administrators can also change the domain of the project.

Deprecation of ovn-bgp-agent

Since RHOSO 18.0.10 (Feature Release 3), the OVN BGP Agent ovn-bgp-agent is deprecated. ovn-bgp-agent is the BGP integration component in RHOSO. An alternative BGP integration mechanism is scheduled for a future release. Until then, Red Hat will provide only bug fixes and support for this feature.

TSO for OVS-DPDK promoted from technology preview to general availability

RHOSO 18.0.6 (Feature Release 2) introduced a technology preview of TCP segmentation offload (TSO) for RHOSO environments with OVS-DPDK.

Adoption no longer fails when physical function is attached to an instance

Previously, when the physical function (PF) was attached to the instance, if os-net-config was re-run, os-net-config could not find the SR-IOV PF in the host, and the adoption failed. With this release, the adoption does not fail.

Fixes NetworkManager-dispatcher failures

Before this update, the NetworkManager-dispatcher service was blocked by SELinux permission denial, causing the service to fail when SELinux was enforced. With this release, NetworkManager has been updated to allow running the`NetworkManager-dispatcher` service with SELinux in enforcing mode. As a result, the NetworkManager-dispatcher service now runs with SELinux in enforcing mode, eliminating the failures.

Data plane deployment no longer fails when using the nmstate provider to pre-provision Compute nodes over VLAN

Before this update, when pre-provisioning Compute nodes for communicating with the control plane over VLANs, theNetworkManager CLI (nmcli) connection was not always created with the proper interface name. This caused deployment failures.

Fixes edpm_network_config_nonconfigured_cleanup parameter issue

The flag edpm_network_config_nonconfigured_cleanup: true was introduced as default in Feature Release 2 and caused some new deployments to fail.

Bandwidth limit now applied to instances with VLAN and flat ports with nmstate provider

Previously, in environments using the os-net-config nmstate provider, QoS bandwidth limit rules were not properly applied to the physical NIC attached to the br-ex bridge.

Patch ports no longer cause network update failures

This update fixes an issue in environments with the nmstate provider where network updates failed on Compute nodes that hosted active instances with patch ports present in br-ex.

Multiple RHOSO deployments on a single RHOCP cluster by using namespace separation

This feature enables you to deploy multiple RHOSO environments on a single RHOCP cluster by using namespace (project) isolation for development, staging and testing environments.

Minimizing downtime during a minor update

During a minor update, the control plane services are updated concurrently. This enhancement isolates the galera, rabbitmq, memcached, and keystone services to perform their updates consecutively, in order, within the minor control plane services update phase.

Documentation: Updated "Installing the OpenStack Operator" procedure

The Installing the OpenStack Operator procedure has been updated to include changing the default automatic Operator update approvals to manual approvals. Using manual update approval enables RHOSO administrators to schedule RHOSO Operator updates.

Control plane temporarily unavailable during minor update

During minor updates, 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 instance 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.

Upgrading the OpenStack Operator can fail due to Operators that are not namespaced

This update fixes an issue where upgrades from OpenStack Operator version 1.0.6 or earlier sometimes failed when OpenShift Lifecycle Manager (OLM) Operator resources contain data with no namespace field defined.

NodeName string updated in JSON tag for BGPConfiguration parameter

Before this update, the BGPConfiguration parameter spec.frrNodeConfigurationSelector.nodename had an inconsistency in its JSON tag where the NodeName string json:"frrConfigurationNamespace,omitempty was incorrect because frrConfigurationNamespace is a node name. With this update, the NodeName string in the JSON tag is correctly set as json:"nodeName,omitempty". You can now configure the frrNodeConfigurationSelector by using the following spec:

S3 driver for Image service (glance) has option to specify path to CA bundle

With this update, the S3 driver for the Image service has a new s3_store_cacert option that allows users to specify the path to a Certificate Authority (CA) bundle to use.

Red Hat Ceph Storage 8 NFS is supported

Before this update, NFS was not supported when integrating with Red Hat Ceph Storage 8. With this update, NFS is now supported with Red Hat Ceph Storage 8 integrations.

API token based authentication with the VAST Data storage driver in the Shared File Systems Service (manila)

With this update, cloud administrators can use either vast_mgmt_user and vast_mgmt_password or vast_api_token when configuring authentication in the Shared File Systems service for their VAST Data storage systems. API-based authentication is useful in RHOSO deployments if cloud administrators need an alternative to passwords when specifying VAST Data API users.

Improved Fibre Channel performance when detaching a volume

With this update, there is improved Fibre Channel performance when detaching a volume because there is no longer a requirement to call the lsscsi command.

Distributed zones with third-party storage

RHOSO 18.0.10 (Feature Release 3) supports the integration of third-party storage appliances within distributed zone environments. The NFS and Fiber Channel protocols in distributed zone environments are provided as a technology preview and are not yet recommended for production use.

Image service (glance) notifications for events in image lifecycle

With this update, you can enable notifications in the Image service by using the notificationBusInstance parameter, allowing integration with either the existing RabbitMQ instance or a dedicated one.

CephFS file name added to CephFS share metadata

With this update, you can check a CephFS file name when mounting a native CephFS share by viewing the __mount_options metadata of the share in the output of the following command:

Improved reliability for Fibre Channel volume attachments

Before this update, Fibre Channel volume attachments failed intermittently with a NoFibreChannelVolumeDeviceFound error due to partial scanning of devices. With this update, a broader scan results in better discovery of devices and successful attach operations.

Added options for customizing the Object Storage service (swift)

With this update, you can test two new options to customize deployments of the Object Storage service by using externally-managed rings. With this technology preview, you can now disable automatic ring management and spread large rings over multiple configmaps.

Multipart image upload does not work with S3 back end

If you upload multipart images with an S3 back end, you must use the import workflow.

Red Hat Ceph Storage 8 Object Gateway is not supported

The Red Hat Ceph Storage Object Gateway (RGW) is currently not supported when integrating with Red Hat Ceph Storage 8.

Granular package update workflow

RHOSO 18.0.10 (Feature Release 3) introduces a feature to separate the update process for RHOSO EDPM nodes into two distinct phases: * updating OpenStack (containers & essential packages) and * updating the system (all packages).

The dst_node parameter is now optional for the Zone migration strategy

Before this update, the implementation of the Zone migration strategy was affected by the dst_node parameter. Now the implementation is in line with API schema and the dst_node parameter is optional. If you do not specify a value for dst_node, the Nova scheduler selects an appropriate host automatically.

Fix for RHOSO Watcher Action Plans status

This update fixes an issue where RHOSO Watcher did not correctly report the state of Action Plans after all Actions finished, for example reporting SUCCESS if some Actions actually finished with a state of FAILED.

Support for new strategies for Optimize service (watcher)

RHOSO 18.0.10 (Feature Release 3) introduces support for three new supported strategies in the Optimize service: host maintenance, zone migration for instances, and workload balance. For more information about supported strategies to achieve resource optimization goals, see Sample Optimize service workflows in Optimizing infrastructure resource utilization.

Volume migration operations are technology preview

Volume migration operations that are a part of the zone migration strategy are provided as a technology preview only, and should not be used in production.

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 redhat service is restored to the default list of data plane services

Before this update, the redhat service was removed temporarily from the default list of data plane services, and users had to manually add the redhat service to the list of services in the OpenStackDataPlaneNodeSet CR. With this update, the redhat service is restored to the default list of data plane services.

QoS information for VLAN or flat network ports persists through port updates

Any VLAN or flat network port with egress QoS policy rules (maximum and/or minimum bandwidth) stores this information in the Logical_Switch_Port. options dictionary. Before this update, any update on this port, from a port name change to a live migration, deleted this QoS information. With this update, the QoS information persists through port updates.

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, the ingress packets are dropped with no notification.

Example

For example, suppose that the external network datacentre MTU is 1500.

Data plane deployment no longer fails when using the nmstate provider to pre-provision Compute nodes over VLAN

Before this update, when pre-provisioning Compute nodes for communicating with the control plane over VLANs, theNetworkManager CLI (nmcli) connection was not always created with the proper interface name. This caused deployment failures.

Control plane temporarily unavailable during minor update

During minor updates, 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.

The Instance HA service supports a new parameter

This enhancement adds the TAGGED_AGGREGATES parameter to the RHOSO high availability for Compute instances (Instance HA) service. By default, this parameter is set to true, so that the Instance HA service checks for tagged host aggregates. If you set this parameter to false then the Instance HA service does not check for tagged host aggregates and therefore will evacuate all the eligible Compute nodes.

Multipart image upload does not work with S3 back end

If you upload multipart images with an S3 back end, you must use the import workflow.

Red Hat Ceph Storage 8 NFS is not supported

NFS is currently not supported when integrating with Red Hat Ceph Storage 8.

Red Hat Ceph Storage 8 Object Gateway is not supported

The Red Hat Ceph Storage Object Gateway (RGW) is currently not supported when integrating with Red Hat Ceph Storage 8.

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:

Default policy ensures nftables reload at the end of deployment

Before this update, iptables default tables were added to nftables to ensure backwards compatibility. However, there was a default ALLOW INPUT rule instead of a default DROP rule, and nftables were not reloaded at the end of the deployment. With this update, the correct rules are applied to ensure that nftables are reloaded at the end of the deployment.

Manually add the redhat service to the default list of data plane services

The redhat service has been removed temporarily from the default list of data plane services. As a result, when you attach subscriptions or repositories to Compute nodes and use the documented rhc_* parameters when creating the data plane secrets, the nodes are not registered and the data plane deployment fails.

Bare-metal data plane node with multi-path block storage boots after being provisioned

Before this update, pre-built whole disk images did not include the device-mapper-multipath package, which prevented the paired boot ramdisk from supporting multi-path block storage. This caused bare-metal nodes with multi-path block storage to fail to boot after deployment and instead be stuck in an emergency shell. With this update, pre-built whole disk images now include the device-mapper-multipath package and deployed bare-metal nodes no longer enter an emergency shell after being deployed.

Logs now available for FRR service

Before this update, no logs were available for the Free Range Routing (FRR) service, which is deployed on the data plane nodes when RHOSO is configured to use Dynamic Routing with BGP. With this update, these logs are available.

Legacy tripleo Networking services are removed after adoption

Before this update, there were legacy tripleo Networking service (neutron) services after the edpm_tripleo_cleanup task, which needed to be removed manually. These services were stopped after adoption, so the RHOSO services were not affected. With this update, all tripleo Networking services are removed after adoption on data plane nodes.

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, the ingress packets are dropped with no notification.

Example

For example, suppose that the external network datacentre MTU is 1500.

Port updates delete QoS information for VLAN or flat network ports

Any VLAN or flat network port with egress QoS policy rules (maximum and/or minimum bandwidth) stores this information in the Logical_Switch_Port. options dictionary. Any update on this port, from a port name change to a live migration, will delete this QoS information.

Adoption fails when physical function is attached to a VM instance

When the physical function (PF) is attached to the instance, if os-net-config is re-run, os-net-config cannot find the SR-IOV PF in the host, and thus the deployment, update, or adoption fails.

NetworkManager-dispatcher scripts fail to run when SELinux is enabled

The os-net-config configuration tool uses NetworkManager-dispatcher scripts for driver bindings. When SELinux is enabled, these scripts fail to run, and the os-net-config network deployment fails.

Failed service updates are being reflected accurately by the deployment status

Before this update, when updates to service configurations failed, the failure was not being reflected in the condition status of the deployment. Instead, the Ready condition showed as "True" because the new pods created by the update were not being considered when checking the deployment readiness. With this update, any new pods created during a configuration update are now considered when assessing deployment readiness. If rolling out new pods fails, then the deployment reflects that it is stuck in Deployment in progress.

Control plane temporarily unavailable during minor update

During minor updates, 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.

Generated CA bundle gets installed on data plane nodes

Before this update, the CA bundle that was generated by the RHOSO control plane was deployed on the data plane node for deployed or running services, but it did not get installed as the CA bundle on the data plane node itself. The CA bundle can include custom third-party CA files, for example, to access a satellite. With this update, the CA bundle gets installed on the data plane node.

Compute service fails a ready check for a deployment with an invalid configuration

Before this update, if the Compute service (nova) API raised a configuration error, it returned a 500 error once, and then continued to run with a broken configuration after a reload. This issue occurred because mod_wsgi reloaded the wsgi application into the same Python interpreter when an error was raised during application initialization. With this update, the Compute service has been modified to reraise the configuration error until the application can restart cleanly. Now, if you deploy with an invalid configuration, the Compute service API CR fails the ready check and updates the Status field in the OpenShift CR to prompt you to review the log files for the configuration error.

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:

Manually add the redhat service to the default list of data plane services

The redhat service has been removed temporarily from the default list of data plane services. As a result, when you attach subscriptions or repositories to Compute nodes and use the documented rhc_* parameters when creating the data plane secrets, the nodes are not registered and the data plane deployment fails.

BFD now works as expected in RHOSO deployments with dynamic routing

Before this update, when you deployed RHOSO with Dynamic Routing with border gateway protocol (BGP), bi-directional forwarding (BFD) did not work as expected because there was no nft rule to permit BFD and BGP ports. With this update, an nft rule has been added and BFD works as expected:

No logs available for FRR service

No logs are available for the FRR service, which is deployed on the data plane nodes when RHOSO is configured to use Dynamic Routing with BGP.

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.

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, the ingress packets are dropped with no notification.

Example

For example, suppose that the external network datacentre MTU is 1500.

Port updates delete QoS information for VLAN or flat network ports

Any VLAN or flat network port with egress QoS policy rules (maximum and/or minimum bandwidth) stores this information in the Logical_Switch_Port. options dictionary. Any update on this port, from a port name change to a live migration, will delete this QoS information.

Fixes minor update failures starting with updates from 18.0.6

This update fixes a bug that causes minor update failures during updates from RHOSO 18.0.1 through 18.0.5 to 18.0.6 or later. The failure no longer occurs if you update from RHOSO 18.0.6 or later to any version.

Deprecated the edpm_ovs_dpdk_lcore_list variable

You can stop using the edpm_ovs_dpdk_lcore_list Ansible variable in RHOSO deployments. Previously, it was used in nodeset CR definition files to enable OVS DPDK in data plane deployments in NFV environments. It is no longer required or supported, and its use now causes deployment errors.

Adoption fails when physical function is attached to a VM instance

When the physical function (PF) is attached to the instance, if os-net-config is re-run, os-net-config cannot find the SR-IOV PF in the host, and thus the deployment, update, or adoption fails.

NetworkManager-dispatcher scripts fail to run when SELinux is enabled

The os-net-config configuration tool uses NetworkManager-dispatcher scripts for driver bindings. When SELinux is enabled, these scripts fail to run, and the os-net-config network deployment fails.

TraceEnable parameter disabled by default in httpd configuration

Before this update, HTTP TRACE was enabled by default from the OpenStackProvisionServer CR which resulted in security scanners creating an alert. With this update, the TraceEnable parameter has been set to the value "off" by default in the httpd configuration.

Control plane temporarily unavailable during minor update

During minor updates, 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.

Generated CA bundle does not get installed on data plane nodes

The CA bundle that is generated by the RHOSO control plane gets deployed on the data plane node for deployed or running services, but it does not get installed as the CA bundle on the data plane node itself. The CA bundle can include custom third-party CA files, for example, to access a satellite. Workaround: There is currently no workaround.

Optimize service (watcher) for resource optimization

The Red Hat OpenStack Services on OpenShift (RHOSO) Optimize service (watcher) provides a flexible and scalable resource optimization service for multi-tenant RHOSO-based clouds. The Optimize service provides a framework to help you set and manage goals for infrastructure resource utilization.

Improved metrics for RHOSO Observability

You can now use new metrics for monitoring the health of RHOSO services, including the following:

An additional Ceilometer metric is available

You can now retrieve the VMs: ceilometer_power_state metric to indicate the libvirt power state.

Additional VM metrics are available

You can now use the dashboards to view a dedicated VM Network Traffic Dashboard, as well as monitor the power state of VMs.

Visualize hardware sensor metrics with Ceilometer IPMI

You can now use the dashboards to view the available IPMI sensor hardware metrics from your compute nodes.

Kepler dashboard is more user-friendly (Technology Preview)

You can now view Compute nodes by human-readable hostnames, instead of with Compute service UUIDs.

Improved compatibility between Telemetry Operator and OpenShift Logging

You can now use Telemetry Operator with OpenShift Logging versions 6.1 and newer.

Prometheus connection information is exposed in a secret

Telemetry Operator now creates a secret with the internal Prometheus connection details. Other OpenShift services can use that secret as a service discovery mechanism to connect to Prometheus.

Scrape Kepler metrics without manual intervention (Technology Preview)

Before this update, a firewall was not applied to Compute nodes, which allowed port 8888 to be open. However, access to port 8888 might be lost unexpectedly if a firewall is enabled. With this update, the ansible role checks whether the firewall is enabled and then opens port 8888. As a result, Prometheus can scrape Kepler metrics without manual intervention.

Capture GPU metrics with Kepler (Technology Preview)

With this update to Red Hat OpenStack Services on OpenShift (RHOSO), you can now capture GPU metrics with Kepler.

TLS errors caused node exporter scraping issues

This release of Red Hat OpenStack Services on OpenShift (RHOSO) fixes an issue with scraping metrics in specific dataplane configurations.

Missing square brackets around IPv6 addresses

This release of Red Hat OpenStack Services on OpenShift (RHOSO) rectifies a potential issue with scraping data because of missing square brackets around IPv6 addresses.

IPv6 connection refused with RabbitMQ metrics.

With this update to Red Hat OpenStack Services on OpenShift (RHOSO), the RabbitMQ metrics exporter now listens on the correct interface on the IPv6 Control Plane network.

Unified limits introduced

This update introduces unified limits to RHOSO 18.0. Unified limits is a modern quota system in which quota limits are stored centrally in the Identity service. Unified limits may be enabled by following the documented procedure.

Verify systemd-container package installation on hypervisors

You can now verify that the systemd-container package is installed on the hypervisors before starting the final steps of the data plane adoption. You cannot adopt the source Red Hat OpenStack Platform cloud into Red Hat OpenStack Services on OpenShift (RHOSO) until the package is installed on all hypervisors.

Periodic healing of Nova internal instance info cache is disabled

By default, heal_instance_info_cache_interval is now disabled to improve performance of the neutron API server by removing the load created by the nova-compute agent. This will not affect cache correctness, because it is updated during most VM operations.

Adoption of nodes with hugepages now supported

With this update, data plane adoption now supports importing hypervisors with OSP workloads configured for use of hugepages.

Nova enables the live migration of NVIDIA vGPU instances

Nova enables the live migration instances using vGPU resources between hosts if the target uses the same NVIDIA driver version and the same mediated types.

Topology support for Compute service (nova) and placement service

Implemented a new custom resource definition for scheduling RHOSO Nova and Placement services' pods based on TopologySpreadConstraints and Affinity/Anti-Affinity rules.

Fixed update failure related to nova_statedir_ownership.py

Before this fix, updates from RHOSO18.0.3 to later releases failed with errors related to the missing nova_statedir_ownership.py script. With this fix, updates from RHOSO 18.0.3 to RHOSO 18.0.6 (Feature Release 2) do not generate these errors.

Allocation candidates are spread between hosts in Placement GET /allocation_candidates query

In a deployment with wide and symmetric provider trees, for example, where there are multiple children providers under the same root having inventory from the same resource class, if the allocation candidate request asks for resources from those children resource providers in multiple request groups the number of possible allocation candidates grows rapidly. The Placement service generates these candidates fully before applying the limit parameter provided in the allocation candidate query. The Placement service takes excessive time and memory to generate this amount of allocation candidates and the client might time out.

Instances with ephemeral storage on NFS share continue working after Compute service restart

Before this update, Compute service (nova) instances with ephemeral storage on NFS shares stopped working as soon as the containerized Compute agent service restarted on the hypervisor host.

Fixed update failure related to nova_statedir_ownership.py

Before this fix, updates from RHOSO18.0.3 to later releases failed with errors related to the missing nova_statedir_ownership.py script. With this fix, updates from RHOSO 18.0.3 to RHOSO 18.0.6 (Feature Release 2) do not generate these errors.

Fixed: Instances with ephemeral storage on NFS share stop working after Compute service restart

Before this update, Compute service (nova) instances with ephemeral storage on NFS shares stopped working as soon as the containerized Compute agent service restarted on the hypervisor host. That happened because of changed permissions of /var/lib/nova/ instances.

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:

Block Storage service (cinder) known issue

When you are using Red Hat Ceph Storage as the back end for the Block Storage service (cinder), then you might be unable to extend an attached encrypted volume. Workaround: detach the encrypted RBD volume, extend this volume and then reattach it.

Replace faulty nodes without scaling the cloud

With this update, you have the option of replacing faulty nodes without scaling the cloud.

Documentation: Limitation added detailing maximum length of OpenStackDataPlaneNodeSet CR names

The description of the rules around naming`OpenStackDataPlaneNodeSet` CRs has been updated to include that the maximum length is 53 characters.

Fixed default anti-affinity policy in the Load-balancing service

Before this update, the octavia operator did not enable anti-affinity when creating amphorae in active-standby topology. In some cases, the virtual machine were scheduled on the same compute node.

Corrected Load-balancing service provider network visibility

Before this update, end users could see the Load-balancing service provider network. Now the Load-balancing service provider network is only visible to the administrators.

Deploy Load-balancing service in an offline cluster

Before this update, the container image URL of the octavia-rsyslog pod was hard-coded and could not be overridden, with the result that users could not deploy the Load-balancing service (octavia) in an offline cluster.

Fixed stability issue with Load-balancing service health manager in DCN mode

Before this update, when you ran Load-balancing service (octavia) health manager pods in DCN mode, pods were randomly restarted by the operator. With this update, the random restarts do not occur.

Load-balancing service rsyslog endpoints no longer drop logs from remote area zones

Before this update, if you used the rsyslog service with DCN, the rsyslog pods dropped incoming rsyslog packets because the routes to the remote DCNs were missing. Now the packets are not dropped.

Amphora Vertical Scaling (Threading/CPU pinning) (Technology Preview)

With this technology preview you can test an improved handling of Load-balancing service vertical scaling support for the amphora driver. The update in this technology preview use an additional amphora image that is specifically optimized for improved vertical scaling and an additional load balancer flavor that uses multiple vCPUs. This can help improve latency and throughput of the load balancer.

TLS client authentication with the Load-balancing service (Technology Preview)

This update includes a Technology Preview of TLS web client communication with a RHOSO Load-balancing service (octavia) TLS-terminated HTTPS load balancer by using certificates to establish two-way TLS authentication.

Load-balancing service (octavia) support for Distributed zones feature (Technology Preview)

This update introduces a Technology Preview of Load-balancing service (octavia) availability zones (AZs) that enable project users to create load balancers in a Distributed zones environment to increase traffic throughput and reduce latency.

Multiple Load-balancing service VIP addresses from same network

There are use-cases where a Load-balancing service in Octavia with the Amphora provider needs multiple VIP addresses allocated from the same Neutron network. With this technology preview, you can test the ability to specify additional subnet_id/ip_address pairs to associate with the VIP port. This enables scenarios such as having a load balancer with both IPv4 and IPv6 addresses simultaneously or being exposed to both public and private subnets.

Improved TLS cipher and protocol support (Technology Preview)

This update introduces a Technology Preview of improved Load-balancing service (octavia) support for TLS cipher and protocol. You can now override the default cipher list with values that are more appropriate for your site, as well as use additional new features such as setting cipher and protocol lists for each listener.

IPv6 load-balancing network [Technology preview]

You can now test a technology preview that uses IPv6 CIDRs for the load-balancing management network.

No logs available for FRR service

No logs are available for the FRR service, which is deployed on the data plane nodes when RHOSO is configured to use Dynamic Routing with BGP.

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.

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.

Example

For example, suppose that the external network datacentre MTU is 1500.

BFD does not work as expected in RHOSO deployments with dynamic routing; workaround required

When you deploy RHOSO with Dynamic Routing with border gateway protocol (BGP), bi-directional forwarding (BFD) does not work as expected.

QoS policies not enforced when only maximum bandwidth (egress) rules present, on ports in physical networks, when the physical interface is a bond

A port connected to a physical network (VLAN, flat), with maximum-bandwidth-only QoS rules and egress direction uses the physical network interface to enforce the QoS rule, via TC commands.

Change os-net-config provider to nmstate

In previous RHOSO releases, Red Hat did not support NMstate as the os-net-config provider. It is now supported but the default configuration sets the os-net-config provider to ifcfg.

TSO for OVS-DPDK (Technology Preview)

RHOSO 18.0.6 (Feature Release 2) introduces a technology preview of TCP segmentation offload (TSO) for RHOSO environments with OVS-DPDK.

Deprecated the edpm_ovs_dpdk_lcore_list variable

Stop using the edpm_ovs_dpdk_lcore_list Ansible variable in RHOSO deployments. Previously, it was used in nodeset CR definition files to enable OVS DPDK in data plane deployments in NFV environments. It is no longer required or supported. Its use now causes deployment errors.

Adoption fails when physical function is attached to a VM instance

When the physical function (PF) is attached to the instance, if os-net-config is re-run, os-net-config cannot find the SR-IOV PF in the host, and thus the deployment/update/adoption fails.

Cannot set no_turbo when using cpu-partitioning-powersave profile

Due to an issue with setting the no_turbo parameter in the kernel, tuned hangs and fails when using the cpu-partitioning-powersave profile.

Requested service cannot be found during minor update

When updating the remaining services on the data plane, a minor update from 18.0.3 to 18.0.6 fails because the edpm_openstack_network_exporter.service cannot be found.

Manage service Operator installation under single OLM bundle

The OpenStack Operator no longer installs the multiple RHOSO service Operators individually. Instead, a new initialization resource manages the installation of the service Operators under a single Operator Lifecycle Manager (OLM) bundle. For more information about the new installation method, see Installing and preparing the Operators.

Custom environment variables for the OpenStackClient pod

You can set custom environment variables for the OpenStackClient pod.

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.

Enhanced Block Storage volume restoration on thinly provisioned back ends

This enhancement optimizes the process of restoring Block Storage volume backups on any thinly provisioned back end. Previously, when restoring a backup on a thinly provisioned back end, the full volume size was restored instead of only restoring the portion of the volume that was used. This caused unnecessary network traffic and greatly increased the time taken by the restoration process. This enhancement ensures that when restoring a volume on a thinly provisioned back end, only the portion of the volume that was used is restored.

Red Hat Ceph Storage 8 support

This enhancement adds support for integration with external Red Hat Ceph Storage 8. Due to known issues, not all Red Hat Ceph Storage 8 functionality is supported. For more information about these issues, see the Known Issues section.

ExtraMounts can process a per-instance propagation when the pod is prefixed with an arbitrary name

When uniquePodNames is true, every Cinder pod (and in general each component and service) is prefixed by a pseudo-random string. With this update, ExtraMounts can process a per-instance propagation when the pod is prefixed with an arbitrary name.

Multipart image upload does not work with S3 back end

If you upload multipart images with an S3 back end, you must use the import workflow.

Red Hat Ceph Storage 8 NFS is not supported

In RHOSO 18.0.6, NFS is currently not supported when integrating with Red Hat Ceph Storage 8.

Red Hat Ceph Storage 8 Object Gateway is not supported.

In RHOSO 18.0.6, the Red Hat Ceph Storage Object Gateway (RGW) is currently not supported when integrating with Red Hat Ceph Storage 8.

Create instance of openstack during minor update

If you update your Red Hat OpenStack Services on OpenShift environment from any release before 18.0.6, you must create an instance of openstack after you update the openstack-operator to trigger the deployment of all operators. For example:

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.

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.

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:

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.

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.

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.

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-provisioned 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.

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.

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.

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.

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.

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.

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.

Example

names will be dependent on the deployment

# names will be dependent on the deployment
oc 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
'

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.

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.

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.

Example

For example, suppose that the external network datacentre MTU is 1500.

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.

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.

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.

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.

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.

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.

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

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.

vGPUs enablement

This update introduces enhancements for mdev and vGPU.

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.

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.

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.

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:

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.

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.

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.

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.

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.

Example

names will be dependent on the deployment

# names will be dependent on the deployment
oc 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
'

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.

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.

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.

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.

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.

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.

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.

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.

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.

Example command

oc run mariadb-client ${MARIADB_CLIENT_ANNOTATIONS} -q --image ${MARIADB_IMAGE} -i --rm --restart=Never -- \
    mysql -h $SOURCE_MARIADB_IP -u root -p"$SOURCE_DB_ROOT_PASSWORD" -e "repair table mysql.proc;"

oc run mariadb-client ${MARIADB_CLIENT_ANNOTATIONS} -q --image ${MARIADB_IMAGE} -i --rm --restart=Never -- \
    mysql -h $SOURCE_MARIADB_IP -u root -p"$SOURCE_DB_ROOT_PASSWORD" -e "repair table mysql.proc;"

Example output

+------------+--------+----------+---------------------------------+
| Table      | Op     | Msg_type | Msg_text                        |
+------------+--------+----------+---------------------------------+
| mysql.proc | repair | info     | Running zerofill on moved table |
| mysql.proc | repair | status   | OK                              |
+------------+--------+----------+---------------------------------+

+------------+--------+----------+---------------------------------+
| Table      | Op     | Msg_type | Msg_text                        |
+------------+--------+----------+---------------------------------+
| mysql.proc | repair | info     | Running zerofill on moved table |
| mysql.proc | repair | status   | OK                              |
+------------+--------+----------+---------------------------------+

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.

Rebuilding volume-backed server

This release adds the support to rebuild a volume-backed server with the same or different image.

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.

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.

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.

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.

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 RHOSP 17.1 environment configuration and the adopted RHOSO environment configuration.

Baremetal adoption

You can now adopt baremetal RHOSP 17.1 environments into RHOSO environments.

Adoption roll-back

You can now roll back a failed adoption of a RHOSP 17.1 control plane.

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.

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

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.

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:

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.

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.

Metadata rate-limiting feature

This update fixes a bug that prevented successful use of metadata rate-limiting. Metadata rate limiting is now available.

Router deletion problem and workaround

After an update to RHOSO 18.0.2, you cannot delete a pre-existing router as expected.

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.

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.

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.

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:

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.

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.

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:

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.

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.

MAC_Binding aging functionality added back in RHOSO 18.0.1

The MAC_Binding aging functionality that was added in RHOSP 17.1.2 was missing from 18.0 GA. This update to RHOSO 18.0.1 adds it back.

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.

Metadata rate-limiting feature

Metadata rate-limiting is not available in RHOSO 18.0.1. A fix is in progress.

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.

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.

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.

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.

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.

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.

Prometheus replaces Gnocchi for metrics storage and metrics-based autoscaling

In RHOSO 18.0, Prometheus replaces Gnocchi for metrics and metrics-based autoscaling.

Compute node log collection

RHOSO uses the Cluster Logging Operator (cluster-logging-operator) to collect and centrally store logs from OpenStack Compute nodes.

Graphing dashboards for OpenStack metrics

The Red Hat OpenShift Container Platform (RHOCP) console UI now provides graphing dashboards for OpenStack Metrics.

The compute service now supports native Secure RBAC

In RHOSP 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.

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.

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.

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 previous 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.

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.

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.

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:

New default for managing instances on NUMA nodes

In RHOSP 17.1.4, the default was to pack instances on NUMA nodes.

Rebuild a volume-backed instance with a different image

This update adds the ability to rebuild a volume-backed instance from a different image.

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.

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.

More options for the server unshelve command

With this update, new options are added to the server unshelve command in RHOSO 18.0.0.

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.

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.

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].

No network block device (NBD) live migration with TLS enabled

In RHOSO 18.0 Beta, a bug prevents you from using a network block device (NBD) to live migrate storage between Compute nodes with TLS enabled. See https://issues.redhat.com/browse/OSPRH-6931.

Cannot delete instance when cpu_power_managment is set to true

In the RHOSO 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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

MAC_Binding aging functionality missing in RHOSO 18.0.0

The MAC_Binding aging functionality that was added in RHOSP 17.1.2 is missing from 18.0 GA. A fix is in progress.

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.

Metadata rate-limiting feature

Metadata rate-limiting is not available in RHOSO 18.0.0. A fix is in progress.

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.

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 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.

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

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.

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.

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.

Password rotation

This update introduces the ability to generate and rotate OpenStack database passwords.

Shared File Systems support for scalable CephFS-NFS

The Shared File Systems service (manila) now supports a scalable 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.

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.

project_id in API URLs now optional

You are no longer required to include project_id in Block Storage service (cinder) API URLs.

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.

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.

openstack-must-gather SOS report support

You can now collect diagnostic information about your RHOSO deployment using the openstack-must-gather.

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.

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.

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.

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:

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.