[HDDS-8892] OM Node Id from VERSION file should removed after the OM node has been decommissioned

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Component/s: Ozone Manager
• Labels: pull-request-available
• Assignee: Aryan Gupta
• Reporter: Aryan Gupta
• Created: 20/Jun/23 19:49
• Updated: 21/Jun/23 12:40
• Resolved: 21/Jun/23 12:40

Description

OM node id should be removed from the VERSION file after the OM node has been decommissioned to avoid OM node Id mismatch in case an ex-OM node is bootstrapped again. This can happen when an ex-OM node is bootstrapped, then it will be bootstrapped with a new OM node id and the existing VERSION file will contain the old OM node id which will cause an OM node id mismatch during the bootstrap, therefore we need to remove the OM node id from the VERSION file upon successful decommissioning. Also, when an OM is bootstrapped if the VERSION file doesn’t exist then it will be created and if it exists then a new entry of OM node id will be appended. 

Issue Links

• links to: GitHub Pull Request #4945