[
https://issues.apache.org/jira/browse/VCL-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Kurth reopened VCL-988:
----------------------------
The change committed in
[r1759025|https://svn.apache.org/viewvc?view=revision&revision=1759025] broke
the ability to delete KVM VMs and pretty much rendered libvirt/KVM provisioning
useless.
Changing the VM naming convention is a significant change since the code parses
existing VM/domain names to determine which can be *safely* deleted.
Even when the code is fixed to properly delete VMs with a different naming
convention, thought has to be put into how the change will be handled when
upgrading the VCL code when existing KVM hosts contain VMs using the old names.
Every place which requires exact VM names needs to handle both the old and new
names.
> KVM libvirt provisioning module colon char in domain name Error starting
> domain: Invalid machine name
> -----------------------------------------------------------------------------------------------------
>
> Key: VCL-988
> URL: https://issues.apache.org/jira/browse/VCL-988
> Project: VCL
> Issue Type: Bug
> Components: vcld (backend)
> Reporter: Aaron Peeler
> Fix For: 2.5
>
>
> The use of a colon character in the domain name prevents the vm from starting
> with Error starting domain: Invalid machine name
> libvirt can define and undefine a VM with the colon char but cannot start the
> vm
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
