This job view page is being replaced by Spyglass soon. Check out the new job view.
PRjsturtevant: Fix Capi e2e tests by upgrading from 1.22
ResultABORTED
Tests 3 failed / 9 succeeded
Started2021-10-25 17:46
Elapsed2h9m
Revisionebd91e9b15a83c8ddeeb1b2eb61b131d2c6133c7
Refs 1792

Test Failures


capz-e2e Running the Cluster API E2E tests Running the MachineDeployment rollout spec Should successfully upgrade Machines upon changes in relevant MachineDeployment fields 1h16m

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\sRunning\sthe\sCluster\sAPI\sE2E\stests\sRunning\sthe\sMachineDeployment\srollout\sspec\sShould\ssuccessfully\supgrade\sMachines\supon\schanges\sin\srelevant\sMachineDeployment\sfields$'
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.0.0/e2e/md_rollout.go:73
Timed out after 3600.001s.
Expected
    <bool>: false
to be true
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.0.0/framework/machinedeployment_helpers.go:208
				
				Click to see stdout/stderrfrom junit.e2e_suite.3.xml

Filter through log files | View test history on testgrid


capz-e2e Running the Cluster API E2E tests Should successfully exercise machine pools Should successfully create a cluster with machine pool machines 36m51s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\sRunning\sthe\sCluster\sAPI\sE2E\stests\sShould\ssuccessfully\sexercise\smachine\spools\sShould\ssuccessfully\screate\sa\scluster\swith\smachine\spool\smachines$'
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.0.0/e2e/machine_pool.go:76
Timed out after 1800.002s.
Error: Unexpected non-nil/non-zero extra argument at index 1:
	<*url.Error>: &url.Error{Op:"Get", URL:"https://127.0.0.1:33173/apis/cluster.x-k8s.io/v1beta1/namespaces/machine-pool-2q4hk7/machinepools/machine-pool-4zbf89-mp-0", Err:(*net.OpError)(0xc000e33630)}
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.0.0/framework/machinepool_helpers.go:85
				
				Click to see stdout/stderrfrom junit.e2e_suite.1.xml

Filter through log files | View test history on testgrid


capz-e2e Running the Cluster API E2E tests Should successfully set and use node drain timeout A node should be forcefully removed if it cannot be drained in time 11m16s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\sRunning\sthe\sCluster\sAPI\sE2E\stests\sShould\ssuccessfully\sset\sand\suse\snode\sdrain\stimeout\sA\snode\sshould\sbe\sforcefully\sremoved\sif\sit\scannot\sbe\sdrained\sin\stime$'
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.0.0/e2e/node_drain_timeout.go:82
Failed to get controller-runtime client
Unexpected error:
    <*url.Error | 0xc00043c3c0>: {
        Op: "Get",
        URL: "https://127.0.0.1:33173/api?timeout=32s",
        Err: <*net.OpError | 0xc000345ef0>{
            Op: "dial",
            Net: "tcp",
            Source: nil,
            Addr: <*net.TCPAddr | 0xc00043c390>{
                IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 127, 0, 0, 1],
                Port: 33173,
                Zone: "",
            },
            Err: <*os.SyscallError | 0xc000ccb020>{
                Syscall: "connect",
                Err: <syscall.Errno>0x6f,
            },
        },
    }
    Get "https://127.0.0.1:33173/api?timeout=32s": dial tcp 127.0.0.1:33173: connect: connection refused
occurred
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.0.0/framework/cluster_proxy.go:171
				
				Click to see stdout/stderrfrom junit.e2e_suite.3.xml

Filter through log files | View test history on testgrid


Show 9 Passed Tests

Show 10 Skipped Tests