Add a "Try Again" button to prevent synchronization issue between the Discover and Verify stages when dealing with large partition volumes

See Case TS021897288.

When you go in the GUI Menu to do a Failover Rehearsal, the GUI runs 3 commands which are 'ksysmgr discover', then 'ksysmgr verify' and then 'ksysmgr move' (where the 'move' actually performs the WG failover). The problem is that the 'ksysmgr discover' ends while the discover is in reality still running in the background. But since the 'ksysmgr discover' commands ends with return code 0 (success), the GUI moves on to the next step ('ksysmgr verify'). But 'ksysmgr verify' fails because it realizes that the previous 'discover' in reality is not finished yet. This is why you need to press the GUI button 'Try again', and when you press 'Try again' while 'discover' has finally really finished then the GUI can move on successfully to the next steps 'verify'.

The feedback of the VMRM Developers is that fixing this problem is very complicated.

A complete solution of this problem will be possible only in some future VMRM release.

However the Developers are willing to explore the possibility to provide some sort of 'relief', which however may only solve the problem in certain cases and not in all scenarios.

The time between 'ksysmgr discover' ending, and the time when the 'discover' still runs in the background can vary a lot. There're different factors which determine how long this 'time' can be, for ex some are:

are we doing rehearsal for a WG or a HG

how many VMs the WG includes

how many disks the VMs have

the response time received back from SAN / Storage

how long SAN / Storage need to complete certain tasks

etc.

To provide some sort of 'relief', based on the logs we've got, we can guess how much extra 'time' the GUI has to wait. But this will be only a best effort guess / assumption, it could resolve for some WGs/VMs sometime but not in all cases (so you would have to still manually press 'Try again').