Red Hat Summit Red Hat Summit지원콘솔개발자평가판 시작연락처

이 콘텐츠는 선택한 언어로 제공되지 않습니다.

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
    Copy to Clipboard Toggle word wrap
    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
    Copy to Clipboard Toggle word wrap

  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
    Copy to Clipboard Toggle word wrap
    • 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
    Copy to Clipboard Toggle word wrap

    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
    Copy to Clipboard Toggle word wrap

    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

3.4. Setting bare-metal provisioned nodes to the active state
링크 복사

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
    Copy to Clipboard Toggle word wrap

  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>
    Copy to Clipboard Toggle word wrap
    • Replace <node_uuid> with the UUID of the node.

  3. Unset the MAINTENANCE state: 

     $ openstack baremetal node maintenance unset <node_uuid>
    Copy to Clipboard Toggle word wrap

    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.

맨 위로 이동
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2025 Red Hat