HoustonPutman commented on issue #574: URL: https://github.com/apache/solr-operator/issues/574#issuecomment-1568740624
Ahh yeah that log line might be a bit unclear. You cannot "cancel" an update to a pod, it's postponed till later, but eventually the pod will be updated (if the conditions to update are met). That log line is telling you that one of the pods is not healthy, so at some point the pod is not "ready". If there are pods not updated still. Look for the most recent log lines in the operator, to tell you why it isn't continuing and deleting the last few pods. If that log line is still being printed, then for some reason the solr operator does not believe that all Solr pods are "ready". Maybe the cluster is having issues scheduling the pods after they are being deleted? Can you do a `kubectl get pods` to show the solr pods? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
