rancher / rancher

Complete container management platform
http://rancher.com
Apache License 2.0
23.49k stars 2.98k forks source link

[Backport v2.6] GlusterFS kubelet image issue #40542

Closed rancherbot closed 1 year ago

rancherbot commented 1 year ago

This is a backport issue for https://github.com/rancher/rancher/issues/40508, automatically created via rancherbot by @snasovich

Original issue description:

Issue description: To make glusterfs work properly, we have a workaround in https://docs.ranchermanager.rancher.io/how-to-guides/advanced-user-guides/manage-clusters/create-kubernetes-persistent-storage/manage-persistent-storage/about-glusterfs-volumes

But it appears to be giving an error as required libraries missing inside the hyperkube image

Business impact: Medium

Troubleshooting steps: Mount the system-run binary to hyperkube image and execute the following command

/usr/bin/systemd-run --version

Repro steps:

Run the following command in any RKE cluster node

Workaround: Is workararound available and implemented? yes What is the workaround: Adding a volume with specific library works and it can be configured directly on kubelet by using extra_binds

-v /lib/systemd/libsystemd-shared-249.so:/lib/systemd/libsystemd-shared-249.so

Actual behavior: systemd-run --version display the following error

/usr/bin/systemd-run: error while loading shared libraries: libsystemd-shared-249.so: cannot open shared object file: No such file or directory

Expected behavior: systemd-run --version should be executed correctly and list the following result

systemd 249 (249.11-0ubuntu3)

+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL +ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP -LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified

Files, logs, traces:

$ docker run -v /usr/bin/systemd-run:/usr/bin/systemd-run --entrypoint /usr/bin/systemd-run rancher/hyperkube:v1.21.13-rancher1 --version

/usr/bin/systemd-run: error while loading shared libraries: libsystemd-shared-249.so: cannot open shared object file: No such file or directory

SURE-5281

vivek-shilimkar commented 1 year ago

Issue is not active anymore on newly bumped hyperkube images.

The issue is resolved in following hyperkube images.

Closing the issue.

vivek-shilimkar commented 1 year ago

Issue is not active anymore on newly bumped hyperkube images.

Running below command lists the version. docker run --entrypoint /usr/bin/systemd-run <IMAGE-TAG> --version The issue is resolved in following hyperkube images.

Hence closing the issue.