Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Fri, 27 May 2016 15:54:12 +0000 (UTC)
From: "Nate Cole (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12973443.1464364397000.317323.1464364452944@Atlassian.JIRA>
In-Reply-To: <JIRA.12973443.1464364397000@Atlassian.JIRA>
References: <JIRA.12973443.1464364397000@Atlassian.JIRA> <JIRA.12973443.1464364397583@arcas>
Subject: [jira] [Created] (AMBARI-16933) VDF should use package-version for
 the os, not the release
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 27 May 2016 15:54:14 -0000

Nate Cole created AMBARI-16933:
----------------------------------

             Summary: VDF should use package-version for the os, not the release
                 Key: AMBARI-16933
                 URL: https://issues.apache.org/jira/browse/AMBARI-16933
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
            Reporter: Nate Cole
            Assignee: Nate Cole
             Fix For: 2.4.0


The aggregated VDF skips package-version as it is defined in the {{release}} element.  This is incorrect as it implies that information is consistent for all repositories in the VDF.  The element has been moved, so code needs to account for that when formulating commands to the agent.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)