During Full VM recovery, new disk creation or attachment to the created VM failed.
1. Incompatibility with the target disk configuration selected from the BDR UI for new disk creation/attachment.2. Insufficient space or permissions in the chosen storage domain for the new disk creation.3. Special characters in the disk name.4. Connection to oVirt engine failure.5. Authentication failure of oVirt Engine console credentials.
1. Verify Disk Configuration Parameters:
- Ensure that the correct parameters are chosen for new disk creation, including Allocation Policy, Interface, Storage Domain, and Disk Profile.
2. Check Storage Domain:
- Confirm that the appropriate storage domain is selected and has sufficient space and proper permissions.
- Ensure the connectivity of the respective storage domain.
3. Avoid Special Characters in Disk Name:
- Do not use special characters when adding the new disk name.
4. Check oVirt Engine Status:
- Ensure that the oVirt Engine status is good and that the engine is up.
- Use the following command to check the engine status on the oVirt Engine (self-hosted) machine:
hosted-engine --vm-statusExample output:Host host1.india.domain.com (id: 1) statusHost ID : 1Host timestamp : 241871Score : 3400Engine status : {"vm": "up", "health": "good", "detail": "Up"}Hostname : example.india.domain.comLocal maintenance : Falsestopped : Falsecrc32 : 099bd52fconf_on_shared_storage : Truelocal_conf_timestamp : 241874Status up-to-date : TrueExtra metadata (valid at timestamp):metadata_parse_version=1metadata_feature_version=1timestamp=241871 (Mon Jan 15 11:12:26 2024)host-id=1score=3400vm_conf_refresh_time=241874 (Mon Jan 15 11:12:28 2024)conf_on_shared_storage=Truemaintenance=Falsestate=EngineUpstopped=False5. Verify oVirt Engine Console Credentials:
- Ensure the provided oVirt Engine console credentials are correct and valid.