🌱 Bump OpenStack and Ubuntu in devstack

[mdbooth]

/hold

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mdbooth

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [mdbooth]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!

Name	Link
🔨 Latest commit	f68fbe3
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-cluster-api-openstack/deploys/652555f1b3b625000808fb6d
😎 Deploy Preview	https://deploy-preview-1721--kubernetes-sigs-cluster-api-openstack.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[mdbooth]

/help

Looks like this actually deployed devstack! Then the e2e tests failed. Haven't looked into that yet.

[lentzi90]

Oct 10 14:03:57 capo-e2e-controller cloud-init[1721]: The system is finally up, after 825.36 seconds

This is phenomenal! 🤯

Usually we have something like this

Oct 10 18:06:25 capo-e2e-controller cloud-init[1735]: The system is finally up, after 2372.42 seconds

[jichenjc]

/test pull-cluster-api-provider-openstack-e2e-test

[k8s-ci-robot]

@mdbooth: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cluster-api-provider-openstack-e2e-test	f68fbe3	link	true	/test pull-cluster-api-provider-openstack-e2e-test

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[mdbooth]

Oct 10 14:03:57 capo-e2e-controller cloud-init[1721]: The system is finally up, after 825.36 seconds

This is phenomenal! 🤯

Usually we have something like this

Oct 10 18:06:25 capo-e2e-controller cloud-init[1735]: The system is finally up, after 2372.42 seconds

Probably because it's failing to deploy something critical, which results in the tests failing 😆 Still haven't had a chance to get back to this.

[seanschneeweiss]

Not entirely sure, but maybe related to:

  �[38;5;9m[FAILED] Timed out after 1800.000s.
  No Control Plane machines came into existence. 
  Expected
      <bool>: false
  to be true�[0m
  �[38;5;9mIn �[1m[It]�[0m�[38;5;9m at: �[1m/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.5.1/framework/controlplane_helpers.go:153�[0m �[38;5;243m@ 10/13/23 03:56:58.66�[0m

  �[38;5;9mFull Stack Trace�[0m
    sigs.k8s.io/cluster-api/test/framework.WaitForOneKubeadmControlPlaneMachineToExist({0x2920438?, 0x3d69640}, {{0x7f5e680c9040?, 0xc000a21200?}, 0xc0005a64e0?, 0xc001969900?}, {0xc0023c3ec0, 0x2, 0x2})
    	/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.5.1/framework/controlplane_helpers.go:153 +0x41b
    sigs.k8s.io/cluster-api/test/framework.DiscoveryAndWaitForControlPlaneInitialized({0x2920438?, 0x3d69640}, {{0x7f5e680c9040?, 0xc000a21200?}, 0xc0005a64e0?}, {0xc0023c3ec0, 0x2, 0x2})
    	/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.5.1/framework/controlplane_helpers.go:262 +0x53e
    sigs.k8s.io/cluster-api/test/framework/clusterctl.ApplyCustomClusterTemplateAndWait.setDefaults.func2({_, _}, {{0x2930898, 0xc002364b40}, {0xc001490001, 0x400e9, 0x400ea}, {0xc002871d10, 0x12}, {0xc0023af330, ...}, ...}, ...)
    	/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.5.1/framework/clusterctl/clusterctl_helpers.go:443 +0x98
    sigs.k8s.io/cluster-api/test/framework/clusterctl.ApplyCustomClusterTemplateAndWait({_, _}, {{0x2930898, 0xc002364b40}, {0xc001490001, 0x400e9, 0x400ea}, {0xc002871d10, 0x12}, {0xc0023af330, ...}, ...}, ...)
    	/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.5.1/framework/clusterctl/clusterctl_helpers.go:404 +0xd56
    sigs.k8s.io/cluster-api/test/framework/clusterctl.ApplyClusterTemplateAndWait({_, _}, {{0x2930898, 0xc002364b40}, {{0xc00222ddd0, 0x22}, {0xc00099a800, 0x31}, {0xc001ab3410, 0x17}, ...}, ...}, ...)
    	/root/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.5.1/framework/clusterctl/clusterctl_helpers.go:312 +0x994
    sigs.k8s.io/cluster-api-provider-openstack/test/e2e/suites/e2e.createCluster({0x2920438, 0x3d69640}, {{0xc00222ddd0, 0x22}, {0xc00099a800, 0x31}, {0xc001ab3410, 0x17}, {0x28f6b18, 0x0}, ...}, ...)
    	/home/prow/go/src/sigs.k8s.io/cluster-api-provider-openstack/test/e2e/suites/e2e/e2e_test.go:653 +0x230
    sigs.k8s.io/cluster-api-provider-openstack/test/e2e/suites/e2e.glob..func7.2.1()
    	/home/prow/go/src/sigs.k8s.io/cluster-api-provider-openstack/test/e2e/suites/e2e/e2e_test.go:96 +0x19d

Seems that the control plane node was not bootstrapped correctly. Also the AfterEach part was unable to collect logs via SSH, so no clue if cloud-init failed.

logs

[Updated Event] e2e-0113cg/cluster-e2e-0113cg-control-plane.178d8cf5955f5d3d
	resource: controlplane.cluster.x-k8s.io/v1beta1/KubeadmControlPlane/cluster-e2e-0113cg-control-plane
	reason: ControlPlaneUnhealthy
	message: Waiting for control plane to pass preflight checks to continue reconciliation: Machine cluster-e2e-0113cg-control-plane-kx992 does not have a corresponding Node yet (Machine.status.nodeRef not set)

  [2023-10-13T03:56:58Z] Collecting logs for machine "cluster-e2e-0113cg-control-plane-kx992" and storing them in "/logs/artifacts/clusters/bootstrap/e2e-0113cg/machines/cluster-e2e-0113cg-control-plane-kx992"
  couldn't dial from local to bastion host 172.24.4.155: ssh: handshake failed: EOF

The machines status:

  - lastTransitionTime: "2023-10-13T03:26:50Z"
    reason: WaitingForNodeRef
    severity: Info
    status: "False"
    type: NodeHealthy

[k8s-ci-robot]

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[lentzi90]

I guess this was replaced by #1804? Can we close it?