Uploaded image for project: 'Multiple Architecture Enablement'
  1. Multiple Architecture Enablement
  2. MULTIARCH-5363

The label [multiarch.openshift.io/preferred-node-affinity] isn't correctly set when hitting circuit breaking due to permanent image inspection error

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • Multi-Arch Sprint 268, Multi-Arch Sprint 269
    • Proposed
    • Bug Fix
    • Hide
      Previously, if image inspection failed after all retries, and the nodeAffinityScoring plugin was enabled, pod labels for nodeAffinityScoring were incorrectly set. This release ensures that nodeAffinityScoring labels are now applied independently of the required affinity process results.
      Show
      Previously, if image inspection failed after all retries, and the nodeAffinityScoring plugin was enabled, pod labels for nodeAffinityScoring were incorrectly set. This release ensures that nodeAffinityScoring labels are now applied independently of the required affinity process results.

      "multiarch.openshift.io/preferred-node-affinity" label doesn't been set correctly when ppc can't inspect pod image correct after max retries, it set preferred node affinity, but the label is "multiarch.openshift.io/preferred-node-affinity=not-set"

              tzivkovi@redhat.com Tori Zivkovic
              lwan-wanglin Lin Wang
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: