On 08/12/2013 11:16 PM, Marty Sweet wrote:
Hi all,
I've hit a problem that I have been chewing on for the past few hours. A
few months ago I changed the local storage path naming convention (examples
below) and updated the corresponding records in the cloudstack database
manually. This works gre
just dawned on me, you might have to forget the storage pools (if no vm's
are running) on the hosts. Then reconnect the kvm agents (by restarting the
service on the hosts or from cloudstack-> force reconnect command). they
should get programmed correctly!
On Mon, Aug 12, 2013 at 2:16 PM, Marty Sw
Hi all,
I've hit a problem that I have been chewing on for the past few hours. A
few months ago I changed the local storage path naming convention (examples
below) and updated the corresponding records in the cloudstack database
manually. This works great until old templates are used. I understand