From 0fe18807a167423cd0c67f5f6a835d63b96f08d4 Mon Sep 17 00:00:00 2001 From: Gaurav Mehta Date: Wed, 4 Dec 2024 10:56:48 +1100 Subject: [PATCH 1/4] known vm-import-controller issues Signed-off-by: Gaurav Mehta --- docs/advanced/addons/vmimport.md | 15 ++++++++++++++- .../version-v1.3/advanced/addons/vmimport.md | 15 ++++++++++++++- .../version-v1.4/advanced/addons/vmimport.md | 15 ++++++++++++++- 3 files changed, 42 insertions(+), 3 deletions(-) diff --git a/docs/advanced/addons/vmimport.md b/docs/advanced/addons/vmimport.md index 988e74b6bc8..db69451736b 100644 --- a/docs/advanced/addons/vmimport.md +++ b/docs/advanced/addons/vmimport.md @@ -128,6 +128,7 @@ metadata: namespace: default spec: virtualMachineName: "alpine-export-test" + folder: "Discovered VM" #optional folder name, in case your vm is placed in a folder networkMapping: - sourceNetwork: "dvSwitch 1" destinationNetwork: "default/vlan1" @@ -185,4 +186,16 @@ spec: :::note OpenStack allows users to have multiple instances with the same name. In such a scenario, users are advised to use the Instance ID. The reconciliation logic tries to perform a name-to-ID lookup when a name is used. -::: \ No newline at end of file +::: + +#### Known issues +* **Source VM name is not RFC1123 compliant:** vm-import-controller will create the Harvester VM object with the same name as the source VM name. Harvester VM names need to be meet the K8s Object naming [criteria](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names). +In case the source VM does not meet these criteria the VM import may fail. Users may need to rename the source VM to allow import to be successful. + + +* **VM image name too long:** vm-import-controller, labels each imported disk with a label of format `vm-import-$VMname-$DiskName`. In certain scenarios this can exceed 63 characters. Users will notice the following error in the vm-import-controller logs +```shell +harvester-vm-import-controller-5698cd57c4-zw9l5 time="2024-08-30T19:20:34Z" level=error msg="error syncing 'default/mike-mr-tumbleweed-test': handler virtualmachine-import-job-change: error creating vmi: VirtualMachineImage.harvesterhci.io \"image-z +nqsp\" is invalid: metadata.labels: Invalid value: \"vm-import-mike-mr-tumbleweed-test-mike-mr-tumbleweed-test-default-disk-0.img\": must be no more than 63 characters, requeuing" +``` +Users may need to rename the source VM to allow import to be successful. \ No newline at end of file diff --git a/versioned_docs/version-v1.3/advanced/addons/vmimport.md b/versioned_docs/version-v1.3/advanced/addons/vmimport.md index b7734daa183..57971ef2a73 100644 --- a/versioned_docs/version-v1.3/advanced/addons/vmimport.md +++ b/versioned_docs/version-v1.3/advanced/addons/vmimport.md @@ -128,6 +128,7 @@ metadata: namespace: default spec: virtualMachineName: "alpine-export-test" + folder: "Discovered VM" #optional folder name, in case your vm is placed in a folder networkMapping: - sourceNetwork: "dvSwitch 1" destinationNetwork: "default/vlan1" @@ -185,4 +186,16 @@ spec: :::note OpenStack allows users to have multiple instances with the same name. In such a scenario, users are advised to use the Instance ID. The reconciliation logic tries to perform a name-to-ID lookup when a name is used. -::: \ No newline at end of file +::: + +#### Known issues +* **Source VM name is not RFC1123 compliant:** vm-import-controller will create the Harvester VM object with the same name as the source VM name. Harvester VM names need to be meet the K8s Object naming [criteria](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names). +In case the source VM does not meet these criteria the VM import may fail. Users may need to rename the source VM to allow import to be successful. + + +* **VM image name too long:** vm-import-controller, labels each imported disk with a label of format `vm-import-$VMname-$DiskName`. In certain scenarios this can exceed 63 characters. Users will notice the following error in the vm-import-controller logs +```shell +harvester-vm-import-controller-5698cd57c4-zw9l5 time="2024-08-30T19:20:34Z" level=error msg="error syncing 'default/mike-mr-tumbleweed-test': handler virtualmachine-import-job-change: error creating vmi: VirtualMachineImage.harvesterhci.io \"image-z +nqsp\" is invalid: metadata.labels: Invalid value: \"vm-import-mike-mr-tumbleweed-test-mike-mr-tumbleweed-test-default-disk-0.img\": must be no more than 63 characters, requeuing" +``` +Users may need to rename the source VM to allow import to be successful. \ No newline at end of file diff --git a/versioned_docs/version-v1.4/advanced/addons/vmimport.md b/versioned_docs/version-v1.4/advanced/addons/vmimport.md index f9f92f602ee..45dc4661076 100644 --- a/versioned_docs/version-v1.4/advanced/addons/vmimport.md +++ b/versioned_docs/version-v1.4/advanced/addons/vmimport.md @@ -128,6 +128,7 @@ metadata: namespace: default spec: virtualMachineName: "alpine-export-test" + folder: "Discovered VM" #optional folder name, in case your vm is placed in a folder networkMapping: - sourceNetwork: "dvSwitch 1" destinationNetwork: "default/vlan1" @@ -185,4 +186,16 @@ spec: :::note OpenStack allows users to have multiple instances with the same name. In such a scenario, users are advised to use the Instance ID. The reconciliation logic tries to perform a name-to-ID lookup when a name is used. -::: \ No newline at end of file +::: + +#### Known issues +* **Source VM name is not RFC1123 compliant:** vm-import-controller will create the Harvester VM object with the same name as the source VM name. Harvester VM names need to be meet the K8s Object naming [criteria](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names). +In case the source VM does not meet these criteria the VM import may fail. Users may need to rename the source VM to allow import to be successful. + + +* **VM image name too long:** vm-import-controller, labels each imported disk with a label of format `vm-import-$VMname-$DiskName`. In certain scenarios this can exceed 63 characters. Users will notice the following error in the vm-import-controller logs +```shell +harvester-vm-import-controller-5698cd57c4-zw9l5 time="2024-08-30T19:20:34Z" level=error msg="error syncing 'default/mike-mr-tumbleweed-test': handler virtualmachine-import-job-change: error creating vmi: VirtualMachineImage.harvesterhci.io \"image-z +nqsp\" is invalid: metadata.labels: Invalid value: \"vm-import-mike-mr-tumbleweed-test-mike-mr-tumbleweed-test-default-disk-0.img\": must be no more than 63 characters, requeuing" +``` +Users may need to rename the source VM to allow import to be successful. \ No newline at end of file From f3dc849ec05d1fc2c3a07aca4a7888338a3b70ef Mon Sep 17 00:00:00 2001 From: Gaurav Mehta Date: Wed, 18 Dec 2024 12:31:21 +1100 Subject: [PATCH 2/4] Apply suggestions from code review include feedback from Jillian. Co-authored-by: Jillian <67180770+jillian-maroket@users.noreply.github.com> Signed-off-by: Gaurav Mehta --- docs/advanced/addons/vmimport.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/advanced/addons/vmimport.md b/docs/advanced/addons/vmimport.md index db69451736b..4bffa38c318 100644 --- a/docs/advanced/addons/vmimport.md +++ b/docs/advanced/addons/vmimport.md @@ -189,13 +189,12 @@ OpenStack allows users to have multiple instances with the same name. In such a ::: #### Known issues -* **Source VM name is not RFC1123 compliant:** vm-import-controller will create the Harvester VM object with the same name as the source VM name. Harvester VM names need to be meet the K8s Object naming [criteria](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names). -In case the source VM does not meet these criteria the VM import may fail. Users may need to rename the source VM to allow import to be successful. +* **Source virtual machine name is not RFC1123 compliant**: When creating a virtual machine object, the vm-import-controller add-on uses the name of the source virtual machine, which may not meet the Kubernetes object [naming criteria](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names). You may need to rename the source virtual machine to allow successful completion of the import. -* **VM image name too long:** vm-import-controller, labels each imported disk with a label of format `vm-import-$VMname-$DiskName`. In certain scenarios this can exceed 63 characters. Users will notice the following error in the vm-import-controller logs +* **Virtual machine image name too long**: The vm-import-controller add-on labels each imported disk using the format `vm-import-$VMname-$DiskName`. If a label exceeds 63 characters, you will see the following error message in the vm-import-controller logs: ```shell harvester-vm-import-controller-5698cd57c4-zw9l5 time="2024-08-30T19:20:34Z" level=error msg="error syncing 'default/mike-mr-tumbleweed-test': handler virtualmachine-import-job-change: error creating vmi: VirtualMachineImage.harvesterhci.io \"image-z nqsp\" is invalid: metadata.labels: Invalid value: \"vm-import-mike-mr-tumbleweed-test-mike-mr-tumbleweed-test-default-disk-0.img\": must be no more than 63 characters, requeuing" ``` -Users may need to rename the source VM to allow import to be successful. \ No newline at end of file +You may need to modify the assigned labels to allow successful completion of the import. \ No newline at end of file From dbb5b6f1fb32c6f3f6c0a0c1dd226bec15ee2f31 Mon Sep 17 00:00:00 2001 From: Volker Theile Date: Tue, 8 Apr 2025 11:07:51 +0200 Subject: [PATCH 3/4] Several improvements Signed-off-by: Volker Theile Signed-off-by: Gaurav Mehta --- docs/advanced/addons/vmimport.md | 12 +++--------- .../version-v1.3/advanced/addons/vmimport.md | 17 +++++++++-------- .../version-v1.4/advanced/addons/vmimport.md | 17 +++++++++-------- 3 files changed, 21 insertions(+), 25 deletions(-) diff --git a/docs/advanced/addons/vmimport.md b/docs/advanced/addons/vmimport.md index 4bffa38c318..76e69a189f4 100644 --- a/docs/advanced/addons/vmimport.md +++ b/docs/advanced/addons/vmimport.md @@ -128,7 +128,7 @@ metadata: namespace: default spec: virtualMachineName: "alpine-export-test" - folder: "Discovered VM" #optional folder name, in case your vm is placed in a folder + folder: "Discovered VM" networkMapping: - sourceNetwork: "dvSwitch 1" destinationNetwork: "default/vlan1" @@ -146,6 +146,8 @@ This will trigger the controller to export the VM named "alpine-export-test" on This can take a while based on the size of the virtual machine, but users should see `VirtualMachineImages` created for each disk in the defined virtual machine. +If the source VM is placed in a folder, then you can specify the folder name in the optional `folder` field. + The list of items in `networkMapping` will define how the source network interfaces are mapped to the Harvester Networks. If a match is not found, each unmatched network interface is attached to the default `managementNetwork`. @@ -190,11 +192,3 @@ OpenStack allows users to have multiple instances with the same name. In such a #### Known issues * **Source virtual machine name is not RFC1123 compliant**: When creating a virtual machine object, the vm-import-controller add-on uses the name of the source virtual machine, which may not meet the Kubernetes object [naming criteria](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names). You may need to rename the source virtual machine to allow successful completion of the import. - - -* **Virtual machine image name too long**: The vm-import-controller add-on labels each imported disk using the format `vm-import-$VMname-$DiskName`. If a label exceeds 63 characters, you will see the following error message in the vm-import-controller logs: -```shell -harvester-vm-import-controller-5698cd57c4-zw9l5 time="2024-08-30T19:20:34Z" level=error msg="error syncing 'default/mike-mr-tumbleweed-test': handler virtualmachine-import-job-change: error creating vmi: VirtualMachineImage.harvesterhci.io \"image-z -nqsp\" is invalid: metadata.labels: Invalid value: \"vm-import-mike-mr-tumbleweed-test-mike-mr-tumbleweed-test-default-disk-0.img\": must be no more than 63 characters, requeuing" -``` -You may need to modify the assigned labels to allow successful completion of the import. \ No newline at end of file diff --git a/versioned_docs/version-v1.3/advanced/addons/vmimport.md b/versioned_docs/version-v1.3/advanced/addons/vmimport.md index 57971ef2a73..ccc7a3a0c63 100644 --- a/versioned_docs/version-v1.3/advanced/addons/vmimport.md +++ b/versioned_docs/version-v1.3/advanced/addons/vmimport.md @@ -128,7 +128,7 @@ metadata: namespace: default spec: virtualMachineName: "alpine-export-test" - folder: "Discovered VM" #optional folder name, in case your vm is placed in a folder + folder: "Discovered VM" networkMapping: - sourceNetwork: "dvSwitch 1" destinationNetwork: "default/vlan1" @@ -146,6 +146,8 @@ This will trigger the controller to export the VM named "alpine-export-test" on This can take a while based on the size of the virtual machine, but users should see `VirtualMachineImages` created for each disk in the defined virtual machine. +If the source VM is placed in a folder, then you can specify the folder name in the optional `folder` field. + The list of items in `networkMapping` will define how the source network interfaces are mapped to the Harvester Networks. If a match is not found, each unmatched network interface is attached to the default `managementNetwork`. @@ -192,10 +194,9 @@ OpenStack allows users to have multiple instances with the same name. In such a * **Source VM name is not RFC1123 compliant:** vm-import-controller will create the Harvester VM object with the same name as the source VM name. Harvester VM names need to be meet the K8s Object naming [criteria](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names). In case the source VM does not meet these criteria the VM import may fail. Users may need to rename the source VM to allow import to be successful. - -* **VM image name too long:** vm-import-controller, labels each imported disk with a label of format `vm-import-$VMname-$DiskName`. In certain scenarios this can exceed 63 characters. Users will notice the following error in the vm-import-controller logs -```shell -harvester-vm-import-controller-5698cd57c4-zw9l5 time="2024-08-30T19:20:34Z" level=error msg="error syncing 'default/mike-mr-tumbleweed-test': handler virtualmachine-import-job-change: error creating vmi: VirtualMachineImage.harvesterhci.io \"image-z -nqsp\" is invalid: metadata.labels: Invalid value: \"vm-import-mike-mr-tumbleweed-test-mike-mr-tumbleweed-test-default-disk-0.img\": must be no more than 63 characters, requeuing" -``` -Users may need to rename the source VM to allow import to be successful. \ No newline at end of file +* **VM image name too long:** vm-import-controller, labels each imported disk with a label of format `vm-import-$VMname-$DiskName`. In certain scenarios this can exceed 63 characters. Users will notice the following error in the vm-import-controller logs: + ```shell + harvester-vm-import-controller-5698cd57c4-zw9l5 time="2024-08-30T19:20:34Z" level=error msg="error syncing 'default/mike-mr-tumbleweed-test': handler virtualmachine-import-job-change: error creating vmi: VirtualMachineImage.harvesterhci.io \"image-z + nqsp\" is invalid: metadata.labels: Invalid value: \"vm-import-mike-mr-tumbleweed-test-mike-mr-tumbleweed-test-default-disk-0.img\": must be no more than 63 characters, requeuing" + ``` + Users may need to rename the source VM to allow import to be successful. diff --git a/versioned_docs/version-v1.4/advanced/addons/vmimport.md b/versioned_docs/version-v1.4/advanced/addons/vmimport.md index 45dc4661076..22199363bd7 100644 --- a/versioned_docs/version-v1.4/advanced/addons/vmimport.md +++ b/versioned_docs/version-v1.4/advanced/addons/vmimport.md @@ -128,7 +128,7 @@ metadata: namespace: default spec: virtualMachineName: "alpine-export-test" - folder: "Discovered VM" #optional folder name, in case your vm is placed in a folder + folder: "Discovered VM" networkMapping: - sourceNetwork: "dvSwitch 1" destinationNetwork: "default/vlan1" @@ -145,6 +145,8 @@ This will trigger the controller to export the VM named "alpine-export-test" on This can take a while based on the size of the virtual machine, but users should see `VirtualMachineImages` created for each disk in the defined virtual machine. +If the source VM is placed in a folder, then you can specify the folder name in the optional `folder` field. + The list of items in `networkMapping` will define how the source network interfaces are mapped to the Harvester Networks. If a match is not found, each unmatched network interface is attached to the default `managementNetwork`. @@ -192,10 +194,9 @@ OpenStack allows users to have multiple instances with the same name. In such a * **Source VM name is not RFC1123 compliant:** vm-import-controller will create the Harvester VM object with the same name as the source VM name. Harvester VM names need to be meet the K8s Object naming [criteria](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names). In case the source VM does not meet these criteria the VM import may fail. Users may need to rename the source VM to allow import to be successful. - -* **VM image name too long:** vm-import-controller, labels each imported disk with a label of format `vm-import-$VMname-$DiskName`. In certain scenarios this can exceed 63 characters. Users will notice the following error in the vm-import-controller logs -```shell -harvester-vm-import-controller-5698cd57c4-zw9l5 time="2024-08-30T19:20:34Z" level=error msg="error syncing 'default/mike-mr-tumbleweed-test': handler virtualmachine-import-job-change: error creating vmi: VirtualMachineImage.harvesterhci.io \"image-z -nqsp\" is invalid: metadata.labels: Invalid value: \"vm-import-mike-mr-tumbleweed-test-mike-mr-tumbleweed-test-default-disk-0.img\": must be no more than 63 characters, requeuing" -``` -Users may need to rename the source VM to allow import to be successful. \ No newline at end of file +* **VM image name too long:** vm-import-controller, labels each imported disk with a label of format `vm-import-$VMname-$DiskName`. In certain scenarios this can exceed 63 characters. Users will notice the following error in the vm-import-controller logs: + ```shell + harvester-vm-import-controller-5698cd57c4-zw9l5 time="2024-08-30T19:20:34Z" level=error msg="error syncing 'default/mike-mr-tumbleweed-test': handler virtualmachine-import-job-change: error creating vmi: VirtualMachineImage.harvesterhci.io \"image-z + nqsp\" is invalid: metadata.labels: Invalid value: \"vm-import-mike-mr-tumbleweed-test-mike-mr-tumbleweed-test-default-disk-0.img\": must be no more than 63 characters, requeuing" + ``` + Users may need to rename the source VM to allow import to be successful. \ No newline at end of file From e9775615cbc921a61a248025dfde281db1e1565c Mon Sep 17 00:00:00 2001 From: Volker Theile Date: Wed, 23 Apr 2025 11:41:08 +0200 Subject: [PATCH 4/4] Address review comments Signed-off-by: Volker Theile Signed-off-by: Gaurav Mehta --- docs/advanced/addons/vmimport.md | 2 +- versioned_docs/version-v1.3/advanced/addons/vmimport.md | 9 ++++----- versioned_docs/version-v1.4/advanced/addons/vmimport.md | 9 ++++----- 3 files changed, 9 insertions(+), 11 deletions(-) diff --git a/docs/advanced/addons/vmimport.md b/docs/advanced/addons/vmimport.md index 76e69a189f4..1119c903bac 100644 --- a/docs/advanced/addons/vmimport.md +++ b/docs/advanced/addons/vmimport.md @@ -146,7 +146,7 @@ This will trigger the controller to export the VM named "alpine-export-test" on This can take a while based on the size of the virtual machine, but users should see `VirtualMachineImages` created for each disk in the defined virtual machine. -If the source VM is placed in a folder, then you can specify the folder name in the optional `folder` field. +If the source virtual machine is placed in a folder, you can specify the folder name in the optional `folder` field. The list of items in `networkMapping` will define how the source network interfaces are mapped to the Harvester Networks. diff --git a/versioned_docs/version-v1.3/advanced/addons/vmimport.md b/versioned_docs/version-v1.3/advanced/addons/vmimport.md index ccc7a3a0c63..fb226583d15 100644 --- a/versioned_docs/version-v1.3/advanced/addons/vmimport.md +++ b/versioned_docs/version-v1.3/advanced/addons/vmimport.md @@ -146,7 +146,7 @@ This will trigger the controller to export the VM named "alpine-export-test" on This can take a while based on the size of the virtual machine, but users should see `VirtualMachineImages` created for each disk in the defined virtual machine. -If the source VM is placed in a folder, then you can specify the folder name in the optional `folder` field. +If the source virtual machine is placed in a folder, you can specify the folder name in the optional `folder` field. The list of items in `networkMapping` will define how the source network interfaces are mapped to the Harvester Networks. @@ -191,12 +191,11 @@ OpenStack allows users to have multiple instances with the same name. In such a ::: #### Known issues -* **Source VM name is not RFC1123 compliant:** vm-import-controller will create the Harvester VM object with the same name as the source VM name. Harvester VM names need to be meet the K8s Object naming [criteria](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names). -In case the source VM does not meet these criteria the VM import may fail. Users may need to rename the source VM to allow import to be successful. +* **Source virtual machine name is not RFC1123 compliant**: When creating a virtual machine object, the vm-import-controller add-on uses the name of the source virtual machine, which may not meet the Kubernetes object [naming criteria](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names). You may need to rename the source virtual machine to allow successful completion of the import. -* **VM image name too long:** vm-import-controller, labels each imported disk with a label of format `vm-import-$VMname-$DiskName`. In certain scenarios this can exceed 63 characters. Users will notice the following error in the vm-import-controller logs: +* **Virtual machine image name is too long**: The vm-import-controller add-on labels each imported disk using the format `vm-import-$VMname-$DiskName`. If a label exceeds 63 characters, you will see the following error message in the vm-import-controller logs: ```shell harvester-vm-import-controller-5698cd57c4-zw9l5 time="2024-08-30T19:20:34Z" level=error msg="error syncing 'default/mike-mr-tumbleweed-test': handler virtualmachine-import-job-change: error creating vmi: VirtualMachineImage.harvesterhci.io \"image-z nqsp\" is invalid: metadata.labels: Invalid value: \"vm-import-mike-mr-tumbleweed-test-mike-mr-tumbleweed-test-default-disk-0.img\": must be no more than 63 characters, requeuing" ``` - Users may need to rename the source VM to allow import to be successful. + You may need to rename the source virtual machine to allow successful completion of the import. diff --git a/versioned_docs/version-v1.4/advanced/addons/vmimport.md b/versioned_docs/version-v1.4/advanced/addons/vmimport.md index 22199363bd7..ab0391fcb5e 100644 --- a/versioned_docs/version-v1.4/advanced/addons/vmimport.md +++ b/versioned_docs/version-v1.4/advanced/addons/vmimport.md @@ -145,7 +145,7 @@ This will trigger the controller to export the VM named "alpine-export-test" on This can take a while based on the size of the virtual machine, but users should see `VirtualMachineImages` created for each disk in the defined virtual machine. -If the source VM is placed in a folder, then you can specify the folder name in the optional `folder` field. +If the source virtual machine is placed in a folder, you can specify the folder name in the optional `folder` field. The list of items in `networkMapping` will define how the source network interfaces are mapped to the Harvester Networks. @@ -191,12 +191,11 @@ OpenStack allows users to have multiple instances with the same name. In such a ::: #### Known issues -* **Source VM name is not RFC1123 compliant:** vm-import-controller will create the Harvester VM object with the same name as the source VM name. Harvester VM names need to be meet the K8s Object naming [criteria](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names). -In case the source VM does not meet these criteria the VM import may fail. Users may need to rename the source VM to allow import to be successful. +* **Source virtual machine name is not RFC1123 compliant**: When creating a virtual machine object, the vm-import-controller add-on uses the name of the source virtual machine, which may not meet the Kubernetes object [naming criteria](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names). You may need to rename the source virtual machine to allow successful completion of the import. -* **VM image name too long:** vm-import-controller, labels each imported disk with a label of format `vm-import-$VMname-$DiskName`. In certain scenarios this can exceed 63 characters. Users will notice the following error in the vm-import-controller logs: +* **Virtual machine image name is too long**: The vm-import-controller add-on labels each imported disk using the format `vm-import-$VMname-$DiskName`. If a label exceeds 63 characters, you will see the following error message in the vm-import-controller logs: ```shell harvester-vm-import-controller-5698cd57c4-zw9l5 time="2024-08-30T19:20:34Z" level=error msg="error syncing 'default/mike-mr-tumbleweed-test': handler virtualmachine-import-job-change: error creating vmi: VirtualMachineImage.harvesterhci.io \"image-z nqsp\" is invalid: metadata.labels: Invalid value: \"vm-import-mike-mr-tumbleweed-test-mike-mr-tumbleweed-test-default-disk-0.img\": must be no more than 63 characters, requeuing" ``` - Users may need to rename the source VM to allow import to be successful. \ No newline at end of file + You may need to rename the source virtual machine to allow successful completion of the import.