has no VMs running and this is why I am
>> unable to attach the volume :-) After upgrading and testing this I was
>> thinking it has to do with the upgrade, my fault.
>>
>> Thanks to everybody for the pointers.
>>
>> Sincerely,
>> Thomas Moroder
>>
>>
>&g
ding and testing this I was
> thinking it has to do with the upgrade, my fault.
>
> Thanks to everybody for the pointers.
>
> Sincerely,
> Thomas Moroder
>
>
>
>>
>> - Si
>>
>> ____________
>> From: Rafael Weingärtner
>&
pache.org
Subject: Re: Volumes created without HyperVisor specified
You are only creating volumes and not attaching them anywhere. I think this
“create volume” is only logical. It probably only creates entries in DB,
but probably until you do something with the volume, it does not exist in
reality.
Have
tc/cloudstack/agent/log4j-cloud.xml on the host and restarting the agent.
- Si
From: Rafael Weingärtner
Sent: Wednesday, January 18, 2017 1:05 PM
To: dev@cloudstack.apache.org
Subject: Re: Volumes created without HyperVisor specified
You are only creating volum
On 1/18/2017 8:05 PM, Rafael Weingärtner wrote:
You are only creating volumes and not attaching them anywhere. I think this
“create volume” is only logical. It probably only creates entries in DB,
but probably until you do something with the volume, it does not exist in
reality.
Have you tried to
Yes, when a volume is first created, it exists only as a row in the
cloud.volumes table.
When you first attach it to a VM, then the hypervisor type is associated with
it (and the volume is actually created).
On 1/18/17, 12:05 PM, "Rafael Weingärtner" wrote:
You are only creating volumes a
Thomas,
What version did you upgrade from?
From: Thomas Moroder
Sent: Wednesday, January 18, 2017 1:00 PM
To: dev@cloudstack.apache.org
Subject: Volumes created without HyperVisor specified
Dear CloudStack dev-team,
after upgrading a CloudStack installation
You are only creating volumes and not attaching them anywhere. I think this
“create volume” is only logical. It probably only creates entries in DB,
but probably until you do something with the volume, it does not exist in
reality.
Have you tried to attach the volume in a VM?
On Wed, Jan 18, 2017
Dear CloudStack dev-team,
after upgrading a CloudStack installation to version 4.9.2 new volumes are
created without HyperVisor specified. This happens when creating from the UI, as
well as by using CloudMonkey/the API:
###
(local) 🐵 > create volume name="testdisk2"
diskofferingid=30fa0e20-4
