[AMBARI-24416] Component Versions Are Not Reported On Initial Status Commands Anymore

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.7.1
• Labels: pull-request-available
• Assignee: Andrew Onischuk
• Reporter: Andrew Onischuk
• Created: 07/Aug/18 19:27
• Updated: 20/Aug/18 20:27
• Resolved: 20/Aug/18 20:27

Description

In Ambari 2.6, some status commands were able to supply the version of the
component they were running for. This was needed especially during upgrades to
correct situations where components would fail to start but the processes were
actually running and reporting.

• During heartbeat registration, Ambari asked the agent to get the version in the next status command:
  <https://github.com/apache/ambari/blob/branch-2.6/ambari-
  server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java#L416-L419>

• The status command would place the version information from the structured out into the "extra" mapping, which would then be handled here via an event:
  <https://github.com/apache/ambari/blob/trunk/ambari-
  server/src/main/java/org/apache/ambari/server/agent/HeartbeatProcessor.java#L599-L603>

We need to replace this functionality so that component versions are reported
on registration of agents.

Issue Links

• links to: GitHub Pull Request #1987
• links to: GitHub Pull Request #1988