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

Installer does not default to RPM for SLES #5132

Closed
abonillabeeche opened this issue Dec 13, 2023 · 5 comments
Closed

Installer does not default to RPM for SLES #5132

abonillabeeche opened this issue Dec 13, 2023 · 5 comments

Comments

@abonillabeeche
Copy link

abonillabeeche commented Dec 13, 2023

Describe the bug:
The installer does not default to RPMs with SLES, only with SLE Micro. For other RPM distros, the installer will default to RPM.

Steps To Reproduce:
Install RKE2 via

curl -sfL https://get.rke2.io | sh -

Expected behavior:
Add the repos to SLES as it does for SLE Micro

Actual behavior:
Tar ball install is used.

Additional context / logs:

[INFO]  finding release for channel stable
[INFO]  using v1.26.11+rke2r1 as release
[INFO]  downloading checksums at https://github.com/rancher/rke2/releases/download/v1.26.11+rke2r1/sha256sum-amd64.txt
[INFO]  downloading tarball at https://github.com/rancher/rke2/releases/download/v1.26.11+rke2r1/rke2.linux-amd64.tar.gz
[INFO]  verifying tarball
[INFO]  unpacking tarball file to /usr/local

test-vm:~ # cat /etc/os-release
NAME="SLES"
VERSION="15-SP5"
VERSION_ID="15.5"
PRETTY_NAME="SUSE Linux Enterprise Server 15 SP5"
ID="sles"
ID_LIKE="suse"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:15:sp5"
DOCUMENTATION_URL="https://documentation.suse.com/"
@brandond
Copy link
Member

brandond commented Dec 13, 2023

As @Martin-Weiss said in #3386 (comment):

this is still broken for SLES as the RPM for SLES requires selinux but we do not provide a supported selinux policy RPM for SLES as part of the RKE2 delivery via RPMs.

Until SLES provides selinux policies, we cannot support RPM installs on SLES systems, or at least not as the default install mode. You can put the installer into RPM mode, but you'll need to install unsupported selinux policies from opensuse or SLE Micro to make it work properly.

IMO, the SLES claim to support selinux is disingenuous, as actually using it will void your support terms. SLES does not provide any policies, and does not support use of third party policies - so you can install it, but as soon as you configure any policies you are in an unsupported configuration.

See: https://documentation.suse.com/sles/15-SP3/html/SLES-all/cha-selinux.html

SLES offers all binaries and libraries you need to use SELinux on your server.
A policy is not included, and you must build your own. Third-party policies are not supported.

@abonillabeeche
Copy link
Author

SLES offers all binaries and libraries you need to use SELinux on your server.
A policy is not included, and you must build your own. Third-party policies are not supported.

This means the 3rd party policy isn't supported, not that the entire system would fall out of support.

Why can't we install the RPM without using SELinux, since it is not enabled by default... ?

@brandond
Copy link
Member

brandond commented Dec 14, 2023

The rke2-common RPM depends on rke2-selinux, which in turn depends on container-selinux. We do not offer an RPM that does not have a selinux dependency.

In general, the recommendation is to disable selinux on the host, and use a tarball install, if you do not want selinux support.

@Martin-Weiss
Copy link

Martin-Weiss commented Dec 15, 2023

It still would be nice to deliver an RPM without the SElinux dependency for SLES.. (maybe it would be possible to change the forced dependency to an optinal dependency in the RPM with "suggests" or "recommends" insead of "requires")

Copy link
Contributor

github-actions bot commented Feb 8, 2024

This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 45 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants