Skip to Main Content

Infrastructure Software

Announcement

Testing banner

olvm disaster recovery fail with direct lun machine

User_G5E5UJan 24 2023

Good night

I am configuring the disaster recovery with the following environment

Ovirt 4.4.10

Site A

An external manager
A hypervisor server

Site B

An external manager
A hypervisor server

*Mons are being replicated from one storage to another with the conditions mentioned in
the active passive guide.

In the File

disaster_recovery_vars.yml

**** The mapping of the virtual machines is carried out, one of these has direct luns

When I execute the failover the virtual machines are not importing in the secondary site.

If I comment on the mapping of the direct luns, it is possible to import the virtual
machines and they remain working correctly.

NOTE: The direct lun that the vm has is without format or partition, since I am in the
testing phase.

I think I know what the problem is

In the A or main site there is the mapping to the virtual machine that has the direct luns
like this

- logical_unit_alias: dbproduction_db_Disk1
logical_unit_description: 017c
wipe_after_delete: False
shareable: False
primary_logical_unit_id: 360050768128100d4d00000000000017c
primary_storage_type: fcp
# Fill in the following properties of the external LUN disk in the secondary site
secondary_storage_type: fcp
secondary_logical_unit_id: 360050763808106251000000000000030

the fail over is initiated with the command

ansible-playbook -vvvv dr-olvm-failover.yml --tags "fail_over"

As I mentioned before, it is not possible for me to import the virtual machines

when I try to import the virtual machine through the web manually

reviewing the engine.log I find that it is mapped and trying to load the direct lun of the
main site, as if it were not loading the values of the luns of the secondary site.

This is the log that generates me where it is seen that the Lun id in the secondary site

2023-01-23 14:47:32,118-05 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetDeviceListVDSCommand] (default task-97) []
START, GetDeviceListVDSCommand(HostName = ovmextix01.admin.usc,
GetDeviceListVDSCommandParameters: {hostId='24b29292-ebe3-4203-9e21-e9eeab4819e1',
storageType='FCP', checkStatus='false',
lunIds='[360050768128100d4d00000000000017c]'}), log id: 687ddeff
2023-01-23 14:47:34,317-05 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.GetDeviceListVDSCommand] (default task-97) []
FINISH, GetDeviceListVDSCommand, return: [], log id: 687ddeff
2023-01-23 14:47:34,317-05 WARN
[org.ovirt.engine.core.bll.exportimport.ImportVmFromConfigurationCommand] (default
task-97) [] Validation of action 'ImportVmFromConfiguration' failed for user
admin@internal-authz . Reasons:
VAR__ACTION__IMPORT,VAR__TYPE__VM,ACTION_TYPE_FAILED_DISK_LUN_INVALID

Can you please guide me as I should correct or change the LUN in the secondary site.

Comments
Post Details
Added on Jan 24 2023
0 comments
19 views