When pods are created with a node name already set, the pod scheduling web hook should not add the scheduling gate.

    0.9.0

    Always

    1. Install the multiarch tuning operator
    2. Deploy the PodPlacementConfig CR
    3. Create a pod with the node name already set:

apiVersion: v1
kind: Pod
metadata:
  name: example
  labels:
    app: httpd
  namespace: mmo-devel-test
spec:
  nodeName: ip-10-29-1-81.us-east-2.compute.internal
  securityContext:
    runAsNonRoot: true
    seccompProfile:
      type: RuntimeDefault
  containers:
    - name: httpd
      image: 'image-registry.openshift-image-registry.svc:5000/openshift/httpd:latest'
      ports:
        - containerPort: 8080
      securityContext:
        allowPrivilegeEscalation: false
        capabilities:
          drop:
            - ALL
     

    >Error creating Pod: Pod "master" is invalid: spec.nodeName: Forbidden: cannot be set until all schedulingGates have been cleared Ginkgo exit error 1: exit with code 1}

    The webhook doesn't add the scheduling gate if the field spec.nodeName is not empty