Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VM migration is failing as it is referring to old and stale MigrationPlan. #154

Open
cniket opened this issue Jan 28, 2025 · 0 comments
Open

Comments

@cniket
Copy link

cniket commented Jan 28, 2025

Hello,

VM migration is failing as it is referring to an old migrationplan resource. That migrationplan is in turn referring to some stale migrationtemplate which had incorrect storagemapping reference.

Below are the steps;

  1. I first tried a VM migration by selecting __DEFAULT__ under 'OpenStack VolumeType' on vjailbreak. The process failed as the 'volume' creation on PCD failed.
  2. After few days, in the next attempt, I tried migrating the same VM, however this time selected 'nfs' as my volume type name(which I created in blueprint) under 'OpenStack VolumeType' on vjailbreak.
  3. The migration resources that got created, referred to that earlier/old and incorrect migrationplan, which referred to old migrationtemplate and that in turn to wrong storagemapping.

Below are the outputs.

The migration that I triggered (with 'nfs' as my OpenStack Volume Type) is of 114s age, however it is referring to other resources which are 5d21h age.

root@vjailbreak:~# k get migrations
NAME                   AGE
migration-niket-test   114s   <<-----
root@vjailbreak:~#
root@vjailbreak:~# k describe migrations migration-niket-test
Name:         migration-niket-test
Namespace:    migration-system
Labels:       migrationplan=8c581797-cf60-4625-a986-84692999cd12
Annotations:  <none>
API Version:  vjailbreak.k8s.pf9.io/v1alpha1
Kind:         Migration
Metadata:
  Creation Timestamp:  2025-01-28T10:10:53Z
  Generation:          1
  Owner References:
    API Version:           vjailbreak.k8s.pf9.io/v1alpha1
    Block Owner Deletion:  true
    Controller:            true
    Kind:                  MigrationPlan
    Name:                  8c581797-cf60-4625-a986-84692999cd12
    UID:                   921f9437-e64f-4fcb-8c7f-e6929601bb83
  Resource Version:        649630
  UID:                     25420c45-ce8a-4049-bdd1-0d83518253df
Spec:
  Initiate Cutover:  true
  Migration Plan:    8c581797-cf60-4625-a986-84692999cd12   <----
  Pod Ref:           v2v-helper-niket-test
  Vm Name:           niket-test
[...]


root@vjailbreak:~# k get migrationplan 8c581797-cf60-4625-a986-84692999cd12
NAME                                   AGE
8c581797-cf60-4625-a986-84692999cd12   5d21h   <<----
root@vjailbreak:~#


root@vjailbreak:~# k describe migrationplan 8c581797-cf60-4625-a986-84692999cd12
Name:         8c581797-cf60-4625-a986-84692999cd12
Namespace:    migration-system
Labels:       <none>
Annotations:  <none>
API Version:  vjailbreak.k8s.pf9.io/v1alpha1
Kind:         MigrationPlan
Metadata:
  Creation Timestamp:  2025-01-22T13:14:34Z
  Finalizers:
    migrationplan.vjailbreak.pf9.io/finalizer
  Generation:        3
  Resource Version:  110292
  UID:               921f9437-e64f-4fcb-8c7f-e6929601bb83
Spec:
  Advanced Options:
  First Boot Script:  echo "Add your startup script here!"
  Migration Strategy:
    Admin Initiated Cut Over:  false
    Health Check Port:         443
    Perform Health Checks:     true
    Type:                      cold
  Migration Template:          a9878ff5-5c2e-4e8e-85d9-1f69962266b4
  Virtualmachines:
    [niket-test]
[...]


root@vjailbreak:~# k get migrationtemplate a9878ff5-5c2e-4e8e-85d9-1f69962266b4
NAME                                   AGE
a9878ff5-5c2e-4e8e-85d9-1f69962266b4   5d22h   <<-----
root@vjailbreak:~#

root@vjailbreak:~# k describe migrationtemplate a9878ff5-5c2e-4e8e-85d9-1f69962266b4
Name:         a9878ff5-5c2e-4e8e-85d9-1f69962266b4
Namespace:    migration-system
Labels:       <none>
Annotations:  <none>
API Version:  vjailbreak.k8s.pf9.io/v1alpha1
Kind:         MigrationTemplate
Metadata:
  Creation Timestamp:  2025-01-22T12:43:29Z
  Generation:          2
  Resource Version:    592083
  UID:                 dca43c1b-baaa-4eec-b7c2-0355f227d73b
Spec:
  Destination:
    Openstack Ref:  21962b25-a928-4af4-b477-0868cb8ae5b0
  Network Mapping:  5af7f4ff-8aa0-47c2-ae99-660a4ca225da
  Source:
    Datacenter:     PNAP BMC
    Vmware Ref:     04527173-7e7a-41d5-94c1-52fb29866018
  Storage Mapping:  e683cf5d-634e-4fe1-99f1-d6c907b16d81
Status:
[...]


root@vjailbreak:~# k get storagemapping e683cf5d-634e-4fe1-99f1-d6c907b16d81
NAME                                   AGE
e683cf5d-634e-4fe1-99f1-d6c907b16d81   5d21h  <<-----
root@vjailbreak:~#
root@vjailbreak:~#
root@vjailbreak:~# k describe storagemapping e683cf5d-634e-4fe1-99f1-d6c907b16d81
Name:         e683cf5d-634e-4fe1-99f1-d6c907b16d81
Namespace:    migration-system
Labels:       <none>
Annotations:  <none>
API Version:  vjailbreak.k8s.pf9.io/v1alpha1
Kind:         StorageMapping
Metadata:
  Creation Timestamp:  2025-01-22T13:14:33Z
  Generation:          1
  Resource Version:    110109
  UID:                 883eecbb-edb0-4d5a-8f5f-801854fa0a6f
Spec:
  Storages:
    Source:  vcenter-datastore-1
    Target:  __DEFAULT__       <<<------
Status:
  Storage Mapping Validation Message:  StorageMapping validated
  Storage Mapping Validation Status:   Succeeded
Events:                                <none>
root@vjailbreak:~#

In the above storagemapping we can see spec.storages.target as __DEFAULT__ which is NOT what I had set on vjailbreak console.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant