Loading...
Loading...
The output for kubectl get nodes shows that the nodes are in a Ready status, but not yet uncondoned, that is, in Ready,SchedulingDisabled status: The upgrade job runs endlessly, looking for a "ready" MVM: thindeployer deployment.log INFO [2025-04-11T16:37:21.239167] 13316: type/virtualmachine.rb:543:in `block in svm_ready?': b6d56d39-959f-44ad-a348-8103baae71eb: Checking if mvm is ready for 1.1.1.1 ... INFO [2025-04-11T16:38:49.736277] 13316: type/virtualmachine.rb:543:in `block in svm_ready?': b6d56d39-959f-44ad-a348-8103baae71eb: Checking if mvm is ready for 1.1.1.1 ... Impact Upgrade of the RG never finishes.
During the upgrade job, the code attempts to cordon the MVM and evacuates all pods before upgrading. The job gets stuck and never completes the uncordon operation for the MVM to become READY.
Manually uncordon the problematic MVM SSH to any of the other two MVMs and run the uncordon command for the problematic MVM: # kubectl uncordon <MVM Name> After manually running the uncordon command, the RG upgrade finishes Impacted version PowerFlex 4.x Fixed version PowerFlex 4.5.2
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.