Red Hat Summit 红帽全球峰会支持控制台（Console）开发人员开始试用联系人

此内容没有您所选择的语言版本。

Chapter 3. Performing pre-upgrade actions

Perform pre-upgrade actions to ensure that your Red Hat OpenStack Platform environment is ready to be upgraded and to avoid potential issues during the upgrade.

For more information about additional pre-upgrade checks to perform on the undercloud, see the Pre-upgrade Checks section in the Red Hat Knowledgebase article FFU 16.2 - 17.1. Undercloud Upgrade Checks.

3.1. Checking the health of the OVN cluster
复制链接

Before you upgrade your environment, validate that the OVN cluster is healthy. If the output from the overcloud Controller node shows the ovndb_servers resource in Failed Resource Actions, you must resolve this issue to avoid a data plane failure during the upgrade.

Procedure

  1. Check the status of the OVN cluster resources and fix any issues: 

    $ sudo pcs status
    Note

    If you need help resolving any issues, contact Red Hat Support before you proceed with the upgrade.

  2. Check in the Failed Resource Actions section of the output of the OVN cluster resources status for the following error: 

    Failed Resource Actions:
  * ovndb_servers_monitor_30000 on ovn-dbs-bundle-1 'not running' (7): call=24, status='complete', exitreason='', last-rc-change='2025-08-08 09:21:30Z', queued=0ms, exec=159ms

  3. If you see the error, check the status of the ovndb_servers resource on controller-0: 

    $ sudo podman exec <ovn-dbs container> ovs-appctl -t /var/run/openvswitch/ovnnb_db.ctl ovsdb-server/sync-status
    • Replace <ovn-dbs container> with the name of the ovn-dbs container that you want to check.

  4. If the output includes a reference to the IP address, 192.0.2.254, instead of the virtual IP address, you must restart the ovn-dbs-bundle on the overcloud Controller node: 

    $ sudo pcs resource restart ovn-dbs-bundle

    192.0.2.254 is a fallback IP address. Its presence in the output indicates that there is an issue.

Verification

  • Check the status of the OVN cluster resources and confirm that the Failed Resource Actions error is gone: 

    $ sudo pcs status
$ sudo podman exec <ovn-dbs container> ovs-appctl -t /var/run/openvswitch/ovnnb_db.ctl ovsdb-server/sync-status

    If the error is still there, contact Red Hat Support for assistance.

3.2. Network configuration file conversion
复制链接

If your network configuration templates include the following functions, you must manually convert your NIC templates to Jinja2 Ansible format before you upgrade the undercloud. The following functions are not supported with automatic conversion:

  • 'get_file'
  • 'get_resource'
  • 'digest'
  • 'repeat'
  • 'resource_facade'
  • 'str_replace'
  • 'str_replace_strict'
  • 'str_split'
  • 'map_merge'
  • 'map_replace'
  • 'yaql'
  • 'equals'
  • 'if'
  • 'not'
  • 'and'
  • 'or'
  • 'filter'
  • 'make_url'
  • 'contains'

For more information about manually converting your NIC templates, see Manually converting NIC templates to Jinja2 Ansible format in Customizing your Red Hat OpenStack Platform deployment.

3.3. Deployment file configuration
复制链接

Before you run the undercloud upgrade, extract the following files and check that there are no issues. If there are issues, the files might not generate during the undercloud upgrade. For more information about extracting the files, see Files are not generated after undercloud upgrade during RHOSP upgrade from 16.2 to 17.1.

  • tripleo-<stack>-passwords.yaml
  • tripleo-<stack>-network-data.yaml
  • tripleo-<stack>-virtual-ips.yaml
  • tripleo-<stack>-baremetal-deployment.yaml

Before you upgrade your environment, you must confirm that all of your bare-metal provisioned nodes are in the ACTIVE state. If any nodes are in the MAINTENANCE state, you must unset the MAINTENANCE state. If any nodes remain in the MAINTENANCE state, you cannot proceed with the upgrade.

Procedure

  1. Confirm that all bare-metal provisioned nodes are in the ACTIVE state: 

    $ openstack baremetal node list

  2. If any nodes are in the MAINTENANCE state, identify and troubleshoot the root cause of the nodes that are in MAINTENANCE by running the following command and checking the last_error field: 

    $ openstack baremetal node show <node_uuid>
    • Replace <node_uuid> with the UUID of the node.

  3. Unset the MAINTENANCE state: 

     $ openstack baremetal node maintenance unset <node_uuid>

    Wait three to five minutes to see if the node returns to the MAINTENANCE state.

    Important

    If you are unable to remove the nodes from MAINTENANCE, contact Red Hat Support.

3.5. Replacing the unsupported OVNDBS service
复制链接

Before you upgrade from Red Hat OpenStack Platform 16.2 to 17.1, replace the following unsupported service to avoid an upgrade failure: 

OS::TripleO::Services::OVNDBs: deployment/ovn/ovn-dbs-pacemaker-puppet.yaml

Procedure

  1. Open the configuration file that includes the following service: 

    OS::TripleO::Services::OVNDBs: deployment/ovn/ovn-dbs-pacemaker-puppet.yaml

  2. Replace OS::TripleO::Services::OVNDBs: deployment/ovn/ovn-dbs-pacemaker-puppet.yaml with the following service: 

    OS::TripleO::Services::OVNDBs: deployment/ovn/ovn-dbs-cluster-ansible.yaml
  3. Save the file.

Next steps

The updated configuration is applied when you run the openstack overcloud upgrade prepare script, and then upgrade the overcloud. For more information about the upgrade preparation, see Performing the overcloud adoption and preparation. For more information about the overcloud upgrade, see Upgrading RHOSP on all nodes in each stack.

Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务，以及可以信赖的内容，帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情，请参阅红帽博客.

關於紅帽

我们提供强化的解决方案，使企业能够更轻松地跨平台和环境（从核心数据中心到网络边缘）工作。

Theme

© 2026 Red Hat返回顶部