[ https://issues.apache.org/jira/browse/AMBARI-23246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hurley resolved AMBARI-23246. -------------------------------------- Resolution: Fixed > Pass Mpack ID In Agent Commands For Installation Updates > -------------------------------------------------------- > > Key: AMBARI-23246 > URL: https://issues.apache.org/jira/browse/AMBARI-23246 > Project: Ambari > Issue Type: Task > Affects Versions: 3.0.0 > Reporter: Jonathan Hurley > Assignee: Jonathan Hurley > Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 4h 20m > Remaining Estimate: 0h > > 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. -- This message was sent by Atlassian JIRA (v7.6.3#76005)