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

Hudson commented on AMBARI-13335:
---------------------------------

FAILURE: Integrated in Ambari-branch-2.1 #723 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/723/])
AMBARI-13335. Install package command during RU should honor excluded 
(dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a0a005b2a88ed356a49671204c670097a74b3107])
* ambari-server/conf/unix/ambari.properties
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostStackVersionResourceProvider.java
* 
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProvider.java


> Install package command during RU should honor excluded packages
> ----------------------------------------------------------------
>
>                 Key: AMBARI-13335
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13335
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.2
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13335.patch
>
>
> It seems that install package custom action is not taking into account the 
> logic in the stack to exclude packages. Therefore, it is installing 
> hadooplzo, phoenix, even if they should be installed. This causes issue for 
> folks using local repo which may not include these packages.
> We need a design where package exclusion logic lives in a single location - 
> perhaps stack definition itself - that is shared by Upgrade code as well as 
> regular stack install code.
> Meanwhile, we may need a hot-fix to avoid installing hadooplzo during RU. 
> This can be a bit hacky as its needed on 2.1.2.



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

Reply via email to