Hi,
Just for the record: setting STATE to 1, CLONING_OPS to 0 and set
in the body column for an images in CLONE or LOCKED state
resets the state to READY for the image and it can be used once more.
It would be nice if there were some utility repair tools to do this
kind of thing easily.
Hi,
What needs to be set in the image_pool table body column to turn
state CLONE and LOCKED off?
Regards,
Gerry
On 03/02/2015 18:17, Gerry O'Brien wrote:
> Hi,
>
> Below is the XML of the source image database entry. If I change
> STATE to 1, CLONING_OPS to
Hi Daniel,
Thanks for the reply. Sorry, but that didn't work. It won't let me
change state while an IMAGE is in CLONE or LOCKED.
I have an image which is unusable because I cannot change its state.
Regards,
Gerry
On 04/02/2015 06:56, Daniel Dehennin wrote:
> Gerry O'Brie
Gerry O'Brien writes:
> Hi,
Hello,
> The oned (4.6.2) daemon was restarted during a clone and now the
> source image is stuck in state CLONE and target image is stuck in state
> LOCKED. The actual Linux copy completed so both images are OK.
>
> How to I reset them to the READY state? Is
Hi,
Below is the XML of the source image database entry. If I change
STATE to 1, CLONING_OPS to 0 and set , will this fix the
problem? If so, is there any utility that will allow me edit the XML and
then update the database or will I have to update the database manually?
Gerry
4
