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

Static installation broken on older versions (<1.27) due to packages adding prefix crio- #7923

Open
NymanRobin opened this issue Mar 22, 2024 · 6 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@NymanRobin
Copy link

What happened?

Was not sure if this Issue should be opened here or in https://github.com/cri-o/packaging, please correct me if this is wrong place.

So recently some packages added crio- prefix in name due to conflict with redhat packages this causes the static installation to fail on older builds. I see updated packages are released in 1.28.4 and 1.29.2, but is there any plans for back-ports to 1.27 and 1.26? Otherwise is there a possibility to extend the packaging script to support these versions?

Also the README example suggest that the static installation would work on 1.21.0 which it won't so I think some disclaimer there would be very useful and an example that is actually working.

What did you expect to happen?

cri-o to be installed

How can we reproduce it (as minimally and precisely as possible)?

The example from the README can be used, but also more recent version such as v1.27.4

$ curl https://raw.githubusercontent.com/cri-o/packaging/main/get | bash -s -- -t v1.27.4

Anything else we need to know?

No response

CRI-O and Kubernetes version

Not applicable fails installation for versions below v1.28

OS version

# On Linux:
$ cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
$ uname -a
Linux test-vm 5.15.0-100-generic

Additional environment details (AWS, VirtualBox, physical, etc.)

Virtual machine, but should not affect the result

@NymanRobin NymanRobin added the kind/bug Categorizes issue or PR as related to a bug. label Mar 22, 2024
@saschagrunert
Copy link
Member

Thank you for the report @NymanRobin!

any plans for back-ports to 1.27 and 1.26

Unfortunately not :-/ 1.26 is technically EOL (together with Kubernetes), but we may find a workaround for 1.27.

Do we have anyone from @cri-o/cri-o-maintainers / @kwilczynski that may want to look into this?

@NymanRobin
Copy link
Author

Okay thanks for letting me know! Would be nice with a fix to 1.27 and updated README example

Copy link

A friendly reminder that this issue had no activity for 30 days.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 22, 2024
@kwilczynski
Copy link
Member

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 2, 2024
@kwilczynski kwilczynski self-assigned this May 2, 2024
@kwilczynski
Copy link
Member

/assign kwilczynski

Copy link

github-actions bot commented Jun 2, 2024

A friendly reminder that this issue had no activity for 30 days.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants