-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Closed
Description
Description
Steps to reproduce the issue:
- Install kubernetes with version 1.22.1 and CRI-O 1.22.0
- Then simply run
crio version
Describe the results you received:
$ crio version
INFO[0000] RDT is not enabled: failed to detect resctrl mount point: resctrl not found in /proc/mounts
INFO[2021-09-11 23:57:02.787660012Z] Starting CRI-O, version: 1.22.0, git: 6becad23eadd7dfdd25fd8df386bf3b706cf7758(clean)
Version: 1.22.0
GitCommit: 6becad23eadd7dfdd25fd8df386bf3b706cf7758
GitTreeState: clean
BuildDate: 2021-08-27T17:12:26Z
GoVersion: go1.16.6
Compiler: gc
Platform: linux/amd64
Linkmode: dynamic
BuildTags: apparmor, exclude_graphdriver_devicemapper, containers_image_ostree_stub, seccomp
SeccompEnabled: true
AppArmorEnabled: falseDescribe the results you expected:
Output without the error.
Additional information you deem important (e.g. issue happens only occasionally):
Output of crio --version:
$ crio version
INFO[0000] RDT is not enabled: failed to detect resctrl mount point: resctrl not found in /proc/mounts
INFO[2021-09-11 23:57:02.787660012Z] Starting CRI-O, version: 1.22.0, git: 6becad23eadd7dfdd25fd8df386bf3b706cf7758(clean)
Version: 1.22.0
GitCommit: 6becad23eadd7dfdd25fd8df386bf3b706cf7758
GitTreeState: clean
BuildDate: 2021-08-27T17:12:26Z
GoVersion: go1.16.6
Compiler: gc
Platform: linux/amd64
Linkmode: dynamic
BuildTags: apparmor, exclude_graphdriver_devicemapper, containers_image_ostree_stub, seccomp
SeccompEnabled: true
AppArmorEnabled: falseAdditional environment details (AWS, VirtualBox, physical, etc.):
Bare metal and cluster starts with kubeadm.
Metadata
Metadata
Assignees
Labels
No labels