[ovirt-users] Cannot remove Snapshot. The VM is during a backup operation.

2024-01-23 Thread and
Hello!

Running ovirt Version 4.5.5-1.el8

I had an issue with the iscsi server during the backup and I have two VMs that 
cannot be backed up anymore by Veeam.

In the ovirt event log i have the following errors:

Snapshot 'Auto-generated for Backup VM' creation for VM 'dns-a' has been 
completed.
VDSM ovirt1-02 command StartNbdServerVDS failed: Bitmap does not exist: 
"{'reason': 'Bitmap does not exist in 
/rhev/data-center/mnt/blockSD/b2fa3469-a380-4180-a89a-43d65085d1b9/images/6a4de98a-b544-4df8-beb1-e560fd61c0e6/cdb26b8b-c447-48de-affa-d7f778aebac7',
 'bitmap': '12d2fb20-74da-4e63-b240-f1a42210760c'}"
Transfer was stopped by system. Reason: failed to create a signed image ticket.
Image Download with disk dns-a_Disk1 was initiated by veeam@internal-authz
Image Download with disk dns-a_Disk1 was cancelled.

The error on the Veeam backup proxy:
dns-a: Unable to create image transfer: Reason: 'Operation Failed', Detail: '[]'

When trying to delete the snapshot from the administration interface I receive 
the following error in the web interface (and nothing gets logged in the event 
log)
Cannot remove Snapshot. The VM is during a backup operation.

How should I go about fixing this issue?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BH4NXS4KGL6USLOGUJY3XPSGZWBBXLYB/


[ovirt-users] Cannot remove Snapshot. Related operation is currently in progress. Please try again later.

2022-04-13 Thread Martin Marusinec
Hello,

my storage got disconnected during the image migration, resulting is stuck 
migration. Task had been cleaned with restart of vdsdm service, but lead to 
stuck disk image. The VM got powered down in the meantime, and currently I 
cannot do anything with it, I always get a message like "Cannot Related 
operation is currently in progress."  I already used the unlock_entity.sh 
script, it cleaned something, but did not help me. I cannot delete the VM, 
delete the disk, delete the snapshots. I even deleted the wrong snapshot from 
disk. All I need is it get rid of the VM and its disk, as I can restore it from 
the backup. Could you please somebody try to navigate me how to solve the 
problem? Engine log keeps filling up with messages which indicate there is an 
orphaned task, however I am not sure what to delete from database:


2022-04-13 22:26:41,822+02 INFO  [org.ovirt.engine.core.bll.StorageJobCallback] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-87) 
[e546bb30-7d18-4348-9c28-9dbbf4ab1893] Command CopyData id: 
'62b1976b-729a-41ae-972c-a42de750ad1d': couldn't get the status of job 
'6ef3cb28-14cf-486a-ad71-96484c1a596e' on host 'kvm2.finamis.com' (id: 
'f880cfbe-5827-4853-a4fc-11199c439f79'), assuming it's still running
2022-04-13 22:26:41,846+02 INFO  
[org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-87) 
[e546bb30-7d18-4348-9c28-9dbbf4ab1893] Command 'LiveMigrateDisk' (id: 
'3cd698fd-08a2-419e-bdd8-6b3516bb3127') waiting on child command id: 
'2e9ad954-8f4e-41ed-9c75-015afeed337d' type:'CopyImageGroupVolumesData' to 
complete
2022-04-13 22:26:41,847+02 INFO  [org.ovirt.engine.core.bll.StorageJobCallback] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-87) 
[e546bb30-7d18-4348-9c28-9dbbf4ab1893] Command FenceVolumeJob id: 
'831828a3-2e0f-4989-965b-91761fa9601f': job 
'9dc88836-db04-49ae-b01e-18a56e24c91a' wasn't executed on any host, considering 
the job status as failed
2022-04-13 22:26:41,847+02 INFO  [org.ovirt.engine.core.bll.StorageJobCallback] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-87) 
[e546bb30-7d18-4348-9c28-9dbbf4ab1893] Command FenceVolumeJob id: 
'831828a3-2e0f-4989-965b-91761fa9601f': execution was completed, the command 
status is 'FAILED'
2022-04-13 22:26:42,850+02 ERROR 
[org.ovirt.engine.core.bll.job.JobRepositoryImpl] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-6) 
[e546bb30-7d18-4348-9c28-9dbbf4ab1893] Failed to save step 
'499b0207-61ba-4998-8cb8-2cb93b89422b', 'FINALIZING': 
CallableStatementCallback; SQL [{call insertstep(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, 
?, ?, ?, ?)}ERROR: insert or update on table "step" violates foreign key 
constraint "fk_step_job"
  Detail: Key (job_id)=(ed10f993-cfd2-4a8b-806f-3fbd823101ef) is not present in 
table "job".
  Where: SQL statement "INSERT INTO step (
step_id,
parent_step_id,
job_id,
step_type,
description,
step_number,
status,
progress,
start_time,
end_time,
correlation_id,
external_id,
external_system_type,
is_external
)
VALUES (
v_step_id,
v_parent_step_id,
v_job_id,
v_step_type,
v_description,
v_step_number,
v_status,
v_progress,
v_start_time,
v_end_time,
v_correlation_id,
v_external_id,
v_external_system_type,
v_is_external
)"
PL/pgSQL function insertstep(uuid,uuid,uuid,character 
varying,text,integer,character varying,smallint,timestamp with time 
zone,timestamp with time zone,character varying,uuid,character varying,boolean) 
line 3 at SQL statement; nested exception is org.postgresql.util.PSQLException: 
ERROR: insert or update on table "step" violates foreign key constraint 
"fk_step_job"
  Detail: Key (job_id)=(ed10f993-cfd2-4a8b-806f-3fbd823101ef) is not present in 
table "job".
  Where: SQL statement "INSERT INTO step (
step_id,
parent_step_id,
job_id,
step_type,
description,
step_number,
status,
progress,
start_time,
end_time,
correlation_id,
external_id,
external_system_type,
is_external
)
VALUES (
v_step_id,
v_parent_step_id,
v_job_id,
v_step_type,
v_description,
v_step_number,
v_status,
v_progress,
v_start_time,
v_end_time,
v_correlation_id,
v_external_id,
v_external_system_type,
v_is_external
)"
PL/pgSQL function insertstep(uuid,uuid,uuid,character 
varying,text,integer,character varying,smallint,timestamp with time 
zone,timestamp with time zone,character varying,uuid,character varying,boolean) 
line 3 at SQL statement
2022-04-13 22:26:42,851+02 ERROR 

Re: [ovirt-users] Cannot remove snapshot

2017-11-21 Thread Nicolas Ecarnot

Le 17/11/2017 à 16:38, Nicolas Ecarnot a écrit :
- export the VM then re-import, if this is related to some LV space 
missing. Then removing the snapshot the usual way.


Self-replying, for the record:

The backing image was seen full of errors by qemu-img check.
I exported the whole backing + img without commiting the snapshot.
I then imported with commiting, and it all went well.

4 hours of doubt.

--
Nicolas ECARNOT
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[ovirt-users] Cannot remove snapshot

2017-11-17 Thread Nicolas Ecarnot

Hello,

oVirt 3.6.7.5-1
I'm trying to remove a snapshot in a cold way (VM shut down).
It is failing, and VDSM is telling :

4f1588f3-ae2d-4702-b7e1-4ef53b5b5a1d::DEBUG::2017-11-17 
13:04:11,448::lvm::290::Storage.Misc.excCmd::(cmd) SUCCESS:  = ' 
WARNING: lvmetad is running but disabled. Restart lvmetad before 
enabling it!\n';  = 0
4f1588f3-ae2d-4702-b7e1-4ef53b5b5a1d::DEBUG::2017-11-17 
13:04:11,456::lvm::462::Storage.LVM::(_reloadlvs) lvs reloaded
4f1588f3-ae2d-4702-b7e1-4ef53b5b5a1d::DEBUG::2017-11-17 
13:04:11,456::lvm::462::Storage.OperationMutex::(_reloadlvs) Operation 
'lvm reload operation' released the operation mutex
4f1588f3-ae2d-4702-b7e1-4ef53b5b5a1d::ERROR::2017-11-17 
13:04:11,457::image::1302::Storage.Image::(merge) Unexpected error

Traceback (most recent call last):
  File "/usr/share/vdsm/storage/image.py", line 1293, in merge
sdDom, srcVolParams, volParams, reqSize, chain)
  File "/usr/share/vdsm/storage/image.py", line 1039, in 
_baseCowVolumeMerge

unsafe=False, rollback=True)
  File "/usr/share/vdsm/storage/volume.py", line 278, in rebase
raise se.MergeSnapshotsError(self.volUUID)
MergeSnapshotsError: Error merging snapshots: 
('4a8c17aa-5882-45a1-8a6e-40db39ed06ca',)


I read this : https://bugzilla.redhat.com/show_bug.cgi?id=1069610 , 
hoping I could find some workaround. But I couldn't.


If there is no abvious workaround, would there be other ways like :
- find the bare logical volume, shut down the VM, and play with low 
level qemu-img commands. I think I knwn how to do that, but I'm worried 
the oVirt database won't be in sync once I've removed the snapshot


or

- export the VM then re-import, if this is related to some LV space 
missing. Then removing the snapshot the usual way.


Any advice (apart the obvious upgrade-to-4.X-sir)?

--
Nicolas ECARNOT
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users