
The WEB interface show that the VM is locked, but when we run unlock_entity.sh there is no problem reported. How we think the VM were locked : There were filesystem issues (shortage disk space on the ovirt engine HOST) during a backup sequence, those consequences were discovered a few days later. The VMs are backed-up with this way: https://github.com/wefixit-AT/oVirtBackup The ovirt-engine logs tell us that Postgres DB has encountered problem like this one during the backup process: Message: PL/pgSQL function updatevdsdynamic(integer,integer,character varying,numeric,character varying,boolean,integer,integer,integer,uuid,integer,integer,integer,integer,integer,integer,integer,integer,character varying,character varying,character varying,character varying,integer,character varying,integer,integer,integer,boolean,character varying,character varying,character varying,character varying,character varying,character varying,character varying,character varying,character varying,character varying,character varying,integer,text,integer,character varying,character varying,character varying,character varying,character varying,character varying,text,text,smallint,integer,smallint,boolean,character varying,text,text,boolean,boolean,text,character varying,boolean,uuid,boolean,jsonb) line 4 at SQL statement; nested exception is org.postgresql.util.PSQLException: ERROR: could not extend file "base/16385/190997": No space left on device Later, we saw that those VMs they got a lock icon in the status column since this episode. This did not appear immediatly, but maybe a few hours after. It happens that those locked VMs are sort-of limited in the way that there are numerous things we cannot do with them, such as: - edit parameters (i.e. memory). - start them again after they get halted by unix command (halt -p) - copy the related disk. The version of ovirt used 4.2.1 Is there an other way to unlock the VMs ? Or to get unlock_entity.sh to work ?