[
https://issues.apache.org/jira/browse/AMBARI-22318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16256775#comment-16256775
]
Hudson commented on AMBARI-22318:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8407 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8407/])
AMBARI-22318 repositoryFile entity populating for wrong repository for
(hapylestat:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1d1c55644d77ea0e63683001cdb7303c4d379d8b])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariActionExecutionHelper.java
> repositoryFile entity populating for wrong repository for RU
> --------------------------------------------------------------
>
> Key: AMBARI-22318
> URL: https://issues.apache.org/jira/browse/AMBARI-22318
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.6.1
> Reporter: Dmytro Grinenko
> Assignee: Dmytro Grinenko
> Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22318-trunk-unused-imports.patch,
> AMBARI-22318-trunk.patch, AMBARI-22318.patch, AMBARI-22318.v1.patch,
> AMBARI-22318.v2.preview.patch
>
>
> In populating repositoryFile entity we relating to desired stack version,
> what i correct for RU, as desired state switched there exactly at upgrade
> creation time, while for RU we doing it later.
> Due to entity populating far ahead of real upgrade, for RU it populated for
> source repository version instead of target.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
