runc icon indicating copy to clipboard operation
runc copied to clipboard

Rook (ceph) fails to start correctly after upgrading to runc 1.2.0

Open ErickStaal opened this issue 1 year ago • 5 comments

Description

Rook (Ceph) fails starting correctly after upgrading to runc v1.2.0. Rolling back to runc v1.1.15 fixes all errors.

Steps to reproduce the issue

  1. Install rook operator v1.15.3 in kubernetes cluster (on-prem) based upon Kubernetes v1.30.5
  2. Everything works
  3. Upgrade runc to v1.2.0
  4. rook fails with errors: rook-ceph rook-ceph-mds-k8sfs-a-65588bd59d-d9ccf 1/2 CrashLoopBackOff 215 (53s ago) 19h rook-ceph rook-ceph-mds-k8sfs-b-686bdc8d8d-kk498 1/2 CrashLoopBackOff 67 (50s ago) 5h56m rook-ceph rook-ceph-mgr-b-58f9d6576b-4df8v 2/3 CrashLoopBackOff 333 (51s ago) 19h

I checked the output of kubectl describe nodes. There was no memory or storage pressure on the nodes.

Describe the results you received and expected

rook starting just like under runc v1.1.15

What version of runc are you using?

v1.1.15 (I rolled back from v1.2.0 and Everything works again).

Host OS information

PRETTY_NAME="Ubuntu 24.04.1 LTS"

Host kernel information

Linux 6.8.0-47-generic #47-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 21:40:26 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux (on all Kubernetes nodes).

ErickStaal avatar Oct 28 '24 13:10 ErickStaal

Skipping CI for Draft Pull Request. If you want CI signal for your change, please convert it to an actual PR. You can still manually trigger a test run with /test all

k8s-ci-robot avatar Jun 03 '25 19:06 k8s-ci-robot

I guess windows-latest is not pointing to windows-2025 yet? Noticed this in the logs for OS:

Operating System
  Microsoft Windows Server 2022
  10.0.20[3](https://github.com/containerd/containerd/actions/runs/15427653032/job/43418472164?pr=11933#step:1:3)48
  Datacenter

estesp avatar Jun 03 '25 20:06 estesp

Looks like this worked.. was this just a test or are you going to move out of Draft for review? I'm asking because I think @kiashok is going to get a PR ready for all the Windows testing/image updates for actions

estesp avatar Jun 04 '25 17:06 estesp

We can take this, it doesn't make any changes to the tests and we might want to get it backported before the next brownout. While we are waiting for the tests to move off of 2019 this at least allows the rest of CI to complete during the brownouts

dmcgowan avatar Jun 05 '25 00:06 dmcgowan

Needs rebase.

cpuguy83 avatar Jun 13 '25 22:06 cpuguy83

Updated, even if windows-latest is still on 2022, I still think its worth using the latest tag for linters. Whenever it gets updated we know 2025 runs the linters fine anyway.

dmcgowan avatar Jun 25 '25 00:06 dmcgowan