Kubernetes Pod 上的 Trident Pod 未正确终止
适用于
/
OpenShift 的 Trident问题
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
trident-csi-4cbtt 2/2 Running 4 96d <MASTER_IP_1> caas-master01-01 <none> <none>
trident-csi-5b59f59cc8-9wqp5 5/5 Running 0 11h <NODE_IP_11> caas-node01-01 <none> <none>
trident-csi-5b59f59cc8-m9tdz 5/5 Terminating 0 12h <NODE_IP_22> caas-node02-02 <none> <none>
trident-csi-dl972 2/2 Running 6 96d <NODE_IP_22> caas-node03-03 <none> <none>
trident-csi-h25g4 2/2 Running 6 96d <MASTER_IP_1> caas-master03-03 <none> <none>
trident-csi-nzzgj 2/2 Running 4 96d <MASTER_IP_1> caas-master02-02 <none> <none>
time="2020-11-30T23:55:58Z" level=error msg="Trident REST interface was not available after 30.00 seconds."
time="2020-11-30T23:55:58Z" level=debug msg="Updating Trident Provisioner CR after failed installation." name=trident
namespace=trident time="2020-11-30T23:55:58Z" level=info msg="'TridentProvisioner' CR updated." name=trident namespace=trident
time="2020-11-30T23:55:58Z" level=error msg="error syncing 'trident/trident': reconcile failed; error re-installing Trident 'trident' in namespace 'trident'; err: reconcile failed;
unable to upgrade connection: Authorization error (user=kube-apiserver-kubelet-client, verb=create, resource=nodes, subresource=proxy);
unable to upgrade connection: Authorization error (user=kube-apiserver-kubelet-client, verb=create, resource=nodes, subresource=proxy);
use 'tridentctl logs' to learn more, requeuing"