-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
3
-
False
-
-
False
-
CNV v4.17.1.rhel9-13
-
---
-
---
-
-
Storage Core Sprint 261
-
None
Description of problem:
When creating a VirtualMachineExport with a long name (e.g. greater than 63 characters) (I used a VirtualMachine as a source, but I'm not sure it matters), the VirtualMachineExport resource will not receive any status updates.This happens because the Service it will try to apply passes through VirtualMachineExport's name without length validation.
Version-Release number of selected component (if applicable):
Client Version: 4.15.2 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: 4.16.4 Kubernetes Version: v1.29.6+aba1e8d
How reproducible:
100%
Steps to Reproduce:
1.Create a VirtualMachineExport with a name length exceeding 63 characters
Actual results:
The VirtualMachineExport does not receive status updates. The virt-controller fails to reconcile it.
Expected results:
The VirtualMachineExport should receive status updates and progress.
Additional Information:
- I've filed the upstream issue here: https://github.com/kubevirt/kubevirt/issues/12658
- And I've sent a corresponding pull request https://github.com/kubevirt/kubevirt/pull/12659
- is duplicated by
-
CNV-47232 VirtualMachineExport fails to create the export pod if the PVC name exceeds 63 characters
- Closed
- links to