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

PPO doesn't respect to "NeverContactSource" policy in ITMS/IDMS

XMLWordPrintable

    • None
    • Multi-Arch Sprint 258
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      When "mirrorSourcePolicy: NeverContactSource" enabled in ITMS/IDMS, PPO can still verify arch info from source image

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

       multiarch-tuning-operator.v0.9.0   

      How reproducible:

       100%   

      Steps to Reproduce:

          1. Create a ITMS with below content
      cat <<EOF | oc create -f -
      apiVersion: config.openshift.io/v1
      kind: ImageTagMirrorSet
      metadata:
        name: mto-itms-never-test
      spec:
        imageTagMirrors:
        - mirrors:
          - my-fake-itms-never-registry.io/google_containers/redis
          source: gcr.io/google_containers/redis
          mirrorSourcePolicy: NeverContactSource
      EOF
          2. wait for mcp finish updated
          3. create a pod to check
      oc new-project mto-test
      oc create -f - <<EOF
      apiVersion: apps/v1
      kind: Deployment
      metadata:
        name: test-deployment
      spec:
        selector:
          matchLabels:
            app: hello-openshift
        replicas: 1
        template:
          metadata:
            labels:
              app: hello-openshift
          spec:
            containers:
            - name: hello-openshift
              image: gcr.io/google_containers/redis:v1
      EOF      

      Actual results:

          PPO set node affinity for arch info in pod

      Expected results:

         the mirror image is unreachable, it's a fake image, and  NeverContactSource is enabled, so PPO should not set node affinity.   

      Additional info:

         

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

                Created:
                Updated:
                Resolved: