Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1690415 - CDI appends 'source pod' to a label and may fail on error that label must not be longer than 63 characters
Summary: CDI appends 'source pod' to a label and may fail on error that label must not...
Keywords:
Status: MODIFIED
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Storage
Version: 1.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 2.0
Assignee: Tzvi Avni
QA Contact: Qixuan Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-19 12:37 UTC by Radim Hrazdil
Modified: 2019-04-08 06:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)
VM manifests and importer log (deleted)
2019-03-19 12:37 UTC, Radim Hrazdil
no flags Details


Links
System ID Priority Status Summary Last Updated
Github kubevirt containerized-data-importer pull 740 None None None 2019-04-08 06:39:05 UTC

Description Radim Hrazdil 2019-03-19 12:37:48 UTC
Created attachment 1545602 [details]
VM manifests and importer log

Description of problem:
When a VM is created with long enough name, and than this VM is cloned, the cloning process fails on error:
E0319 12:24:27.745852       1 clone-controller.go:215] error processing pvc "default/vm-url-test-jwbfh-clone-vm-url-test-jwbfh-rootdisk-clone": invalid label value: "vm-url-test-jwbfh-clone-vm-url-test-jwbfh-rootdisk-clone-source-pod": must be no more than 63 characters

Version-Release number of selected component (if applicable):
virt-cdi-controller:v1.4.0

How reproducible:
100%

Steps to Reproduce:
1. create vm using origVm.yaml
2. create another vm using clonedVm.yaml
3. Start cloned VM

Actual results:
Cloned VM is stuck on pending, cdi-deployment pod fails on error mentioned above

Expected results:


Additional info:


Note You need to log in before you can comment on or make changes to this bug.