pv-migrate: All strategies are failing

Describe the bug All strategies are failing

Expected behavior At least one should work.

Console output

๐Ÿš€  Starting migration
๐Ÿ’ก  PVC wordembedding-resources-pvc is mounted to node aks-heavyram-33180665-vmss000000, ignoring...
๐Ÿ’ญ  Will attempt 3 strategies: mnt2, svc, lbsvc
๐Ÿš  Attempting strategy: mnt2
๐ŸฆŠ  Strategy 'mnt2' cannot handle this migration, will try the next one
๐Ÿš  Attempting strategy: svc
๐Ÿ”‘  Generating SSH key pair
creating 7 resource(s)
beginning wait for 7 resources with timeout of 1m0s
Deployment is not ready: default/pv-migrate-ff8y3-sshd. 0 out of 1 expected pods are ready
๐Ÿ“‚  Copying data...   0% |                                                                                 | () [0s:0s]๏ฟฝ   Cleaning up
uninstall: Deleting pv-migrate-ff8y3
Starting delete for "pv-migrate-ff8y3-sshd" Service
Starting delete for "pv-migrate-ff8y3-rsync" Job
Starting delete for "pv-migrate-ff8y3-sshd" Deployment
Starting delete for "pv-migrate-ff8y3-sshd" Secret
Starting delete for "pv-migrate-ff8y3-rsync" Secret
Starting delete for "pv-migrate-ff8y3-sshd" ServiceAccount
Starting delete for "pv-migrate-ff8y3-rsync" ServiceAccount
beginning wait for 7 resources to be deleted with timeout of 1m0s
purge requested for pv-migrate-ff8y3
โœจ  Cleanup done
๐Ÿ”ถ  Migration failed with this strategy, will try with the remaining strategies
๐Ÿš  Attempting strategy: lbsvc
๐Ÿ”‘  Generating SSH key pair
creating 4 resource(s)
beginning wait for 4 resources with timeout of 1m0s
Service does not have load balancer ingress IP address: default/pv-migrate-1ei5r-sshd
Service does not have load balancer ingress IP address: default/pv-migrate-1ei5r-sshd
Service does not have load balancer ingress IP address: default/pv-migrate-1ei5r-sshd
Service does not have load balancer ingress IP address: default/pv-migrate-1ei5r-sshd
Service does not have load balancer ingress IP address: default/pv-migrate-1ei5r-sshd
Service does not have load balancer ingress IP address: default/pv-migrate-1ei5r-sshd
Service does not have load balancer ingress IP address: default/pv-migrate-1ei5r-sshd
Service does not have load balancer ingress IP address: default/pv-migrate-1ei5r-sshd
Service does not have load balancer ingress IP address: default/pv-migrate-1ei5r-sshd
๐Ÿงน  Cleaning up
uninstall: Deleting pv-migrate-1ei5r
Starting delete for "pv-migrate-1ei5r-sshd" Service
Starting delete for "pv-migrate-1ei5r-sshd" Deployment
Starting delete for "pv-migrate-1ei5r-sshd" Secret
Starting delete for "pv-migrate-1ei5r-sshd" ServiceAccount
beginning wait for 4 resources to be deleted with timeout of 1m0s
purge requested for pv-migrate-1ei5r
โœจ  Cleanup done
๐Ÿ”ถ  Migration failed with this strategy, will try with the remaining strategies
โŒ  Error: all strategies have failed

Version

  • AKS 1.20
  • Source and destination container runtimes [e.g. containerd://1.4.4-k3s2, docker://19.3.6]
  • pv-migrate version 0.7.2 (commit: 766fddb8040178e20d64490c32df141f818f61c6)
  • Installation method binary download
  • ReadWriteOnce (if I shut down the service that mounts it, it still does not work)

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 21 (10 by maintainers)

Most upvoted comments

Nope, not the same ๐Ÿ˜„ I simply also encountered this message, but I figured out that the error was due to a misconfiguration and shared my workaround.

I did encounter a possible bug, but that is unrelated, so I will open a new thread regarding this.