https://rancher.com/ logo
Join Slack
Powered by
I clicked to upgrade to 1.4.1 and it's been sittin...
# harvester
a
I clicked to upgrade to 1.4.1 and it's been sitting at Download Upgrade Image and everything is marked as pending since yesterday. Doesn't seem like it's tried to do anything.
m
hard to tell without more info... have you had a chance to look at this 👉 https://docs.harvesterhci.io/v1.4/upgrade/troubleshooting?
a
kubectl get upgrade.harvesterhci -A -oyaml
kubectl get pods -A | grep ugprade
maybe the cluster is pending download image due to some unknown reasons
a
Long shot, but if you have v2 data engine enabled, but no v2 disks assigned, disable the v2 data engine setting and the upgrade should proceed. There is a GitHub issue detailing this, but I am unable to find it at the moment.
a
I had to go see what the v2 data engine was, looks like that's set to false.
Copy code
combine2:~ # kubectl get upgrade.harvesterhci -A -oyaml
apiVersion: v1
items:
- apiVersion: harvesterhci.io/v1beta1
  kind: Upgrade
  metadata:
    creationTimestamp: "2025-04-14T18:43:29Z"
    finalizers:
    - wrangler.cattle.io/harvester-upgrade-controller
    generateName: hvst-upgrade-
    generation: 2
    labels:
      harvesterhci.io/latestUpgrade: "true"
      harvesterhci.io/upgradeState: PreparingLoggingInfra
    name: hvst-upgrade-hq67t
    namespace: harvester-system
    resourceVersion: "106924383"
    uid: 8ebc69d0-7492-4909-bb13-aa5a8372bd60
  spec:
    image: ""
    logEnabled: true
    version: v1.4.1
  status:
    conditions:
    - status: Unknown
      type: Completed
    - status: Unknown
      type: LogReady
    previousVersion: v1.4.0
    upgradeLog: hvst-upgrade-hq67t-upgradelog
kind: List
metadata:
  resourceVersion: ""
👍 1
@ancient-pizza-13099 any other ideas, the 
grep pods
command didn't return anything.
ok, I disabled the cpu manager and it just started going. I don't need it I was messing with it to see what it was awhile back and never turned it off..
4 Views
Open in Slack
PreviousNext
Powered by