Uploaded image for project: 'OpenShift Windows Containers'
  1. OpenShift Windows Containers
  2. WINC-1306

Make file transfer logic more resilient

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • 8
    • False
    • None
    • False

      Description

      There are multiple places in the code base where we follow this pattern of looping over nodes for file transfer (configmap_controller, controllerconfig_controller, regstry_controller), and all face the same issue: if any single VM flakes on file transfer, this is going to cause all other instances to go through the file transfer again. We should make this logic more resilient to avoid this potential issue.

      Engineering Details

      Might need to introduce a way to recognize that an instance is up to date in terms of file transfer in order to skip it, much like we do with the version annotation.

      Acceptance Criteria

      File transfer does not re-loop over all nodes in cluster if transfer to one fails.

       

      Spurred from https://github.com/openshift/windows-machine-config-operator/pull/2163/commits/edff154f0b052c9ffd32107df9dfc596b3f020b0#r1619513848

              Unassigned Unassigned
              mohashai Mohammad Shaikh (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: