Skip to content

Conversation

@rajaSahil
Copy link
Contributor

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

What type of PR is this?

Special notes for your reviewer:

Does this PR introduce a user-facing change? Then add your Release Note here:


Documentation:


Signed-off-by: rajaSahil <[email protected]>
@kubermatic-bot
Copy link
Contributor

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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-sigs/prow repository.

@kubermatic-bot
Copy link
Contributor

@rajaSahil: Adding the "do-not-merge/docs-needed" label because no documentation block was detected, please follow our documentation process to remove it.

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.

@kubermatic-bot kubermatic-bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Nov 4, 2025
@kubermatic-bot
Copy link
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@kubermatic-bot kubermatic-bot added the do-not-merge/docs-needed Indicates that a PR should not merge because it's missing one of the documentation labels. label Nov 4, 2025
@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from rajasahil. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

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

@kubermatic-bot kubermatic-bot added the do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. label Nov 4, 2025
@rajaSahil
Copy link
Contributor Author

/test pull-kubeone-e2e-digitalocean-rockylinux-install-containerd-external-v1.32

/test pull-kubeone-e2e-digitalocean-rockylinux-install-containerd-external-v1.33

/test pull-kubeone-e2e-digitalocean-rockylinux-install-containerd-external-v1.34

@kubermatic-bot kubermatic-bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Nov 4, 2025
@rajaSahil
Copy link
Contributor Author

/test pull-kubeone-e2e-digitalocean-default-install-containerd-external-v1.32

/test pull-kubeone-e2e-digitalocean-default-install-containerd-external-v1.33

/test pull-kubeone-e2e-digitalocean-default-install-containerd-external-v1.34

@rajaSahil
Copy link
Contributor Author

/test pull-kubeone-e2e-digitalocean-rockylinux-stable-upgrade-containerd-external-from-v1.32-to-v1.33

/test pull-kubeone-e2e-digitalocean-rockylinux-stable-upgrade-containerd-external-from-v1.33-to-v1.34

1 similar comment
@rajaSahil
Copy link
Contributor Author

/test pull-kubeone-e2e-digitalocean-rockylinux-stable-upgrade-containerd-external-from-v1.32-to-v1.33

/test pull-kubeone-e2e-digitalocean-rockylinux-stable-upgrade-containerd-external-from-v1.33-to-v1.34

@rajaSahil
Copy link
Contributor Author

test pull-kubeone-e2e-digitalocean-rockylinux-stable-upgrade-containerd-external-from-v1.32-to-v1.33

  • Issue with kernel version not supported for k8s v1.32.9
rror was: configuration checking kernel release version\nhost \"k1-1985975265561415680-control-plane-1\" has kernel version \"4.18.0\", which is not supported by kubernetes version \"1.32.9\"; configuration checking kernel release version\nhost \"k1-1985975265561415680-control-plane-2\" has kernel version \"4.18.0\", which is not supported by kubernetes version \"1.32.9\"; configuration checking kernel release version\nhost \"k1-1985975265561415680-control-plane-3\" has kernel version \"4.18.0\", which is not supported by kubernetes version \"1.32.9\""
time="07:45:03 UTC" level=warning msg="Retrying task..."

@rajaSahil
Copy link
Contributor Author

/test pull-kubeone-e2e-digitalocean-default-stable-upgrade-containerd-external-from-v1.32-to-v1.33

/test pull-kubeone-e2e-digitalocean-default-stable-upgrade-containerd-external-from-v1.33-to-v1.34

@rajaSahil
Copy link
Contributor Author

Issue with pull-kubeone-e2e-digitalocean-default-stable-upgrade-containerd-external-from-v1.33-to-v1.34

kubernetes version does not satisfy version constraint '<=1.32': 1.33.5 is greater than 1.32. This version is not yet supported. Please refer to the Compatibility section of docs for more details.
Error: configuration validation

@rajaSahil
Copy link
Contributor Author

The above mentioned issue is coming for all upgrade tests v1.33 to v1.34.

@rajaSahil
Copy link
Contributor Author

/test pull-kubeone-e2e-digitalocean-default-stable-upgrade-containerd-external-from-v1.33-to-v1.34

@rajaSahil
Copy link
Contributor Author

/test pull-kubeone-e2e-digitalocean-rockylinux-stable-upgrade-containerd-external-from-v1.32-to-v1.33

@kubermatic-bot
Copy link
Contributor

@rajaSahil: The following tests 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-kubeone-e2e-digitalocean-rockylinux-stable-upgrade-containerd-external-from-v1.33-to-v1.34 2d3c7db link true /test pull-kubeone-e2e-digitalocean-rockylinux-stable-upgrade-containerd-external-from-v1.33-to-v1.34
pull-kubeone-e2e-digitalocean-rockylinux-stable-upgrade-containerd-external-from-v1.32-to-v1.33 2d3c7db link true /test pull-kubeone-e2e-digitalocean-rockylinux-stable-upgrade-containerd-external-from-v1.32-to-v1.33

Full PR test history

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-sigs/prow repository. I understand the commands that are listed here.

@rajaSahil
Copy link
Contributor Author

/test pull-kubeone-e2e-digitalocean-rockylinux-upgrade-cilium-containerd-external-from-v1.32-to-v1.33
/test pull-kubeone-e2e-digitalocean-rockylinux-upgrade-cilium-containerd-external-from-v1.33-to-v1.34
/test pull-kubeone-e2e-digitalocean-rockylinux-upgrade-containerd-external-from-v1.32-to-v1.33
/test pull-kubeone-e2e-digitalocean-rockylinux-upgrade-containerd-external-from-v1.33-to-v1.34

@rajaSahil rajaSahil changed the title Test KubeOne Release v1.12 - Cluster Provisioning (External) on DigitalOcean Test KubeOne Release v1.12 - Cluster Upgrade (External) on DigitalOcean Nov 17, 2025
@rajaSahil rajaSahil closed this Nov 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. do-not-merge/docs-needed Indicates that a PR should not merge because it's missing one of the documentation labels. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants