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

Migration controller unable to retry unpause resource if it fails

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • No
    • None
    • None
    • Done
    • Bug Fix
    • Hide
      * Before this update, the two-way synchronization controller on clusters that support migrating Machine API resources to Cluster API resources prematurely reported a successful migration.
      As a consequence, if any errors were encountered when updating the status of related objects, the operation was not retried.
      With this release, the controller ensures that all related object statuses are written before reporting a successful status.
      As a result, the controller handles errors during migration better.
      (link:https://issues.redhat.com/browse/OCPBUGS-57040[OCPBUGS-57040])
      Show
      * Before this update, the two-way synchronization controller on clusters that support migrating Machine API resources to Cluster API resources prematurely reported a successful migration. As a consequence, if any errors were encountered when updating the status of related objects, the operation was not retried. With this release, the controller ensures that all related object statuses are written before reporting a successful status. As a result, the controller handles errors during migration better. (link: https://issues.redhat.com/browse/OCPBUGS-57040 [ OCPBUGS-57040 ])
    • None
    • None
    • None
    • None

      Description of problem:

          The migration controllers shortcut reconciliation if their status indicate prior success. Therefore setting this status must be the last thing the controller does after all work is complete.We were unpausing after setting completion status. Therefore if we failed to set unpause due to, e.g. an epheral api-server issue, we would never retry.

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

      4.20.0

      How reproducible:

          Hard to reproduce, only the unpausing would need to fail to trigger this issue

      Steps to Reproduce:

          1. Migrate a resource from MAPI to CAPI 
    2. Somehow fail to unpause resource
    3.

      Actual results:

          CAPI resource stays paused and never gets unpaused

      Expected results:

          The unpausing is retried and the CAPI resource is eventually unpaused

      Additional info:

              rhn-gps-mbooth Matthew Booth
              ddonati@redhat.com Damiano Donati
              None
              None
              Zhaohua Sun Zhaohua Sun
              None
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: