name is reserved caused by removing mount point failed #8596
Comments
|
is this reproducible? |
|
@xuegege5290, are you using any custom storage drivers, perhaps? What would be the storage on which the Also, does it always happen or after an upgrade? What runtime is it? crun or runc? |
|
@xuegege5290, also... any chance if you could try a bit newer version of Kubernetes? Maybe even match it with CRI-O version? So you have both running 1.28? If possible, of course. |
the root cause of the issue has not been identified and it cannot be reproduced, although it occurs quite frequently. I am doing my best to find the reason and try to make it reproducible. |
I'm sorry for not providing detailed information. I am using runc. I have two sets of clusters; the first one is the information mentioned above. The other cluster has consistent versions of kubelet and crio. This issue has occurred in both, showing up intermittently after some time. [root@node crio]# crio --version
crio version 1.25.4
Version: 1.25.4
GitCommit: unknown
GitCommitDate: unknown
GitTreeState: clean
GoVersion: go1.18.4
Compiler: gc
Platform: linux/amd64
Linkmode: dynamic
BuildTags:
rpm_crashtraceback
exclude_graphdriver_btrfs
btrfs_noversion
exclude_graphdriver_devicemapper
libdm_no_deferred_remove
seccomp
selinux
libtrust_openssl
LDFlags: -linkmode=external -compressdwarf=false -X github.com/cri-o/cri-o/version=1.25.4 -B 0xc0ee73ac46a4fa7414849c210d767beff31d5c89 -extldflags '-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 '
SeccompEnabled: true
AppArmorEnabled: false
Dependencies:
[root@node12 crio]# kubelet --version
Kubernetes v1.25.8-65+e623590b219e8f-dirty
[root@node12 crio]# runc --version
runc version 1.1.12
spec: 1.0.2-dev
go: go1.18.4
libseccomp: 2.5.2
|
The first one of the cluster runc version is : [root@ldy5-ceasphere-2 ~]# runc --version
runc version 1.0.2
spec: 1.0.2-dev
go: go1.16.12
libseccomp: 2.5.1
And the storage driver is overlay，storage default configuration is : # This file is generated by the Machine Config Operator's containerruntimeconfig controller.
#
# storage.conf is the configuration file for all tools
# that share the containers/storage libraries
# See man 5 containers-storage.conf for more information
# The "container storage" table contains all of the server options.
[storage]
# Default Storage Driver
driver = "overlay"
# Temporary storage location
runroot = "/var/run/containers/storage"
# Primary Read/Write location of container storage
graphroot = "/var/lib/containers/storage"
[storage.options]
# Storage options to be passed to underlying storage drivers
# AdditionalImageStores is used to pass paths to additional Read/Only image stores
# Must be comma separated list.
additionalimagestores = [
]
# Size is used to set a maximum size of the container image. Only supported by
# certain container storage drivers.
size = "" |
|
A friendly reminder that this issue had no activity for 30 days. |
github-actions
bot
added
the
lifecycle/stale
What happened?
For a container within a certain pod that fails to be created, the error log states: "name is reserved."
Possible reasons for this log error might be:
this is container of the problem pod
What did you expect to happen?
The container is created and running normally.
How can we reproduce it (as minimally and precisely as possible)?
During the process of deleting a container, why can't it be unmounted, with a prompt that related files and folders exist?
Anything else we need to know?
CRI-O and Kubernetes version
$ kubectl version --output=json{
"clientVersion": {
"major": "1",
"minor": "25",
"gitVersion": "v1.25.8-1+2b6d997c6-dirty",
"gitCommit": "2b6d997c6",
"gitTreeState": "dirty",
"buildDate": "2024-05-14T16:08:55Z",
"goVersion": "go1.19.3",
"compiler": "gc",
"platform": "linux/amd64"
},
"kustomizeVersion": "v4.5.7",
"serverVersion": {
"major": "1",
"minor": "25+",
"gitVersion": "v1.25.8-87+25a9d193afa588-dirty",
"gitCommit": "25a9d193afa58836db7a70cbfafe75002a434c4e",
"gitTreeState": "dirty",
"buildDate": "2024-08-08T16:17:11Z",
"goVersion": "go1.19.3",
"compiler": "gc",
"platform": "linux/amd64"
}
}
OS version
Additional environment details (AWS, VirtualBox, physical, etc.)
The text was updated successfully, but these errors were encountered: