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

[4.14] IBU x->y->z with no rhcos delta results in ostree corruption

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • None
    • 4.14, 4.15, 4.16
    • RHCOS
    • Low
    • No
    • 1
    • 256 - Core Packages
    • 1
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, if a new deployment was performed at the OSTree level on a host that was identical to the current deployment but on a different stateroot, the OSTree saw them as equal. This behavior incorrectly prevented the boot loader from updating when `set-default` was invoked, as OSTree did not recognize the two stateroots as a differentiation factor for deployments. With this release, OSTree's logic has been modified to consider the stateroots and allows OSTree to properly set the default deployment to a new deployment with different stateroots. (link:https://issues.redhat.com/browse/OCPBUGS-36437[*OCPBUGS-36437*])
      ____________-
      ostree will now correctly also look at the stateroot to determine if a deployment is unique.
      Show
      * Previously, if a new deployment was performed at the OSTree level on a host that was identical to the current deployment but on a different stateroot, the OSTree saw them as equal. This behavior incorrectly prevented the boot loader from updating when `set-default` was invoked, as OSTree did not recognize the two stateroots as a differentiation factor for deployments. With this release, OSTree's logic has been modified to consider the stateroots and allows OSTree to properly set the default deployment to a new deployment with different stateroots. (link: https://issues.redhat.com/browse/OCPBUGS-36437 [* OCPBUGS-36437 *]) ____________- ostree will now correctly also look at the stateroot to determine if a deployment is unique.
    • Bug Fix
    • In Progress

      If a new deployment is done at the OSTree level on the host, which is identical to the current deployment but on a different stateroot, OSTree sees them as equal. This behavior incorrectly prevents updating the bootloader when set-default is invoked, as OSTree does not recognize the two stateroots as a differentiation factor for deployments. The bug is fixed by modifying OSTree's logic to consider the stateroots. This change allows OSTree to properly set the default deployment to a new deployment that has different stateroots.

              rhn-support-jmarrero Joseph Marrero Corchado
              rhcos-bug-bot RHCOS Bug Bot
              Huijing Hei Huijing Hei
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: