Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-30094

Upgrading from 4.15.0-rc.8 > 4.15.0 results in rpm-ostreed.service failing

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • No
    • None
    • Proposed
    • CNF RAN Sprint 250
    • 1
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-30063. The following is the description of the original issue:

      Description of problem:

      When upgrading an SNO cluster from 4.15.0-rc.8 to 4.15.0, the rpm-ostreed service fails with the error:
      
      Feb 28 21:03:42 target-0-0 rpm-ostree[108678]: error: Couldn't start daemon: Error setting up sysroot: loading sysroot: Parsing deployment /ostree/boot.1/rhcos_4.15.0_rc.8/394d569757117548212df2a310c18885a21afcc4219870f1f3755b858be85253/0 in stateroot 'rhcos_4.15.0_rc.8': readlinkat: No such file or directory

      Version-Release number of selected component (if applicable):

      Current OCP version: 4.15.0-rc.8
      Target OCP version: 4.15.0
      LCA: lifecycle-agent.v4.15.0

      How reproducible:

      1/1

      Steps to Reproduce:

      1. Install SNO cluster with OCP version 4.15.0-rc.8 
      2. Use IBU to upgrade cluster to 4.15.0

      Actual results:

      IBU gets stuck during the Upgrade phase and lca controller manager outputs error:
      
      2024-02-28T22:10:07Z    ERROR    Reconciler error    {"controller": "imagebasedupgrade", "controllerGroup": "lca.openshift.io", "controllerKind": "ImageBasedUpgrade", "ImageBasedUpgrade": {"name":"upgrade"}, "namespace": "", "name": "upgrade", "reconcileID": "85e07ab7-b9e1-431d-b027-aaf991c1094a", "error": "Job for rpm-ostreed.service failed because the control process exited with error code.\nSee \"systemctl status rpm-ostreed.service\" and \"journalctl -xeu rpm-ostreed.service\" for details.\n× rpm-ostreed.service - rpm-ostree System Management Daemon\n     Loaded: loaded (/usr/lib/systemd/system/rpm-ostreed.service; static)\n    Drop-In: /run/systemd/system/rpm-ostreed.service.d\n             └─bug2111817.conf\n             /etc/systemd/system/rpm-ostreed.service.d\n             └─mco-controlplane-nice.conf\n     Active: failed (Result: exit-code) since Wed 2024-02-28 22:10:07 UTC; 10ms ago\n       Docs: man:rpm-ostree(1)\n    Process: 259258 ExecStart=rpm-ostree start-daemon (code=exited, status=1/FAILURE)\n   Main PID: 259258 (code=exited, status=1/FAILURE)\n     Status: \"error: Couldn't start daemon: Error setting up sysroot: loading sysroot: Parsing deployment /ostree/boot.1/rhcos_4.15.0_rc.8/394d569757117548212df2a310c18885a21afcc4219870f1f3755b858be85253/0 in stateroot 'rhcos_4.15.0_rc.8': readlinkat: No such file or directory\"\n        CPU: 155ms\n\nFeb 28 22:10:07 target-0-0 systemd[1]: Starting rpm-ostree System Management Daemon...\nFeb 28 22:10:07 target-0-0 rpm-ostree[259258]: Reading config file '/etc/rpm-ostreed.conf'\nFeb 28 22:10:07 target-0-0 rpm-ostree[259258]: error: Couldn't start daemon: Error setting up sysroot: loading sysroot: Parsing deployment /ostree/boot.1/rhcos_4.15.0_rc.8/394d569757117548212df2a310c18885a21afcc4219870f1f3755b858be85253/0 in stateroot 'rhcos_4.15.0_rc.8': readlinkat: No such file or directory\nFeb 28 22:10:07 target-0-0 systemd[1]: rpm-ostreed.service: Main process exited, code=exited, status=1/FAILURE\nFeb 28 22:10:07 target-0-0 systemd[1]: rpm-ostreed.service: Failed with result 'exit-code'.\nFeb 28 22:10:07 target-0-0 systemd[1]: Failed to start rpm-ostree System Management Daemon.\nerror: Loading sysroot: exit status: 1\n: exit status 1"}

      Expected results:

      Upgrade is successful

      Additional info:

      The cluster was upgraded from 4.14.14 > 4.15.0-rc.8 > 4.15.0

              jche@redhat.com Jun Chen
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              None
              Trey West Trey West
              None
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: