[jira] [Commented] (AMBARI-22076) Use A Scoped Repo When Installing stack-tools

2018-02-13 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-22076:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8721 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8721/])
AMBARI-22076. Unable to create new user after fresh install of Ambari (hiveww: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=6686d11b114f32e999df25deda5a890b1f0bd1c5])
* (edit) 
ambari-admin/src/main/resources/ui/admin-web/app/views/userManagement/modals/userCreate.html


> 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
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> 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-2.7.3.2.6.3.1-1.x86_64 (HDP-2.6-repo-2)
>Requires: hdp-select >= 2.6.3.1-1
>Installed: hdp-select-2.6.3.0-122.noarch (@HDP-2.6.3.0-122)
>hdp-select = 2.6.3.0-122
> {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
(v7.6.3#76005)


[jira] [Commented] (AMBARI-22076) Use A Scoped Repo When Installing stack-tools

2017-09-29 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-22076:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8174 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8174/])
AMBARI-22076 - Use A Scoped Repo When Installing stack-tools (unit test 
(jhurley: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d19f0bb7661404ccc72099621e9c2d7c97609d2a])
* (edit) ambari-agent/src/test/python/resource_management/TestPackageResource.py


> 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
> 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-2.7.3.2.6.3.1-1.x86_64 (HDP-2.6-repo-2)
>Requires: hdp-select >= 2.6.3.1-1
>Installed: hdp-select-2.6.3.0-122.noarch (@HDP-2.6.3.0-122)
>hdp-select = 2.6.3.0-122
> {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
(v6.4.14#64029)


[jira] [Commented] (AMBARI-22076) Use A Scoped Repo When Installing stack-tools

2017-09-29 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-22076:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #310 (See 
[https://builds.apache.org/job/Ambari-branch-2.6/310/])
AMBARI-22076 - Use A Scoped Repo When Installing stack-tools (unit test 
(jhurley: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=eb89ef0482c55a8de9b67b86bc16074ff4a1e505])
* (edit) ambari-agent/src/test/python/resource_management/TestPackageResource.py


> 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
> 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-2.7.3.2.6.3.1-1.x86_64 (HDP-2.6-repo-2)
>Requires: hdp-select >= 2.6.3.1-1
>Installed: hdp-select-2.6.3.0-122.noarch (@HDP-2.6.3.0-122)
>hdp-select = 2.6.3.0-122
> {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
(v6.4.14#64029)


[jira] [Commented] (AMBARI-22076) Use A Scoped Repo When Installing stack-tools

2017-09-27 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-22076:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8156 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8156/])
AMBARI-22076 - Use A Scoped Repo When Installing stack-tools (jhurley: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4da28da7b2fe362d52de34ec3f0ec47bfb30])
* (edit) ambari-server/src/test/python/custom_actions/TestInstallPackages.py
* (edit) 
ambari-server/src/main/resources/custom_actions/scripts/install_packages.py
* (edit) 
ambari-common/src/main/python/resource_management/core/providers/package/yumrpm.py


> 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
> 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-2.7.3.2.6.3.1-1.x86_64 (HDP-2.6-repo-2)
>Requires: hdp-select >= 2.6.3.1-1
>Installed: hdp-select-2.6.3.0-122.noarch (@HDP-2.6.3.0-122)
>hdp-select = 2.6.3.0-122
> {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
(v6.4.14#64029)


[jira] [Commented] (AMBARI-22076) Use A Scoped Repo When Installing stack-tools

2017-09-27 Thread Hudson (JIRA)

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

Hudson commented on AMBARI-22076:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #295 (See 
[https://builds.apache.org/job/Ambari-branch-2.6/295/])
AMBARI-22076 - Use A Scoped Repo When Installing stack-tools (jhurley: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=17212283aad1c2ce1cd3d85ad3742ffe883349f6])
* (edit) 
ambari-common/src/main/python/resource_management/core/providers/package/yumrpm.py
* (edit) 
ambari-server/src/main/resources/custom_actions/scripts/install_packages.py
* (edit) ambari-server/src/test/python/custom_actions/TestInstallPackages.py


> 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
> 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-2.7.3.2.6.3.1-1.x86_64 (HDP-2.6-repo-2)
>Requires: hdp-select >= 2.6.3.1-1
>Installed: hdp-select-2.6.3.0-122.noarch (@HDP-2.6.3.0-122)
>hdp-select = 2.6.3.0-122
> {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
(v6.4.14#64029)