sealer
sealer copied to clipboard
join delete bug
What happen?
action: sealer join -c yt-test --nodes 192.168.142.131 --debug
Relevant log output?
2022-08-17 21:09:24 [DEBUG] [default_image.go:75] image kubernetes:v1.24.2-yt already exists
2022-08-17 21:09:24 [DEBUG] [default_image.go:75] image kubernetes:v1.24.2-yt already exists
2022-08-17 21:09:24 [DEBUG] [default_image.go:75] image kubernetes:v1.24.2-yt already exists
2022-08-17 21:09:24 [DEBUG] [default_image.go:75] image kubernetes:v1.24.2-yt already exists
2022-08-17 21:09:24 [DEBUG] [exec.go:72] failed to execute command(mount | grep /var/lib/sealer/data/yt-test/mount/linux_amd64_): error(exit status 1)
2022-08-17 21:09:24 [DEBUG] [overlay2.go:103] mount data : index=off,lowerdir=/var/lib/sealer/data/overlay2/07c4db7694d26086a998b7a2cfff05dcc5b207a5c51515921111a157eaa74f92:/var/lib/sealer/data/overlay2/cf38867d6326195d5bfbb234e96ac104027e59f3bd26fe41b4d4830dcaaf0f22:/var/lib/sealer/data/overlay2/0172b7118ee2d3ae79ba91b1fc13ef4ca3ee37e0b6a7027e84d351654a6b3685:/var/lib/sealer/data/overlay2/48b759455cd877426cefd56d72578ea2832f19d9bf84cbdfa7c7268562bbc368:/var/lib/sealer/data/overlay2/08af04f363c6b4f76b5dd2f82086ecd4a4e3136e70df400993a6d589bfb52c2d:/var/lib/sealer/data/overlay2/05148b2e78b85090b9a066b3baaa8f2e0191d23d252714d977776a4cf5e27349:/var/lib/sealer/data/overlay2/eecbadcb4cb9d99f2cb8aaf1a2f9a4697cf8970c1bb305ea8243bef366e869b8:/var/lib/sealer/data/overlay2/2a15e08ed29d17506bc619f7b116f850242e69c462045ee55c61ed007d644c40:/var/lib/sealer/data/overlay2/76c6564aa13926a96f1cc04f2b782c758d70762d437c334e5e7ad524f4e1b80c,upperdir=/var/lib/sealer/data/yt-test/mount/linux_amd64_/upper,workdir=/var/lib/sealer/data/yt-test/mount/linux_amd64_/work
2022-08-17 21:09:24 [INFO] [local.go:164] Start to scale this cluster
**2022-08-17 21:09:24 [DEBUG] [local.go:165] current cluster: master [], worker [192.168.142.130 192.168.142.133]**
2022-08-17 21:09:24 [DEBUG] [registry.go:139] show registry info, IP: 192.168.142.130, Domain: sea.hub
2022-08-17 21:09:24 [DEBUG] [registry.go:139] show registry info, IP: 192.168.142.130, Domain: sea.hub
2022-08-17 21:09:24 [DEBUG] [scp.go:145] remote copy files src /var/lib/sealer/data/yt-test/mount/linux_amd64_/Kubefile to dst /var/lib/sealer/data/yt-test/rootfs/Kubefile
2022-08-17 21:09:24 [DEBUG] [scp.go:142] local copy files src /var/lib/sealer/data/yt-test/mount/linux_amd64_/Kubefile to dst /var/lib/sealer/data/yt-test/rootfs/Kubefile
2022-08-17 21:09:24 [DEBUG] [scp.go:142] local copy files src /var/lib/sealer/data/yt-test/mount/linux_amd64_/Metadata to dst /var/lib/sealer/data/yt-test/rootfs/Metadata
2022-08-17 21:09:24 [DEBUG] [scp.go:142] local copy files src /var/lib/sealer/data/yt-test/mount/linux_amd64_/README.md to dst /var/lib/sealer/data/yt-test/rootfs/README.md
2022-08-17 21:09:24 [DEBUG] [scp.go:142] local copy files src /var/lib/sealer/data/yt-test/mount/linux_amd64_/bin to dst /var/lib/sealer/data/yt-test/rootfs/bin
copying files to 192.168.142.131: 0/1
2022-08-17 21:09:24 [DEBUG] [scp.go:248] remote dst /var/lib/sealer/data/yt-test/rootfs/Kubefile already exists and
copying files to 192.168.142.131: 1/1
2022-08-17 21:09:24 [DEBUG] [scp.go:145] remote copy files src /var/lib/sealer/data/yt-test/mount/linux_amd64_/Metadata to dst /var/lib/sealer/data/yt-test/rootfs/Metadata
2022-08-17 21:09:24 [DEBUG] [scp.go:142] local copy files src /var/lib/sealer/data/yt-test/mount/linux_amd64_/cri to
copying files to 192.168.142.131: 1/2
2022-08-17 21:09:24 [DEBUG] [scp.go:142] local copy files src /var/lib/sealer/data/yt-test/mount/linux_amd64_/etc to dst /var/lib/sealer/data/yt-test/rootfs/etc
2022-08-17 21:09:24 [DEBUG] [scp.go:142] local copy files src /var/lib/sealer/data/yt-test/mount/linux_amd64_/images to dst /var/lib/sealer/data/yt-test/rootfs/images
2022-08-17 21:09:24 [DEBUG] [scp.go:142] local copy files src /var/lib/sealer/data/yt-test/mount/linux_amd64_/lib64 to dst /var/lib/sealer/data/yt-test/rootfs/lib64
2022-08-17 21:09:24 [DEBUG] [scp.go:142] local copy files src /var/lib/sealer/data/yt-test/mount/linux_amd64_/manifests to dst /var/lib/sealer/data/yt-test/rootfs/manifests
2022-08-17 21:09:24 [DEBUG] [scp.go:142] local copy files src /var/lib/sealer/data/yt-test/mount/linux_amd64_/scripts to dst /var/lib/sealer/data/yt-test/rootfs/scripts
2022-08-17 21:09:24 [DEBUG] [scp.go:142] local copy files src /var/lib/sealer/data/yt-test/mount/linux_amd64_/statics to dst /var/lib/sealer/data/yt-test/rootfs/statics
2022-08-17 21:09:24 [DEBUG] [scp.go:248] remote dst /var/lib/sealer/data/yt-test/rootfs/Metadata already exists and
copying files to 192.168.142.131: 2/2
2022-08-17 21:09:24 [DEBUG] [scp.go:145] remote copy files src /var/lib/sealer/data/yt-test/mount/linux_amd64_/README.md to dst /var/lib/sealer/data/yt-test/rootfs/README.md
2022-08-17 21:09:24 [DEBUG] [sshcmd.go:114] failed to execute command(cd /var/lib/sealer/data/yt-test/rootfs && chmod +x scripts/* && cd scripts && bash init.sh /var/lib/docker sea.hub 5000) on host(192.168.142.130): error(failed to execute command(cd /var/lib/sealer/data/yt-test/rootfs && chmod +x scripts/* && cd scripts && bash init.sh /var/l
.................
2022-08-17 21:09:24 [DEBUG] [scp.go:248] remote dst /var/lib/sealer/data/yt-test/rootfs/scripts/kubelet-pre-start.sh
copying files to 192.168.142.131: 31/31
2022-08-17 21:09:24 [DEBUG] [scp.go:145] remote copy files src /var/lib/sealer/data/yt-test/mount/linux_amd64_/stati
copying files to 192.168.142.131: 31/32
2022-08-17 21:09:24 [DEBUG] [scp.go:248] remote dst /var/lib/sealer/data/yt-test/rootfs/statics/audit-policy.yml alr
copying files to 192.168.142.131: 32/32
Usage:
sealer join [flags]
Examples:
join default cluster:
sealer join --masters x.x.x.x --nodes x.x.x.x
sealer join --masters x.x.x.x-x.x.x.y --nodes x.x.x.x-x.x.x.y
2022-08-17 21:09:24 [ERROR] [root.go:70] sealer-v0.8.6: failed to mount rootfs(/var/lib/sealer/data/yt-test/rootfs): failed to exec init.sh: failed to execute command(cd /var/lib/sealer/data/yt-test/rootfs && chmod +x scripts/* && cd scripts && bash init.sh /var/lib/docker sea.hub 5000) on host(192.168.142.130): error(exit status 1)
why init in 192.168.142.130 ?
Incorrect information
2022-08-17 21:09:24 [DEBUG] [local.go:165] current cluster: master [], worker [192.168.142.130 192.168.142.133]
bash init.sh /var/lib/docker sea.hub 5000:
+ REGISTRY_DOMAIN=sea.hub
+ REGISTRY_PORT=5000
+ chmod -R 755 ../bin/conntrack ../bin/containerd-rootless-setuptool.sh ../bin/containerd-rootless.sh ../bin/crictl ../bin/kubeadm ../bin/kubectl ../bin/kubelet ../bin/nerdctl ../bin/seautil
+ chmod 644 ../bin
+ cp ../bin/conntrack ../bin/containerd-rootless-setuptool.sh ../bin/containerd-rootless.sh ../bin/crictl ../bin/kubeadm ../bin/kubectl ../bin/kubelet ../bin/nerdctl ../bin/seautil /usr/bin
cp: 无法创建普通文件'/usr/bin/kubelet': 文本文件忙
cp: 无法创建普通文件'/usr/bin/nerdctl': 文本文件忙
What you expected to happen?
No response
How to reproduce it (as minimally and precisely as possible)?
No response
Anything else we need to know?
join ,delete have the same problem
What is the version of Sealer you using?
sealer-v0.8.6
What is your OS environment?
debian 11.4
What is the Kernel version?
5.10
Other environment you want to tell us?
cat ~/.sealer/yt-test/Clusterfile before action
apiVersion: sealer.cloud/v2
kind: Cluster
metadata:
annotations:
ClusterfileName: /home/hadals/Clusterfile
creationTimestamp: null
name: yt-test
spec:
hosts:
- ips:
- 192.168.142.130
roles:
- master
ssh: {}
- ips:
- 192.168.142.133
roles:
- node
ssh: {}
image: kubernetes:v1.24.2-yt
ssh:
encrypted: true
passwd: ==
cat ~/.sealer/yt-test/Clusterfile after action failed
apiVersion: sealer.cloud/v2
kind: Cluster
metadata:
annotations:
ClusterfileName: /home/hadals/Clusterfile
creationTimestamp: null
name: yt-test
spec:
hosts:
- ips:
- 192.168.142.130
roles:
- master
ssh: {}
- ips:
- 192.168.142.133
roles:
- node
ssh: {}
- ips:
- 192.168.142.131
roles:
- node
ssh: {}
image: kubernetes:v1.24.2-yt
ssh:
encrypted: true
passwd: ==
status: {}