Hi,
I got several times my images have been left in USED state, when I
executed CANCEL on RUNNING VM.
In oned.conf there is
DATASTORE_LOCATION=/scratch/lustre/one/lxibm100
In frontend there is a symlink
~/var/datastores -> /scratch/lustre/one/lxibm100
/scratch/lustre is a lustre file system.
Hi,
I don't see how the links could have anything to do with it. Maybe it was
some other ting and the restart solved it...
Did anything else change? Are you using the same commands, from the same VM
state? onevm delete, cancel and shutdown trigger different code in oned.
Regards
--
Carlos Martín,
Hi,
I just tested with changed configuration. I put
DATASTORE_LOCATION=/real_path_to_datastores and I don't see any problems
with images (references counting and in memory name cache) for the moment.
Do symlinks in virtualisation hosts to datastores location could lead to
that ? I saw that i
Hi Rolandas,
I've tried to reproduce the bug following your steps, but there must be
something else that is triggering it.
These are the exact commands I have executed, could you please check if I
missed something?
$ oneuser list
ID NAMEGROUP AUTH VMSMEM
On 2013-01-22 09:58, Rolandas Naujikas wrote:
Hi,
I see that bug http://dev.opennebula.org/issues/1087 reappeared in
3.8.3. The sequence to repeat is:
1) create an image as save from VM (as an user in oneadmin group);
2) change owner to oneadmin;
3) delete image;
4) repeat (1) and (2) will fail
Hi,
I see that bug http://dev.opennebula.org/issues/1087 reappeared in
3.8.3. The sequence to repeat is:
1) create an image as save from VM (as an user in oneadmin group);
2) change owner to oneadmin;
3) delete image;
4) repeat (1) and (2) will fail saying "[ImageChown] USER [0] already
owns I
