Change:
"[] Container Runtime blackbox test when running a container with a new image should be able to pull from private registry with secret [NodeConformance]" is failing consistently for Windows 1909 on GCE, but it's passing for 2019. Likely one of the containers it depends on hasn't been rebuilt as multi-arch? Failure message from
/sig windows cc
More useful output from build- Seems the container doesn't work on 1909. cc
/sig windows
This test is also failing on for Windows 1903.
see
Ah, thanks, I searched k/k for an existing issue but didn't think to search windows-testing. I posted a follow-up there.
Hi. It is a known issue, I've also reported it a while back:
, do you have push right to the ` manifest list to include the newer Windows OS versions. Basically, the commands are: docker manifest create docker manifest push --purge
/kind failing-test
I tried running this but got: I looked into the project and noticed and as owners. Are you able to assist?
/assign
docker manifest push Pushed ref with digest: sha256:ec76696da5a660a02bbfd304549d6e09d8c9fe48f2d4efe642f26cb1e46a6bde Pushed ref with digest: sha256:7c4ee446a647fdf8988672ae5e685cb66d53d4581e057b02e3a2bad728177f48 Pushed ref with digest: sha256:297cce9134ddaa2c09d91dea7ab7af0e58e06e59858c0311a0770143d144ddf1 sha256:fb9b25770487567c02bf90dd3edea7917323556d1b7ba81ec042ffd5f9effeae
this is fixed. the image manifest is available in
/close
Closing this issue. <detailsIn response to : /close Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details

Discussion:
--network="${KUBE_GCE_NETWORK:-${KUBE_GKE_NETWORK:-e2e}}"  --node-tag="${NODE_TAG:-}"  --master-tag="${MASTER_TAG:-}"  <ins> --docker-config-file="${DOCKER_CONFIG_FILE:-}"  </ins> --dns-domain="${KUBE_DNS_DOMAIN:-cluster.local}"  --ginkgo.slowSpecThreshold="${GINKGO_SLOW_SPEC_THRESHOLD:-300}"  ${KUBE_CONTAINER_RUNTIME:+"--container-runtime=${KUBE_CONTAINER_RUNTIME}"} 

import ( "context" "fmt" <ins> "io/ioutil" </ins> "path" "time"

} } }` <ins> // we might be told to use a different docker config JSON. if framework.TestContext.DockerConfigFile != "" { contents, err := ioutil.ReadFile(framework.TestContext.DockerConfigFile) framework.ExpectNoError(err) auth = string(contents) } </ins> secret := &v1.Secret{ Data: map[string][]byte{v1.DockerConfigJsonKey: []byte(auth)}, Type: v1.SecretTypeDockerConfigJson,

// SpecSummaryOutput is the file to write ginkgo.SpecSummary objects to as tests complete. Useful for debugging and test introspection. SpecSummaryOutput string <ins> // DockerConfigFile is a file that contains credentials which can be used to pull images from certain private registries, needed for a test. DockerConfigFile string </ins> } // NodeKillerConfig describes configuration of NodeKiller -- a utility to

flags.StringVar(&TestContext.ProgressReportURL, "progress-report-url", "", "The URL to POST progress updates to as the suite runs to assist in aiding integrations. If empty, no messages sent.") flags.StringVar(&TestContext.SpecSummaryOutput, "spec-dump", "", "The file to dump all ginkgo.SpecSummary to after tests run. If empty, no objects are saved/printed.") <ins> flags.StringVar(&TestContext.DockerConfigFile, "docker-config-file", "", "A file that contains credentials which can be used to pull images from certain private registries, needed for a test.") </ins> } // RegisterClusterFlags registers flags specific to the cluster e2e test suite.