[
https://issues.apache.org/jira/browse/VCL-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Kurth updated VCL-913:
---------------------------
Description: When VCL use KVM and libvirt provisioning module to create an
new image, it does not check the length of the image name. However, libvirt
restrict the length of the name for a VM to be less than 50 characters. When I
create an new image, VCL can create a very long image name, and final VM's name
can be longer than 50 characters and libvirt will reject to boot the VM. (was:
When VCL use KVM and libvert provisioning module to create an new image, it
does not check the length of the image name. However, libvert restrict the
length of the name for a VM to be less than 50 characters. When I create an new
image, VCL can create a very long image name, and final VM's name can be longer
than 50 characters and libvert will reject to boot the VM.)
Summary: VCL KVM Libvirt provisioning module does not check length of
the image's name when create an new image (was: VCL KVM Libvert provisioning
modeldoes not check length of the image's name when create an new image)
> VCL KVM Libvirt provisioning module does not check length of the image's name
> when create an new image
> ------------------------------------------------------------------------------------------------------
>
> Key: VCL-913
> URL: https://issues.apache.org/jira/browse/VCL-913
> Project: VCL
> Issue Type: Bug
> Components: vcld (backend)
> Affects Versions: 2.4.2
> Reporter: Xianqing Yu
>
> When VCL use KVM and libvirt provisioning module to create an new image, it
> does not check the length of the image name. However, libvirt restrict the
> length of the name for a VM to be less than 50 characters. When I create an
> new image, VCL can create a very long image name, and final VM's name can be
> longer than 50 characters and libvirt will reject to boot the VM.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
