kubernetes: [Failing test] periodic-conformance-main-k8s-main
Which jobs are failing?
master-informing
- periodic-conformance-main-k8s-main
Which tests are failing?
- capa-e2e-conformance.AfterSuite
- capa-e2e-conformance.BeforeSuite
Since when has it been failing?
10-25 22:18 IST
Testgrid link
https://testgrid.k8s.io/sig-release-master-informing#periodic-conformance-main-k8s-main
Reason for failure (if possible)
{ Failure /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/suites/conformance/conformance_suite_test.go:46
Failed to read file "aws" / "/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/data/infrastructure-aws/withclusterclass/generated/cluster-template-topology.yaml"
Unexpected error:
<*fs.PathError | 0xc000ada690>: {
Op: "open",
Path: "/home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/data/infrastructure-aws/withclusterclass/generated/cluster-template-topology.yaml",
Err: <syscall.Errno>0x2,
}
open /home/prow/go/src/sigs.k8s.io/cluster-api-provider-aws/test/e2e/data/infrastructure-aws/withclusterclass/generated/cluster-template-topology.yaml: no such file or directory
occurred
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.2/framework/clusterctl/repository.go:101}
Anything else we need to know?
No response
Relevant SIG(s)
/sig cloud-provider /area provider/aws cc @kubernetes/ci-signal
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 18 (7 by maintainers)
the version upgrade is currently blocked by PR. once this PR is in, we would be generating AMIs within a day or two, and then raise PR with upgraded version in conformance test.
looks like #image-builder is still using containerd_version as v1.6.2 as default version. So we have all the existing AMIs with this version due to which our conformance tests in k8s main branch is failing. We would focus on fixing the generation of AMIs from CAPA side, and post that we would be able to handle this by generating new AMIs with containerd version >= 1.6.11. Till then, this would be in blocked state.
The same tests are running fine in other environments, and locally as well, so this should not be a blocker. But we are not able to find out the root cause.