[jira] [Updated] (AMBARI-21836) 2.6.0 Upgrade Fails Because Of Missing Table
[ https://issues.apache.org/jira/browse/AMBARI-21836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21836: -- Fix Version/s: 2.6.0 trunk > 2.6.0 Upgrade Fails Because Of Missing Table > > > Key: AMBARI-21836 > URL: https://issues.apache.org/jira/browse/AMBARI-21836 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21836.patch > > > STR: > Install Ambari 2.5 > Upgrade to Ambari 2.6 > The following code is throwing a table not found exception: > String supersetConfigMappingRemoveSQL = String.format( > "DELETE FROM %s WHERE type_name like '%s%%'", > CLUSTER_CONFIG_MAPPING_TABLE, configPrefix); > This was introduced in AMBARI-21076. The problem is that the > clusterconfigmapping table no longer exists... > Options -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21836) 2.6.0 Upgrade Fails Because Of Missing Table
[ https://issues.apache.org/jira/browse/AMBARI-21836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21836: -- Status: Patch Available (was: Open) > 2.6.0 Upgrade Fails Because Of Missing Table > > > Key: AMBARI-21836 > URL: https://issues.apache.org/jira/browse/AMBARI-21836 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Attachments: AMBARI-21836.patch > > > STR: > Install Ambari 2.5 > Upgrade to Ambari 2.6 > The following code is throwing a table not found exception: > String supersetConfigMappingRemoveSQL = String.format( > "DELETE FROM %s WHERE type_name like '%s%%'", > CLUSTER_CONFIG_MAPPING_TABLE, configPrefix); > This was introduced in AMBARI-21076. The problem is that the > clusterconfigmapping table no longer exists... > Options -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21836) 2.6.0 Upgrade Fails Because Of Missing Table
[ https://issues.apache.org/jira/browse/AMBARI-21836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishant Bangarwa updated AMBARI-21836: -- Attachment: AMBARI-21836.patch > 2.6.0 Upgrade Fails Because Of Missing Table > > > Key: AMBARI-21836 > URL: https://issues.apache.org/jira/browse/AMBARI-21836 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Attachments: AMBARI-21836.patch > > > STR: > Install Ambari 2.5 > Upgrade to Ambari 2.6 > The following code is throwing a table not found exception: > String supersetConfigMappingRemoveSQL = String.format( > "DELETE FROM %s WHERE type_name like '%s%%'", > CLUSTER_CONFIG_MAPPING_TABLE, configPrefix); > This was introduced in AMBARI-21076. The problem is that the > clusterconfigmapping table no longer exists... > Options -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21836) 2.6.0 Upgrade Fails Because Of Missing Table
Nishant Bangarwa created AMBARI-21836: - Summary: 2.6.0 Upgrade Fails Because Of Missing Table Key: AMBARI-21836 URL: https://issues.apache.org/jira/browse/AMBARI-21836 Project: Ambari Issue Type: Bug Reporter: Nishant Bangarwa Assignee: Nishant Bangarwa STR: Install Ambari 2.5 Upgrade to Ambari 2.6 The following code is throwing a table not found exception: String supersetConfigMappingRemoveSQL = String.format( "DELETE FROM %s WHERE type_name like '%s%%'", CLUSTER_CONFIG_MAPPING_TABLE, configPrefix); This was introduced in AMBARI-21076. The problem is that the clusterconfigmapping table no longer exists... Options -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21835) Support for Zeppelin notebook storage in HDFS
[ https://issues.apache.org/jira/browse/AMBARI-21835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-21835: - Status: Patch Available (was: Open) > Support for Zeppelin notebook storage in HDFS > - > > Key: AMBARI-21835 > URL: https://issues.apache.org/jira/browse/AMBARI-21835 > Project: Ambari > Issue Type: Bug >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-21835_trunk_v1.patch > > > With ZEPPELIN-1515 there is now support for storing Zeppelin's notebook in > HDFS, this patch is for making notebook to be stored by default in HDFS -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21835) Support for Zeppelin notebook storage in HDFS
[ https://issues.apache.org/jira/browse/AMBARI-21835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-21835: - Attachment: AMBARI-21835_trunk_v1.patch > Support for Zeppelin notebook storage in HDFS > - > > Key: AMBARI-21835 > URL: https://issues.apache.org/jira/browse/AMBARI-21835 > Project: Ambari > Issue Type: Bug >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Attachments: AMBARI-21835_trunk_v1.patch > > > With ZEPPELIN-1515 there is now support for storing Zeppelin's notebook in > HDFS, this patch is for making notebook to be stored by default in HDFS -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21835) Support for Zeppelin notebook storage in HDFS
[ https://issues.apache.org/jira/browse/AMBARI-21835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-21835: - Description: With ZEPPELIN-1515 there is now support for storing Zeppelin's notebook in HDFS, this patch is for making notebook to be stored by default in HDFS (was: Make Zeppelin notebook to be stored by default in HDFS (Ambari)) > Support for Zeppelin notebook storage in HDFS > - > > Key: AMBARI-21835 > URL: https://issues.apache.org/jira/browse/AMBARI-21835 > Project: Ambari > Issue Type: Bug >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > > With ZEPPELIN-1515 there is now support for storing Zeppelin's notebook in > HDFS, this patch is for making notebook to be stored by default in HDFS -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21835) Support for Zeppelin notebook storage in HDFS
Prabhjyot Singh created AMBARI-21835: Summary: Support for Zeppelin notebook storage in HDFS Key: AMBARI-21835 URL: https://issues.apache.org/jira/browse/AMBARI-21835 Project: Ambari Issue Type: Bug Reporter: Prabhjyot Singh Assignee: Prabhjyot Singh Make Zeppelin notebook to be stored by default in HDFS (Ambari) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21834) UI changes for Moving Masters
[ https://issues.apache.org/jira/browse/AMBARI-21834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-21834: - Status: Patch Available (was: Open) > UI changes for Moving Masters > - > > Key: AMBARI-21834 > URL: https://issues.apache.org/jira/browse/AMBARI-21834 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21834_branch-2.6.patch, AMBARI-21834.patch, > Screen Shot 2017-08-28 at 6.18.35 PM.png > > > Include all reassignable masters in the relatedServiceMap and restart All > services only when Namenode or SNamenode is being moved. Add to the first > step the list of services that would be restarted. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21834) UI changes for Moving Masters
[ https://issues.apache.org/jira/browse/AMBARI-21834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-21834: - Attachment: Screen Shot 2017-08-28 at 6.18.35 PM.png > UI changes for Moving Masters > - > > Key: AMBARI-21834 > URL: https://issues.apache.org/jira/browse/AMBARI-21834 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21834_branch-2.6.patch, AMBARI-21834.patch, > Screen Shot 2017-08-28 at 6.18.35 PM.png > > > Include all reassignable masters in the relatedServiceMap and restart All > services only when Namenode or SNamenode is being moved. Add to the first > step the list of services that would be restarted. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21834) UI changes for Moving Masters
[ https://issues.apache.org/jira/browse/AMBARI-21834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-21834: - Attachment: AMBARI-21834.patch > UI changes for Moving Masters > - > > Key: AMBARI-21834 > URL: https://issues.apache.org/jira/browse/AMBARI-21834 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21834_branch-2.6.patch, AMBARI-21834.patch > > > Include all reassignable masters in the relatedServiceMap and restart All > services only when Namenode or SNamenode is being moved. Add to the first > step the list of services that would be restarted. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21834) UI changes for Moving Masters
[ https://issues.apache.org/jira/browse/AMBARI-21834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-21834: - Attachment: AMBARI-21834_branch-2.6.patch > UI changes for Moving Masters > - > > Key: AMBARI-21834 > URL: https://issues.apache.org/jira/browse/AMBARI-21834 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Ishan Bhatt >Assignee: Ishan Bhatt > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21834_branch-2.6.patch > > > Include all reassignable masters in the relatedServiceMap and restart All > services only when Namenode or SNamenode is being moved. Add to the first > step the list of services that would be restarted. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21834) UI changes for Moving Masters
Ishan Bhatt created AMBARI-21834: Summary: UI changes for Moving Masters Key: AMBARI-21834 URL: https://issues.apache.org/jira/browse/AMBARI-21834 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Ishan Bhatt Assignee: Ishan Bhatt Fix For: trunk, 2.6.0 Include all reassignable masters in the relatedServiceMap and restart All services only when Namenode or SNamenode is being moved. Add to the first step the list of services that would be restarted. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21833) Add keberos service for 3.0.0 stack
[ https://issues.apache.org/jira/browse/AMBARI-21833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-21833: --- Attachment: AMBARI-21833.patch > Add keberos service for 3.0.0 stack > --- > > Key: AMBARI-21833 > URL: https://issues.apache.org/jira/browse/AMBARI-21833 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 3.0.0 > > Attachments: AMBARI-21833.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21833) Add keberos service for 3.0.0 stack
[ https://issues.apache.org/jira/browse/AMBARI-21833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-21833: --- Status: Patch Available (was: Open) > Add keberos service for 3.0.0 stack > --- > > Key: AMBARI-21833 > URL: https://issues.apache.org/jira/browse/AMBARI-21833 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 3.0.0 > > Attachments: AMBARI-21833.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21833) Add keberos server for 3.0.0
Eugene Chekanskiy created AMBARI-21833: -- Summary: Add keberos server for 3.0.0 Key: AMBARI-21833 URL: https://issues.apache.org/jira/browse/AMBARI-21833 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Eugene Chekanskiy Assignee: Eugene Chekanskiy Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21833) Add keberos service for 3.0.0 stack
[ https://issues.apache.org/jira/browse/AMBARI-21833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy updated AMBARI-21833: --- Summary: Add keberos service for 3.0.0 stack (was: Add keberos server for 3.0.0) > Add keberos service for 3.0.0 stack > --- > > Key: AMBARI-21833 > URL: https://issues.apache.org/jira/browse/AMBARI-21833 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21831) Allow Hiding of PATCH Repository
[
https://issues.apache.org/jira/browse/AMBARI-21831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16144056#comment-16144056
]
Hadoop QA commented on AMBARI-21831:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884079/AMBARI-21831_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12078//console
This message is automatically generated.
> Allow Hiding of PATCH Repository
>
>
> Key: AMBARI-21831
> URL: https://issues.apache.org/jira/browse/AMBARI-21831
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21831.patch, AMBARI-21831_trunk.patch
>
>
> When patches are reverted and no longer desired, there should be a way to
> remove them directly from the Stacks and Versions page. Removal of a
> repository should only be allowed if:
> - The repository type is {{PATCH}} and is in the {{INSTALLED}} or
> {{INSTALL_FAILED}} state
> - The repository is {{NOT_REQUIRED}} (not distributed) regardless of type
> In the dropdown of actions for the repository, we should add a "Discard"
> action which does this by executing a {{PUT}} against the
> {{\{stackName\}/versions/\{stackVersion\}/repository_versions}} endpoint.
> A new property will be exposed, {{RepositoryVersions/hidden}} which will be
> set to a value of {{true}} by the web client. When the web client queries for
> compatible repositories, any which expose {{RepositoryVersions/hidden}} as
> {{true}} should not be shown.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21830) PowerPC - IOP/HDP migration, service restart fails post Ambari upgrade
[ https://issues.apache.org/jira/browse/AMBARI-21830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16144005#comment-16144005 ] Hudson commented on AMBARI-21830: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1832 (See [https://builds.apache.org/job/Ambari-branch-2.5/1832/]) AMBARI-21830 PowerPC - IOP/HDP migration, service restart fails post (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=909902cdf6496ae5863d76b169da16e2e5d7d55f]) * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/repos/repoinfo.xml > PowerPC - IOP/HDP migration, service restart fails post Ambari upgrade > -- > > Key: AMBARI-21830 > URL: https://issues.apache.org/jira/browse/AMBARI-21830 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Di Li >Assignee: Di Li >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21830.patch > > > BI 4.2.5 repoinfo.xml shipped by Ambari 2.5.2 only includes repo urls for x > no p "redhat-ppc7", so restarting services ( with staled configs) failed post > Ambari upgrade. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21831) Allow Hiding of PATCH Repository
[
https://issues.apache.org/jira/browse/AMBARI-21831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-21831:
--
Status: Patch Available (was: In Progress)
> Allow Hiding of PATCH Repository
>
>
> Key: AMBARI-21831
> URL: https://issues.apache.org/jira/browse/AMBARI-21831
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21831.patch, AMBARI-21831_trunk.patch
>
>
> When patches are reverted and no longer desired, there should be a way to
> remove them directly from the Stacks and Versions page. Removal of a
> repository should only be allowed if:
> - The repository type is {{PATCH}} and is in the {{INSTALLED}} or
> {{INSTALL_FAILED}} state
> - The repository is {{NOT_REQUIRED}} (not distributed) regardless of type
> In the dropdown of actions for the repository, we should add a "Discard"
> action which does this by executing a {{PUT}} against the
> {{\{stackName\}/versions/\{stackVersion\}/repository_versions}} endpoint.
> A new property will be exposed, {{RepositoryVersions/hidden}} which will be
> set to a value of {{true}} by the web client. When the web client queries for
> compatible repositories, any which expose {{RepositoryVersions/hidden}} as
> {{true}} should not be shown.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-21831) Allow Hiding of PATCH Repository
[
https://issues.apache.org/jira/browse/AMBARI-21831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143962#comment-16143962
]
Andrii Tkach edited comment on AMBARI-21831 at 8/28/17 4:34 PM:
trunk:
21296 passing (25s)
128 pending
branch-2.6:
30469 passing (26s)
157 pending
was (Author: atkach):
trunk:
21296 passing (25s)
128 pending
> Allow Hiding of PATCH Repository
>
>
> Key: AMBARI-21831
> URL: https://issues.apache.org/jira/browse/AMBARI-21831
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21831.patch, AMBARI-21831_trunk.patch
>
>
> When patches are reverted and no longer desired, there should be a way to
> remove them directly from the Stacks and Versions page. Removal of a
> repository should only be allowed if:
> - The repository type is {{PATCH}} and is in the {{INSTALLED}} or
> {{INSTALL_FAILED}} state
> - The repository is {{NOT_REQUIRED}} (not distributed) regardless of type
> In the dropdown of actions for the repository, we should add a "Discard"
> action which does this by executing a {{PUT}} against the
> {{\{stackName\}/versions/\{stackVersion\}/repository_versions}} endpoint.
> A new property will be exposed, {{RepositoryVersions/hidden}} which will be
> set to a value of {{true}} by the web client. When the web client queries for
> compatible repositories, any which expose {{RepositoryVersions/hidden}} as
> {{true}} should not be shown.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21831) Allow Hiding of PATCH Repository
[
https://issues.apache.org/jira/browse/AMBARI-21831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-21831:
--
Attachment: AMBARI-21831_trunk.patch
> Allow Hiding of PATCH Repository
>
>
> Key: AMBARI-21831
> URL: https://issues.apache.org/jira/browse/AMBARI-21831
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21831.patch, AMBARI-21831_trunk.patch
>
>
> When patches are reverted and no longer desired, there should be a way to
> remove them directly from the Stacks and Versions page. Removal of a
> repository should only be allowed if:
> - The repository type is {{PATCH}} and is in the {{INSTALLED}} or
> {{INSTALL_FAILED}} state
> - The repository is {{NOT_REQUIRED}} (not distributed) regardless of type
> In the dropdown of actions for the repository, we should add a "Discard"
> action which does this by executing a {{PUT}} against the
> {{\{stackName\}/versions/\{stackVersion\}/repository_versions}} endpoint.
> A new property will be exposed, {{RepositoryVersions/hidden}} which will be
> set to a value of {{true}} by the web client. When the web client queries for
> compatible repositories, any which expose {{RepositoryVersions/hidden}} as
> {{true}} should not be shown.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21831) Allow Hiding of PATCH Repository
[
https://issues.apache.org/jira/browse/AMBARI-21831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-21831:
--
Attachment: AMBARI-21831.patch
> Allow Hiding of PATCH Repository
>
>
> Key: AMBARI-21831
> URL: https://issues.apache.org/jira/browse/AMBARI-21831
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21831.patch
>
>
> When patches are reverted and no longer desired, there should be a way to
> remove them directly from the Stacks and Versions page. Removal of a
> repository should only be allowed if:
> - The repository type is {{PATCH}} and is in the {{INSTALLED}} or
> {{INSTALL_FAILED}} state
> - The repository is {{NOT_REQUIRED}} (not distributed) regardless of type
> In the dropdown of actions for the repository, we should add a "Discard"
> action which does this by executing a {{PUT}} against the
> {{\{stackName\}/versions/\{stackVersion\}/repository_versions}} endpoint.
> A new property will be exposed, {{RepositoryVersions/hidden}} which will be
> set to a value of {{true}} by the web client. When the web client queries for
> compatible repositories, any which expose {{RepositoryVersions/hidden}} as
> {{true}} should not be shown.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21831) Allow Hiding of PATCH Repository
[
https://issues.apache.org/jira/browse/AMBARI-21831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143962#comment-16143962
]
Andrii Tkach commented on AMBARI-21831:
---
trunk:
21296 passing (25s)
128 pending
> Allow Hiding of PATCH Repository
>
>
> Key: AMBARI-21831
> URL: https://issues.apache.org/jira/browse/AMBARI-21831
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
>
> When patches are reverted and no longer desired, there should be a way to
> remove them directly from the Stacks and Versions page. Removal of a
> repository should only be allowed if:
> - The repository type is {{PATCH}} and is in the {{INSTALLED}} or
> {{INSTALL_FAILED}} state
> - The repository is {{NOT_REQUIRED}} (not distributed) regardless of type
> In the dropdown of actions for the repository, we should add a "Discard"
> action which does this by executing a {{PUT}} against the
> {{\{stackName\}/versions/\{stackVersion\}/repository_versions}} endpoint.
> A new property will be exposed, {{RepositoryVersions/hidden}} which will be
> set to a value of {{true}} by the web client. When the web client queries for
> compatible repositories, any which expose {{RepositoryVersions/hidden}} as
> {{true}} should not be shown.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21830) PowerPC - IOP/HDP migration, service restart fails post Ambari upgrade
[ https://issues.apache.org/jira/browse/AMBARI-21830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-21830: --- Resolution: Fixed Status: Resolved (was: Patch Available) > PowerPC - IOP/HDP migration, service restart fails post Ambari upgrade > -- > > Key: AMBARI-21830 > URL: https://issues.apache.org/jira/browse/AMBARI-21830 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Di Li >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21830.patch > > > BI 4.2.5 repoinfo.xml shipped by Ambari 2.5.2 only includes repo urls for x > no p "redhat-ppc7", so restarting services ( with staled configs) failed post > Ambari upgrade. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-21830) PowerPC - IOP/HDP migration, service restart fails post Ambari upgrade
[ https://issues.apache.org/jira/browse/AMBARI-21830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li reassigned AMBARI-21830: -- Assignee: Di Li > PowerPC - IOP/HDP migration, service restart fails post Ambari upgrade > -- > > Key: AMBARI-21830 > URL: https://issues.apache.org/jira/browse/AMBARI-21830 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Di Li >Assignee: Di Li >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21830.patch > > > BI 4.2.5 repoinfo.xml shipped by Ambari 2.5.2 only includes repo urls for x > no p "redhat-ppc7", so restarting services ( with staled configs) failed post > Ambari upgrade. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21830) PowerPC - IOP/HDP migration, service restart fails post Ambari upgrade
[ https://issues.apache.org/jira/browse/AMBARI-21830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143956#comment-16143956 ] Di Li commented on AMBARI-21830: pushed to branch-2.5 as https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=909902cdf6496ae5863d76b169da16e2e5d7d55f > PowerPC - IOP/HDP migration, service restart fails post Ambari upgrade > -- > > Key: AMBARI-21830 > URL: https://issues.apache.org/jira/browse/AMBARI-21830 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Di Li >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21830.patch > > > BI 4.2.5 repoinfo.xml shipped by Ambari 2.5.2 only includes repo urls for x > no p "redhat-ppc7", so restarting services ( with staled configs) failed post > Ambari upgrade. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21829) Sqoop: hive import fails with exception 'java.io.IOException:java.lang.RuntimeException: native-lzo library not available' for LZO compression codec
[ https://issues.apache.org/jira/browse/AMBARI-21829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143955#comment-16143955 ] Hudson commented on AMBARI-21829: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #73 (See [https://builds.apache.org/job/Ambari-branch-2.6/73/]) AMBARI-21829. Sqoop: hive import fails with exception (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0f12e045886d9fad1b7faa5eef35b991f608f054]) * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2.5/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/BigInsights/4.2/upgrades/config-upgrade.xml > Sqoop: hive import fails with exception > 'java.io.IOException:java.lang.RuntimeException: native-lzo library not > available' for LZO compression codec > - > > Key: AMBARI-21829 > URL: https://issues.apache.org/jira/browse/AMBARI-21829 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.6.0 > > Attachments: AMBARI-21829.patch > > > Sqoop: hive import fails with exception > 'java.io.IOException:java.lang.RuntimeException: native-lzo library not > available' for LZO compression codec > > > > [hrt_qa@nat-r6-ddfu-sqoop-5 hadoopqe]$ > /usr/hdp/current/hive-client/bin/hive -e "select data from mytable_compress > where id=12;" > 2017-08-25 13:44:40,090 WARN [main] conf.HiveConf: HiveConf of name > hive.optimize.mapjoin.mapreduce does not exist > 2017-08-25 13:44:40,091 WARN [main] conf.HiveConf: HiveConf of name > hive.custom-extensions.root does not exist > > Logging initialized using configuration in > file:/etc/hive/2.6.2.0-200/0/hive-log4j.properties > OK > Failed with exception java.io.IOException:java.lang.RuntimeException: > native-lzo library not available > Time taken: 6.933 seconds > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21831) Allow Hiding of PATCH Repository
[
https://issues.apache.org/jira/browse/AMBARI-21831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-21831:
--
Attachment: (was: AMBARI-21831.patch)
> Allow Hiding of PATCH Repository
>
>
> Key: AMBARI-21831
> URL: https://issues.apache.org/jira/browse/AMBARI-21831
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
>
> When patches are reverted and no longer desired, there should be a way to
> remove them directly from the Stacks and Versions page. Removal of a
> repository should only be allowed if:
> - The repository type is {{PATCH}} and is in the {{INSTALLED}} or
> {{INSTALL_FAILED}} state
> - The repository is {{NOT_REQUIRED}} (not distributed) regardless of type
> In the dropdown of actions for the repository, we should add a "Discard"
> action which does this by executing a {{PUT}} against the
> {{\{stackName\}/versions/\{stackVersion\}/repository_versions}} endpoint.
> A new property will be exposed, {{RepositoryVersions/hidden}} which will be
> set to a value of {{true}} by the web client. When the web client queries for
> compatible repositories, any which expose {{RepositoryVersions/hidden}} as
> {{true}} should not be shown.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21832) Reject PATCH VDFs with Services that are not Included in the Cluster
[
https://issues.apache.org/jira/browse/AMBARI-21832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-21832:
Fix Version/s: 2.6.0
> Reject PATCH VDFs with Services that are not Included in the Cluster
>
>
> Key: AMBARI-21832
> URL: https://issues.apache.org/jira/browse/AMBARI-21832
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21832.patch
>
>
> Currently there is an odd scenario which can occur when patch repositories
> are registered which have services not yet installed. Consider the following
> scenario:
> - Install ZooKeeper, Storm on HDP 2.6.0.0-1234
> - Register/patch a {{PATCH}} VDF for Storm and Accumulo for 2.6.0.1-
> - Install Accumulo
> Which version does Accumulo use - the {{STANDARD}} repository or the
> {{PATCH}}? If the {{PATCH}} repository is chosen, this will now prevent
> reversion of the patch since there's no prior version for Accumulo to revert
> back to.
> If Accumulo uses the {{STANDARD}} repo, then there needs to be a lot of
> design and UX flow work provided to indicate that a {{PATCH}} which was
> previously applied can be re-applied for the new service. This also causes
> problems for patch reversion since now there would be two upgrades which need
> to be reverted to "get rid" of the patch.
> For the timeframe for Ambari 2.6, we should reject VDFs that include services
> which are not installed. This will prevent the problem.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21831) Allow Hiding of PATCH Repository
[
https://issues.apache.org/jira/browse/AMBARI-21831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Tkach updated AMBARI-21831:
--
Attachment: AMBARI-21831.patch
> Allow Hiding of PATCH Repository
>
>
> Key: AMBARI-21831
> URL: https://issues.apache.org/jira/browse/AMBARI-21831
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
>Affects Versions: 2.6.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21831.patch
>
>
> When patches are reverted and no longer desired, there should be a way to
> remove them directly from the Stacks and Versions page. Removal of a
> repository should only be allowed if:
> - The repository type is {{PATCH}} and is in the {{INSTALLED}} or
> {{INSTALL_FAILED}} state
> - The repository is {{NOT_REQUIRED}} (not distributed) regardless of type
> In the dropdown of actions for the repository, we should add a "Discard"
> action which does this by executing a {{PUT}} against the
> {{\{stackName\}/versions/\{stackVersion\}/repository_versions}} endpoint.
> A new property will be exposed, {{RepositoryVersions/hidden}} which will be
> set to a value of {{true}} by the web client. When the web client queries for
> compatible repositories, any which expose {{RepositoryVersions/hidden}} as
> {{true}} should not be shown.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21832) Reject PATCH VDFs with Services that are not Included in the Cluster
[
https://issues.apache.org/jira/browse/AMBARI-21832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-21832:
Component/s: ambari-server
> Reject PATCH VDFs with Services that are not Included in the Cluster
>
>
> Key: AMBARI-21832
> URL: https://issues.apache.org/jira/browse/AMBARI-21832
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Attachments: AMBARI-21832.patch
>
>
> Currently there is an odd scenario which can occur when patch repositories
> are registered which have services not yet installed. Consider the following
> scenario:
> - Install ZooKeeper, Storm on HDP 2.6.0.0-1234
> - Register/patch a {{PATCH}} VDF for Storm and Accumulo for 2.6.0.1-
> - Install Accumulo
> Which version does Accumulo use - the {{STANDARD}} repository or the
> {{PATCH}}? If the {{PATCH}} repository is chosen, this will now prevent
> reversion of the patch since there's no prior version for Accumulo to revert
> back to.
> If Accumulo uses the {{STANDARD}} repo, then there needs to be a lot of
> design and UX flow work provided to indicate that a {{PATCH}} which was
> previously applied can be re-applied for the new service. This also causes
> problems for patch reversion since now there would be two upgrades which need
> to be reverted to "get rid" of the patch.
> For the timeframe for Ambari 2.6, we should reject VDFs that include services
> which are not installed. This will prevent the problem.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21832) Reject PATCH VDFs with Services that are not Included in the Cluster
Dmitry Lysnichenko created AMBARI-21832:
---
Summary: Reject PATCH VDFs with Services that are not Included in
the Cluster
Key: AMBARI-21832
URL: https://issues.apache.org/jira/browse/AMBARI-21832
Project: Ambari
Issue Type: Task
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
Priority: Critical
Currently there is an odd scenario which can occur when patch repositories are
registered which have services not yet installed. Consider the following
scenario:
- Install ZooKeeper, Storm on HDP 2.6.0.0-1234
- Register/patch a {{PATCH}} VDF for Storm and Accumulo for 2.6.0.1-
- Install Accumulo
Which version does Accumulo use - the {{STANDARD}} repository or the {{PATCH}}?
If the {{PATCH}} repository is chosen, this will now prevent reversion of the
patch since there's no prior version for Accumulo to revert back to.
If Accumulo uses the {{STANDARD}} repo, then there needs to be a lot of design
and UX flow work provided to indicate that a {{PATCH}} which was previously
applied can be re-applied for the new service. This also causes problems for
patch reversion since now there would be two upgrades which need to be reverted
to "get rid" of the patch.
For the timeframe for Ambari 2.6, we should reject VDFs that include services
which are not installed. This will prevent the problem.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21832) Reject PATCH VDFs with Services that are not Included in the Cluster
[
https://issues.apache.org/jira/browse/AMBARI-21832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-21832:
Attachment: AMBARI-21832.patch
> Reject PATCH VDFs with Services that are not Included in the Cluster
>
>
> Key: AMBARI-21832
> URL: https://issues.apache.org/jira/browse/AMBARI-21832
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Attachments: AMBARI-21832.patch
>
>
> Currently there is an odd scenario which can occur when patch repositories
> are registered which have services not yet installed. Consider the following
> scenario:
> - Install ZooKeeper, Storm on HDP 2.6.0.0-1234
> - Register/patch a {{PATCH}} VDF for Storm and Accumulo for 2.6.0.1-
> - Install Accumulo
> Which version does Accumulo use - the {{STANDARD}} repository or the
> {{PATCH}}? If the {{PATCH}} repository is chosen, this will now prevent
> reversion of the patch since there's no prior version for Accumulo to revert
> back to.
> If Accumulo uses the {{STANDARD}} repo, then there needs to be a lot of
> design and UX flow work provided to indicate that a {{PATCH}} which was
> previously applied can be re-applied for the new service. This also causes
> problems for patch reversion since now there would be two upgrades which need
> to be reverted to "get rid" of the patch.
> For the timeframe for Ambari 2.6, we should reject VDFs that include services
> which are not installed. This will prevent the problem.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21832) Reject PATCH VDFs with Services that are not Included in the Cluster
[
https://issues.apache.org/jira/browse/AMBARI-21832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Lysnichenko updated AMBARI-21832:
Status: Patch Available (was: Open)
> Reject PATCH VDFs with Services that are not Included in the Cluster
>
>
> Key: AMBARI-21832
> URL: https://issues.apache.org/jira/browse/AMBARI-21832
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
>Priority: Critical
> Attachments: AMBARI-21832.patch
>
>
> Currently there is an odd scenario which can occur when patch repositories
> are registered which have services not yet installed. Consider the following
> scenario:
> - Install ZooKeeper, Storm on HDP 2.6.0.0-1234
> - Register/patch a {{PATCH}} VDF for Storm and Accumulo for 2.6.0.1-
> - Install Accumulo
> Which version does Accumulo use - the {{STANDARD}} repository or the
> {{PATCH}}? If the {{PATCH}} repository is chosen, this will now prevent
> reversion of the patch since there's no prior version for Accumulo to revert
> back to.
> If Accumulo uses the {{STANDARD}} repo, then there needs to be a lot of
> design and UX flow work provided to indicate that a {{PATCH}} which was
> previously applied can be re-applied for the new service. This also causes
> problems for patch reversion since now there would be two upgrades which need
> to be reverted to "get rid" of the patch.
> For the timeframe for Ambari 2.6, we should reject VDFs that include services
> which are not installed. This will prevent the problem.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21831) Allow Hiding of PATCH Repository
Andrii Tkach created AMBARI-21831:
-
Summary: Allow Hiding of PATCH Repository
Key: AMBARI-21831
URL: https://issues.apache.org/jira/browse/AMBARI-21831
Project: Ambari
Issue Type: Task
Components: ambari-web
Affects Versions: 2.6.0
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Priority: Critical
Fix For: 2.6.0
When patches are reverted and no longer desired, there should be a way to
remove them directly from the Stacks and Versions page. Removal of a repository
should only be allowed if:
- The repository type is {{PATCH}} and is in the {{INSTALLED}} or
{{INSTALL_FAILED}} state
- The repository is {{NOT_REQUIRED}} (not distributed) regardless of type
In the dropdown of actions for the repository, we should add a "Discard" action
which does this by executing a {{PUT}} against the
{{\{stackName\}/versions/\{stackVersion\}/repository_versions}} endpoint.
A new property will be exposed, {{RepositoryVersions/hidden}} which will be set
to a value of {{true}} by the web client. When the web client queries for
compatible repositories, any which expose {{RepositoryVersions/hidden}} as
{{true}} should not be shown.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21829) Sqoop: hive import fails with exception 'java.io.IOException:java.lang.RuntimeException: native-lzo library not available' for LZO compression codec
[ https://issues.apache.org/jira/browse/AMBARI-21829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21829: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-2.6 > Sqoop: hive import fails with exception > 'java.io.IOException:java.lang.RuntimeException: native-lzo library not > available' for LZO compression codec > - > > Key: AMBARI-21829 > URL: https://issues.apache.org/jira/browse/AMBARI-21829 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.2 > > Attachments: AMBARI-21829.patch > > > Sqoop: hive import fails with exception > 'java.io.IOException:java.lang.RuntimeException: native-lzo library not > available' for LZO compression codec > > > > [hrt_qa@nat-r6-ddfu-sqoop-5 hadoopqe]$ > /usr/hdp/current/hive-client/bin/hive -e "select data from mytable_compress > where id=12;" > 2017-08-25 13:44:40,090 WARN [main] conf.HiveConf: HiveConf of name > hive.optimize.mapjoin.mapreduce does not exist > 2017-08-25 13:44:40,091 WARN [main] conf.HiveConf: HiveConf of name > hive.custom-extensions.root does not exist > > Logging initialized using configuration in > file:/etc/hive/2.6.2.0-200/0/hive-log4j.properties > OK > Failed with exception java.io.IOException:java.lang.RuntimeException: > native-lzo library not available > Time taken: 6.933 seconds > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21829) Sqoop: hive import fails with exception 'java.io.IOException:java.lang.RuntimeException: native-lzo library not available' for LZO compression codec
[ https://issues.apache.org/jira/browse/AMBARI-21829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21829: - Fix Version/s: (was: 2.5.2) 2.6.0 > Sqoop: hive import fails with exception > 'java.io.IOException:java.lang.RuntimeException: native-lzo library not > available' for LZO compression codec > - > > Key: AMBARI-21829 > URL: https://issues.apache.org/jira/browse/AMBARI-21829 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.6.0 > > Attachments: AMBARI-21829.patch > > > Sqoop: hive import fails with exception > 'java.io.IOException:java.lang.RuntimeException: native-lzo library not > available' for LZO compression codec > > > > [hrt_qa@nat-r6-ddfu-sqoop-5 hadoopqe]$ > /usr/hdp/current/hive-client/bin/hive -e "select data from mytable_compress > where id=12;" > 2017-08-25 13:44:40,090 WARN [main] conf.HiveConf: HiveConf of name > hive.optimize.mapjoin.mapreduce does not exist > 2017-08-25 13:44:40,091 WARN [main] conf.HiveConf: HiveConf of name > hive.custom-extensions.root does not exist > > Logging initialized using configuration in > file:/etc/hive/2.6.2.0-200/0/hive-log4j.properties > OK > Failed with exception java.io.IOException:java.lang.RuntimeException: > native-lzo library not available > Time taken: 6.933 seconds > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21830) PowerPC - IOP/HDP migration, service restart fails post Ambari upgrade
[ https://issues.apache.org/jira/browse/AMBARI-21830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-21830: --- Status: Patch Available (was: Open) > PowerPC - IOP/HDP migration, service restart fails post Ambari upgrade > -- > > Key: AMBARI-21830 > URL: https://issues.apache.org/jira/browse/AMBARI-21830 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Di Li >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21830.patch > > > BI 4.2.5 repoinfo.xml shipped by Ambari 2.5.2 only includes repo urls for x > no p "redhat-ppc7", so restarting services ( with staled configs) failed post > Ambari upgrade. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21830) PowerPC - IOP/HDP migration, service restart fails post Ambari upgrade
[ https://issues.apache.org/jira/browse/AMBARI-21830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Di Li updated AMBARI-21830: --- Attachment: AMBARI-21830.patch > PowerPC - IOP/HDP migration, service restart fails post Ambari upgrade > -- > > Key: AMBARI-21830 > URL: https://issues.apache.org/jira/browse/AMBARI-21830 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Di Li >Priority: Critical > Fix For: 2.5.2 > > Attachments: AMBARI-21830.patch > > > BI 4.2.5 repoinfo.xml shipped by Ambari 2.5.2 only includes repo urls for x > no p "redhat-ppc7", so restarting services ( with staled configs) failed post > Ambari upgrade. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21829) Sqoop: hive import fails with exception 'java.io.IOException:java.lang.RuntimeException: native-lzo library not available' for LZO compression codec
[
https://issues.apache.org/jira/browse/AMBARI-21829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143882#comment-16143882
]
Hadoop QA commented on AMBARI-21829:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884063/AMBARI-21829.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12077//console
This message is automatically generated.
> Sqoop: hive import fails with exception
> 'java.io.IOException:java.lang.RuntimeException: native-lzo library not
> available' for LZO compression codec
> -
>
> Key: AMBARI-21829
> URL: https://issues.apache.org/jira/browse/AMBARI-21829
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.2
>
> Attachments: AMBARI-21829.patch
>
>
> Sqoop: hive import fails with exception
> 'java.io.IOException:java.lang.RuntimeException: native-lzo library not
> available' for LZO compression codec
>
>
>
> [hrt_qa@nat-r6-ddfu-sqoop-5 hadoopqe]$
> /usr/hdp/current/hive-client/bin/hive -e "select data from mytable_compress
> where id=12;"
> 2017-08-25 13:44:40,090 WARN [main] conf.HiveConf: HiveConf of name
> hive.optimize.mapjoin.mapreduce does not exist
> 2017-08-25 13:44:40,091 WARN [main] conf.HiveConf: HiveConf of name
> hive.custom-extensions.root does not exist
>
> Logging initialized using configuration in
> file:/etc/hive/2.6.2.0-200/0/hive-log4j.properties
> OK
> Failed with exception java.io.IOException:java.lang.RuntimeException:
> native-lzo library not available
> Time taken: 6.933 seconds
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (AMBARI-21830) PowerPC - IOP/HDP migration, service restart fails post Ambari upgrade
Di Li created AMBARI-21830: -- Summary: PowerPC - IOP/HDP migration, service restart fails post Ambari upgrade Key: AMBARI-21830 URL: https://issues.apache.org/jira/browse/AMBARI-21830 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.5.2 Reporter: Di Li Priority: Critical Fix For: 2.5.2 BI 4.2.5 repoinfo.xml shipped by Ambari 2.5.2 only includes repo urls for x no p "redhat-ppc7", so restarting services ( with staled configs) failed post Ambari upgrade. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21829) Sqoop: hive import fails with exception 'java.io.IOException:java.lang.RuntimeException: native-lzo library not available' for LZO compression codec
Andrew Onischuk created AMBARI-21829: Summary: Sqoop: hive import fails with exception 'java.io.IOException:java.lang.RuntimeException: native-lzo library not available' for LZO compression codec Key: AMBARI-21829 URL: https://issues.apache.org/jira/browse/AMBARI-21829 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.5.2 Sqoop: hive import fails with exception 'java.io.IOException:java.lang.RuntimeException: native-lzo library not available' for LZO compression codec [hrt_qa@nat-r6-ddfu-sqoop-5 hadoopqe]$ /usr/hdp/current/hive-client/bin/hive -e "select data from mytable_compress where id=12;" 2017-08-25 13:44:40,090 WARN [main] conf.HiveConf: HiveConf of name hive.optimize.mapjoin.mapreduce does not exist 2017-08-25 13:44:40,091 WARN [main] conf.HiveConf: HiveConf of name hive.custom-extensions.root does not exist Logging initialized using configuration in file:/etc/hive/2.6.2.0-200/0/hive-log4j.properties OK Failed with exception java.io.IOException:java.lang.RuntimeException: native-lzo library not available Time taken: 6.933 seconds -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21829) Sqoop: hive import fails with exception 'java.io.IOException:java.lang.RuntimeException: native-lzo library not available' for LZO compression codec
[ https://issues.apache.org/jira/browse/AMBARI-21829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21829: - Status: Patch Available (was: Open) > Sqoop: hive import fails with exception > 'java.io.IOException:java.lang.RuntimeException: native-lzo library not > available' for LZO compression codec > - > > Key: AMBARI-21829 > URL: https://issues.apache.org/jira/browse/AMBARI-21829 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.2 > > Attachments: AMBARI-21829.patch > > > Sqoop: hive import fails with exception > 'java.io.IOException:java.lang.RuntimeException: native-lzo library not > available' for LZO compression codec > > > > [hrt_qa@nat-r6-ddfu-sqoop-5 hadoopqe]$ > /usr/hdp/current/hive-client/bin/hive -e "select data from mytable_compress > where id=12;" > 2017-08-25 13:44:40,090 WARN [main] conf.HiveConf: HiveConf of name > hive.optimize.mapjoin.mapreduce does not exist > 2017-08-25 13:44:40,091 WARN [main] conf.HiveConf: HiveConf of name > hive.custom-extensions.root does not exist > > Logging initialized using configuration in > file:/etc/hive/2.6.2.0-200/0/hive-log4j.properties > OK > Failed with exception java.io.IOException:java.lang.RuntimeException: > native-lzo library not available > Time taken: 6.933 seconds > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21829) Sqoop: hive import fails with exception 'java.io.IOException:java.lang.RuntimeException: native-lzo library not available' for LZO compression codec
[ https://issues.apache.org/jira/browse/AMBARI-21829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21829: - Attachment: AMBARI-21829.patch > Sqoop: hive import fails with exception > 'java.io.IOException:java.lang.RuntimeException: native-lzo library not > available' for LZO compression codec > - > > Key: AMBARI-21829 > URL: https://issues.apache.org/jira/browse/AMBARI-21829 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 2.5.2 > > Attachments: AMBARI-21829.patch > > > Sqoop: hive import fails with exception > 'java.io.IOException:java.lang.RuntimeException: native-lzo library not > available' for LZO compression codec > > > > [hrt_qa@nat-r6-ddfu-sqoop-5 hadoopqe]$ > /usr/hdp/current/hive-client/bin/hive -e "select data from mytable_compress > where id=12;" > 2017-08-25 13:44:40,090 WARN [main] conf.HiveConf: HiveConf of name > hive.optimize.mapjoin.mapreduce does not exist > 2017-08-25 13:44:40,091 WARN [main] conf.HiveConf: HiveConf of name > hive.custom-extensions.root does not exist > > Logging initialized using configuration in > file:/etc/hive/2.6.2.0-200/0/hive-log4j.properties > OK > Failed with exception java.io.IOException:java.lang.RuntimeException: > native-lzo library not available > Time taken: 6.933 seconds > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21826) Install button showing wrong list of services to install
[ https://issues.apache.org/jira/browse/AMBARI-21826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143877#comment-16143877 ] Hudson commented on AMBARI-21826: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7949 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7949/]) AMBARI-21826. Install button showing wrong list of services to install (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=91155b152625cafb296b62961cf70c6f3fb6d72c]) * (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js * (edit) ambari-web/test/controllers/main/service/reassign/step1_controller_test.js > Install button showing wrong list of services to install > > > Key: AMBARI-21826 > URL: https://issues.apache.org/jira/browse/AMBARI-21826 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21826.patch, AMBARI-21826_trunk.patch, Screen > Shot 2017-08-23 at 5.17.14 PM.png, Screen Shot 2017-08-23 at 5.20.08 PM.png > > > See screenshots. The FE is correctly showing the MAINT version (2.6.1.0-14) > that Only ZK will be in the Upgrade, but clicking the Install button shows > both Storm and ZK. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21826) Install button showing wrong list of services to install
[ https://issues.apache.org/jira/browse/AMBARI-21826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143850#comment-16143850 ] Hudson commented on AMBARI-21826: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #72 (See [https://builds.apache.org/job/Ambari-branch-2.6/72/]) AMBARI-21826. Install button showing wrong list of services to install (aantonenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=80aa50b6624ed1cd6a9c5e8b1c4cc41bb4b01b0d]) * (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js * (edit) ambari-web/app/styles/stack_versions.less * (edit) ambari-web/app/templates/main/admin/stack_upgrade/upgrade_version_column.hbs > Install button showing wrong list of services to install > > > Key: AMBARI-21826 > URL: https://issues.apache.org/jira/browse/AMBARI-21826 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21826.patch, AMBARI-21826_trunk.patch, Screen > Shot 2017-08-23 at 5.17.14 PM.png, Screen Shot 2017-08-23 at 5.20.08 PM.png > > > See screenshots. The FE is correctly showing the MAINT version (2.6.1.0-14) > that Only ZK will be in the Upgrade, but clicking the Install button shows > both Storm and ZK. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21682) Patched Service Doesn't Display Correct Hadoop Version on Stacks Page
[
https://issues.apache.org/jira/browse/AMBARI-21682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143835#comment-16143835
]
Hudson commented on AMBARI-21682:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7948 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7948/])
AMBARI-21682. Patched Service Doesn't Display Correct Hadoop Version on
(aantonenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=0bd85d754512f220be307b0baa6e7f26d208d45a])
* (edit) ambari-web/app/messages.js
* (edit)
ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js
* (edit) ambari-web/app/models/stack_version/repository_version.js
* (edit)
ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_column_view.js
> Patched Service Doesn't Display Correct Hadoop Version on Stacks Page
> -
>
> Key: AMBARI-21682
> URL: https://issues.apache.org/jira/browse/AMBARI-21682
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.5.3
>
> Attachments: AMBARI-21682.patch
>
>
> STR:
> - Install ZK, YARN, HDFS with HDP 2.5.0.0
> - Apply a {{PATCH}} VDF for ZooKeeper for 2.5.4.0
> Notice that on the stacks/versions page, the columns show ZooKeeper as green
> for both versions.
> Also - notice that when clicking on the hosts number to see where a
> particular repository is installed, the text that is displayed sounds a
> little off. It says
> {quote}
> "HDP-2.5.4.0-121 Version is Current on 3 hosts"
> {quote}
> We can probably just drop the word "version". And maybe change the word
> "Current" to applied. Something like this:
> {quote}
> "HDP-2.5.4.0-121 is applied to 3 hosts"
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21826) Install button showing wrong list of services to install
[
https://issues.apache.org/jira/browse/AMBARI-21826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143833#comment-16143833
]
Hadoop QA commented on AMBARI-21826:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884049/AMBARI-21826_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12076//console
This message is automatically generated.
> Install button showing wrong list of services to install
>
>
> Key: AMBARI-21826
> URL: https://issues.apache.org/jira/browse/AMBARI-21826
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21826.patch, AMBARI-21826_trunk.patch, Screen
> Shot 2017-08-23 at 5.17.14 PM.png, Screen Shot 2017-08-23 at 5.20.08 PM.png
>
>
> See screenshots. The FE is correctly showing the MAINT version (2.6.1.0-14)
> that Only ZK will be in the Upgrade, but clicking the Install button shows
> both Storm and ZK.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21826) Install button showing wrong list of services to install
[ https://issues.apache.org/jira/browse/AMBARI-21826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143816#comment-16143816 ] Antonenko Alexander commented on AMBARI-21826: -- Committed to trunk and branch-2.6 > Install button showing wrong list of services to install > > > Key: AMBARI-21826 > URL: https://issues.apache.org/jira/browse/AMBARI-21826 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21826.patch, AMBARI-21826_trunk.patch, Screen > Shot 2017-08-23 at 5.17.14 PM.png, Screen Shot 2017-08-23 at 5.20.08 PM.png > > > See screenshots. The FE is correctly showing the MAINT version (2.6.1.0-14) > that Only ZK will be in the Upgrade, but clicking the Install button shows > both Storm and ZK. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21826) Install button showing wrong list of services to install
[ https://issues.apache.org/jira/browse/AMBARI-21826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21826: - Resolution: Fixed Status: Resolved (was: Patch Available) > Install button showing wrong list of services to install > > > Key: AMBARI-21826 > URL: https://issues.apache.org/jira/browse/AMBARI-21826 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21826.patch, AMBARI-21826_trunk.patch, Screen > Shot 2017-08-23 at 5.17.14 PM.png, Screen Shot 2017-08-23 at 5.20.08 PM.png > > > See screenshots. The FE is correctly showing the MAINT version (2.6.1.0-14) > that Only ZK will be in the Upgrade, but clicking the Install button shows > both Storm and ZK. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-21820) Force Regeneration of Cached RCO After Upgrade
[ https://issues.apache.org/jira/browse/AMBARI-21820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hurley resolved AMBARI-21820. -- Resolution: Won't Do I decided that this fix isn't right - more investigation needs to be make into why the RCO isn't being recalculated after an upgrade ... > Force Regeneration of Cached RCO After Upgrade > -- > > Key: AMBARI-21820 > URL: https://issues.apache.org/jira/browse/AMBARI-21820 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.6.0 >Reporter: Jonathan Hurley >Assignee: Jonathan Hurley >Priority: Critical > Fix For: 2.6.0 > > > After the stack upgrade has completed, force the RCO to clear and > reinitialize. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21826) Install button showing wrong list of services to install
[
https://issues.apache.org/jira/browse/AMBARI-21826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143810#comment-16143810
]
Hadoop QA commented on AMBARI-21826:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884049/AMBARI-21826_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12075//console
This message is automatically generated.
> Install button showing wrong list of services to install
>
>
> Key: AMBARI-21826
> URL: https://issues.apache.org/jira/browse/AMBARI-21826
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21826.patch, AMBARI-21826_trunk.patch, Screen
> Shot 2017-08-23 at 5.17.14 PM.png, Screen Shot 2017-08-23 at 5.20.08 PM.png
>
>
> See screenshots. The FE is correctly showing the MAINT version (2.6.1.0-14)
> that Only ZK will be in the Upgrade, but clicking the Install button shows
> both Storm and ZK.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21828) Backend should sort repo_version by version string
[ https://issues.apache.org/jira/browse/AMBARI-21828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole updated AMBARI-21828: --- Description: The BE should be providing repository versions in the order of version string. > Backend should sort repo_version by version string > -- > > Key: AMBARI-21828 > URL: https://issues.apache.org/jira/browse/AMBARI-21828 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > > The BE should be providing repository versions in the order of version string. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21828) Backend should sort repo_version by version string
Nate Cole created AMBARI-21828: -- Summary: Backend should sort repo_version by version string Key: AMBARI-21828 URL: https://issues.apache.org/jira/browse/AMBARI-21828 Project: Ambari Issue Type: Bug Components: ambari-server Reporter: Nate Cole Priority: Critical Fix For: 2.6.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (AMBARI-21828) Backend should sort repo_version by version string
[ https://issues.apache.org/jira/browse/AMBARI-21828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate Cole reassigned AMBARI-21828: -- Assignee: Nate Cole > Backend should sort repo_version by version string > -- > > Key: AMBARI-21828 > URL: https://issues.apache.org/jira/browse/AMBARI-21828 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Fix For: 2.6.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21682) Patched Service Doesn't Display Correct Hadoop Version on Stacks Page
[
https://issues.apache.org/jira/browse/AMBARI-21682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143802#comment-16143802
]
Antonenko Alexander commented on AMBARI-21682:
--
Committed to trunk
> Patched Service Doesn't Display Correct Hadoop Version on Stacks Page
> -
>
> Key: AMBARI-21682
> URL: https://issues.apache.org/jira/browse/AMBARI-21682
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.5.3
>
> Attachments: AMBARI-21682.patch
>
>
> STR:
> - Install ZK, YARN, HDFS with HDP 2.5.0.0
> - Apply a {{PATCH}} VDF for ZooKeeper for 2.5.4.0
> Notice that on the stacks/versions page, the columns show ZooKeeper as green
> for both versions.
> Also - notice that when clicking on the hosts number to see where a
> particular repository is installed, the text that is displayed sounds a
> little off. It says
> {quote}
> "HDP-2.5.4.0-121 Version is Current on 3 hosts"
> {quote}
> We can probably just drop the word "version". And maybe change the word
> "Current" to applied. Something like this:
> {quote}
> "HDP-2.5.4.0-121 is applied to 3 hosts"
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21827) Fix config paths in libraries folder
[
https://issues.apache.org/jira/browse/AMBARI-21827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143783#comment-16143783
]
Hadoop QA commented on AMBARI-21827:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884046/AMBARI-21827.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12074//console
This message is automatically generated.
> Fix config paths in libraries folder
>
>
> Key: AMBARI-21827
> URL: https://issues.apache.org/jira/browse/AMBARI-21827
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-21827.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21827) Fix config paths in libraries folder
[ https://issues.apache.org/jira/browse/AMBARI-21827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21827: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-3.0-perf > Fix config paths in libraries folder > > > Key: AMBARI-21827 > URL: https://issues.apache.org/jira/browse/AMBARI-21827 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-21827.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21826) Install button showing wrong list of services to install
[ https://issues.apache.org/jira/browse/AMBARI-21826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21826: - Attachment: AMBARI-21826_trunk.patch > Install button showing wrong list of services to install > > > Key: AMBARI-21826 > URL: https://issues.apache.org/jira/browse/AMBARI-21826 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21826.patch, AMBARI-21826_trunk.patch, Screen > Shot 2017-08-23 at 5.17.14 PM.png, Screen Shot 2017-08-23 at 5.20.08 PM.png > > > See screenshots. The FE is correctly showing the MAINT version (2.6.1.0-14) > that Only ZK will be in the Upgrade, but clicking the Install button shows > both Storm and ZK. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21827) Fix config paths in libraries folder
[ https://issues.apache.org/jira/browse/AMBARI-21827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21827: - Attachment: AMBARI-21827.patch > Fix config paths in libraries folder > > > Key: AMBARI-21827 > URL: https://issues.apache.org/jira/browse/AMBARI-21827 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-21827.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21827) Fix config paths in libraries folder
Andrew Onischuk created AMBARI-21827: Summary: Fix config paths in libraries folder Key: AMBARI-21827 URL: https://issues.apache.org/jira/browse/AMBARI-21827 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21826) Install button showing wrong list of services to install
[ https://issues.apache.org/jira/browse/AMBARI-21826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21826: - Attachment: (was: AMBARI-21826_trunk.patch) > Install button showing wrong list of services to install > > > Key: AMBARI-21826 > URL: https://issues.apache.org/jira/browse/AMBARI-21826 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21826.patch, Screen Shot 2017-08-23 at 5.17.14 > PM.png, Screen Shot 2017-08-23 at 5.20.08 PM.png > > > See screenshots. The FE is correctly showing the MAINT version (2.6.1.0-14) > that Only ZK will be in the Upgrade, but clicking the Install button shows > both Storm and ZK. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21827) Fix config paths in libraries folder
[ https://issues.apache.org/jira/browse/AMBARI-21827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21827: - Status: Patch Available (was: Open) > Fix config paths in libraries folder > > > Key: AMBARI-21827 > URL: https://issues.apache.org/jira/browse/AMBARI-21827 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-21827.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21825) Fix new logsearch UI rat issues
[ https://issues.apache.org/jira/browse/AMBARI-21825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-21825: -- Status: Patch Available (was: Open) > Fix new logsearch UI rat issues > --- > > Key: AMBARI-21825 > URL: https://issues.apache.org/jira/browse/AMBARI-21825 > Project: Ambari > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21789) Component version is not reported
[ https://issues.apache.org/jira/browse/AMBARI-21789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-21789: - Resolution: Fixed Status: Resolved (was: Patch Available) Committed to branch-3.0-perf > Component version is not reported > - > > Key: AMBARI-21789 > URL: https://issues.apache.org/jira/browse/AMBARI-21789 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-21789.patch, AMBARI-21789.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21826) Install button showing wrong list of services to install
[
https://issues.apache.org/jira/browse/AMBARI-21826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143751#comment-16143751
]
Hadoop QA commented on AMBARI-21826:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884042/AMBARI-21826_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in
[ambari-web|https://builds.apache.org/job/Ambari-trunk-test-patch/12073//artifact/patch-work/testrun_ambari-web.txt]
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12073//console
This message is automatically generated.
> Install button showing wrong list of services to install
>
>
> Key: AMBARI-21826
> URL: https://issues.apache.org/jira/browse/AMBARI-21826
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21826.patch, AMBARI-21826_trunk.patch, Screen
> Shot 2017-08-23 at 5.17.14 PM.png, Screen Shot 2017-08-23 at 5.20.08 PM.png
>
>
> See screenshots. The FE is correctly showing the MAINT version (2.6.1.0-14)
> that Only ZK will be in the Upgrade, but clicking the Install button shows
> both Storm and ZK.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21826) Install button showing wrong list of services to install
[ https://issues.apache.org/jira/browse/AMBARI-21826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143734#comment-16143734 ] Andrii Tkach commented on AMBARI-21826: --- +1 for the patch > Install button showing wrong list of services to install > > > Key: AMBARI-21826 > URL: https://issues.apache.org/jira/browse/AMBARI-21826 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21826.patch, AMBARI-21826_trunk.patch, Screen > Shot 2017-08-23 at 5.17.14 PM.png, Screen Shot 2017-08-23 at 5.20.08 PM.png > > > See screenshots. The FE is correctly showing the MAINT version (2.6.1.0-14) > that Only ZK will be in the Upgrade, but clicking the Install button shows > both Storm and ZK. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21826) Install button showing wrong list of services to install
[ https://issues.apache.org/jira/browse/AMBARI-21826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21826: - Attachment: AMBARI-21826_trunk.patch > Install button showing wrong list of services to install > > > Key: AMBARI-21826 > URL: https://issues.apache.org/jira/browse/AMBARI-21826 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21826.patch, AMBARI-21826_trunk.patch, Screen > Shot 2017-08-23 at 5.17.14 PM.png, Screen Shot 2017-08-23 at 5.20.08 PM.png > > > See screenshots. The FE is correctly showing the MAINT version (2.6.1.0-14) > that Only ZK will be in the Upgrade, but clicking the Install button shows > both Storm and ZK. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21826) Install button showing wrong list of services to install
[ https://issues.apache.org/jira/browse/AMBARI-21826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21826: - Priority: Critical (was: Major) > Install button showing wrong list of services to install > > > Key: AMBARI-21826 > URL: https://issues.apache.org/jira/browse/AMBARI-21826 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.6.0 > > Attachments: AMBARI-21826.patch, Screen Shot 2017-08-23 at 5.17.14 > PM.png, Screen Shot 2017-08-23 at 5.20.08 PM.png > > > See screenshots. The FE is correctly showing the MAINT version (2.6.1.0-14) > that Only ZK will be in the Upgrade, but clicking the Install button shows > both Storm and ZK. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21826) Install button showing wrong list of services to install
[ https://issues.apache.org/jira/browse/AMBARI-21826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21826: - Assignee: Antonenko Alexander Status: Patch Available (was: Open) > Install button showing wrong list of services to install > > > Key: AMBARI-21826 > URL: https://issues.apache.org/jira/browse/AMBARI-21826 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21826.patch, Screen Shot 2017-08-23 at 5.17.14 > PM.png, Screen Shot 2017-08-23 at 5.20.08 PM.png > > > See screenshots. The FE is correctly showing the MAINT version (2.6.1.0-14) > that Only ZK will be in the Upgrade, but clicking the Install button shows > both Storm and ZK. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21826) Install button showing wrong list of services to install
[ https://issues.apache.org/jira/browse/AMBARI-21826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21826: - Attachment: AMBARI-21826.patch > Install button showing wrong list of services to install > > > Key: AMBARI-21826 > URL: https://issues.apache.org/jira/browse/AMBARI-21826 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: AMBARI-21826.patch, Screen Shot 2017-08-23 at 5.17.14 > PM.png, Screen Shot 2017-08-23 at 5.20.08 PM.png > > > See screenshots. The FE is correctly showing the MAINT version (2.6.1.0-14) > that Only ZK will be in the Upgrade, but clicking the Install button shows > both Storm and ZK. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21826) Install button showing wrong list of services to install
[ https://issues.apache.org/jira/browse/AMBARI-21826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-21826: - Attachment: Screen Shot 2017-08-23 at 5.17.14 PM.png Screen Shot 2017-08-23 at 5.20.08 PM.png > Install button showing wrong list of services to install > > > Key: AMBARI-21826 > URL: https://issues.apache.org/jira/browse/AMBARI-21826 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Antonenko Alexander > Fix For: 2.6.0 > > Attachments: Screen Shot 2017-08-23 at 5.17.14 PM.png, Screen Shot > 2017-08-23 at 5.20.08 PM.png > > > See screenshots. The FE is correctly showing the MAINT version (2.6.1.0-14) > that Only ZK will be in the Upgrade, but clicking the Install button shows > both Storm and ZK. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21826) Install button showing wrong list of services to install
Antonenko Alexander created AMBARI-21826: Summary: Install button showing wrong list of services to install Key: AMBARI-21826 URL: https://issues.apache.org/jira/browse/AMBARI-21826 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Antonenko Alexander Fix For: 2.6.0 See screenshots. The FE is correctly showing the MAINT version (2.6.1.0-14) that Only ZK will be in the Upgrade, but clicking the Install button shows both Storm and ZK. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21296) Python tests fail for ambari-server and ambari-agent on ppc64le
[
https://issues.apache.org/jira/browse/AMBARI-21296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143698#comment-16143698
]
Hadoop QA commented on AMBARI-21296:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884024/AMBARI-21296-1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-agent ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12072//console
This message is automatically generated.
> Python tests fail for ambari-server and ambari-agent on ppc64le
> ---
>
> Key: AMBARI-21296
> URL: https://issues.apache.org/jira/browse/AMBARI-21296
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 3.0.0
> Environment: $ uname -a
> Linux pts00607-vm4 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15
> 17:42:36 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Pravin Dsilva
>Assignee: Andrew Onischuk
> Labels: powerpc, ppc64le
> Fix For: 3.0.0
>
> Attachments: AMBARI-21296-1.patch, AMBARI-21296.patch
>
>
> There are 78 python test failures in Ambari agent for ppc64le
> Error:
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-agent/src/test/python/resource_management/TestXmlConfigResource.py",
> line 68, in test_action_create_empty_xml_config
> configuration_attributes={}
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/core/environment.py",
> line 118, in run_action
> resource.provider)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/core/providers/__init__.py",
> line 93, in find_provider
> if resource in os_family_provider:
> UnboundLocalError: local variable 'os_family_provider' referenced before
> assignment
> {code}
> In Ambari-server, the below tests fail:
> {code:java}
> ERROR: test_configure_default (test_ganglia_server.TestGangliaServer)
> --
> Traceback (most recent call last):
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/2.0.6/GANGLIA/test_ganglia_server.py",
> line 37, in test_configure_default
> target = RMFTestCase.TARGET_COMMON_SERVICES
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
> line 155, in executeScript
> method(RMFTestCase.env, *command_args)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/libraries/script/script.py",
> line 120, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/GANGLIA/3.5.0/package/scripts/ganglia_server.py",
> line 78, in configure
> change_permission()
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/GANGLIA/3.5.0/package/scripts/ganglia_server.py",
> line 93, in change_permission
> Directory(params.dwoo_path,
> AttributeError: 'module' object has no attribute 'dwoo_path'
> ERROR: test_install_default (test_ganglia_server.TestGangliaServer)
> --
> Traceback (most recent call last):
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/2.0.6/GANGLIA/test_ganglia_server.py",
> line 79, in test_install_default
> target = RMFTestCase.TARGET_COMMON_SERVICES
[jira] [Commented] (AMBARI-21777) Remove Ambiguous Repository Version When Creating Clusters via Blueprints
[
https://issues.apache.org/jira/browse/AMBARI-21777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143677#comment-16143677
]
Hudson commented on AMBARI-21777:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #71 (See
[https://builds.apache.org/job/Ambari-branch-2.6/71/])
AMBARI-21777 Remove Ambiguous Repository Version When Creating Clusters
(hapylestat:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=24639dd02bfa8c60e972569515f01fae0679b598])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterInstallWithoutStartOnComponentLevelTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterDeployWithStartOnlyTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/topology/ClusterInstallWithoutStartTest.java
> Remove Ambiguous Repository Version When Creating Clusters via Blueprints
> -
>
> Key: AMBARI-21777
> URL: https://issues.apache.org/jira/browse/AMBARI-21777
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21777-2.6.patch, AMBARI-21777-2.6-UT-FIX.patch,
> AMBARI-21777.patch
>
>
> When creating a new cluster via a blueprint, we currently use a combination
> of stack and version:
> {code}
> {
> "blueprint" : "foo",
> "repository_version": "2.5.0.0-1237",
> "host_groups" :[
> {
> "name" : "host_group_1",
> "hosts" : [
> {
> "fqdn" : "c6401.ambari.apache.org"
> },
> {
> "fqdn" : "c6402.ambari.apache.org"
> },
> {
> "fqdn" : "c6403.ambari.apache.org"
> }
> ]
> }
> ]
> }
> {code}
> We lookup the repository using a query by stack/version. We could instead
> also take a repo ID which removes any ambiguity.
> Something like:
> {code}
> {
> "blueprint" : "foo",
> "repository_id": 1,
> "host_groups" :[
> {
> "name" : "host_group_1",
> "hosts" : [
> {
> "fqdn" : "c6401.ambari.apache.org"
> },
> {
> "fqdn" : "c6402.ambari.apache.org"
> },
> {
> "fqdn" : "c6403.ambari.apache.org"
> }
> ]
> }
> ]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21777) Remove Ambiguous Repository Version When Creating Clusters via Blueprints
[
https://issues.apache.org/jira/browse/AMBARI-21777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143649#comment-16143649
]
Dmytro Grinenko commented on AMBARI-21777:
--
ut fix committed to 2.6:
To https://git-wip-us.apache.org/repos/asf/ambari.git
e55745f3e6..24639dd02b branch-2.6 -> branch-2.6
> Remove Ambiguous Repository Version When Creating Clusters via Blueprints
> -
>
> Key: AMBARI-21777
> URL: https://issues.apache.org/jira/browse/AMBARI-21777
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21777-2.6.patch, AMBARI-21777-2.6-UT-FIX.patch,
> AMBARI-21777.patch
>
>
> When creating a new cluster via a blueprint, we currently use a combination
> of stack and version:
> {code}
> {
> "blueprint" : "foo",
> "repository_version": "2.5.0.0-1237",
> "host_groups" :[
> {
> "name" : "host_group_1",
> "hosts" : [
> {
> "fqdn" : "c6401.ambari.apache.org"
> },
> {
> "fqdn" : "c6402.ambari.apache.org"
> },
> {
> "fqdn" : "c6403.ambari.apache.org"
> }
> ]
> }
> ]
> }
> {code}
> We lookup the repository using a query by stack/version. We could instead
> also take a repo ID which removes any ambiguity.
> Something like:
> {code}
> {
> "blueprint" : "foo",
> "repository_id": 1,
> "host_groups" :[
> {
> "name" : "host_group_1",
> "hosts" : [
> {
> "fqdn" : "c6401.ambari.apache.org"
> },
> {
> "fqdn" : "c6402.ambari.apache.org"
> },
> {
> "fqdn" : "c6403.ambari.apache.org"
> }
> ]
> }
> ]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21704) Upgrade Wizard Has Incorrect Title
[
https://issues.apache.org/jira/browse/AMBARI-21704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143645#comment-16143645
]
Hudson commented on AMBARI-21704:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7947 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7947/])
AMBARI-21704 Upgrade Wizard Has Incorrect Title. (atkach) (atkach:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6b5232088c87d07eaa8b740d12a35c3d1b171590])
* (edit) ambari-web/app/utils/ajax/ajax.js
* (edit)
ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js
* (edit)
ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js
* (edit)
ambari-web/test/views/main/admin/stack_upgrade/upgrade_version_box_view_test.js
* (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js
* (edit) ambari-web/app/messages.js
> Upgrade Wizard Has Incorrect Title
> --
>
> Key: AMBARI-21704
> URL: https://issues.apache.org/jira/browse/AMBARI-21704
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.3
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.3
>
> Attachments: AMBARI-21704.patch, Screen Shot 2017-08-03 at 1.53.31
> PM.png
>
>
> Perform an Express {{PATCH}} upgrade. The upgrade wizard dialog will have an
> incorrect title of "Upgrade to Express Upgrade". I would have expected
> something like:
> - Express Upgrade to HDP-2.5.4.0-1234
> - Express Patch Upgrade to HDP-2.5.4.0-1234
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21709) Finalize Warns that it is Permanent Even For PATCH Upgrades
[
https://issues.apache.org/jira/browse/AMBARI-21709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143647#comment-16143647
]
Hudson commented on AMBARI-21709:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7947 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7947/])
AMBARI-21709 Finalize Warns that it is Permanent Even For PATCH (atkach:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2a57959f5b8ddaa545dba1b5496f82902fa0e75c])
* (edit) ambari-web/app/messages.js
* (edit)
ambari-web/app/templates/main/admin/stack_upgrade/stack_upgrade_wizard.hbs
* (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_wizard_view.js
> Finalize Warns that it is Permanent Even For PATCH Upgrades
> ---
>
> Key: AMBARI-21709
> URL: https://issues.apache.org/jira/browse/AMBARI-21709
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.3
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.3
>
> Attachments: AMBARI-21709.patch, Screen Shot 2017-08-03 at 2.01.52
> PM.png
>
>
> Perform either a {{PATCH}} or {{MAINT}} upgrade and get to Finalize. The
> upgrade wizard warns that finalization is permanent.
> {quote}
> Your cluster version has been upgraded. Click on Finalize when you are ready
> to finalize the upgrade and commit to the new version. You are strongly
> encouraged to run tests on your cluster to ensure it is fully operational
> before finalizing. You cannot go back to the original version once the
> upgrade is finalized.
> {quote}
> This is not true for certain upgrade types. Finalization is a required step,
> yes, but you can still revert {{PATCH}} and {{MAINT}} upgrades that have
> finalized. The message for these types should read something like:
> {quote}
> The {{PATCH}} upgrade to HDP-2.5.4.0-1234 is ready to be completed. After
> finalization, the patch can be reverted from the Stacks and Versions page if
> it is no longer required."
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21739) Patch Reversion Dialog Has Some Clipping
[ https://issues.apache.org/jira/browse/AMBARI-21739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143646#comment-16143646 ] Hudson commented on AMBARI-21739: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7947 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7947/]) AMBARI-21739 Patch Reversion Dialog Has Some Clipping. (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b4f0c5abe323f93aab29c814b1a05d9368342a2e]) * (edit) ambari-web/app/styles/stack_versions.less * (edit) ambari-web/app/templates/common/modal_popups/revert_patch_upgrade_confirmation.hbs > Patch Reversion Dialog Has Some Clipping > > > Key: AMBARI-21739 > URL: https://issues.apache.org/jira/browse/AMBARI-21739 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.3 > > Attachments: AMBARI-21739.patch, Screen Shot 2017-08-15 at 11.00.07 > PM.png > > > When reverting a patch, the confirmation dialog has some clipped text. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21700) Expose Patch Reversion in the Web Client
[ https://issues.apache.org/jira/browse/AMBARI-21700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143644#comment-16143644 ] Hudson commented on AMBARI-21700: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7947 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7947/]) AMBARI-21700 Expose Patch Reversion in the Web Client. (atkach) (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8f0bcc0197a5aee36aa0a38b8e8b16dbda1182f0]) * (edit) ambari-web/app/styles/stack_versions.less * (edit) ambari-web/app/models/stack_version/stack_upgrade_history.js * (add) ambari-web/app/templates/common/modal_popups/revert_patch_upgrade_confirmation.hbs * (edit) ambari-web/app/messages.js * (edit) ambari-web/test/controllers/global/cluster_controller_test.js * (edit) ambari-web/test/views/main/admin/stack_upgrade/upgrade_version_box_view_test.js * (edit) ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js * (edit) ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js * (edit) ambari-web/app/routes/stack_upgrade_routes.js * (edit) ambari-web/app/mappers/stack_upgrade_history_mapper.js * (edit) ambari-web/app/utils/ajax/ajax.js * (edit) ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js * (edit) ambari-web/app/controllers/global/cluster_controller.js > Expose Patch Reversion in the Web Client > > > Key: AMBARI-21700 > URL: https://issues.apache.org/jira/browse/AMBARI-21700 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.5.3 > > Attachments: AMBARI-21700.patch, patch-revert.gif > > > The web client will need to expose the ability to revert a patch which was > successfully applied to one or more services. Patch upgrades allows one or > more services to effectively be "patched" to a new version. Some facts: > - Patching will only apply to the current stack. If the cluster was installed > with HDP 2.5, then all patches must be scoped to 2.5.x.y - you cannot patch > outside the stack. > - Each service/component now exposes the repository version they are on. > The following work should be scoped in this Jira. If the scope turns out to > be too great, then it can be broken up into several JIras: > - The stacks and versions page will change to show multiple "CURRENT" stacks. > - The most recent patch will be able to be reverted. The revert button will > only show for the newest applied patch. Once reverted, the prior patch can be > reverted now. > - If a full stack upgrade is performed, then the bar is reset, regardless the > version upgraded to. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21777) Remove Ambiguous Repository Version When Creating Clusters via Blueprints
[
https://issues.apache.org/jira/browse/AMBARI-21777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-21777:
-
Attachment: AMBARI-21777-2.6-UT-FIX.patch
> Remove Ambiguous Repository Version When Creating Clusters via Blueprints
> -
>
> Key: AMBARI-21777
> URL: https://issues.apache.org/jira/browse/AMBARI-21777
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21777-2.6.patch, AMBARI-21777-2.6-UT-FIX.patch,
> AMBARI-21777.patch
>
>
> When creating a new cluster via a blueprint, we currently use a combination
> of stack and version:
> {code}
> {
> "blueprint" : "foo",
> "repository_version": "2.5.0.0-1237",
> "host_groups" :[
> {
> "name" : "host_group_1",
> "hosts" : [
> {
> "fqdn" : "c6401.ambari.apache.org"
> },
> {
> "fqdn" : "c6402.ambari.apache.org"
> },
> {
> "fqdn" : "c6403.ambari.apache.org"
> }
> ]
> }
> ]
> }
> {code}
> We lookup the repository using a query by stack/version. We could instead
> also take a repo ID which removes any ambiguity.
> Something like:
> {code}
> {
> "blueprint" : "foo",
> "repository_id": 1,
> "host_groups" :[
> {
> "name" : "host_group_1",
> "hosts" : [
> {
> "fqdn" : "c6401.ambari.apache.org"
> },
> {
> "fqdn" : "c6402.ambari.apache.org"
> },
> {
> "fqdn" : "c6403.ambari.apache.org"
> }
> ]
> }
> ]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21647) PATCH upgrade with version less than current should be displayed
[ https://issues.apache.org/jira/browse/AMBARI-21647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143601#comment-16143601 ] Hudson commented on AMBARI-21647: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #7946 (See [https://builds.apache.org/job/Ambari-trunk-Commit/7946/]) AMBARI-21647 PATCH upgrade with version less than current should be (atkach: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cad25398cadc94e19cbdc4e7751d6030a4e733e3]) * (edit) ambari-web/app/views/main/admin/stack_upgrade/versions_view.js > PATCH upgrade with version less than current should be displayed > > > Key: AMBARI-21647 > URL: https://issues.apache.org/jira/browse/AMBARI-21647 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.3 > > Attachments: AMBARI-21647.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-21825) Fix new logsearch UI rat issues
Olivér Szabó created AMBARI-21825: - Summary: Fix new logsearch UI rat issues Key: AMBARI-21825 URL: https://issues.apache.org/jira/browse/AMBARI-21825 Project: Ambari Issue Type: Bug Affects Versions: 3.0.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21296) Python tests fail for ambari-server and ambari-agent on ppc64le
[
https://issues.apache.org/jira/browse/AMBARI-21296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143599#comment-16143599
]
Pravin Dsilva commented on AMBARI-21296:
The existing patch was not getting applied due to code changes. I have
attached a new updated patch, however, the test "test_registration_build"
continues to fail.
> Python tests fail for ambari-server and ambari-agent on ppc64le
> ---
>
> Key: AMBARI-21296
> URL: https://issues.apache.org/jira/browse/AMBARI-21296
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 3.0.0
> Environment: $ uname -a
> Linux pts00607-vm4 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15
> 17:42:36 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Pravin Dsilva
>Assignee: Andrew Onischuk
> Labels: powerpc, ppc64le
> Fix For: 3.0.0
>
> Attachments: AMBARI-21296-1.patch, AMBARI-21296.patch
>
>
> There are 78 python test failures in Ambari agent for ppc64le
> Error:
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-agent/src/test/python/resource_management/TestXmlConfigResource.py",
> line 68, in test_action_create_empty_xml_config
> configuration_attributes={}
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/core/environment.py",
> line 118, in run_action
> resource.provider)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/core/providers/__init__.py",
> line 93, in find_provider
> if resource in os_family_provider:
> UnboundLocalError: local variable 'os_family_provider' referenced before
> assignment
> {code}
> In Ambari-server, the below tests fail:
> {code:java}
> ERROR: test_configure_default (test_ganglia_server.TestGangliaServer)
> --
> Traceback (most recent call last):
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/2.0.6/GANGLIA/test_ganglia_server.py",
> line 37, in test_configure_default
> target = RMFTestCase.TARGET_COMMON_SERVICES
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
> line 155, in executeScript
> method(RMFTestCase.env, *command_args)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/libraries/script/script.py",
> line 120, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/GANGLIA/3.5.0/package/scripts/ganglia_server.py",
> line 78, in configure
> change_permission()
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/GANGLIA/3.5.0/package/scripts/ganglia_server.py",
> line 93, in change_permission
> Directory(params.dwoo_path,
> AttributeError: 'module' object has no attribute 'dwoo_path'
> ERROR: test_install_default (test_ganglia_server.TestGangliaServer)
> --
> Traceback (most recent call last):
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/2.0.6/GANGLIA/test_ganglia_server.py",
> line 79, in test_install_default
> target = RMFTestCase.TARGET_COMMON_SERVICES
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
> line 155, in executeScript
> method(RMFTestCase.env, *command_args)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/GANGLIA/3.5.0/package/scripts/ganglia_server.py",
> line 41, in install
> self.configure(env)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/libraries/script/script.py",
> line 120, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/jenkins/workspace/ambari-
[jira] [Updated] (AMBARI-21296) Python tests fail for ambari-server and ambari-agent on ppc64le
[
https://issues.apache.org/jira/browse/AMBARI-21296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pravin Dsilva updated AMBARI-21296:
---
Attachment: AMBARI-21296-1.patch
> Python tests fail for ambari-server and ambari-agent on ppc64le
> ---
>
> Key: AMBARI-21296
> URL: https://issues.apache.org/jira/browse/AMBARI-21296
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-server
>Affects Versions: 3.0.0
> Environment: $ uname -a
> Linux pts00607-vm4 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15
> 17:42:36 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
>Reporter: Pravin Dsilva
>Assignee: Andrew Onischuk
> Labels: powerpc, ppc64le
> Fix For: 3.0.0
>
> Attachments: AMBARI-21296-1.patch, AMBARI-21296.patch
>
>
> There are 78 python test failures in Ambari agent for ppc64le
> Error:
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-agent/src/test/python/resource_management/TestXmlConfigResource.py",
> line 68, in test_action_create_empty_xml_config
> configuration_attributes={}
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/core/base.py",
> line 155, in __init__
> self.env.run()
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/core/environment.py",
> line 118, in run_action
> resource.provider)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/core/providers/__init__.py",
> line 93, in find_provider
> if resource in os_family_provider:
> UnboundLocalError: local variable 'os_family_provider' referenced before
> assignment
> {code}
> In Ambari-server, the below tests fail:
> {code:java}
> ERROR: test_configure_default (test_ganglia_server.TestGangliaServer)
> --
> Traceback (most recent call last):
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/2.0.6/GANGLIA/test_ganglia_server.py",
> line 37, in test_configure_default
> target = RMFTestCase.TARGET_COMMON_SERVICES
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
> line 155, in executeScript
> method(RMFTestCase.env, *command_args)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/libraries/script/script.py",
> line 120, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/GANGLIA/3.5.0/package/scripts/ganglia_server.py",
> line 78, in configure
> change_permission()
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/GANGLIA/3.5.0/package/scripts/ganglia_server.py",
> line 93, in change_permission
> Directory(params.dwoo_path,
> AttributeError: 'module' object has no attribute 'dwoo_path'
> ERROR: test_install_default (test_ganglia_server.TestGangliaServer)
> --
> Traceback (most recent call last):
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/2.0.6/GANGLIA/test_ganglia_server.py",
> line 79, in test_install_default
> target = RMFTestCase.TARGET_COMMON_SERVICES
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
> line 155, in executeScript
> method(RMFTestCase.env, *command_args)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/GANGLIA/3.5.0/package/scripts/ganglia_server.py",
> line 41, in install
> self.configure(env)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-common/src/main/python/resource_management/libraries/script/script.py",
> line 120, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/jenkins/workspace/ambari-trunk/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/GANGLIA/3.5.0/package/scripts/ganglia_server.py",
> line 78, in configure
> change_permissi
[jira] [Commented] (AMBARI-21709) Finalize Warns that it is Permanent Even For PATCH Upgrades
[
https://issues.apache.org/jira/browse/AMBARI-21709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143594#comment-16143594
]
Andrii Tkach commented on AMBARI-21709:
---
committed to trunk
> Finalize Warns that it is Permanent Even For PATCH Upgrades
> ---
>
> Key: AMBARI-21709
> URL: https://issues.apache.org/jira/browse/AMBARI-21709
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.3
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.3
>
> Attachments: AMBARI-21709.patch, Screen Shot 2017-08-03 at 2.01.52
> PM.png
>
>
> Perform either a {{PATCH}} or {{MAINT}} upgrade and get to Finalize. The
> upgrade wizard warns that finalization is permanent.
> {quote}
> Your cluster version has been upgraded. Click on Finalize when you are ready
> to finalize the upgrade and commit to the new version. You are strongly
> encouraged to run tests on your cluster to ensure it is fully operational
> before finalizing. You cannot go back to the original version once the
> upgrade is finalized.
> {quote}
> This is not true for certain upgrade types. Finalization is a required step,
> yes, but you can still revert {{PATCH}} and {{MAINT}} upgrades that have
> finalized. The message for these types should read something like:
> {quote}
> The {{PATCH}} upgrade to HDP-2.5.4.0-1234 is ready to be completed. After
> finalization, the patch can be reverted from the Stacks and Versions page if
> it is no longer required."
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21739) Patch Reversion Dialog Has Some Clipping
[ https://issues.apache.org/jira/browse/AMBARI-21739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143591#comment-16143591 ] Andrii Tkach commented on AMBARI-21739: --- committed to trunk > Patch Reversion Dialog Has Some Clipping > > > Key: AMBARI-21739 > URL: https://issues.apache.org/jira/browse/AMBARI-21739 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Andrii Tkach >Assignee: Andrii Tkach > Fix For: 2.5.3 > > Attachments: AMBARI-21739.patch, Screen Shot 2017-08-15 at 11.00.07 > PM.png > > > When reverting a patch, the confirmation dialog has some clipped text. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21704) Upgrade Wizard Has Incorrect Title
[
https://issues.apache.org/jira/browse/AMBARI-21704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143587#comment-16143587
]
Andrii Tkach commented on AMBARI-21704:
---
committed to trunk
> Upgrade Wizard Has Incorrect Title
> --
>
> Key: AMBARI-21704
> URL: https://issues.apache.org/jira/browse/AMBARI-21704
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.3
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Fix For: 2.5.3
>
> Attachments: AMBARI-21704.patch, Screen Shot 2017-08-03 at 1.53.31
> PM.png
>
>
> Perform an Express {{PATCH}} upgrade. The upgrade wizard dialog will have an
> incorrect title of "Upgrade to Express Upgrade". I would have expected
> something like:
> - Express Upgrade to HDP-2.5.4.0-1234
> - Express Patch Upgrade to HDP-2.5.4.0-1234
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21700) Expose Patch Reversion in the Web Client
[ https://issues.apache.org/jira/browse/AMBARI-21700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143575#comment-16143575 ] Andrii Tkach commented on AMBARI-21700: --- committed to trunk > Expose Patch Reversion in the Web Client > > > Key: AMBARI-21700 > URL: https://issues.apache.org/jira/browse/AMBARI-21700 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.5.3 > > Attachments: AMBARI-21700.patch, patch-revert.gif > > > The web client will need to expose the ability to revert a patch which was > successfully applied to one or more services. Patch upgrades allows one or > more services to effectively be "patched" to a new version. Some facts: > - Patching will only apply to the current stack. If the cluster was installed > with HDP 2.5, then all patches must be scoped to 2.5.x.y - you cannot patch > outside the stack. > - Each service/component now exposes the repository version they are on. > The following work should be scoped in this Jira. If the scope turns out to > be too great, then it can be broken up into several JIras: > - The stacks and versions page will change to show multiple "CURRENT" stacks. > - The most recent patch will be able to be reverted. The revert button will > only show for the newest applied patch. Once reverted, the prior patch can be > reverted now. > - If a full stack upgrade is performed, then the bar is reset, regardless the > version upgraded to. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21647) PATCH upgrade with version less than current should be displayed
[ https://issues.apache.org/jira/browse/AMBARI-21647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143563#comment-16143563 ] Andrii Tkach commented on AMBARI-21647: --- committed to trunk > PATCH upgrade with version less than current should be displayed > > > Key: AMBARI-21647 > URL: https://issues.apache.org/jira/browse/AMBARI-21647 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.5.3 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Fix For: 2.5.3 > > Attachments: AMBARI-21647.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21824) Make services as sub-resource of ServiceGroups and use Servicegroup while doing Creation, Update and retrieval of HostComponents and ServiceComponents.
[ https://issues.apache.org/jira/browse/AMBARI-21824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21824: - Description: ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. This Task involves : - moving *Services* which was earlier a sub-resource of *Cluster* under *ServiceGroup* now, and - using *Servicegroup* while doing Creation, Update and retrieval of *HostComponents* and *ServiceComponents*. The new API calls will be the following: - *Service:* http://:/api/v1/clusters//*servicegroups/*/services http://:/api/v1/clusters//*servicegroups/*/services/ *ServiceComponent:* http://:/api/v1/clusters//*servicegroups/*/services//components/ http://:/api/v1/clusters//*servicegroups/*/services//components/ZOOKEEPER_SERVER - *HostComponent:* (API remains same, but has notion of servicegroup in Ambari backend) http://:/api/v1/clusters/c1/hosts//host_components/ http://:/api/v1/clusters/c1/hosts//host_components/ The change also includes UI changes as well, which create a *default ServiceGroup named 'core'*, and all services created goes under it. was: ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. This Task involves : - moving *Services* which was earlier a sub-resource of *Cluster* under *ServiceGroup* now, and - using *Servicegroup* while doing Creation, Update and retrieval of *HostComponents* and *ServiceComponents*. The new API calls will be the following: - *Service:* http://:/api/v1/clusters//*servicegroups/*/services http://:/api/v1/clusters//*servicegroups/*/services/ *ServiceComponent:* http://:/api/v1/clusters//*servicegroups/*/services//components/ http://:/api/v1/clusters//*servicegroups/*/services//components/ZOOKEEPER_SERVER - *HostComponent:* (API remains same, but has notion of servicegroup in Ambari backend) http://:/api/v1/clusters/c1/hosts//host_components/ http://:/api/v1/clusters/c1/hosts//host_components/ > Make services as sub-resource of ServiceGroups and use Servicegroup while > doing Creation, Update and retrieval of HostComponents and ServiceComponents. > --- > > Key: AMBARI-21824 > URL: https://issues.apache.org/jira/browse/AMBARI-21824 > Project: Ambari > Issue Type: Task > Components: ambari-server, ambari-web >Affects Versions: 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 3.0.0 > > > ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. > This Task involves : > - moving *Services* which was earlier a sub-resource of *Cluster* under > *ServiceGroup* now, and > - using *Servicegroup* while doing Creation, Update and retrieval of > *HostComponents* and *ServiceComponents*. > The new API calls will be the following: > - > *Service:* > http://:/api/v1/clusters//*servicegroups/*/services > http://:/api/v1/clusters//*servicegroups/*/services/ > *ServiceComponent:* > http://:/api/v1/clusters//*servicegroups/*/services//components/ > http://:/api/v1/clusters//*servicegroups/*/services//components/ZOOKEEPER_SERVER > - > *HostComponent:* (API remains same, but has notion of servicegroup in Ambari > backend) > http://:/api/v1/clusters/c1/hosts//host_components/ > http://:/api/v1/clusters/c1/hosts//host_components/ > The change also includes UI changes as well, which create a *default > ServiceGroup named 'core'*, and all services created goes under it. -- This message was
[jira] [Updated] (AMBARI-21824) Make services as sub-resource of ServiceGroups and use Servicegroup while doing Creation, Update and retrieval of HostComponents and ServiceComponents.
[ https://issues.apache.org/jira/browse/AMBARI-21824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21824: - Description: ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. This Task involves : - moving *Services* which was earlier a sub-resource of *Cluster* under *ServiceGroup* now, and - using *Servicegroup* while doing Creation, Update and retrieval of *HostComponents* and *ServiceComponents*. The new API calls will be the following: - *Service:* http://:/api/v1/clusters//*servicegroups/*/services http://:/api/v1/clusters//*servicegroups/*/services/ *ServiceComponent:* http://:/api/v1/clusters//*servicegroups/*/services//components/ http://:/api/v1/clusters//*servicegroups/*/services//components/ZOOKEEPER_SERVER - *HostComponent:* (API remains same, but has notion of servicegroup in Ambari backend) http://:/api/v1/clusters/c1/hosts//host_components/ http://:/api/v1/clusters/c1/hosts//host_components/ - The change also includes UI changes as well, which create a *default ServiceGroup named 'core'*, and all services created goes under it. was: ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. This Task involves : - moving *Services* which was earlier a sub-resource of *Cluster* under *ServiceGroup* now, and - using *Servicegroup* while doing Creation, Update and retrieval of *HostComponents* and *ServiceComponents*. The new API calls will be the following: - *Service:* http://:/api/v1/clusters//*servicegroups/*/services http://:/api/v1/clusters//*servicegroups/*/services/ *ServiceComponent:* http://:/api/v1/clusters//*servicegroups/*/services//components/ http://:/api/v1/clusters//*servicegroups/*/services//components/ZOOKEEPER_SERVER - *HostComponent:* (API remains same, but has notion of servicegroup in Ambari backend) http://:/api/v1/clusters/c1/hosts//host_components/ http://:/api/v1/clusters/c1/hosts//host_components/ The change also includes UI changes as well, which create a *default ServiceGroup named 'core'*, and all services created goes under it. > Make services as sub-resource of ServiceGroups and use Servicegroup while > doing Creation, Update and retrieval of HostComponents and ServiceComponents. > --- > > Key: AMBARI-21824 > URL: https://issues.apache.org/jira/browse/AMBARI-21824 > Project: Ambari > Issue Type: Task > Components: ambari-server, ambari-web >Affects Versions: 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 3.0.0 > > > ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. > This Task involves : > - moving *Services* which was earlier a sub-resource of *Cluster* under > *ServiceGroup* now, and > - using *Servicegroup* while doing Creation, Update and retrieval of > *HostComponents* and *ServiceComponents*. > The new API calls will be the following: > - > *Service:* > http://:/api/v1/clusters//*servicegroups/*/services > http://:/api/v1/clusters//*servicegroups/*/services/ > *ServiceComponent:* > http://:/api/v1/clusters//*servicegroups/*/services//components/ > http://:/api/v1/clusters//*servicegroups/*/services//components/ZOOKEEPER_SERVER > - > *HostComponent:* (API remains same, but has notion of servicegroup in Ambari > backend) > http://:/api/v1/clusters/c1/hosts//host_components/ > http://:/api/v1/clusters/c1/hosts//host_components/ > - The change also inc
[jira] [Updated] (AMBARI-21824) Make services as sub-resource of ServiceGroups and use Servicegroup while doing Creation, Update and retrieval of HostComponents and ServiceComponents.
[ https://issues.apache.org/jira/browse/AMBARI-21824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21824: - Description: ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. This Task involves : - moving *Services* which was earlier a sub-resource of *Cluster* under *ServiceGroup* now, and - using *Servicegroup* while doing Creation, Update and retrieval of *HostComponents* and *ServiceComponents*. The new API calls will be the following: - *Service:* http://:/api/v1/clusters//*servicegroups/*/services http://:/api/v1/clusters//*servicegroups/*/services/ *ServiceComponent:* http://:/api/v1/clusters//*servicegroups/*/services//components/ http://:/api/v1/clusters//*servicegroups/*/services//components/ZOOKEEPER_SERVER - *HostComponent:* (API remains same, but has notion of servicegroup in Ambari backend) http://:/api/v1/clusters/c1/hosts//host_components/ http://:/api/v1/clusters/c1/hosts//host_components/ was: ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. This Task involves : - moving *Services* which was earlier a sub-resource of *Cluster* under *ServiceGroup* now, and - using *Servicegroup* while doing Creation, Update and retrieval of *HostComponents* and *ServiceComponents*. The new API calls will be the following: *Service:* http://:/api/v1/clusters//*servicegroups/*/services http://:/api/v1/clusters//*servicegroups/*/services/ *ServiceComponent:* http://:/api/v1/clusters//*servicegroups/*/services//components/ http://:/api/v1/clusters//*servicegroups/*/services//components/ZOOKEEPER_SERVER --- *HostComponent:* (API remains same, but has notion of servicegroup in Ambari backend) http://:/api/v1/clusters/c1/hosts//host_components/ http://:/api/v1/clusters/c1/hosts//host_components/ > Make services as sub-resource of ServiceGroups and use Servicegroup while > doing Creation, Update and retrieval of HostComponents and ServiceComponents. > --- > > Key: AMBARI-21824 > URL: https://issues.apache.org/jira/browse/AMBARI-21824 > Project: Ambari > Issue Type: Task > Components: ambari-server, ambari-web >Affects Versions: 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 3.0.0 > > > ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. > This Task involves : > - moving *Services* which was earlier a sub-resource of *Cluster* under > *ServiceGroup* now, and > - using *Servicegroup* while doing Creation, Update and retrieval of > *HostComponents* and *ServiceComponents*. > The new API calls will be the following: > - > *Service:* > http://:/api/v1/clusters//*servicegroups/*/services > http://:/api/v1/clusters//*servicegroups/*/services/ > *ServiceComponent:* > http://:/api/v1/clusters//*servicegroups/*/services//components/ > http://:/api/v1/clusters//*servicegroups/*/services//components/ZOOKEEPER_SERVER > - > *HostComponent:* (API remains same, but has notion of servicegroup in Ambari > backend) > http://:/api/v1/clusters/c1/hosts//host_components/ > http://:/api/v1/clusters/c1/hosts//host_components/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21824) Make services as sub-resource of ServiceGroups and use Servicegroup while doing Creation, Update and retrieval of HostComponents and ServiceComponents.
[ https://issues.apache.org/jira/browse/AMBARI-21824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21824: - Description: ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. This Task involves : - moving *Services* which was earlier a sub-resource of *Cluster* under *ServiceGroup* now, and - using *Servicegroup* while doing Creation, Update and retrieval of *HostComponents* and *ServiceComponents*. The new API calls will be the following: *Service:* http://:/api/v1/clusters//*servicegroups/*/services http://:/api/v1/clusters//*servicegroups/*/services/ *ServiceComponent:* http://:/api/v1/clusters//*servicegroups/*/services//components/ http://:/api/v1/clusters//*servicegroups/*/services//components/ZOOKEEPER_SERVER --- *HostComponent:* (API remains same, but has notion of servicegroup in Ambari backend) http://:/api/v1/clusters/c1/hosts//host_components/ http://:/api/v1/clusters/c1/hosts//host_components/ was: ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. This Task involves : - moving *Services* which was earlier a sub-resource of *Cluster* under *ServiceGroup* now, and - using *Servicegroup* while doing Creation, Update and retrieval of *HostComponents* and *ServiceComponents*. The new API calls will be the following: *Service:* http://:/api/v1/clusters//*servicegroups/*/services http://:/api/v1/clusters//*servicegroups/*/services/ *ServiceComponent:* http://:/api/v1/clusters//*servicegroups/*/services//components/ http://:/api/v1/clusters//*servicegroups/*/services//components/ZOOKEEPER_SERVER *HostComponent:* (API remains same, but has notion of servicegroup in Ambari backend) http://:/api/v1/clusters/c1/hosts//host_components/ http://:/api/v1/clusters/c1/hosts//host_components/ > Make services as sub-resource of ServiceGroups and use Servicegroup while > doing Creation, Update and retrieval of HostComponents and ServiceComponents. > --- > > Key: AMBARI-21824 > URL: https://issues.apache.org/jira/browse/AMBARI-21824 > Project: Ambari > Issue Type: Task > Components: ambari-server, ambari-web >Affects Versions: 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 3.0.0 > > > ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. > This Task involves : > - moving *Services* which was earlier a sub-resource of *Cluster* under > *ServiceGroup* now, and > - using *Servicegroup* while doing Creation, Update and retrieval of > *HostComponents* and *ServiceComponents*. > The new API calls will be the following: > *Service:* > http://:/api/v1/clusters//*servicegroups/*/services > http://:/api/v1/clusters//*servicegroups/*/services/ > *ServiceComponent:* > http://:/api/v1/clusters//*servicegroups/*/services//components/ > http://:/api/v1/clusters//*servicegroups/*/services//components/ZOOKEEPER_SERVER > --- > *HostComponent:* (API remains same, but has notion of servicegroup in Ambari > backend) > http://:/api/v1/clusters/c1/hosts//host_components/ > http://:/api/v1/clusters/c1/hosts//host_components/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21824) Make services as sub-resource of ServiceGroups and use Servicegroup while doing Creation, Update and retrieval of HostComponents and ServiceComponents.
[ https://issues.apache.org/jira/browse/AMBARI-21824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21824: - Description: ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. This Task involves : - moving *Services* which was earlier a sub-resource of *Cluster* under *ServiceGroup* now, and - using *Servicegroup* while doing Creation, Update and retrieval of *HostComponents* and *ServiceComponents*. The new API calls will be the following: *Service:* http://:/api/v1/clusters//*servicegroups/*/services http://:/api/v1/clusters//*servicegroups/*/services/ *ServiceComponent:* http://:/api/v1/clusters//*servicegroups/*/services//components/ http://:/api/v1/clusters//*servicegroups/*/services//components/ZOOKEEPER_SERVER *HostComponent:* (API remains same, but has notion of servicegroup in Ambari backend) http://:/api/v1/clusters/c1/hosts//host_components/ http://:/api/v1/clusters/c1/hosts//host_components/ was: ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. This Task involves : - moving *Services* which was earlier a sub-resource of *Cluster* under *ServiceGroup* now, and - using *Servicegroup* while doing Creation, Update and retrieval of *HostComponents* and *ServiceComponents*. The new API calls will be the following: *Service:* http://:/api/v1/clusters//*servicegroups/*/services http://:/api/v1/clusters//*servicegroups/*/services/ *ServiceComponent:* http://:/api/v1/clusters//*servicegroups/*/services//components/ http://:/api/v1/clusters//*servicegroups/*/services//components/ZOOKEEPER_SERVER *HostComponent:* http://:/api/v1/clusters/c1/hosts//host_components/ http://:/api/v1/clusters/c1/hosts//host_components/ > Make services as sub-resource of ServiceGroups and use Servicegroup while > doing Creation, Update and retrieval of HostComponents and ServiceComponents. > --- > > Key: AMBARI-21824 > URL: https://issues.apache.org/jira/browse/AMBARI-21824 > Project: Ambari > Issue Type: Task > Components: ambari-server, ambari-web >Affects Versions: 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 3.0.0 > > > ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. > This Task involves : > - moving *Services* which was earlier a sub-resource of *Cluster* under > *ServiceGroup* now, and > - using *Servicegroup* while doing Creation, Update and retrieval of > *HostComponents* and *ServiceComponents*. > The new API calls will be the following: > *Service:* > http://:/api/v1/clusters//*servicegroups/*/services > http://:/api/v1/clusters//*servicegroups/*/services/ > *ServiceComponent:* > http://:/api/v1/clusters//*servicegroups/*/services//components/ > http://:/api/v1/clusters//*servicegroups/*/services//components/ZOOKEEPER_SERVER > *HostComponent:* (API remains same, but has notion of servicegroup in Ambari > backend) > http://:/api/v1/clusters/c1/hosts//host_components/ > http://:/api/v1/clusters/c1/hosts//host_components/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21824) Make services as sub-resource of ServiceGroups and use Servicegroup while doing Creation, Update and retrieval of HostComponents and ServiceComponents.
[ https://issues.apache.org/jira/browse/AMBARI-21824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21824: - Description: ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. This Task involves : - moving *Services* which was earlier a sub-resource of *Cluster* under *ServiceGroup* now, and - using *Servicegroup* while doing Creation, Update and retrieval of *HostComponents* and *ServiceComponents*. The new API calls will be the following: *Service:* http://:/api/v1/clusters//*servicegroups/*/services http://:/api/v1/clusters//*servicegroups/*/services/ *ServiceComponent:* http://:/api/v1/clusters//*servicegroups/*/services//components/ http://:/api/v1/clusters//*servicegroups/*/services//components/ZOOKEEPER_SERVER *HostComponent:* http://:/api/v1/clusters/c1/hosts//host_components/ http://:/api/v1/clusters/c1/hosts//host_components/ was: ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. This Task involves : - moving *Services* which was earlier a sub-resource of *Cluster* under *ServiceGroup* now, and - using *Servicegroup* while doing Creation, Update and retrieval of *HostComponents* and *ServiceComponents*. The new API calls will be the following: *Service:* http://:/api/v1/clusters//servicegroups//services http://:/api/v1/clusters//servicegroups//services/ *ServiceComponent:* http://:/api/v1/clusters//servicegroups//services//components/ http://:/api/v1/clusters//servicegroups//services//components/ZOOKEEPER_SERVER *HostComponent:* http://:/api/v1/clusters/c1/hosts//host_components/ http://:/api/v1/clusters/c1/hosts//host_components/ > Make services as sub-resource of ServiceGroups and use Servicegroup while > doing Creation, Update and retrieval of HostComponents and ServiceComponents. > --- > > Key: AMBARI-21824 > URL: https://issues.apache.org/jira/browse/AMBARI-21824 > Project: Ambari > Issue Type: Task > Components: ambari-server, ambari-web >Affects Versions: 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 3.0.0 > > > ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. > This Task involves : > - moving *Services* which was earlier a sub-resource of *Cluster* under > *ServiceGroup* now, and > - using *Servicegroup* while doing Creation, Update and retrieval of > *HostComponents* and *ServiceComponents*. > The new API calls will be the following: > *Service:* > http://:/api/v1/clusters//*servicegroups/*/services > http://:/api/v1/clusters//*servicegroups/*/services/ > *ServiceComponent:* > http://:/api/v1/clusters//*servicegroups/*/services//components/ > http://:/api/v1/clusters//*servicegroups/*/services//components/ZOOKEEPER_SERVER > *HostComponent:* > http://:/api/v1/clusters/c1/hosts//host_components/ > http://:/api/v1/clusters/c1/hosts//host_components/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21824) Make services as sub-resource of ServiceGroups and use Servicegroup while doing Creation, Update and retrieval of HostComponents and ServiceComponents.
[ https://issues.apache.org/jira/browse/AMBARI-21824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21824: - Description: ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. This Task involves : - moving *Services* which was earlier a sub-resource of *Cluster* under *ServiceGroup* now, and - using *Servicegroup* while doing Creation, Update and retrieval of *HostComponents* and *ServiceComponents*. The new API calls will be the following: *Service:* http://:/api/v1/clusters//servicegroups//services http://:/api/v1/clusters//servicegroups//services/ *ServiceComponent:* http://:/api/v1/clusters//servicegroups//services//components/ http://:/api/v1/clusters//servicegroups//services//components/ZOOKEEPER_SERVER *HostComponent:* http://:/api/v1/clusters/c1/hosts//host_components/ http://:/api/v1/clusters/c1/hosts//host_components/ was: ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. This Task involves : - moving *Services* which was earlier a sub-resource of *Cluster* under *ServiceGroup* now, and - using *Servicegroup* while doing Creation, Update and retrieval of *HostComponents* and *ServiceComponents*. The new API calls will be the following: *Service:* http://:/api/v1/clusters//servicegroups//services http://:/api/v1/clusters//servicegroups//services/ ** > Make services as sub-resource of ServiceGroups and use Servicegroup while > doing Creation, Update and retrieval of HostComponents and ServiceComponents. > --- > > Key: AMBARI-21824 > URL: https://issues.apache.org/jira/browse/AMBARI-21824 > Project: Ambari > Issue Type: Task > Components: ambari-server, ambari-web >Affects Versions: 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 3.0.0 > > > ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. > This Task involves : > - moving *Services* which was earlier a sub-resource of *Cluster* under > *ServiceGroup* now, and > - using *Servicegroup* while doing Creation, Update and retrieval of > *HostComponents* and *ServiceComponents*. > The new API calls will be the following: > *Service:* > http://:/api/v1/clusters//servicegroups//services > http://:/api/v1/clusters//servicegroups//services/ > *ServiceComponent:* > http://:/api/v1/clusters//servicegroups//services//components/ > http://:/api/v1/clusters//servicegroups//services//components/ZOOKEEPER_SERVER > *HostComponent:* > http://:/api/v1/clusters/c1/hosts//host_components/ > http://:/api/v1/clusters/c1/hosts//host_components/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21824) Make services as sub-resource of ServiceGroups and use Servicegroup while doing Creation, Update and retrieval of HostComponents and ServiceComponents.
[ https://issues.apache.org/jira/browse/AMBARI-21824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21824: - Description: ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. This Task involves : - moving *Services* which was earlier a sub-resource of *Cluster* under *ServiceGroup* now, and - using *Servicegroup* while doing Creation, Update and retrieval of *HostComponents* and *ServiceComponents*. The new API calls will be the following: *Service:* http://:/api/v1/clusters//servicegroups//services http://:/api/v1/clusters//servicegroups//services/ ** was: ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. This Task involves : - moving *Services* which was earlier a sub-resource of *Cluster* under *ServiceGroup* now, and - The calls for > Make services as sub-resource of ServiceGroups and use Servicegroup while > doing Creation, Update and retrieval of HostComponents and ServiceComponents. > --- > > Key: AMBARI-21824 > URL: https://issues.apache.org/jira/browse/AMBARI-21824 > Project: Ambari > Issue Type: Task > Components: ambari-server, ambari-web >Affects Versions: 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 3.0.0 > > > ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. > This Task involves : > - moving *Services* which was earlier a sub-resource of *Cluster* under > *ServiceGroup* now, and > - using *Servicegroup* while doing Creation, Update and retrieval of > *HostComponents* and *ServiceComponents*. > The new API calls will be the following: > *Service:* > http://:/api/v1/clusters//servicegroups//services > http://:/api/v1/clusters//servicegroups//services/ > ** -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21824) Make services as sub-resource of ServiceGroups and use Servicegroup while doing Creation, Update and retrieval of HostComponents and ServiceComponents.
[ https://issues.apache.org/jira/browse/AMBARI-21824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21824: - Description: ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. This Task involves : - moving *Services* which was earlier a sub-resource of *Cluster* under *ServiceGroup* now, and - The calls for > Make services as sub-resource of ServiceGroups and use Servicegroup while > doing Creation, Update and retrieval of HostComponents and ServiceComponents. > --- > > Key: AMBARI-21824 > URL: https://issues.apache.org/jira/browse/AMBARI-21824 > Project: Ambari > Issue Type: Task > Components: ambari-server, ambari-web >Affects Versions: 2.5.1 >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar > Fix For: 3.0.0 > > > ServiceGroup was a new sub-resource added for cluster in AMBARI-21594. > This Task involves : > - moving *Services* which was earlier a sub-resource of *Cluster* under > *ServiceGroup* now, and > - > The calls for -- This message was sent by Atlassian JIRA (v6.4.14#64029)
