This job view page is being replaced by Spyglass soon. Check out the new job view.
PRk8s-infra-cherrypick-robot: [release-1.2] 🐛 patch managed fields after `clusterctl move` so that it does not own all fields
Tests 1 failed / 1 succeeded
Started2022-11-07 19:17
Refs 7512

Test Failures

capi-e2e When upgrading a workload cluster using ClusterClass with RuntimeSDK [PR-Informing] [ClusterClass] Should create, upgrade and delete a workload cluster 7m11s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capi\-e2e\sWhen\supgrading\sa\sworkload\scluster\susing\sClusterClass\swith\sRuntimeSDK\s\[PR\-Informing\]\s\[ClusterClass\]\sShould\screate\,\supgrade\sand\sdelete\sa\sworkload\scluster$'
Timed out after 60.001s.
Failed to list MachineList object for Cluster k8s-upgrade-with-runtimesdk-ybet0h/k8s-upgrade-with-runtimesdk-pg9k76
Expected success, but got an error:
    <*url.Error | 0xc000bb8540>: {
        Op: "Get",
        URL: "",
        Err: <*net.OpError | 0xc000317a40>{
            Op: "dial",
            Net: "tcp",
            Source: nil,
            Addr: <*net.TCPAddr | 0xc000bb8480>{
                IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 127, 0, 0, 1],
                Port: 44015,
                Zone: "",
            Err: <*os.SyscallError | 0xc0009c5300>{
                Syscall: "connect",
                Err: <syscall.Errno>0x6f,
    Get "": dial tcp connect: connection refused
				Click to see stdout/stderrfrom junit.e2e_suite.3.xml

Filter through log files | View test history on testgrid

Show 1 Passed Tests

Show 19 Skipped Tests

Error lines from build-log.txt

... skipping 1131 lines ...
INFO: Waiting for the machine deployments to be provisioned
STEP: Waiting for the workload nodes to exist
STEP: Checking all the machines controlled by quick-start-98fmcm-md-0-sfnbr are in the "fd4" failure domain
INFO: Waiting for the machine pools to be provisioned
STEP: Dumping logs from the "quick-start-98fmcm" workload cluster
Failed to get logs for machine quick-start-98fmcm-md-0-sfnbr-67dc969b47-vhq5d, cluster quick-start-ekcy3d/quick-start-98fmcm: exit status 2
Failed to get logs for machine quick-start-98fmcm-sfp6f-lqtwq, cluster quick-start-ekcy3d/quick-start-98fmcm: exit status 2
STEP: Dumping all the Cluster API resources in the "quick-start-ekcy3d" namespace
STEP: Deleting cluster quick-start-ekcy3d/quick-start-98fmcm
STEP: Deleting cluster quick-start-98fmcm
INFO: Waiting for the Cluster quick-start-ekcy3d/quick-start-98fmcm to be deleted
STEP: Waiting for cluster quick-start-98fmcm to be deleted
STEP: Deleting namespace used for hosting the "quick-start" test spec
... skipping 3 lines ...
• [SLOW TEST:115.163 seconds]
When following the Cluster API quick-start with ClusterClass [PR-Informing] [ClusterClass]
  Should create a workload cluster
{"component":"entrypoint","file":"","func":"","level":"error","msg":"Entrypoint received interrupt: terminated","severity":"error","time":"2022-11-07T19:30:40Z"}
++ early_exit_handler
++ '[' -n 164 ']'
++ kill -TERM 164
++ cleanup_dind
++ [[ true == \t\r\u\e ]]
++ echo 'Cleaning up after docker'
... skipping 6 lines ...