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

CNI config load failed on fs change event

XMLWordPrintable

    • Low
    • 3
    • WINC - Sprint 246, WINC - Sprint 248
    • 2
    • False
    • Hide

      None

      Show
      None
    • Hide
      Fixes an issue where the containerd CNI config would be reloaded unnecessarily, potentially resulting in container restarts and brief network outages. This was caused by WICD not correctly accounting for carriage returns when identifying if the CNI config had been modified or not. This has been taken into account, and WICD will now only alter the CNI configuration when a change needs to be reverted.
      Show
      Fixes an issue where the containerd CNI config would be reloaded unnecessarily, potentially resulting in container restarts and brief network outages. This was caused by WICD not correctly accounting for carriage returns when identifying if the CNI config had been modified or not. This has been taken into account, and WICD will now only alter the CNI configuration when a change needs to be reverted.
    • Bug Fix
    • In Progress
    • Customer Escalated

      Description of problem:
      Seeing

      time="2022-10-26T00:52:43.727448300Z" level=error msg="failed to reload cni configuration after receiving fs change event(\"C:\\\\k\\\\cni\\\\config\\\\cni.conf\": WRITE)" error="cni config load failed: failed to load CNI config file C:\\k\\cni\\config\\cni.conf: error parsing configuration: unexpected end of JSON input: invalid cni config: failed to load cni config"
time="2022-10-26T00:52:56.906464200Z" level=error msg="failed to reload cni configuration after receiving fs change event(\"C:\\\\k\\\\cni\\\\config\\\\cni.conf\": WRITE)" error="cni config load failed: failed to load CNI config file C:\\k\\cni\\config\\cni.conf: error reading C:\\k\\cni\\config\\cni.conf: open C:\\k\\cni\\config\\cni.conf: The process cannot access the file because it is being used by another process.: invalid cni config: failed to load cni config"

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

      WMCO 7.0.0

      How reproducible:

      Always

      Steps to Reproduce:

      1. Bring up a Windows node
2. Check the containerd log

      Actual results:

      Failure to reload CNI config, occurs every 2 minutes or so.

      Expected results:

      This error should not show up after initial setup.

      Additional info:

      It is unclear if this is causing any issues but we need to confirm that and preferably make the error go away. Otherwise most bugs from the field are going to point at this.

            rh-ee-ssoto Sebastian Soto
            paravindh Aravindh Puthiyaparambil
            Aharon Rasouli Aharon Rasouli
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated: