Upgrade from 2.6.x to 2.7.0 fails when cleaning sparse loop volumes #3064
Labels
kind:bug
Something isn't working
severity:major
Major impact on live deployments (e.g. some non-critical feature is not working at all)
topic:lifecycle
Issues related to upgrade or downgrade of MetalK8s
Milestone
Component: salt, upgrade, storage
Summary:
When running the
upgrade.sh
script to upgrade a MetalK8s 2.6.x cluster to 2.7.0, theUpgrading all nodes one by one
step will abort for each node which has noSparseLoopDevice
Volume provisioned, during themetalk8s.volumes.cleanup
state execution. It will show an error similar to:The only available workaround is to restart the
upgrade.sh
script, once per failing node, until completion.The text was updated successfully, but these errors were encountered: