ASF GitHub Bot updated AMBARI-22076:
    Labels: pull-request-available  (was: )

> Use A Scoped Repo When Installing stack-tools
> ---------------------------------------------
>                 Key: AMBARI-22076
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22076
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 2.6.0
>         Attachments: AMBARI-22076.patch
> Ambari does not write out repositories with a "priority" attribute since this 
> is a plugin and is not guaranteed to be installed. Also, when installing 
> packages with versions "in the middle" of two other installed stacks, 
> priority would be incorrect as the most recent stack-tools should always be 
> used.
> The following is seen when trying to distribute a stack for a patch upgrade:
> {code}
> 2017-09-26 16:28:58,652 - Package Manager failed to install packages. Error: 
> Execution of '/usr/bin/yum -d 0 -e 0 -y install hive_2_6_3_1_1' returned 1. 
> Error: Package: hadoop_2_6_3_1_1- (HDP-2.6-repo-2)
>            Requires: hdp-select >=
>            Installed: hdp-select- (@HDP-
>                hdp-select =
> {code}
> The cause of this seems to be that the repository for HDP-2.6-repo-2 does not 
> take priority over the existing installed repository for {{hdp-select}}. 
> That's actually good - it shouldn't take priority over it arbitrarily. 
> However, this means that the {{hdp-select}} which is installed did not get 
> taken from {{HDP-2.6-repo-2}}. So, when installing {{hdp-select}}, we should 
> scope the install to the repo we are trying to calculate the version for.
> This works because the stack-select tools do not have their package names 
> versioned ({{hdp-select}} as opposed to {{hdp-select_x_y_z}}.

This message was sent by Atlassian JIRA

Reply via email to