action #114457
closedRun kubectl tests on SLES
Added by ph03nix almost 2 years ago. Updated almost 2 years ago.
0%
Description
After implementing the kubectl test in https://progress.opensuse.org/issues/112457 for Tumbleweed, this ticket is about implementing the same test run on all supported SLES versions.
First step is to determine, where kubectl is supported and then schedule a new test run on those version.
Updated by ph03nix almost 2 years ago
- Related to action #112457: [New test] Test coverage for kubernetes client (kubectl) added
Updated by ph03nix almost 2 years ago
I'd like to work on this issue after my vacation, unless it becomes urgent and someone else takes it.
Updated by jlausuch almost 2 years ago
ph03nix wrote:
First step is to determine, where kubectl is supported and then schedule a new test run on those version.
This is well described in the original ticket: https://progress.opensuse.org/issues/112457
15-SP1 and beyond.
Updated by pdostal almost 2 years ago
- Status changed from Workable to In Progress
- Assignee set to pdostal
Updated by pdostal almost 2 years ago
Updated by pdostal almost 2 years ago
Updated by jlausuch almost 2 years ago
@pdostal @ph03nix do you know why the test started to fail on SLES? https://openqa.suse.de/tests/9411098#step/kubectl/57
Updated by jlausuch almost 2 years ago
BTW, a new kubectl version will come soon: https://jira.suse.com/browse/SLE-24655
SR: https://build.suse.de/request/show/274800
Updated by ph03nix almost 2 years ago
jlausuch wrote:
@pdostal @ph03nix do you know why the test started to fail on SLES? https://openqa.suse.de/tests/9411098#step/kubectl/57
Works on Tumbleweed:
curl -sfL https://get.k3s.io | sh -s - --disable=metrics-server
[INFO] Finding release for channel stable
[INFO] Using v1.24.4+k3s1 as release
[INFO] Downloading hash https://github.com/k3s-io/k3s/releases/download/v1.24.4+k3s1/sha256sum-amd64.txt
[INFO] Downloading binary https://github.com/k3s-io/k3s/releases/download/v1.24.4+k3s1/k3s
[INFO] Verifying binary download
[INFO] Installing k3s to /usr/local/bin/k3s
[INFO] Skipping installation of SELinux RPM
[INFO] Creating /usr/local/bin/kubectl symlink to k3s
[INFO] Creating /usr/local/bin/crictl symlink to k3s
[INFO] Creating /usr/local/bin/ctr symlink to k3s
[INFO] Creating killall script /usr/local/bin/k3s-killall.sh
[INFO] Creating uninstall script /usr/local/bin/k3s-uninstall.sh
[INFO] env: Creating environment file /etc/systemd/system/k3s.service.env
[INFO] systemd: Creating service file /etc/systemd/system/k3s.service
[INFO] systemd: Enabling k3s unit
Created symlink /etc/systemd/system/multi-user.target.wants/k3s.service → /etc/systemd/system/k3s.service.
[INFO] systemd: Starting k3s
Works also on SLES15-SP4:
sles15-sp4:~ # curl -sfL https://get.k3s.io | sh -s - --disable=metrics-server
[INFO] Finding release for channel stable
[INFO] Using v1.24.4+k3s1 as release
[INFO] Downloading hash https://github.com/k3s-io/k3s/releases/download/v1.24.4+k3s1/sha256sum-amd64.txt
[INFO] Downloading binary https://github.com/k3s-io/k3s/releases/download/v1.24.4+k3s1/k3s
[INFO] Verifying binary download
[INFO] Installing k3s to /usr/local/bin/k3s
[INFO] Skipping installation of SELinux RPM
[INFO] Creating /usr/local/bin/kubectl symlink to k3s
[INFO] Creating /usr/local/bin/crictl symlink to k3s
[INFO] Creating /usr/local/bin/ctr symlink to k3s
[INFO] Creating killall script /usr/local/bin/k3s-killall.sh
[INFO] Creating uninstall script /usr/local/bin/k3s-uninstall.sh
[INFO] env: Creating environment file /etc/systemd/system/k3s.service.env
[INFO] systemd: Creating service file /etc/systemd/system/k3s.service
[INFO] systemd: Enabling k3s unit
Created symlink /etc/systemd/system/multi-user.target.wants/k3s.service → /etc/systemd/system/k3s.service.
[INFO] systemd: Starting k3s
Transient issue that maybe got fixed in the meantime?
Updated by jlausuch almost 2 years ago
ph03nix wrote:
jlausuch wrote:
@pdostal @ph03nix do you know why the test started to fail on SLES? https://openqa.suse.de/tests/9411098#step/kubectl/57
Transient issue that maybe got fixed in the meantime?
I hope. There was another failure today in a different place https://openqa.suse.de/tests/9414591#step/kubectl/138 , but the restart is green. Let's see how it behaves in the next days.
Updated by pdostal almost 2 years ago
I just merged github.com/os-autoinst/os-autoinst-distri-opensuse!15429 so let's wait for tomorrow's build to verify.
Updated by pdostal almost 2 years ago
@pdostal @ph03nix do you know why the test started to fail on SLES? https://openqa.suse.de/tests/9411098#step/kubectl/57
Because of k3s-io/k3s!6052.
Updated by pdostal almost 2 years ago
- Status changed from In Progress to Resolved
9427689 kubectl_tests@aarch64-virtio https://openqa.suse.de/tests/9427689 passed
9427690 kubectl_tests@aarch64-virtio https://openqa.suse.de/tests/9427690 passed
9427703 kubectl_tests@aarch64-virtio https://openqa.suse.de/tests/9427703 passed
I restarted today's aggregates and they all passed so resolving the ticket.
Updated by dimstar almost 2 years ago
pdostal wrote:
I just merged [github.com/os-autoinst/os-autoinst-distri-opensuse!15429] so let's wait for tomorrow's build to verify.
[github.com/os-autoinst/os-autoinst-distri-opensuse!15429]: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15429
Restuled in a fallout on helm_k3S - filed as https://progress.opensuse.org/issues/116161