EOS-28599: Update version for each component in bootstrap phase

[tanujashinde0405]

Signed-off-by: Tanuja Shinde tanuja.shinde@seagate.com

Problem Statement

• In the config apply stage of the provisioner , we add a version field for all components by searching all component rpms in the RELEASE.INFO file. so even if it's a data pod or any other pod, we search all components to add versions in it and not only data pod components. so for granular images, if other component RPMs are missing, the provisioner throws an error saying "rpm for csm not found".

Design

• Fix For above solution would be:
  1. Remove add version for component from config apply state.
  2. add version only after mini provisioning for the component is successful. This way only for that particular component utils will return version.

Coding

Checklist for Author

• [x] Coding conventions are followed and code is consistent

Testing

Checklist for Author

• [x] Unit and System Tests are added
• [x] Test Cases cover Happy Path, Non-Happy Path and Scalability
• [x] Testing was performed with RPM

Impact Analysis

Checklist for Author/Reviewer/GateKeeper

• [ ] Interface change (if any) are documented
• [x] Side effects on other features (deployment/upgrade)
• [ ] Dependencies on other component(s)

Review Checklist

Checklist for Author

• [x] JIRA number/GitHub Issue added to PR
• [x] PR is self reviewed
• [x] Jira and state/status is updated and JIRA is updated with PR link
• [x] Check if the description is clear and explained

Documentation

Checklist for Author

• [ ] Changes done to WIKI / Confluence page / Quick Start Guide

[cortx-admin]

Can one of the admins verify this patch?