[ovirt-users] Re: Veeam Backup for RHV (oVirt)
Hi, I will document the required steps to revert from Keycloak. I only need some time to test the procedure. Definitely, it is possible. Stay tuned, I will post it first here (today) Artur On Thu, Jul 28, 2022 at 8:30 AM wrote: > Ah, I see.. > Then, is there any good guide or documentation how to revert from Keycloak > to AAA? > All I could find is how to move from AAA to Keycloak, but not reverse. > ___ > 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/6HNKNAXW2ACO5VAJAH2BTMD3T3BKTUHK/ > -- Artur Socha Senior Software Engineer, RHV Red Hat ___ 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/LY33XM7SMBORJSJUQ33C77B2DJDXAI4C/
[ovirt-users] Re: Veeam Backup for RHV (oVirt)
Ah, I see.. Then, is there any good guide or documentation how to revert from Keycloak to AAA? All I could find is how to move from AAA to Keycloak, but not reverse. ___ 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/6HNKNAXW2ACO5VAJAH2BTMD3T3BKTUHK/
[ovirt-users] Re: Veeam Backup for RHV (oVirt)
Hello there, Thank you for the report. The problem is described there https://bugzilla.redhat.com/show_bug.cgi?id=2111207 Veeam backup for RHV isn't supporting this credentials format now > > 2022-07-27 08:08:44.176 00031 [19545] INFO | [RhevCluster_31]: Test > connection to cluster [IP: engine.example.org, Port: 443, User: > admin@ovirt@internalsso] You should revert authorization mechanism to older variant instead of keyclock > -Исходное сообщение- > От: Nir Soffer > Отправлено: Wednesday, July 27, 2022 6:34 PM > Кому: markec...@gmail.com > Копия: users; Yury Panchenko > Тема: Re: [ovirt-users] Veeam Backup for RHV (oVirt) > > On Wed, Jul 27, 2022 at 2:56 PM wrote: > > > > Hi! > > Not really sure if this is right place to ask, but.. > > > > I am trying to use Veeam Backup for Red Hat Virtualization on oVirt 4.5.1. > > I have been using it on version 4.4.10.7 and it works ok there. > > > > On Veeam Release page it says that supported OS is RHV 4.4SP1 (oVirt 4.5). > > > > When i try to do backup, this is what i get from Veeam backup. > > No errors in vdsm.log and engine.log.. > > > > 2022-07-27 08:08:44.153 00039 [19545] INFO | > [LoggingEventsManager_39]: Add to storage LoggingEvent [id: 34248685- > a193-4df5-8ff2-838f738e211c, Type: BackupStartedNew] > > 2022-07-27 08:08:44.168 00039 [19545] INFO | [TaskManager_39]: Create > and run new async task. [call method:'RunBackupChain'] > > 2022-07-27 08:08:44.168 00039 [19545] INFO | [AsyncTask_39]: New > AsynTask created [id:'aafa22ac-ff2e-4647-becb-dca88e3eb67f', description:'', > type:'BACKUP_VM_POLICY'] > > 2022-07-27 08:08:44.168 00039 [19545] INFO | [AsyncTask_39]: Prepare > AsynTask to run [id:'aafa22ac-ff2e-4647-becb-dca88e3eb67f'] > > 2022-07-27 08:08:44.176 00031 [19545] INFO | [BackupPolicy_31]: Refresh > VMs for policy '6e090c98-d44b-4785-acb4-82a627da5d9b' > > 2022-07-27 08:08:44.176 00031 [19545] INFO | [BackupPolicy_31]: Begin > updating list of active VMs for policy '6e090c98-d44b-4785-acb4- > 82a627da5d9b' [forceRefresh = True] > > 2022-07-27 08:08:44.176 00031 [19545] INFO | [RhevCluster_31]: Test > connection to cluster [IP: engine.example.org, Port: 443, User: > admin@ovirt@internalsso] > > 2022-07-27 08:08:44.189 00039 [19545] INFO | [TaskManager_39]: > AsyncTask registered. [id:'aafa22ac-ff2e-4647-becb-dca88e3eb67f'] > > 2022-07-27 08:08:44.371 00031 [19545] INFO | [RhevCluster_31]: Test > connection to cluster success. Status: Success. Message: > > 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicyManager_31]: > Refreshing the policies data... > > 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicy_31]: Begin > updating list of active VMs for policy '6e090c98-d44b-4785-acb4- > 82a627da5d9b' [forceRefresh = False] > > 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicy_31]: List of > active VMs updated for policy '6e090c98-d44b-4785-acb4-82a627da5d9b' > [forceRefresh = False]. Number of active VMs '1' > > 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicyManager_31]: > Policies data has been refreshed. > > 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicy_31]: List of > active VMs updated for policy '6e090c98-d44b-4785-acb4-82a627da5d9b' > [forceRefresh = True]. Number of active VMs '1' > > 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicy_31]: Found > the '1' VMs to backup in policy '6e090c98-d44b-4785-acb4-82a627da5d9b' > > 2022-07-27 08:08:44.564 00031 [19545] INFO | [BackupPolicy_31]: * > Parallel policy runner has started * for policy [Name:'test5', ID: '6e090c98- > d44b-4785-acb4-82a627da5d9b' > > 2022-07-27 08:08:44.564 00031 [19545] INFO | [VeeamBackupServer_31]: > Test connection to backup server [IP: 'veeambr.example.org', Port: '10006', > User: 'rhvproxy'] > > 2022-07-27 08:08:44.931 00031 [19545] INFO | [VeeamBackupServer_31]: > Test connection to backup server [IP: 'veeambr.example.org', Port: '10006']. > Connection status: ConnectionSuccess. Version: 11.0.1.1261 > > 2022-07-27 08:08:45.423 00031 [19545] INFO | [BackupPolicy_31]: > Successfully called CreateVeeamPolicySession for job [UID: '6e090c98-d44b- > 4785-acb4-82a627da5d9b'], session [UID: 'aafa22ac-ff2e-4647-becb- > dca88e3eb67f'] > > 2022-07-27 08:08:45.820 00031 [19545] INFO | [BackupPolicy_31]: > Successfully called RetainPolicyVms for job [UID: '6e090c98-d44b-4785-acb4- > 82a627da5d9b'] with VMs: 50513a65-6ccc-479b-9b61-032e0961b016 > > 2022-07-27 08:08:45.820 00031 [19545] INFO | [BackupPolicy_31]: Start > calculating maxPointsCount > > 2022-07-27 08:08:45.820 00031 [19545] INFO | [BackupPolicy_31]: End > calculating maxPointsCount. Result = 7 > > 2022-07-27 08:08:45.820 00031 [19545] INFO | [BackupPolicy_31]: Starting > validate repository schedule. Repository [UID: '237e41d6-7c67-4a1f-80bf- > d7c73c481209', MaxPointsCount: '7', IsPeriodicFullRequired: 'False'] > > 2022-07-27 08:08:46.595 00031 [19545] INFO
[ovirt-users] Re: Veeam Backup for RHV (oVirt)
On Wed, Jul 27, 2022 at 2:56 PM wrote: > > Hi! > Not really sure if this is right place to ask, but.. > > I am trying to use Veeam Backup for Red Hat Virtualization on oVirt 4.5.1. > I have been using it on version 4.4.10.7 and it works ok there. > > On Veeam Release page it says that supported OS is RHV 4.4SP1 (oVirt 4.5). > > When i try to do backup, this is what i get from Veeam backup. > No errors in vdsm.log and engine.log.. > > 2022-07-27 08:08:44.153 00039 [19545] INFO | [LoggingEventsManager_39]: > Add to storage LoggingEvent [id: 34248685-a193-4df5-8ff2-838f738e211c, Type: > BackupStartedNew] > 2022-07-27 08:08:44.168 00039 [19545] INFO | [TaskManager_39]: Create and > run new async task. [call method:'RunBackupChain'] > 2022-07-27 08:08:44.168 00039 [19545] INFO | [AsyncTask_39]: New AsynTask > created [id:'aafa22ac-ff2e-4647-becb-dca88e3eb67f', description:'', > type:'BACKUP_VM_POLICY'] > 2022-07-27 08:08:44.168 00039 [19545] INFO | [AsyncTask_39]: Prepare > AsynTask to run [id:'aafa22ac-ff2e-4647-becb-dca88e3eb67f'] > 2022-07-27 08:08:44.176 00031 [19545] INFO | [BackupPolicy_31]: Refresh > VMs for policy '6e090c98-d44b-4785-acb4-82a627da5d9b' > 2022-07-27 08:08:44.176 00031 [19545] INFO | [BackupPolicy_31]: Begin > updating list of active VMs for policy '6e090c98-d44b-4785-acb4-82a627da5d9b' > [forceRefresh = True] > 2022-07-27 08:08:44.176 00031 [19545] INFO | [RhevCluster_31]: Test > connection to cluster [IP: engine.example.org, Port: 443, User: > admin@ovirt@internalsso] > 2022-07-27 08:08:44.189 00039 [19545] INFO | [TaskManager_39]: AsyncTask > registered. [id:'aafa22ac-ff2e-4647-becb-dca88e3eb67f'] > 2022-07-27 08:08:44.371 00031 [19545] INFO | [RhevCluster_31]: Test > connection to cluster success. Status: Success. Message: > 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicyManager_31]: > Refreshing the policies data... > 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicy_31]: Begin > updating list of active VMs for policy '6e090c98-d44b-4785-acb4-82a627da5d9b' > [forceRefresh = False] > 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicy_31]: List of > active VMs updated for policy '6e090c98-d44b-4785-acb4-82a627da5d9b' > [forceRefresh = False]. Number of active VMs '1' > 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicyManager_31]: > Policies data has been refreshed. > 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicy_31]: List of > active VMs updated for policy '6e090c98-d44b-4785-acb4-82a627da5d9b' > [forceRefresh = True]. Number of active VMs '1' > 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicy_31]: Found the > '1' VMs to backup in policy '6e090c98-d44b-4785-acb4-82a627da5d9b' > 2022-07-27 08:08:44.564 00031 [19545] INFO | [BackupPolicy_31]: * > Parallel policy runner has started * for policy [Name:'test5', ID: > '6e090c98-d44b-4785-acb4-82a627da5d9b' > 2022-07-27 08:08:44.564 00031 [19545] INFO | [VeeamBackupServer_31]: Test > connection to backup server [IP: 'veeambr.example.org', Port: '10006', User: > 'rhvproxy'] > 2022-07-27 08:08:44.931 00031 [19545] INFO | [VeeamBackupServer_31]: Test > connection to backup server [IP: 'veeambr.example.org', Port: '10006']. > Connection status: ConnectionSuccess. Version: 11.0.1.1261 > 2022-07-27 08:08:45.423 00031 [19545] INFO | [BackupPolicy_31]: > Successfully called CreateVeeamPolicySession for job [UID: > '6e090c98-d44b-4785-acb4-82a627da5d9b'], session [UID: > 'aafa22ac-ff2e-4647-becb-dca88e3eb67f'] > 2022-07-27 08:08:45.820 00031 [19545] INFO | [BackupPolicy_31]: > Successfully called RetainPolicyVms for job [UID: > '6e090c98-d44b-4785-acb4-82a627da5d9b'] with VMs: > 50513a65-6ccc-479b-9b61-032e0961b016 > 2022-07-27 08:08:45.820 00031 [19545] INFO | [BackupPolicy_31]: Start > calculating maxPointsCount > 2022-07-27 08:08:45.820 00031 [19545] INFO | [BackupPolicy_31]: End > calculating maxPointsCount. Result = 7 > 2022-07-27 08:08:45.820 00031 [19545] INFO | [BackupPolicy_31]: Starting > validate repository schedule. Repository [UID: > '237e41d6-7c67-4a1f-80bf-d7c73c481209', MaxPointsCount: '7', > IsPeriodicFullRequired: 'False'] > 2022-07-27 08:08:46.595 00031 [19545] INFO | [BackupPolicy_31]: End > validate repository schedule. Result: [IsScheduleValid: 'True', ErrorMessage: > ''] > 2022-07-27 08:08:46.597 00031 [19545] INFO | [SessionManager_31]: Start > registering a new session[Id: 'b6f3f0e1-7aab-41cb-b0e7-10f5b2ed6708'] > 2022-07-27 08:08:46.639 00031 [19545] INFO | [SessionManager_31]: Session > registered. [Id:'b6f3f0e1-7aab-41cb-b0e7-10f5b2ed6708'] > 2022-07-27 08:08:46.639 00031 [19545] INFO | [BackupPolicy_31]: Backup VM > [id:'50513a65-6ccc-479b-9b61-032e0961b016'] starting... > 2022-07-27 08:08:46.639 00031 [19545] INFO | [BackupPolicy_31]: > RetentionMergeDisabled: false > 2022-07-27 08:08:46.640 00031 [19545] IN
[ovirt-users] Veeam Backup for RHV (oVirt)
Hi! Not really sure if this is right place to ask, but.. I am trying to use Veeam Backup for Red Hat Virtualization on oVirt 4.5.1. I have been using it on version 4.4.10.7 and it works ok there. On Veeam Release page it says that supported OS is RHV 4.4SP1 (oVirt 4.5). When i try to do backup, this is what i get from Veeam backup. No errors in vdsm.log and engine.log.. 2022-07-27 08:08:44.153 00039 [19545] INFO | [LoggingEventsManager_39]: Add to storage LoggingEvent [id: 34248685-a193-4df5-8ff2-838f738e211c, Type: BackupStartedNew] 2022-07-27 08:08:44.168 00039 [19545] INFO | [TaskManager_39]: Create and run new async task. [call method:'RunBackupChain'] 2022-07-27 08:08:44.168 00039 [19545] INFO | [AsyncTask_39]: New AsynTask created [id:'aafa22ac-ff2e-4647-becb-dca88e3eb67f', description:'', type:'BACKUP_VM_POLICY'] 2022-07-27 08:08:44.168 00039 [19545] INFO | [AsyncTask_39]: Prepare AsynTask to run [id:'aafa22ac-ff2e-4647-becb-dca88e3eb67f'] 2022-07-27 08:08:44.176 00031 [19545] INFO | [BackupPolicy_31]: Refresh VMs for policy '6e090c98-d44b-4785-acb4-82a627da5d9b' 2022-07-27 08:08:44.176 00031 [19545] INFO | [BackupPolicy_31]: Begin updating list of active VMs for policy '6e090c98-d44b-4785-acb4-82a627da5d9b' [forceRefresh = True] 2022-07-27 08:08:44.176 00031 [19545] INFO | [RhevCluster_31]: Test connection to cluster [IP: engine.example.org, Port: 443, User: admin@ovirt@internalsso] 2022-07-27 08:08:44.189 00039 [19545] INFO | [TaskManager_39]: AsyncTask registered. [id:'aafa22ac-ff2e-4647-becb-dca88e3eb67f'] 2022-07-27 08:08:44.371 00031 [19545] INFO | [RhevCluster_31]: Test connection to cluster success. Status: Success. Message: 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicyManager_31]: Refreshing the policies data... 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicy_31]: Begin updating list of active VMs for policy '6e090c98-d44b-4785-acb4-82a627da5d9b' [forceRefresh = False] 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicy_31]: List of active VMs updated for policy '6e090c98-d44b-4785-acb4-82a627da5d9b' [forceRefresh = False]. Number of active VMs '1' 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicyManager_31]: Policies data has been refreshed. 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicy_31]: List of active VMs updated for policy '6e090c98-d44b-4785-acb4-82a627da5d9b' [forceRefresh = True]. Number of active VMs '1' 2022-07-27 08:08:44.556 00031 [19545] INFO | [BackupPolicy_31]: Found the '1' VMs to backup in policy '6e090c98-d44b-4785-acb4-82a627da5d9b' 2022-07-27 08:08:44.564 00031 [19545] INFO | [BackupPolicy_31]: * Parallel policy runner has started * for policy [Name:'test5', ID: '6e090c98-d44b-4785-acb4-82a627da5d9b' 2022-07-27 08:08:44.564 00031 [19545] INFO | [VeeamBackupServer_31]: Test connection to backup server [IP: 'veeambr.example.org', Port: '10006', User: 'rhvproxy'] 2022-07-27 08:08:44.931 00031 [19545] INFO | [VeeamBackupServer_31]: Test connection to backup server [IP: 'veeambr.example.org', Port: '10006']. Connection status: ConnectionSuccess. Version: 11.0.1.1261 2022-07-27 08:08:45.423 00031 [19545] INFO | [BackupPolicy_31]: Successfully called CreateVeeamPolicySession for job [UID: '6e090c98-d44b-4785-acb4-82a627da5d9b'], session [UID: 'aafa22ac-ff2e-4647-becb-dca88e3eb67f'] 2022-07-27 08:08:45.820 00031 [19545] INFO | [BackupPolicy_31]: Successfully called RetainPolicyVms for job [UID: '6e090c98-d44b-4785-acb4-82a627da5d9b'] with VMs: 50513a65-6ccc-479b-9b61-032e0961b016 2022-07-27 08:08:45.820 00031 [19545] INFO | [BackupPolicy_31]: Start calculating maxPointsCount 2022-07-27 08:08:45.820 00031 [19545] INFO | [BackupPolicy_31]: End calculating maxPointsCount. Result = 7 2022-07-27 08:08:45.820 00031 [19545] INFO | [BackupPolicy_31]: Starting validate repository schedule. Repository [UID: '237e41d6-7c67-4a1f-80bf-d7c73c481209', MaxPointsCount: '7', IsPeriodicFullRequired: 'False'] 2022-07-27 08:08:46.595 00031 [19545] INFO | [BackupPolicy_31]: End validate repository schedule. Result: [IsScheduleValid: 'True', ErrorMessage: ''] 2022-07-27 08:08:46.597 00031 [19545] INFO | [SessionManager_31]: Start registering a new session[Id: 'b6f3f0e1-7aab-41cb-b0e7-10f5b2ed6708'] 2022-07-27 08:08:46.639 00031 [19545] INFO | [SessionManager_31]: Session registered. [Id:'b6f3f0e1-7aab-41cb-b0e7-10f5b2ed6708'] 2022-07-27 08:08:46.639 00031 [19545] INFO | [BackupPolicy_31]: Backup VM [id:'50513a65-6ccc-479b-9b61-032e0961b016'] starting... 2022-07-27 08:08:46.639 00031 [19545] INFO | [BackupPolicy_31]: RetentionMergeDisabled: false 2022-07-27 08:08:46.640 00031 [19545] INFO | [TaskManager_31]: Create new async task. [call method:'DoBackup'] 2022-07-27 08:08:46.640 00031 [19545] INFO | [AsyncTask_31]: New AsynTask created [id:'15a63192
[ovirt-users] Re: Moving raw/sparse disk from NFS to iSCSI fails on oVirt 4.5.1
Did anyone have the chance to look at this problem?
It seems that it may be related to another problem we have encountered when
trying to import a vm with qcow2 disks that have been sparsified first
(virt-sparsify), from a kvm/libvirt provider to a iSCSI storage domain.
In those case, we get an error that the import failed, and in the import
log we can see a similar "qemu-img: error while writing at byte xxx: No
space left on device"
Obviously, it is not a storage space problem as in both situations we are
using an iSCSI LUN with ample free space.
Best regards,
Guillaume Pavese
Ingénieur Système et Réseau
Interactiv-Group
On Thu, Jul 21, 2022 at 11:49 PM Guillaume Pavese <
guillaume.pav...@interactiv-group.com> wrote:
> On a 4.5.1 DC, I have imported a vm and its disk from an old 4.3 DC
> (through an export domain if that's relevant)
>
> The DC/Cluster compat level is 4.7 and the vm was upgraded to it.
>
> "Original custom compatibility version 4.3 of imported VM xxx is not
> supported. Changing it to the lowest supported version: 4.7."
>
>
> The disk is raw and sparse :
>
> raw
> true
>
>
> I initially put the VM's disks on an NFS storage domain, but I want to
> move the disks to an iSCSI one
> However, after copying data for a while the task fails "User has failed
> to move disk VM-TEMPLATE-COS7_Disk1 to domain iSCSI-STO-FR-301"
>
> in engine.log :
>
> qemu-img: error while writing at byte xxx: No space left on device
>
>
> 2022-07-21 08:58:23,240+02 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHostJobsVDSCommand]
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-48)
> [65fed1dc-e33b-471e-bc49-8b9662400e5f] FINISH, GetHostJobsVDSCommand,
> return:
> {0aa2d519-8130-4e2f-bc4f-892e5f7b5206=HostJobInfo:{id='0aa2d519-8130-4e2f-bc4f-892e5f7b5206',
> type='storage', description='copy_data', status='failed', progress='79',
> error='VDSError:{code='GeneralException', message='General Exception:
> ("Command ['/usr/bin/qemu-img', 'convert', '-p', '-t', 'none', '-T',
> 'none', '-f', 'raw', '-O', 'qcow2', '-o', 'compat=1.1',
> '/rhev/data-center/mnt/svc-int-prd-sto-fr-301.hostics.fr:_volume1_ovirt-int-2_data/1ce95c4a-2ec5-47b7-bd24-e540165c6718/images/d3c33cc7-f2c3-4613-84d0-d3c9fa3d5ebd/2c4a0041-b18b-408f-9c0d-971c19a552ea',
> '/rhev/data-center/mnt/blockSD/b5dc9c01-3749-4326-99c5-f84f683190bd/images/d3c33cc7-f2c3-4613-84d0-d3c9fa3d5ebd/2c4a0041-b18b-408f-9c0d-971c19a552ea']
> failed with rc=1 out=b'' err=bytearray(b'qemu-img: error while writing at
> byte 13639873536: No space left on device\\n')",)'}'}}, log id: 73f77495
>
> 2022-07-21 08:58:23,241+02 INFO
> [org.ovirt.engine.core.bll.StorageJobCallback]
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-48)
> [65fed1dc-e33b-471e-bc49-8b9662400e5f] Command CopyData id:
> '521bdf57-8379-40ce-a682-af859fb0cad7': job
> '0aa2d519-8130-4e2f-bc4f-892e5f7b5206' execution was completed with VDSM
> job status 'failed'
>
>
>
>
> I do want the conversion from raw/sparse to qcow2/sparse to happen, as I
> want to activate incremental backups.
>
> I think that it may fail because the virtual size is bigger than the
> initial size, as I think someone as explained on this list earlier? Can
> anybody confirm?
> It seems to be a pretty common use case to support though?
>
> Guillaume Pavese
> Ingénieur Système et Réseau
> Interactiv-Group
>
--
Ce message et toutes les pièces jointes (ci-après le “message”) sont
établis à l’intention exclusive de ses destinataires et sont confidentiels.
Si vous recevez ce message par erreur, merci de le détruire et d’en avertir
immédiatement l’expéditeur. Toute utilisation de ce message non conforme a
sa destination, toute diffusion ou toute publication, totale ou partielle,
est interdite, sauf autorisation expresse. L’internet ne permettant pas
d’assurer l’intégrité de ce message . Interactiv-group (et ses filiales)
décline(nt) toute responsabilité au titre de ce message, dans l’hypothèse
ou il aurait été modifié. IT, ES, UK.
___
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/JBJYWWTAMJBZJ7A6FTJE2BROUPRGEG3D/
