Open SZT0728 opened 2 weeks ago
Hi @SZT0728, thanks for your feedback. Is the problem still present in v1.9 or in the master branch?
Hi @SZT0728, thanks for your feedback. Is the problem still present in v1.9 or in the master branch?
Sorry, I don't know whether it still exist because the server will shutdown with the below info in v1.9:
What you point out in the picture, I understand should not be directly related.
I look at the code now and the logic has changed,
so I guess the bug you pointed out may have been fixed.
What you point out in the picture, I understand should not be directly related.
I look at the code now and the logic has changed,
so I guess the bug you pointed out may have been fixed.
so which version i should use? becase the karmada-controller-manager throw another bug in v1.9.0.
so which version i should use?
I recommend using the new version of the tutorial. The community currently maintains only the three most recent versions.
becase the karmada-controller-manager throw another bug in v1.9.0.
What bug do you encounter?
This issue has been fixed in the latest version.
PS: This issue has been fixed in release 1.7, by #3950.
Karmada version: v1.4.2
@SZT0728 are you still using v1.4?
the karmada-controller-manager throw a error "index out of range" even though i change the image version,such as v1.5.1、v1.6.0、v1.6.1:
fix this bug:
the karmada will auto throw the error and panic while it running:
Anything else we need to know?:
Environment:
Karmada version: v1.4.2
kubectl-karmada or karmadactl version (the result of
kubectl-karmada version
orkarmadactl version
): v1.4.2Others: