You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Getting errors from any pods with a PVC after upgrading and with fresh paas-full install with talos 1.9.0. There doesn't seem to be any issue with the pvc's when describing them.
Warning FailedScheduling 3m44s default-scheduler running PreBind plugin "VolumeBinding": binding volumes: pv "pvc-2f246518-7bed-4088-847a-69e5bee1aa6c" node affinity doesn't match node "korg-n1": no matching NodeSelectorTerms
Normal Scheduled 3m43s default-scheduler Successfully assigned tenant-root/vmstorage-longterm-0 to korg-n3
Warning FailedAttachVolume 91s (x9 over 3m43s) attachdetach-controller AttachVolume.Attach failed for volume "pvc-2f246518-7bed-4088-847a-69e5bee1aa6c" : rpc error: code = Internal desc = ControllerPublishVolume failed for pvc-2f246518-7bed-4088-847a-69e5bee1aa6c: could not determine device path
If I downgrade to talos 1.8.4 then they come up no problem.
The text was updated successfully, but these errors were encountered:
Getting errors from any pods with a PVC after upgrading and with fresh paas-full install with talos 1.9.0. There doesn't seem to be any issue with the pvc's when describing them.
If I downgrade to talos 1.8.4 then they come up no problem.
The text was updated successfully, but these errors were encountered: