Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: add Ubuntu 24.04 support #11132

Merged
merged 1 commit into from
May 18, 2024

Conversation

tico88612
Copy link
Member

What type of PR is this?

/kind feature

What this PR does / why we need it:

Support Ubuntu 24.04

Which issue(s) this PR fixes:

Related #11124

Special notes for your reviewer:

Ubuntu 22.04 Ref. #8958

Does this PR introduce a user-facing change?:

Support Ubuntu 24.04

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Apr 28, 2024
@k8s-ci-robot
Copy link
Contributor

Hi @tico88612. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@k8s-ci-robot k8s-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Apr 28, 2024
@tico88612 tico88612 changed the title CI: add ubuntu 24.04 support CI: add Ubuntu 24.04 support Apr 28, 2024
@yankay
Copy link
Member

yankay commented Apr 30, 2024

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Apr 30, 2024
@VannTen
Copy link
Contributor

VannTen commented May 7, 2024

If there is one, please also add a vagrant box in the supported_os map in Vagrantfile. That makes it vastly easier to locally test stuff, rather than relying on CI (on my machine that's 5 minutes vs more than 1 hour)

@ant31
Copy link
Contributor

ant31 commented May 7, 2024

do you have access the the CI logs ?

here the error:

Tuesday 07 May 2024  11:23:49 +0000 (0:00:01.132)       0:02:36.626 *********** 
FAILED - RETRYING: [instance-1]: Ensure docker packages are installed (4 retries left).
FAILED - RETRYING: [instance-1]: Ensure docker packages are installed (3 retries left).
FAILED - RETRYING: [instance-1]: Ensure docker packages are installed (2 retries left).
FAILED - RETRYING: [instance-1]: Ensure docker packages are installed (1 retries left).
TASK [container-engine/docker : Ensure docker packages are installed] **********
task path: /builds/kargo-ci/kubernetes-sigs-kubespray/roles/container-engine/docker/tasks/main.yml:120
fatal: [instance-1]: FAILED! => {"attempts": 4, "cache_update_time": 1715081056, "cache_updated": true, "changed": false, "msg": "no available installation candidate for containerd.io=1.6.28-1"}

and others:

        "kube-system   coredns-69db55dd76-wmrd9                   0/1     CrashLoopBackOff   4 (32s ago)    2m      10.233.87.129    instance-1   <none>           <none>",

@tico88612
Copy link
Member Author

@ant31 Docker has a history of past commits, so I think I can handle that part, but I don't have any idea about CoreDNS for now.

@ant31
Copy link
Contributor

ant31 commented May 7, 2024

yes, hard to tell without the pod logs.
You could modify the CI script to fetch the logs of CrashLooping pods, or deploy it in a kind locally or something and check what's up.

@VannTen
Copy link
Contributor

VannTen commented May 7, 2024 via email

@tico88612
Copy link
Member Author

@VannTen How to run local tests via Vagrantfile?

@VannTen
Copy link
Contributor

VannTen commented May 8, 2024 via email

@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels May 10, 2024
@tico88612
Copy link
Member Author

I tested in the local Vagrant and searched for some relevant documentation, but I still had no idea why it happened.

vagrant@kub-1:~$ sudo kubectl logs -n kube-system   coredns-69db55dd76-vh84k
.:53
[INFO] plugin/reload: Running configuration SHA512 = b59f020f1adb6e5c87959bc087937219d9fbc5f07c6c4b35020e657de3e09d7fcc37ed823d95753545db7a75d74f874aa9c61574e83129ec6c4f4fb1f4fe8444
CoreDNS-1.11.1
linux/arm64, go1.20.7, ae2bbc2
[FATAL] plugin/loop: Loop (127.0.0.1:39337 -> :53) detected for zone ".", see https://coredns.io/plugins/loop#troubleshooting. Query: "HINFO 7329737346017710518.3032102461366805169."

(This error wasn't seen in other OS.)

@ant31
Copy link
Contributor

ant31 commented May 10, 2024

@tico88612
you should look around for all vars that are specific to ubuntu-xx
for example:
your error is probably because this file is missing for ubuntu-24:
https://github.com/kubernetes-sigs/kubespray/blob/master/roles/kubernetes/node/vars/ubuntu-22.yml

you can copy and create an ubuntu-24.yml

@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels May 16, 2024
@ant31
Copy link
Contributor

ant31 commented May 17, 2024

all green ! /lgtm

@yankay
Copy link
Member

yankay commented May 17, 2024

Thanks @tico88612
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ant31, tico88612, yankay

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

The pull request process is described 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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 17, 2024
@tico88612 tico88612 force-pushed the feat/ubuntu-2404 branch 2 times, most recently from 962b3b5 to 725f160 Compare May 17, 2024 14:15
@VannTen
Copy link
Contributor

VannTen commented May 17, 2024

/lgtm

@k8s-ci-robot k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels May 17, 2024
@k8s-ci-robot k8s-ci-robot removed lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels May 17, 2024
@VannTen
Copy link
Contributor

VannTen commented May 18, 2024 via email

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 18, 2024
@k8s-ci-robot k8s-ci-robot merged commit f85111f into kubernetes-sigs:master May 18, 2024
64 checks passed
@tico88612 tico88612 deleted the feat/ubuntu-2404 branch May 18, 2024 09:40
itayporezky pushed a commit to itayporezky/kubespray that referenced this pull request May 19, 2024
Rickkwa pushed a commit to Rickkwa/kubespray that referenced this pull request Jun 26, 2024
davidumea pushed a commit to elastisys/kubespray that referenced this pull request Oct 25, 2024
robinAwallace pushed a commit to elastisys/kubespray that referenced this pull request Oct 31, 2024
robinAwallace pushed a commit to elastisys/kubespray that referenced this pull request Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants