Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-85432

RSCT config wiped after update from RHEL 8.6 to 8.8

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • rhel-8.8.0
    • cloud-init
    • None
    • No
    • Moderate
    • 3
    • rhel-virt-cloud
    • ssg_virtualization
    • 3
    • False
    • False
    • Hide

      None

      Show
      None
    • Yes
    • Red Hat Enterprise Linux
    • RHELOPC Sprint 43, RHELOPC Sprint 44, RHELOPC Sprint 45
    • None
    • None
    • Known Issue
    • Hide
      Cause:
      In RHEL 8.7 and later versions, `cloud-init` no longer uses rhel downstream only configuration in the `/rhel/` directory, and instead uses configuration in the `/etc/cloud/cloud.cfg` file which align with upstream cloud.cfg.tmpl. Some modules(e.g. reset_rmc) are updated with this change.

      Consequence:
      As a consequence, RHEL instances configured by using `cloud-init` might lose some of their configuration after you upgrade them from RHEL 8.6 or prior to RHEL 8.7 or later. The RSCT configuration gets reset and it affects clusters with an RSCT peer domain configured. e.g. This prevents the node from rejoining the peer domain and puts it in an unhealthy state.

      Workaround:
      Manually create the lock file before upgrade, so reset_rmc does not run after the update.
      $ touch /var/lib/cloud/instances/$instance-id/sem/config_reset_rmc

      Result:
      The issue could be avoid with this workaround
      Show
      Cause: In RHEL 8.7 and later versions, `cloud-init` no longer uses rhel downstream only configuration in the `/rhel/` directory, and instead uses configuration in the `/etc/cloud/cloud.cfg` file which align with upstream cloud.cfg.tmpl. Some modules(e.g. reset_rmc) are updated with this change. Consequence: As a consequence, RHEL instances configured by using `cloud-init` might lose some of their configuration after you upgrade them from RHEL 8.6 or prior to RHEL 8.7 or later. The RSCT configuration gets reset and it affects clusters with an RSCT peer domain configured. e.g. This prevents the node from rejoining the peer domain and puts it in an unhealthy state. Workaround: Manually create the lock file before upgrade, so reset_rmc does not run after the update. $ touch /var/lib/cloud/instances/$instance-id/sem/config_reset_rmc Result: The issue could be avoid with this workaround
    • Proposed
    • Unspecified
    • Unspecified
    • Unspecified
    • x86_64
    • None

      On an AWS instance, after updating from RHEL 8.6 to 8.8, the config in /var/ct/cfg is wiped since recfgct is run after the host is rebooted. This prevents the node from rejoining the peer domain and puts it in an unhealthy state.

      The file "cloudinit/config/:.py" seems to responsible for this behaviour, from the "cloud-init-22.1-8.el8_8.1.noarch" package.

      {{{{2025-03-28 14:50:25,858 - cc_reset_rmc.py[DEBUG]: Attempting to reset RMC.
      2025-03-28 14:50:25,858 - util.py[DEBUG]: Reading from /etc/ct_node_id (quiet=False)
      2025-03-28 14:50:25,858 - util.py[DEBUG]: Read 129 bytes from /etc/ct_node_id
      2025-03-28 14:50:25,858 - cc_reset_rmc.py[DEBUG]: Node ID at beginning of module: 6f26e400d297e97f
      2025-03-28 14:50:25,858 - subp.py[DEBUG]: Running command ['rmcctrl', '-z'] with allowed return codes [0] (shell=False, capture=True)
      2025-03-28 14:50:32,139 - subp.py[DEBUG]: Running command ['recfgct'] with allowed return codes [0] (shell=False, capture=True)
      2025-03-28 14:50:36,268 - cc_reset_rmc.py[DEBUG]: 0513-071 The ctcas Subsystem has been added.
      0513-071 The ctrmc Subsystem has been added.
      Enabling ctrmc.service for systemctl ...
      0513-059 The ctrmc Subsystem has been started. Subsystem PID is 8453.
      2025-03-28 14:50:36,268 - util.py[DEBUG]: Reading from /etc/ct_node_id (quiet=False)
      2025-03-28 14:50:36,268 - util.py[DEBUG]: Read 129 bytes from /etc/ct_node_id
      2025-03-28 14:50:36,268 - cc_reset_rmc.py[DEBUG]: Node ID at end of module: 9432a23ebe67a103}}}}

        1. logs.tar.gz
          379 kB
          Ryan Woodard
        2. logs_2.tar.gz
          1.02 MB
          Ryan Woodard

              rh-ee-anisinha Ani Sinha
              ryan_w55 Ryan Woodard (Inactive)
              virt-maint virt-maint
              Amy Chen Amy Chen
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: