[ 
https://issues.apache.org/jira/browse/AMBARI-22051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16179407#comment-16179407
 ] 

Hudson commented on AMBARI-22051:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8136 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8136/])
AMBARI-22051 -  VDFs Which Are Correct Never Get Resolved (jhurley: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=08da9611188d9c4c246ee6d77894da5edf317860])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/events/listeners/upgrade/StackVersionListener.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/events/listeners/upgrade/DistributeRepositoriesActionListener.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/events/listeners/upgrade/StackVersionListenerTest.java


> VDFs Which Are Correct Never Get Resolved
> -----------------------------------------
>
>                 Key: AMBARI-22051
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22051
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.6.0
>
>         Attachments: AMBARI-22051.patch
>
>
> VDFs which include the version and build number as the build number are never 
> marked as resolved. This causes the repository to never be trusted and can 
> leave errant symlinks when a cluster is patch upgraded.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to