Hi,
The problem was clear after a few tests, I don't think we need those
outputs anymore. The final 4.2 version will be released pretty soon,
including this fix.
Thanks
--
Join us at OpenNebulaConf2013 http://opennebulaconf.com in Berlin, 24-26
September, 2013
--
Carlos Martín, MSc
Project
Ok. Thank you.
Regards
Piotr Kandziora
On Wed, Jul 24, 2013 at 1:00 PM, Carlos Martín Sánchez
cmar...@opennebula.org wrote:
Hi,
The problem was clear after a few tests, I don't think we need those
outputs anymore. The final 4.2 version will be released pretty soon,
including this fix.
Hi,
Thank you for your reponse. It's nice that you fixed the problem. In my
opinion it was an easy way to bypass quota limits - as far as number of
allowed VMs is concerned.
Unfortunatelly I can not give you now outputs of comamnds you are asking
for. I'll try to provide them to you after a
Hi,
Looks like you've found a bug, I can confirm it. If the resize operation
fails because of the group limits, the user's VM usage is decremented [1].
Can you share a bit more about your quotas? At least the output of
oneuser/onegroup show/defaultquota.
Regards
[1]
Hi,
I try to resize VM capacity (add 0.5 CPU and 1GB RAM). According to the
available quota resources this action should succeed,
but
every time I try to change VM capacity via Sunstone this action fails due
to exceeded quota (FAILURE [VirtualMachineResize] group [1] limit of 2.5
reached for
