-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
False
-
None
-
False
-
-
We saw the following output in MTV-946:
- oc describe plan vc7-plan-mxie-mtv -n mxie-mtv
Name: vc7-plan-mxie-mtv
Namespace: mxie-mtv
Labels: <none>
Annotations: populatorLabels: True
API Version: forklift.konveyor.io/v1beta1
Kind: Plan
Metadata:
Creation Timestamp: 2024-03-15T08:03:31Z
Generation: 1
Resource Version: 18471686
UID: f9888170-87ac-4ad1-a80f-e1a6ff19e042
Spec:
Description:
Map:
Network:
Name: networkmap-vc7
Namespace: mxie-mtv
Storage:
Name: storagemap-vc7
Namespace: mxie-mtv
Provider:
Destination:
Name: host
Namespace: mxie-mtv
Source:
Name: vc7
Namespace: mxie-mtv
Target Namespace: mxie-mtv
Vms:
Name: esx7.0-rhel9.3-x86_64
Warm: falseStatus:
Conditions:
Category: Required
Last Transition Time: 2024-03-15T08:03:40Z
Message: The migration plan is ready.
Status: True
Type: Ready
Category: Advisory
Durable: true Last Transition Time: 2024-03-15T08:03:56Z
Message: The plan execution has FAILED.
Status: True
Type: Failed
Category: Warn
Items:
id:vm-121 name:'esx7.0-rhel9.3-x86_64'
Last Transition Time: 2024-03-15T08:04:00Z
Message: Target VM name does not comply with DNS1123 RFC, will be automatically changed.
Reason: NotValid
Status: True
Type: TargetNameNotValid
Migration:
Completed: 2024-03-15T08:03:56Z
History:
Conditions:
Category: Advisory
Durable: true Last Transition Time: 2024-03-15T08:03:56Z
Message: The plan execution has FAILED.
Status: True
Type: Failed
Map:
Network:
Generation: 1
Name: networkmap-vc7
Namespace: mxie-mtv
UID: 01a9d3b5-824d-4d51-9990-1806bb349bae
Storage:
Generation: 1
Name: storagemap-vc7
Namespace: mxie-mtv
UID: c0a68bf4-cc7b-470d-b0c9-b402fa5fa525
Migration:
Generation: 1
Name: vc7-plan-mxie-mtv-1710489822821
Namespace: mxie-mtv
UID: 1757e142-2c02-415e-86d9-930950fa9c7e
Plan:
Generation: 1
Name: vc7-plan-mxie-mtv
Namespace: mxie-mtv
UID: f9888170-87ac-4ad1-a80f-e1a6ff19e042
Provider:
Destination:
Generation: 1
Name: host
Namespace: mxie-mtv
UID: 128d44cc-2ff2-40af-8031-c83f20bfa63d
Source:
Generation: 1
Name: vc7
Namespace: mxie-mtv
UID: 0aef4c04-3aef-48b2-8303-7339cb01eaea
Started: 2024-03-15T08:03:43Z
Vms:
Completed: 2024-03-15T08:03:56Z
Conditions:
Category: Advisory
Durable: true Last Transition Time: 2024-03-15T08:03:53Z
Message: The VM migration has FAILED.
Status: True
Type: Failed
Error:
Phase: CreateDataVolumes
Reasons:
pods "vc7-plan-mxie-mtv-vm-121-pvcinit-" is forbidden: unable to validate against any security context constraint: [pod.metadata.annotations[seccomp.security.alpha.kubernetes.io/pod]: Forbidden: seccomp may not be set, pod.metadata.annotations[container.seccomp.security.alpha.kubernetes.io/main]: Forbidden: seccomp may not be set, provider restricted-v2: .containers[0].runAsUser: Invalid value: 107: must be in the ranges: [1000770000, 1000779999], provider "restricted": Forbidden: not usable by user or serviceaccount, provider "containerized-data-importer": Forbidden: not usable by user or serviceaccount, provider "nonroot-v2": Forbidden: not usable by user or serviceaccount, provider "nonroot": Forbidden: not usable by user or serviceaccount, provider "forklift-controller-scc": Forbidden: not usable by user or serviceaccount, provider "hostmount-anyuid": Forbidden: not usable by user or serviceaccount, provider "kubevirt-controller": Forbidden: not usable by user or serviceaccount, provider "machine-api-termination-handler": Forbidden: not usable by user or serviceaccount, provider "bridge-marker": Forbidden: not usable by user or serviceaccount, provider "hostnetwork-v2": Forbidden: not usable by user or serviceaccount, provider "hostnetwork": Forbidden: not usable by user or serviceaccount, provider "hostaccess": Forbidden: not usable by user or serviceaccount, provider "linux-bridge": Forbidden: not usable by user or serviceaccount, provider "kubevirt-handler": Forbidden: not usable by user or serviceaccount, provider "node-exporter": Forbidden: not usable by user or serviceaccount, provider "privileged": Forbidden: not usable by user or serviceaccount]
Id: vm-121
Name: esx7.0-rhel9.3-x86_64
Phase: Completed
Pipeline:
Description: Initialize migration.
Error:
Phase: Running
Reasons:
pods "vc7-plan-mxie-mtv-vm-121-pvcinit-" is forbidden: unable to validate against any security context constraint: [pod.metadata.annotations[seccomp.security.alpha.kubernetes.io/pod]: Forbidden: seccomp may not be set, pod.metadata.annotations[container.seccomp.security.alpha.kubernetes.io/main]: Forbidden: seccomp may not be set, provider restricted-v2: .containers[0].runAsUser: Invalid value: 107: must be in the ranges: [1000770000, 1000779999], provider "restricted": Forbidden: not usable by user or serviceaccount, provider "containerized-data-importer": Forbidden: not usable by user or serviceaccount, provider "nonroot-v2": Forbidden: not usable by user or serviceaccount, provider "nonroot": Forbidden: not usable by user or serviceaccount, provider "forklift-controller-scc": Forbidden: not usable by user or serviceaccount, provider "hostmount-anyuid": Forbidden: not usable by user or serviceaccount, provider "kubevirt-controller": Forbidden: not usable by user or serviceaccount, provider "machine-api-termination-handler": Forbidden: not usable by user or serviceaccount, provider "bridge-marker": Forbidden: not usable by user or serviceaccount, provider "hostnetwork-v2": Forbidden: not usable by user or serviceaccount, provider "hostnetwork": Forbidden: not usable by user or serviceaccount, provider "hostaccess": Forbidden: not usable by user or serviceaccount, provider "linux-bridge": Forbidden: not usable by user or serviceaccount, provider "kubevirt-handler": Forbidden: not usable by user or serviceaccount, provider "node-exporter": Forbidden: not usable by user or serviceaccount, provider "privileged": Forbidden: not usable by user or serviceaccount]
Name: Initialize
Phase: Running
Progress:
Completed: 0
Total: 1
Started: 2024-03-15T08:03:43Z
Annotations:
Unit: MB
Description: Allocate disks.
Name: DiskAllocation
Phase: Pending
Progress:
Completed: 0
Total: 16384
Tasks:
Annotations:
Unit: MB
Name: [esx7.0-matrix] esx7.0-rhel9.3-x86_64/esx7.0-rhel9.3-x86_64.vmdk
Progress:
Completed: 0
Total: 16384
Description: Convert image to kubevirt.
Name: ImageConversion
Phase: Pending
Progress:
Completed: 0
Total: 1
Annotations:
Unit: MB
Description: Copy disks.
Name: DiskTransferV2v
Phase: Pending
Progress:
Completed: 0
Total: 16384
Tasks:
Annotations:
Unit: MB
Name: [esx7.0-matrix] esx7.0-rhel9.3-x86_64/esx7.0-rhel9.3-x86_64.vmdk
Progress:
Completed: 0
Total: 16384
Description: Create VM.
Name: VirtualMachineCreation
Phase: Pending
Progress:
Completed: 0
Total: 1
Restore Power State: Off
Started: 2024-03-15T08:03:43Z
Observed Generation: 1
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning TargetNameNotValid 93s plan Target VM name does not comply with DNS1123 RFC, will be automatically changed.
Normal ValidatingVDDK 84s (x2 over 93s) plan Validating VDDK init image
Normal ValidatingVDDK 84s (x2 over 93s) plan Validating VDDK init image
Normal ValidatingVDDK 84s (x2 over 93s) plan Validating VDDK init image
Normal ValidatingVDDK 84s (x2 over 93s) plan Validating VDDK init image
Normal Ready 84s plan The migration plan is ready.
Normal Ready 84s plan The migration plan is ready.
Normal Ready 84s plan The migration plan is ready.
Normal Ready 84s plan The migration plan is ready.
Warning TargetNameNotValid 64s (x3 over 93s) plan Target VM name does not comply with DNS1123 RFC, will be automatically changed.
Warning TargetNameNotValid 64s (x3 over 93s) plan Target VM name does not comply with DNS1123 RFC, will be automatically changed.
Warning TargetNameNotValid 64s (x3 over 93s) plan Target VM name does not comply with DNS1123 RFC, will be automatically changed.
We recently fixed a similar issue with the VDDK validation pod so we can do the same for the PVC-init pod.