You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
After deleting the CR in federated learning, the Pod instances will keep restarting What you expected to happen:
After deleting the CR in federated learning, the Pod instances are deleted normally. How to reproduce it (as minimally and precisely as possible):
Deploy a federated learning task. After the instances are generated, delete the task and observe whether the Pod instances can be deleted normally. Anything else we need to know?:
This bug is in the sedna main branch, and it's unclear whether this issue exists in the released versions. Environment:
Sedna Version
$ kubectl get -n sedna deploy gm -o jsonpath='{.spec.template.spec.containers[0].image}'
# paste output here
$ kubectl get -n sedna ds lc -o jsonpath='{.spec.template.spec.containers[0].image}'
# paste output here
Kubernets Version
$ kubectl version
# paste output here
KubeEdge Version
$ cloudcore --version
# paste output here
$ edgecore --version
# paste output here
CloudSide Environment:
Hardware configuration
$ lscpu
# paste output here
OS
$ cat /etc/os-release
# paste output here
Kernel
$ uname -a
# paste output here
Others
EdgeSide Environment:
Hardware configuration
$ lscpu
# paste output here
OS
$ cat /etc/os-release
# paste output here
Kernel
$ uname -a
# paste output here
Others
The text was updated successfully, but these errors were encountered:
What happened:
After deleting the CR in federated learning, the Pod instances will keep restarting
What you expected to happen:
After deleting the CR in federated learning, the Pod instances are deleted normally.
How to reproduce it (as minimally and precisely as possible):
Deploy a federated learning task. After the instances are generated, delete the task and observe whether the Pod instances can be deleted normally.
Anything else we need to know?:
This bug is in the sedna main branch, and it's unclear whether this issue exists in the released versions.
Environment:
Sedna Version
Kubernets Version
KubeEdge Version
CloudSide Environment:
Hardware configuration
OS
Kernel
Others
EdgeSide Environment:
Hardware configuration
OS
Kernel
Others
The text was updated successfully, but these errors were encountered: