[AMBARI-23246] Pass Mpack ID In Agent Commands For Installation Updates

• Type: Task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.0.0
• Fix Version/s: 3.0.0
• Labels: pull-request-available
• Epic Link: Management Packs: Repository Version Refactor
• Assignee: Jonathan Hurley
• Reporter: Jonathan Hurley
• Created: 15/Mar/18 15:13
• Updated: 12/Apr/18 01:19
• Resolved: 12/Apr/18 01:19

Description

When an mpack is initially registered in Ambari, we will create NOT_INSTALLED records for it on every host. During a normal installation, the resource provider will set the correct rows to a value of INSTALLING.

However, on a blueprint deployment or initial cluster deployment, this doesn't happen. As a result, the value stays at NOT_INSTALLED until the installation commands come back.

If for some reason the installation command fails (aborts, times out, etc), then there will be no structured output indicating the mpack which was attempted. Therefore, we cannot find the right values to lookup.

This Jira will allow the mpack ID to be set on the command so that it doesn't need to be specifically reported by an agent.

Issue Links

• links to: GitHub Pull Request #963