[HDDS-10937] Ozone Recon - Handle startup failure and log reasons as error due to SCM non-HA scenario

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.0
• Component/s: Ozone Recon
• Labels: pull-request-available
• Assignee: Devesh Kumar Singh
• Reporter: Devesh Kumar Singh
• Created: 29/May/24 08:16
• Updated: 04/Jun/24 08:30
• Resolved: 04/Jun/24 08:30

Description

Ozone Recon - Handle startup failure and log reasons as error due to SCM non-HA scenario

1. While Recon.start() method is called, if any runtime errors being thrown, those are not being logged and Recon startup fails silently without logging any reason of failure. E.g. In case of non-HA SCM case, few configurations made Recon fails to start. This scenario or any runtime exception  needs to be handled for proper logging.
2. In non-HA SCM case, while trying to fetch SCM DB snapshot, SCM peer roles are not being returned correctly, so the logic needs to handle.

Issue Links

• links to: GitHub Pull Request #6752