[jira] [Updated] (AMBARI-23350) Issues: 1. ServiceConfig API call uses "MpackName-Vesion" for SG instead of just "MpackName". 2. POST host API calls fail as HostResourceProvider has few member variabl
[
https://issues.apache.org/jira/browse/AMBARI-23350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23350:
Labels: pull-request-available (was: )
> Issues: 1. ServiceConfig API call uses "MpackName-Vesion" for SG instead of
> just "MpackName". 2. POST host API calls fail as HostResourceProvider has few
> member variables uninitialized.
> -
>
> Key: AMBARI-23350
> URL: https://issues.apache.org/jira/browse/AMBARI-23350
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, ambari-web
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Attachments: Screen Shot 2018-03-23 at 1.05.13 PM.png
>
>
> 1. ServiceConfig API call uses "MpackName-Vesion" for SG instead of just
> "MpackName".
> - With "[AMBARI-23269] Removed mpack version from service group name (#692)"
> we have started using just the *Mpack* Name to create the SG.
> - But we haven't updated the Service Configs API POST calls, which still
> continue to use *MpackName-Vesion* for referring SG. This needs to be updated.
> Failure :
> POST
> http://:8080/api/v1/clusters/c1/servicegroups/HDPCORE-1.0.0-b140/services/HDFS/configurations
> [^Screen Shot 2018-03-23 at 1.05.13 PM.png]
> *2. POST host API calls fail as HostResourceProvider has few member variables
> uninitialized.*
> *Issue:*
> POST http://172.22.65.77:8080/api/v1/clusters/c1/hosts returns 500.
> *Reason:*
> Stack Trace:
> {code:title=ambari-server.log}
> java.lang.NullPointerException
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider.createHosts(HostResourceProvider.java:588)
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider$1.invoke(HostResourceProvider.java:255)
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider$1.invoke(HostResourceProvider.java:252)
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:465)
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:288)
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider.createResourcesAuthorized(HostResourceProvider.java:252)
> at
> org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:231)
> {code}
> *Code Line:*
> {code:title=https://github.com/apache/ambari/blob/branch-feature-AMBARI-14714/ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostResourceProvider.java#L575}
> HostLevelParamsUpdateEvent hostLevelParamsUpdateEvent = new
> HostLevelParamsUpdateEvent(clusterId, new HostLevelParamsCluster(
> getManagementController().retrieveHostRepositories(cl, addedHost),
> recoveryConfigHelper.getRecoveryConfig(cl.getClusterName(),
> addedHost.getHostName())
> ));
> {code}
> NPE is because *recoveryConfigHelper* is not initialized. Further,
> *hostLevelParamsHolder* and *topologyHolder* are also null.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23350) Issues: 1. ServiceConfig API call uses "MpackName-Vesion" for SG instead of just "MpackName". 2. POST host API calls fail as HostResourceProvider has few member variabl
[
https://issues.apache.org/jira/browse/AMBARI-23350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-23350:
-
Summary: Issues: 1. ServiceConfig API call uses "MpackName-Vesion" for SG
instead of just "MpackName". 2. POST host API calls fail as
HostResourceProvider has few member variables uninitialized. (was:
ServiceConfig API call uses "MpackName-Vesion" for SG instead of just
"MpackName".)
> Issues: 1. ServiceConfig API call uses "MpackName-Vesion" for SG instead of
> just "MpackName". 2. POST host API calls fail as HostResourceProvider has few
> member variables uninitialized.
> -
>
> Key: AMBARI-23350
> URL: https://issues.apache.org/jira/browse/AMBARI-23350
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, ambari-web
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: Screen Shot 2018-03-23 at 1.05.13 PM.png
>
>
> 1. ServiceConfig API call uses "MpackName-Vesion" for SG instead of just
> "MpackName".
> - With "[AMBARI-23269] Removed mpack version from service group name (#692)"
> we have started using just the *Mpack* Name to create the SG.
> - But we haven't updated the Service Configs API POST calls, which still
> continue to use *MpackName-Vesion* for referring SG. This needs to be updated.
> Failure :
> POST
> http://:8080/api/v1/clusters/c1/servicegroups/HDPCORE-1.0.0-b140/services/HDFS/configurations
> [^Screen Shot 2018-03-23 at 1.05.13 PM.png]
> *2. POST host API calls fail as HostResourceProvider has few member variables
> uninitialized.*
> *Issue:*
> POST http://172.22.65.77:8080/api/v1/clusters/c1/hosts returns 500.
> *Reason:*
> Stack Trace:
> {code:title=ambari-server.log}
> java.lang.NullPointerException
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider.createHosts(HostResourceProvider.java:588)
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider$1.invoke(HostResourceProvider.java:255)
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider$1.invoke(HostResourceProvider.java:252)
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:465)
> at
> org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:288)
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider.createResourcesAuthorized(HostResourceProvider.java:252)
> at
> org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:231)
> {code}
> *Code Line:*
> {code:title=https://github.com/apache/ambari/blob/branch-feature-AMBARI-14714/ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostResourceProvider.java#L575}
> HostLevelParamsUpdateEvent hostLevelParamsUpdateEvent = new
> HostLevelParamsUpdateEvent(clusterId, new HostLevelParamsCluster(
> getManagementController().retrieveHostRepositories(cl, addedHost),
> recoveryConfigHelper.getRecoveryConfig(cl.getClusterName(),
> addedHost.getHostName())
> ));
> {code}
> NPE is because *recoveryConfigHelper* is not initialized. Further,
> *hostLevelParamsHolder* and *topologyHolder* are also null.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23350) ServiceConfig API call uses "MpackName-Vesion" for SG instead of just "MpackName".
[
https://issues.apache.org/jira/browse/AMBARI-23350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-23350:
-
Description:
1. ServiceConfig API call uses "MpackName-Vesion" for SG instead of just
"MpackName".
- With "[AMBARI-23269] Removed mpack version from service group name (#692)" we
have started using just the *Mpack* Name to create the SG.
- But we haven't updated the Service Configs API POST calls, which still
continue to use *MpackName-Vesion* for referring SG. This needs to be updated.
Failure :
POST
http://:8080/api/v1/clusters/c1/servicegroups/HDPCORE-1.0.0-b140/services/HDFS/configurations
[^Screen Shot 2018-03-23 at 1.05.13 PM.png]
*2. POST host API calls fail as HostResourceProvider has few member variables
uninitialized.*
*Issue:*
POST http://172.22.65.77:8080/api/v1/clusters/c1/hosts returns 500.
*Reason:*
Stack Trace:
{code:title=ambari-server.log}
java.lang.NullPointerException
at
org.apache.ambari.server.controller.internal.HostResourceProvider.createHosts(HostResourceProvider.java:588)
at
org.apache.ambari.server.controller.internal.HostResourceProvider$1.invoke(HostResourceProvider.java:255)
at
org.apache.ambari.server.controller.internal.HostResourceProvider$1.invoke(HostResourceProvider.java:252)
at
org.apache.ambari.server.controller.internal.AbstractResourceProvider.invokeWithRetry(AbstractResourceProvider.java:465)
at
org.apache.ambari.server.controller.internal.AbstractResourceProvider.createResources(AbstractResourceProvider.java:288)
at
org.apache.ambari.server.controller.internal.HostResourceProvider.createResourcesAuthorized(HostResourceProvider.java:252)
at
org.apache.ambari.server.controller.internal.AbstractAuthorizedResourceProvider.createResources(AbstractAuthorizedResourceProvider.java:231)
{code}
*Code Line:*
{code:title=https://github.com/apache/ambari/blob/branch-feature-AMBARI-14714/ambari-server/src/main/java/org/apache/ambari/server/controller/internal/HostResourceProvider.java#L575}
HostLevelParamsUpdateEvent hostLevelParamsUpdateEvent = new
HostLevelParamsUpdateEvent(clusterId, new HostLevelParamsCluster(
getManagementController().retrieveHostRepositories(cl, addedHost),
recoveryConfigHelper.getRecoveryConfig(cl.getClusterName(),
addedHost.getHostName())
));
{code}
NPE is because *recoveryConfigHelper* is not initialized. Further,
*hostLevelParamsHolder* and *topologyHolder* are also null.
was:
1. ServiceConfig API call uses "MpackName-Vesion" for SG instead of just
"MpackName".
- With "[AMBARI-23269] Removed mpack version from service group name (#692)" we
have started using just the *Mpack* Name to create the SG.
- But we haven't updated the Service Configs API POST calls, which still
continue to use *MpackName-Vesion* for referring SG. This needs to be updated.
Failure :
POST
http://:8080/api/v1/clusters/c1/servicegroups/HDPCORE-1.0.0-b140/services/HDFS/configurations
[^Screen Shot 2018-03-23 at 1.05.13 PM.png]
> ServiceConfig API call uses "MpackName-Vesion" for SG instead of just
> "MpackName".
> ---
>
> Key: AMBARI-23350
> URL: https://issues.apache.org/jira/browse/AMBARI-23350
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, ambari-web
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: Screen Shot 2018-03-23 at 1.05.13 PM.png
>
>
> 1. ServiceConfig API call uses "MpackName-Vesion" for SG instead of just
> "MpackName".
> - With "[AMBARI-23269] Removed mpack version from service group name (#692)"
> we have started using just the *Mpack* Name to create the SG.
> - But we haven't updated the Service Configs API POST calls, which still
> continue to use *MpackName-Vesion* for referring SG. This needs to be updated.
> Failure :
> POST
> http://:8080/api/v1/clusters/c1/servicegroups/HDPCORE-1.0.0-b140/services/HDFS/configurations
> [^Screen Shot 2018-03-23 at 1.05.13 PM.png]
> *2. POST host API calls fail as HostResourceProvider has few member variables
> uninitialized.*
> *Issue:*
> POST http://172.22.65.77:8080/api/v1/clusters/c1/hosts returns 500.
> *Reason:*
> Stack Trace:
> {code:title=ambari-server.log}
> java.lang.NullPointerException
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider.createHosts(HostResourceProvider.java:588)
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider$1.invoke(HostResourceProvider.java:255)
> at
> org.apache.ambari.server.controller.internal.HostResourceProvider$1.invoke(HostResourceProvider.java:252)
> at
>
[jira] [Updated] (AMBARI-23351) The Ambari-DDL-Postgres-EMBEDDED-CREATE.sql file contains incorrect filename inside it.
[ https://issues.apache.org/jira/browse/AMBARI-23351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] JaySenSharma updated AMBARI-23351: -- Status: Patch Available (was: In Progress) [Pull Request|https://github.com/apache/ambari/pull/773] > The Ambari-DDL-Postgres-EMBEDDED-CREATE.sql file contains incorrect filename > inside it. > --- > > Key: AMBARI-23351 > URL: https://issues.apache.org/jira/browse/AMBARI-23351 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: JaySenSharma >Assignee: JaySenSharma >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > There seems to be some typo issue inside the > "Ambari-DDL-Postgres-EMBEDDED-CREATE.sql" which is pointing to some incorrect > file name (due to typo). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23351) The Ambari-DDL-Postgres-EMBEDDED-CREATE.sql file contains incorrect filename inside it.
[ https://issues.apache.org/jira/browse/AMBARI-23351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23351: Labels: pull-request-available (was: ) > The Ambari-DDL-Postgres-EMBEDDED-CREATE.sql file contains incorrect filename > inside it. > --- > > Key: AMBARI-23351 > URL: https://issues.apache.org/jira/browse/AMBARI-23351 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: JaySenSharma >Assignee: JaySenSharma >Priority: Major > Labels: pull-request-available > > There seems to be some typo issue inside the > "Ambari-DDL-Postgres-EMBEDDED-CREATE.sql" which is pointing to some incorrect > file name (due to typo). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23351) The Ambari-DDL-Postgres-EMBEDDED-CREATE.sql file contains incorrect filename inside it.
JaySenSharma created AMBARI-23351: - Summary: The Ambari-DDL-Postgres-EMBEDDED-CREATE.sql file contains incorrect filename inside it. Key: AMBARI-23351 URL: https://issues.apache.org/jira/browse/AMBARI-23351 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Reporter: JaySenSharma Assignee: JaySenSharma There seems to be some typo issue inside the "Ambari-DDL-Postgres-EMBEDDED-CREATE.sql" which is pointing to some incorrect file name (due to typo). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23350) ServiceConfig API call uses "MpackName-Vesion" for SG instead of just "MpackName".
[ https://issues.apache.org/jira/browse/AMBARI-23350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-23350: - Description: 1. ServiceConfig API call uses "MpackName-Vesion" for SG instead of just "MpackName". - With "[AMBARI-23269] Removed mpack version from service group name (#692)" we have started using just the *Mpack* Name to create the SG. - But we haven't updated the Service Configs API POST calls, which still continue to use *MpackName-Vesion* for referring SG. This needs to be updated. Failure : POST http://:8080/api/v1/clusters/c1/servicegroups/HDPCORE-1.0.0-b140/services/HDFS/configurations [^Screen Shot 2018-03-23 at 1.05.13 PM.png] was: 1. ServiceConfig API call uses "MpackName-Vesion" for SG instead of just "MpackName". - With "[AMBARI-23269] Removed mpack version from service group name (#692)" we have started using just the *Mpack* Name to create the SG. - But we haven't updated the Service Configs API POST calls, which still continue to use *MpackName-Vesion* for referring SG. This needs to be updated. Failure : POST http://:8080/api/v1/clusters/c1/servicegroups/HDPCORE-1.0.0-b140/services/HDFS/configurations !Screen Shot 2018-03-23 at 1.05.13 PM.png|thumbnail! > ServiceConfig API call uses "MpackName-Vesion" for SG instead of just > "MpackName". > --- > > Key: AMBARI-23350 > URL: https://issues.apache.org/jira/browse/AMBARI-23350 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-web >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Major > Fix For: 3.0.0 > > Attachments: Screen Shot 2018-03-23 at 1.05.13 PM.png > > > 1. ServiceConfig API call uses "MpackName-Vesion" for SG instead of just > "MpackName". > - With "[AMBARI-23269] Removed mpack version from service group name (#692)" > we have started using just the *Mpack* Name to create the SG. > - But we haven't updated the Service Configs API POST calls, which still > continue to use *MpackName-Vesion* for referring SG. This needs to be updated. > Failure : > POST > http://:8080/api/v1/clusters/c1/servicegroups/HDPCORE-1.0.0-b140/services/HDFS/configurations > [^Screen Shot 2018-03-23 at 1.05.13 PM.png] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23350) ServiceConfig API call uses "MpackName-Vesion" for SG instead of just "MpackName".
[ https://issues.apache.org/jira/browse/AMBARI-23350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-23350: - Attachment: Screen Shot 2018-03-23 at 1.05.13 PM.png > ServiceConfig API call uses "MpackName-Vesion" for SG instead of just > "MpackName". > --- > > Key: AMBARI-23350 > URL: https://issues.apache.org/jira/browse/AMBARI-23350 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-web >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Major > Fix For: 3.0.0 > > Attachments: Screen Shot 2018-03-23 at 1.05.13 PM.png > > > 1. ServiceConfig API call uses "MpackName-Vesion" for SG instead of just > "MpackName". > - With "[AMBARI-23269] Removed mpack version from service group name (#692)" > we have started using just the *Mpack* Name to create the SG. > - But we haven't updated the Service Configs API POST calls, which still > continue to use *MpackName-Vesion* for referring SG. This needs to be updated. > Failure : > POST > http://:8080/api/v1/clusters/c1/servicegroups/HDPCORE-1.0.0-b140/services/HDFS/configurations > !Screen Shot 2018-03-23 at 1.05.13 PM.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23350) ServiceConfig API call uses "MpackName-Vesion" for SG instead of just "MpackName".
[ https://issues.apache.org/jira/browse/AMBARI-23350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-23350: - Description: 1. ServiceConfig API call uses "MpackName-Vesion" for SG instead of just "MpackName". - With "[AMBARI-23269] Removed mpack version from service group name (#692)" we have started using just the *Mpack* Name to create the SG. - But we haven't updated the Service Configs API POST calls, which still continue to use *MpackName-Vesion* for referring SG. This needs to be updated. Failure : POST http://:8080/api/v1/clusters/c1/servicegroups/HDPCORE-1.0.0-b140/services/HDFS/configurations !Screen Shot 2018-03-23 at 1.05.13 PM.png|thumbnail! > ServiceConfig API call uses "MpackName-Vesion" for SG instead of just > "MpackName". > --- > > Key: AMBARI-23350 > URL: https://issues.apache.org/jira/browse/AMBARI-23350 > Project: Ambari > Issue Type: Bug > Components: ambari-server, ambari-web >Reporter: Swapan Shridhar >Assignee: Swapan Shridhar >Priority: Major > Fix For: 3.0.0 > > Attachments: Screen Shot 2018-03-23 at 1.05.13 PM.png > > > 1. ServiceConfig API call uses "MpackName-Vesion" for SG instead of just > "MpackName". > - With "[AMBARI-23269] Removed mpack version from service group name (#692)" > we have started using just the *Mpack* Name to create the SG. > - But we haven't updated the Service Configs API POST calls, which still > continue to use *MpackName-Vesion* for referring SG. This needs to be updated. > Failure : > POST > http://:8080/api/v1/clusters/c1/servicegroups/HDPCORE-1.0.0-b140/services/HDFS/configurations > !Screen Shot 2018-03-23 at 1.05.13 PM.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23350) ServiceConfig API call uses "MpackName-Vesion" for SG instead of just "MpackName".
Swapan Shridhar created AMBARI-23350: Summary: ServiceConfig API call uses "MpackName-Vesion" for SG instead of just "MpackName". Key: AMBARI-23350 URL: https://issues.apache.org/jira/browse/AMBARI-23350 Project: Ambari Issue Type: Bug Components: ambari-server, ambari-web Reporter: Swapan Shridhar Assignee: Swapan Shridhar Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23349) Add NameNode federation support for Host Details page
[ https://issues.apache.org/jira/browse/AMBARI-23349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23349: Labels: pull-request-available (was: ) > Add NameNode federation support for Host Details page > - > > Key: AMBARI-23349 > URL: https://issues.apache.org/jira/browse/AMBARI-23349 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > > - Display namespace id for NameNode entries on Host Details page > - Perform DataNode decommission status check using data of the correct > NameNode > - Add NameNode widgets to Host Metrics section -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23349) Add NameNode federation support for Host Details page
Andrii Babiichuk created AMBARI-23349: - Summary: Add NameNode federation support for Host Details page Key: AMBARI-23349 URL: https://issues.apache.org/jira/browse/AMBARI-23349 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 2.7.0 - Display namespace id for NameNode entries on Host Details page - Perform DataNode decommission status check using data of the correct NameNode - Add NameNode widgets to Host Metrics section -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23348) service advisor has the option to calculate colocatServices with more information from the services list
[ https://issues.apache.org/jira/browse/AMBARI-23348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23348: Labels: pull-request-available (was: ) > service advisor has the option to calculate colocatServices with more > information from the services list > > > Key: AMBARI-23348 > URL: https://issues.apache.org/jira/browse/AMBARI-23348 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li >Priority: Major > Labels: pull-request-available > Fix For: trunk > > > Besides the current colocateService method in service_advisor.py, we propose > to add one more method that takes in the full services list so the script may > calculate colocate components with more information. > We are adding a new method so the existing service advisor code in HDP 3.0 > remain compatible, while 3rd party services, such as Big SQL can implement > the new method. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23314) Prevent Multiple OS Entries For a Single Mpack
[
https://issues.apache.org/jira/browse/AMBARI-23314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23314:
Labels: pull-request-available (was: )
> Prevent Multiple OS Entries For a Single Mpack
> --
>
> Key: AMBARI-23314
> URL: https://issues.apache.org/jira/browse/AMBARI-23314
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Labels: pull-request-available
> Fix For: 3.0.0
>
>
> The operating systems endpoint allows for creation and deletion of
> repositories which are associated with a single management pack:
> {code}
> PUT http://{{ambari-server}}:8080/api/v1/mpacks/1/operating_systems/redhat7
> {
> "OperatingSystems" : {
> "is_ambari_managed" : true,
> "repositories" : [
> {
> "distribution" : null,
> "components" : null,
> "unique" : true,
> "tags" : [ ],
> "base_url" :
> "http://repo.ambari.apache.org/hdpcore/centos7/HDPCORE-1.0.0-b96/foo;,
> "os_type" : "redhat7",
> "repo_id" : "HDPCORE-1.0.0-b96",
> "repo_name" : "HDPCORE",
> "mirrors_list" : null,
> "default_base_url" : null,
> "ambari_managed" : true
> },
> {
> "distribution" : null,
> "components" : null,
> "unique" : false,
> "tags" : [ ],
> "base_url" :
> "http://repo.ambari.apache.org/hdpcore/centos7/HDP-UTILS-1.1.0.22/foo;,
> "os_type" : "redhat7",
> "repo_id" : "HDP-UTILS-1.1.0.21",
> "repo_name" : "HDP-UTILS",
> "mirrors_list" : null,
> "default_base_url" : null,
> "ambari_managed" : true
> }
> ]
> }
> }
> {code}
> However, multiple PUTs causes duplicate entries for the same OS. This should
> be prevented.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23348) service advisor has the option to calculate colocatServices with more information from the services list
Di Li created AMBARI-23348: -- Summary: service advisor has the option to calculate colocatServices with more information from the services list Key: AMBARI-23348 URL: https://issues.apache.org/jira/browse/AMBARI-23348 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: trunk Reporter: Di Li Assignee: Di Li Fix For: trunk Besides the current colocateService method in service_advisor.py, we propose to add one more method that takes in the full services list so the script may calculate colocate components with more information. We are adding a new method so the existing service advisor code in HDP 3.0 remain compatible, while 3rd party services, such as Big SQL can implement the new method. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23338) Blueprints with an installed cluster should be read-only
[ https://issues.apache.org/jira/browse/AMBARI-23338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-23338: --- Status: Patch Available (was: In Progress) > Blueprints with an installed cluster should be read-only > > > Key: AMBARI-23338 > URL: https://issues.apache.org/jira/browse/AMBARI-23338 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Deleting a blueprint with a cluster installed can cause heartbeat issues with > agents. Such blueprints should be read-only -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23345) Install Wizard: Add a Cancel button to go back to Admin View.
[ https://issues.apache.org/jira/browse/AMBARI-23345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23345: Labels: pull-request-available (was: ) > Install Wizard: Add a Cancel button to go back to Admin View. > - > > Key: AMBARI-23345 > URL: https://issues.apache.org/jira/browse/AMBARI-23345 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: cancel-button.png > > > See screenshot. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23345) Install Wizard: Add a Cancel button to go back to Admin View.
[ https://issues.apache.org/jira/browse/AMBARI-23345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-23345: -- Summary: Install Wizard: Add a Cancel button to go back to Admin View. (was: Installer Wizard: Add a Cancel button to go back to Admin View.) > Install Wizard: Add a Cancel button to go back to Admin View. > - > > Key: AMBARI-23345 > URL: https://issues.apache.org/jira/browse/AMBARI-23345 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Fix For: 2.7.0 > > Attachments: cancel-button.png > > > See screenshot. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23347) Components Requiring restart shows components multiplied by 6
[ https://issues.apache.org/jira/browse/AMBARI-23347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoltan Haindrich updated AMBARI-23347: -- Attachment: screenshot.png > Components Requiring restart shows components multiplied by 6 > - > > Key: AMBARI-23347 > URL: https://issues.apache.org/jira/browse/AMBARI-23347 > Project: Ambari > Issue Type: Bug >Reporter: Zoltan Haindrich >Priority: Major > Attachments: screenshot.png > > > I've installed a 20 node cluster and when I've changed replication from 3 to > 2; it displayed that it will need to restart *168* components...including: > *120* datanodes :) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23347) Components Requiring restart shows components multiplied by 6
Zoltan Haindrich created AMBARI-23347: - Summary: Components Requiring restart shows components multiplied by 6 Key: AMBARI-23347 URL: https://issues.apache.org/jira/browse/AMBARI-23347 Project: Ambari Issue Type: Bug Reporter: Zoltan Haindrich Attachments: screenshot.png I've installed a 20 node cluster and when I've changed replication from 3 to 2; it displayed that it will need to restart *168* components...including: *120* datanodes :) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23346) Ambari server start exits with non zero
[
https://issues.apache.org/jira/browse/AMBARI-23346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23346:
Labels: pull-request-available (was: )
> Ambari server start exits with non zero
> ---
>
> Key: AMBARI-23346
> URL: https://issues.apache.org/jira/browse/AMBARI-23346
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> On slower machines, ambari server (2.7.0) start command fails because the web
> UI availability check times out at 50 seconds.
> {code}
> Restarting ambari-server
> Waiting for server stop...
> Ambari Server stopped
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server
> start
> DB configs consistency check: no errors and warnings were found.
> ERROR: Exiting with exit code 1.
> REASON: Server not yet listening on http port 8080 after 50 seconds. Exiting.
> failed and return code :1
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23346) Ambari server start exits with non zero
[
https://issues.apache.org/jira/browse/AMBARI-23346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16411592#comment-16411592
]
Aravindan Vijayan commented on AMBARI-23346:
*Analysis*
No single point of slowness seen in the Ambari Server startup. It took about 1
min for the UI to be accessible while the startup script fails at 50 seconds.
Some high latency actions (~5 seconds)
{code}
14 Mar 2018 19:53:59,447 INFO [main] ViewExtractor:94 - Extracting files from
ambari-admin-2.7.0.0.143.jar.
14 Mar 2018 19:54:04,452 INFO [main] AmbariServer:214 - Found
org/apache/ambari/server/controller/AmbariServer.class class in
file:/usr/lib/ambari-server
/ambari-server-2.7.0.0.143.jar!/org/apache/ambari/server/controller/AmbariServer.class
{code}
{code}
14 Mar 2018 19:54:12,459 INFO [main] AuditLoggerModule:82 - Binding audit
event creator class
org.apache.ambari.server.audit.request.eventcreator.ViewPrivilegeEventCreator
14 Mar 2018 19:54:17,270 INFO [main] HostRoleCommandDAO:275 - Host role
command status summary cache enabled !
{code}
{code}
14 Mar 2018 19:54:22,875 INFO [pool-4-thread-1]
AbstractPoolBackedDataSource:212 - Initializing c3p0 pool...
14 Mar 2018 19:54:26,354 INFO [pool-4-thread-1]
AmbariLdapConfigurationProvider:103 - Loaded LDAP configuration instance: [ {} ]
{code}
{code}
14 Mar 2018 19:54:40,485 INFO [main] StackContext:222 - Loaded all VDF in
5530ms
{code}
{code}
14 Mar 2018 19:54:58,374 INFO [main] ViewExtractor:94 - Extracting files from
hive-jdbc-2.7.0.0.143.jar.
14 Mar 2018 19:55:01,602 INFO [main] ViewRegistry:1898 - setting up logging
for view HIVE{1.5.0} as per property file view.log4j.properties
{code}
And some VDF related exceptions like
{code}
14 Mar 2018 19:58:58,612 WARN [Stack Version Loading Thread]
RepoVdfCallable:142 - Could not load version definition for HDP-3.0 identified
by http://s3.
amazonaws.com/dev.hortonworks.com/HDP/ubuntu12/3.x/BUILDS/2.6.0.0-598/HDP-2.6.0.0-598.xml.
http://s3.amazonaws.com/dev.hortonworks.com/HDP/ubuntu12/3.x/BU
ILDS/2.6.0.0-598/HDP-2.6.0.0-598.xml
java.io.FileNotFoundException:
http://s3.amazonaws.com/dev.hortonworks.com/HDP/ubuntu12/3.x/BUILDS/2.6.0.0-598/HDP-2.6.0.0-598.xml
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1890)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
at java.net.URL.openStream(URL.java:1045)
at
org.apache.ambari.server.state.repository.VersionDefinitionXml.load(VersionDefinitionXml.java:543)
at
org.apache.ambari.server.state.stack.RepoVdfCallable.timedVDFLoad(RepoVdfCallable.java:154)
at
org.apache.ambari.server.state.stack.RepoVdfCallable.mergeDefinitions(RepoVdfCallable.java:136)
at
org.apache.ambari.server.state.stack.RepoVdfCallable.call(RepoVdfCallable.java:79)
at
org.apache.ambari.server.state.stack.RepoVdfCallable.call(RepoVdfCallable.java:41)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}
The number of jars in /usr/lib/ambari-server/ have increased from 144 (2.6.2)
to 172 (2.7.0).
The number of classes loaded during server start has increased from 11681 to
15814. That is about a 35% jump.
*Fix*
Increasing the timeout to 90 seconds to make sure start command does not fail
on slower systems.
> Ambari server start exits with non zero
> ---
>
> Key: AMBARI-23346
> URL: https://issues.apache.org/jira/browse/AMBARI-23346
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.7.0
>
>
> On slower machines, ambari server (2.7.0) start command fails because the web
> UI availability check times out at 50 seconds.
> {code}
> Restarting ambari-server
> Waiting for server stop...
> Ambari Server stopped
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server
> start
> DB configs consistency check: no errors and warnings were found.
> ERROR: Exiting with exit code 1.
> REASON: Server not yet listening on http port 8080 after 50 seconds. Exiting.
> failed and return code :1
>
[jira] [Created] (AMBARI-23346) Ambari server start exits with non zero
Aravindan Vijayan created AMBARI-23346:
--
Summary: Ambari server start exits with non zero
Key: AMBARI-23346
URL: https://issues.apache.org/jira/browse/AMBARI-23346
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
Fix For: 2.7.0
On slower machines, ambari server (2.7.0) start command fails because the web
UI availability check times out at 50 seconds.
{code}
Restarting ambari-server
Waiting for server stop...
Ambari Server stopped
Ambari Server running with administrator privileges.
Organizing resource files at /var/lib/ambari-server/resources...
Ambari database consistency check started...
Server PID at: /var/run/ambari-server/ambari-server.pid
Server out at: /var/log/ambari-server/ambari-server.out
Server log at: /var/log/ambari-server/ambari-server.log
Waiting for server
start
DB configs consistency check: no errors and warnings were found.
ERROR: Exiting with exit code 1.
REASON: Server not yet listening on http port 8080 after 50 seconds. Exiting.
failed and return code :1
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23345) Installer Wizard: Add a Cancel button to go back to Admin View.
Andrii Tkach created AMBARI-23345: - Summary: Installer Wizard: Add a Cancel button to go back to Admin View. Key: AMBARI-23345 URL: https://issues.apache.org/jira/browse/AMBARI-23345 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.7.0 Attachments: cancel-button.png See screenshot. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23345) Installer Wizard: Add a Cancel button to go back to Admin View.
[ https://issues.apache.org/jira/browse/AMBARI-23345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-23345: -- Attachment: cancel-button.png > Installer Wizard: Add a Cancel button to go back to Admin View. > --- > > Key: AMBARI-23345 > URL: https://issues.apache.org/jira/browse/AMBARI-23345 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Fix For: 2.7.0 > > Attachments: cancel-button.png > > > See screenshot. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23344) install step6: broken list
[ https://issues.apache.org/jira/browse/AMBARI-23344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoltan Haindrich updated AMBARI-23344: -- Description: the "host" column doesn't scroll - noticed it while deploying to 20 nodes > install step6: broken list > -- > > Key: AMBARI-23344 > URL: https://issues.apache.org/jira/browse/AMBARI-23344 > Project: Ambari > Issue Type: Bug >Reporter: Zoltan Haindrich >Priority: Major > Attachments: screenshot.png > > > the "host" column doesn't scroll - noticed it while deploying to 20 nodes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23344) install step6: broken list
[ https://issues.apache.org/jira/browse/AMBARI-23344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoltan Haindrich updated AMBARI-23344: -- Attachment: screenshot.png > install step6: broken list > -- > > Key: AMBARI-23344 > URL: https://issues.apache.org/jira/browse/AMBARI-23344 > Project: Ambari > Issue Type: Bug >Reporter: Zoltan Haindrich >Priority: Major > Attachments: screenshot.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23344) install step6: broken list
Zoltan Haindrich created AMBARI-23344: - Summary: install step6: broken list Key: AMBARI-23344 URL: https://issues.apache.org/jira/browse/AMBARI-23344 Project: Ambari Issue Type: Bug Reporter: Zoltan Haindrich -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23338) Blueprints with an installed cluster should be read-only
[ https://issues.apache.org/jira/browse/AMBARI-23338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Balázs Bence Sári updated AMBARI-23338: --- Description: Deleting a blueprint with a cluster installed can cause heartbeat issues with agents. Such blueprints should be read-only (was: Deleting a blueprint with a cluster installed can cause heartbeat issues with agents. Such blueprints should be reado-only) > Blueprints with an installed cluster should be read-only > > > Key: AMBARI-23338 > URL: https://issues.apache.org/jira/browse/AMBARI-23338 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Deleting a blueprint with a cluster installed can cause heartbeat issues with > agents. Such blueprints should be read-only -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23342) Admin View: Users and Groups style tweaks
[ https://issues.apache.org/jira/browse/AMBARI-23342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23342: Labels: pull-request-available (was: ) > Admin View: Users and Groups style tweaks > - > > Key: AMBARI-23342 > URL: https://issues.apache.org/jira/browse/AMBARI-23342 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: add-user.png, add-users.png, delete-button.png > > > See screenshots -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23337) Remove python3 files from ws4py since they can cause build failure
[ https://issues.apache.org/jira/browse/AMBARI-23337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16411322#comment-16411322 ] Hudson commented on AMBARI-23337: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8903 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8903/]) AMBARI-23337. Remove python3 files from ws4py since they can cause build (aonishuk: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=79f0cc36923fa214cf6017d3b0d261f6d4ee2b2d]) * (delete) ambari-common/src/main/python/ambari_ws4py/server/tulipserver.py * (delete) ambari-common/src/main/python/ambari_ws4py/async_websocket.py > Remove python3 files from ws4py since they can cause build failure > -- > > Key: AMBARI-23337 > URL: https://issues.apache.org/jira/browse/AMBARI-23337 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23337.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > On some envs (not reproducible for me) it can result in failure like this: > > > 2018/03/22 23:49:21 INFO: [INFO] File > "/usr/lib/ambari-agent/lib/ambari_ws4py/async_websocket.py", line 85 > 2018/03/22 23:49:21 INFO: [INFO] yield from > self.proto.writer.drain() > 2018/03/22 23:49:21 INFO: [INFO] ^ > 2018/03/22 23:49:21 INFO: [INFO] SyntaxError: invalid syntax > 2018/03/22 23:49:21 INFO: [INFO] > 2018/03/22 23:49:21 INFO: [INFO] Compiling > /grid/0/jenkins/workspace/Zuul_Ambari_Build_Job/build-support/SOURCES/ambari/ambari-agent/target/rpm/ambari-agent/buildroot/usr/lib/ambari-agent/lib/ambari_ws4py/server/tulipserver.py > ... > 2018/03/22 23:49:21 INFO: [INFO] File > "/usr/lib/ambari-agent/lib/ambari_ws4py/server/tulipserver.py", line 101 > 2018/03/22 23:49:21 INFO: [INFO] request_line = yield from > self.next_line() > 2018/03/22 23:49:21 INFO: [INFO] ^ > 2018/03/22 23:49:21 INFO: [INFO] SyntaxError: invalid syntax > 2018/03/22 23:49:21 INFO: [INFO] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23343) Server should acknowledge agent about received reports
Myroslav Papirkovskyi created AMBARI-23343: -- Summary: Server should acknowledge agent about received reports Key: AMBARI-23343 URL: https://issues.apache.org/jira/browse/AMBARI-23343 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.7.0 Reporter: Myroslav Papirkovskyi Assignee: Myroslav Papirkovskyi Fix For: 2.7.0 Server should sent reply for requests to agent reports stomp endpoint. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23311) Use Ambari CLI to specify which services should be setup for SSO integration
[
https://issues.apache.org/jira/browse/AMBARI-23311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23311:
Labels: pull-request-available security sso (was: security sso)
> Use Ambari CLI to specify which services should be setup for SSO integration
>
>
> Key: AMBARI-23311
> URL: https://issues.apache.org/jira/browse/AMBARI-23311
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Major
> Labels: pull-request-available, security, sso
> Fix For: 2.7.0
>
>
> Use Ambari CLI to specify which services should be setup for SSO integration.
> {noformat:title=Example}
> # ambari-server setup-sso
> Using python /usr/bin/python
> Setting up SSO authentication properties...
> Do you want to configure SSO authentication [y/n] (y)?y
> Enter Ambari Admin login: admin
> Enter Ambari Admin password: admin
> Provider URL [URL] (http://example.com):http://knox.ambari.apache.org:8080
> Public Certificate pem (stored) (empty line to finish input):
> B3NzaC1yc2EDAQABAAABAQD
> Use SSO for all services [y/n] (y)? n
> Use SSO for Ambari [y/n] (y)? y
> Use SSO for HDFS [y/n] (y)? y
> Use SSO for YARN [y/n] (y)? y
> ...
> Use SSO for ZOOKEEPER [y/n] (y)? n
> Do you want to configure advanced properties [y/n] (n) ?
> Ambari Server 'setup-sso' completed successfully.
> {noformat}
> NOTE: this will require obtaining an Ambari administrator username and
> password to GET, PUT, and POST to the Ambari REST API.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23342) Admin View: Users and Groups style tweaks
[ https://issues.apache.org/jira/browse/AMBARI-23342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-23342: -- Attachment: add-users.png add-user.png delete-button.png > Admin View: Users and Groups style tweaks > - > > Key: AMBARI-23342 > URL: https://issues.apache.org/jira/browse/AMBARI-23342 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Major > Fix For: 2.7.0 > > Attachments: add-user.png, add-users.png, delete-button.png > > > See screenshots -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23342) Admin View: Users and Groups style tweaks
Andrii Tkach created AMBARI-23342: - Summary: Admin View: Users and Groups style tweaks Key: AMBARI-23342 URL: https://issues.apache.org/jira/browse/AMBARI-23342 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.7.0 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.7.0 See screenshots -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23341) Add yarn.scheduler.capacity.node-locality-delay = 0 from OneFS serviceAdvisor
Attila Magyar created AMBARI-23341: -- Summary: Add yarn.scheduler.capacity.node-locality-delay = 0 from OneFS serviceAdvisor Key: AMBARI-23341 URL: https://issues.apache.org/jira/browse/AMBARI-23341 Project: Ambari Issue Type: Improvement Components: ambari-server Affects Versions: 2.7.0 Reporter: Attila Magyar Assignee: Attila Magyar Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23341) Add yarn.scheduler.capacity.node-locality-delay = 0 from OneFS serviceAdvisor
[ https://issues.apache.org/jira/browse/AMBARI-23341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated AMBARI-23341: --- Description: There is a bug in ambari (possibly in UI) which prevents adding yarn.scheduler.capacity.node-locality-delay = 0 from OneFS serviceAdvisor. This bug should be fixed first. > Add yarn.scheduler.capacity.node-locality-delay = 0 from OneFS serviceAdvisor > - > > Key: AMBARI-23341 > URL: https://issues.apache.org/jira/browse/AMBARI-23341 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Fix For: 2.7.0 > > > There is a bug in ambari (possibly in UI) which prevents adding > yarn.scheduler.capacity.node-locality-delay = 0 from OneFS serviceAdvisor. > This bug should be fixed first. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23340) refreshing step#5 during installation looses services
[
https://issues.apache.org/jira/browse/AMBARI-23340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Haindrich updated AMBARI-23340:
--
Attachment: step5_before.png
step5_after_refresh.png
> refreshing step#5 during installation looses services
> -
>
> Key: AMBARI-23340
> URL: https://issues.apache.org/jira/browse/AMBARI-23340
> Project: Ambari
> Issue Type: Bug
>Reporter: Zoltan Haindrich
>Priority: Major
> Attachments: step4_selected.png, step5_after_refresh.png,
> step5_before.png
>
>
> * I've selected only Hive and required components
> * on the next page; "Assign Master" I see {{Activity Analyzer}},{{Timeline
> Reader}} and other things which became absent after a refreshing the page
> * IIRC when I've first seen this step today there was also a timeline 1.5
> server which is missing ever since...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23340) refreshing step#5 during installation looses services
[
https://issues.apache.org/jira/browse/AMBARI-23340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltan Haindrich updated AMBARI-23340:
--
Attachment: step4_selected.png
> refreshing step#5 during installation looses services
> -
>
> Key: AMBARI-23340
> URL: https://issues.apache.org/jira/browse/AMBARI-23340
> Project: Ambari
> Issue Type: Bug
>Reporter: Zoltan Haindrich
>Priority: Major
> Attachments: step4_selected.png
>
>
> * I've selected only Hive and required components
> * on the next page; "Assign Master" I see {{Activity Analyzer}},{{Timeline
> Reader}} and other things which became absent after a refreshing the page
> * IIRC when I've first seen this step today there was also a timeline 1.5
> server which is missing ever since...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23340) refreshing step#5 during installation looses services
Zoltan Haindrich created AMBARI-23340:
-
Summary: refreshing step#5 during installation looses services
Key: AMBARI-23340
URL: https://issues.apache.org/jira/browse/AMBARI-23340
Project: Ambari
Issue Type: Bug
Reporter: Zoltan Haindrich
* I've selected only Hive and required components
* on the next page; "Assign Master" I see {{Activity Analyzer}},{{Timeline
Reader}} and other things which became absent after a refreshing the page
* IIRC when I've first seen this step today there was also a timeline 1.5
server which is missing ever since...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23339) Broken layout; became unusable
[ https://issues.apache.org/jira/browse/AMBARI-23339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16411256#comment-16411256 ] Zoltan Haindrich commented on AMBARI-23339: --- refreshing the page fixed for now... > Broken layout; became unusable > -- > > Key: AMBARI-23339 > URL: https://issues.apache.org/jira/browse/AMBARI-23339 > Project: Ambari > Issue Type: Bug >Reporter: Zoltan Haindrich >Priority: Major > Attachments: screenshot.png > > > during installing a cluster which had 20 nodes; I was not able to select node > 18 for a service I wanted because the bottom "Licensed under Apache ... " > have "covered" the dropdownbox > I think that okay...I can work around that by using the arrow keys...and > after a few keystrokes the layou kinda broken (but I was able to select my > node) > after that the layou became so broken that I wasn't able to scroll back up > I pushed thinked that pushing the next and then prev restores layout > consistency..I'll attach a screenshot of what I'm seeing now... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23339) Broken layout; became unusable
[ https://issues.apache.org/jira/browse/AMBARI-23339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoltan Haindrich updated AMBARI-23339: -- Attachment: screenshot.png > Broken layout; became unusable > -- > > Key: AMBARI-23339 > URL: https://issues.apache.org/jira/browse/AMBARI-23339 > Project: Ambari > Issue Type: Bug >Reporter: Zoltan Haindrich >Priority: Major > Attachments: screenshot.png > > > during installing a cluster which had 20 nodes; I was not able to select node > 18 for a service I wanted because the bottom "Licensed under Apache ... " > have "covered" the dropdownbox > I think that okay...I can work around that by using the arrow keys...and > after a few keystrokes the layou kinda broken (but I was able to select my > node) > after that the layou became so broken that I wasn't able to scroll back up > I pushed thinked that pushing the next and then prev restores layout > consistency..I'll attach a screenshot of what I'm seeing now... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23339) Broken layout; became unusable
Zoltan Haindrich created AMBARI-23339: - Summary: Broken layout; became unusable Key: AMBARI-23339 URL: https://issues.apache.org/jira/browse/AMBARI-23339 Project: Ambari Issue Type: Bug Reporter: Zoltan Haindrich during installing a cluster which had 20 nodes; I was not able to select node 18 for a service I wanted because the bottom "Licensed under Apache ... " have "covered" the dropdownbox I think that okay...I can work around that by using the arrow keys...and after a few keystrokes the layou kinda broken (but I was able to select my node) after that the layou became so broken that I wasn't able to scroll back up I pushed thinked that pushing the next and then prev restores layout consistency..I'll attach a screenshot of what I'm seeing now... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23310) Add SSO-related configuration recommendations to the stack advisor
[
https://issues.apache.org/jira/browse/AMBARI-23310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23310:
Labels: pull-request-available stack_advisor (was: stack_advisor)
> Add SSO-related configuration recommendations to the stack advisor
> --
>
> Key: AMBARI-23310
> URL: https://issues.apache.org/jira/browse/AMBARI-23310
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available, stack_advisor
> Fix For: 2.7.0
>
>
> Add SSO-related configuration recommendations to the stack advisor.
> # Add a new action - {{recommend-configurations-for-sso}} - to query services
> for only SSO-related configuration changes
> # Append to the stack advisor input data, the Ambari-stored SSO integration
> data (list of services that should enable SSO integration, proxy url, public
> key details, etc...).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23338) Blueprints with an installed cluster should be read-only
[ https://issues.apache.org/jira/browse/AMBARI-23338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23338: Labels: pull-request-available (was: ) > Blueprints with an installed cluster should be read-only > > > Key: AMBARI-23338 > URL: https://issues.apache.org/jira/browse/AMBARI-23338 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: Balázs Bence Sári >Assignee: Balázs Bence Sári >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > > Deleting a blueprint with a cluster installed can cause heartbeat issues with > agents. Such blueprints should be reado-only -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23338) Blueprints with an installed cluster should be read-only
Balázs Bence Sári created AMBARI-23338: -- Summary: Blueprints with an installed cluster should be read-only Key: AMBARI-23338 URL: https://issues.apache.org/jira/browse/AMBARI-23338 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.6.1 Reporter: Balázs Bence Sári Assignee: Balázs Bence Sári Fix For: 2.7.0 Deleting a blueprint with a cluster installed can cause heartbeat issues with agents. Such blueprints should be reado-only -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23335) 400 server error when Cluster Administrator tries to add service and move components
[
https://issues.apache.org/jira/browse/AMBARI-23335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23335:
Labels: pull-request-available (was: )
> 400 server error when Cluster Administrator tries to add service and move
> components
>
>
> Key: AMBARI-23335
> URL: https://issues.apache.org/jira/browse/AMBARI-23335
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Srikanth Janardhan
>Assignee: Attila Magyar
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Attachments: screenshot.png
>
>
> STR:
> # Deploy a HDP-3.0 cluster
> # Create a user with role as "Cluster Administrator"
> # Login as the user
> # Click Add Service from the dashboard
> # Click Next button in the wizard
> The same error occurs while trying the Move Components wizard too.
> Issue also present for Cluster Operator Role while moving components.
> The page is stuck at this stage even after dismissing the popup.
> {code:java|title=ambari-server.log}
> 17 Mar 2018 16:13:51,740 WARN [ambari-client-thread-524]
> StackAdvisorCommand:204 - Error occurred during retrieving ldap
> configuration, status=403, response={
> "status" : 403,
> "message" : "The authenticated user does not have the appropriate
> authorizations to get the requested resource(s)"
> }
> 17 Mar 2018 16:13:51,741 WARN [ambari-client-thread-524]
> StackAdvisorCommand:182 - Error parsing services.json file content: Error
> occurred during retrieving ldap configuration, status=403, response={
> "status" : 403,
> "message" : "The authenticated user does not have the appropriate
> authorizations to get the requested resource(s)"
> }
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorException:
> Error occurred during retrieving ldap configuration, status=403, response={
> "status" : 403,
> "message" : "The authenticated user does not have the appropriate
> authorizations to get the requested resource(s)"
> }
> at
> org.apache.ambari.server.api.services.stackadvisor.commands.StackAdvisorCommand.populateLdapConfiguration(StackAdvisorCommand.java:205)
> at
> org.apache.ambari.server.api.services.stackadvisor.commands.StackAdvisorCommand.adjust(StackAdvisorCommand.java:177)
> at
> org.apache.ambari.server.api.services.stackadvisor.commands.StackAdvisorCommand.invoke(StackAdvisorCommand.java:352)
> at
> org.apache.ambari.server.api.services.stackadvisor.StackAdvisorHelper.recommend(StackAdvisorHelper.java:132)
> at
> org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:145)
> at
> org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:296)
> at
> org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
> at
> org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:50)
> at
> org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:68)
> at
> org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:163)
> at
> org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:127)
> at
> org.apache.ambari.server.api.services.RecommendationService.getRecommendation(RecommendationService.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
> at
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
> at
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
> at
>
[jira] [Commented] (AMBARI-23243) Adding missing properties to OneFS mpack
[ https://issues.apache.org/jira/browse/AMBARI-23243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16411169#comment-16411169 ] Hudson commented on AMBARI-23243: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8902 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8902/]) AMBARI-23243. Adding missing properties to OneFS mpack (amagyar) (m.magyar3: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=8b7422c10f1478b57519642296ffa3aa60a3258b]) * (edit) contrib/management-packs/isilon-onefs-mpack/src/main/resources/addon-services/ONEFS/1.0.0/service_advisor.py * (edit) contrib/management-packs/isilon-onefs-mpack/src/main/resources/addon-services/ONEFS/1.0.0/configuration/hdfs-site.xml * (edit) contrib/management-packs/isilon-onefs-mpack/src/main/resources/addon-services/ONEFS/1.0.0/metainfo.xml * (edit) contrib/management-packs/isilon-onefs-mpack/src/main/resources/addon-services/ONEFS/1.0.0/kerberos.json > Adding missing properties to OneFS mpack > > > Key: AMBARI-23243 > URL: https://issues.apache.org/jira/browse/AMBARI-23243 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 > Environment: > > >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Following properties should be added to the appropriate config > * hadoop.security.token.service.use_ip should be false when kerberos is > enabled > * dfs.checksum.type should always be null > * dfs.datanode.http.address/dfs.datanode.https.address = > 0.0.0.0:8082/0.0.0.0:8080 [?] > * -yarn.scheduler.capacity.node-locality-delay = 0- > * dfs.client-write-packet-size = 131072 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23336) Editing configurations usings configs.py doesnt have options to pass service config version note
[
https://issues.apache.org/jira/browse/AMBARI-23336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil S Naik updated AMBARI-23336:
--
Fix Version/s: 3.0.0
Status: Patch Available (was: In Progress)
> Editing configurations usings configs.py doesnt have options to pass service
> config version note
>
>
> Key: AMBARI-23336
> URL: https://issues.apache.org/jira/browse/AMBARI-23336
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
> Environment: Ambari -2.6.1
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Editing configurations usings configs.py doesnt have options to pass service
> config version note
> But we can pass service config version note via curl command and in ambari-ui
> This feature should be implemented for actions 'SET' and 'DELETE'
> Suggested give '-b' as option to give service config version note
> ex :
> {code:java}
> /var/lib/ambari-server/resources/scripts/configs.py -u admin -p admin -t 8080
> -n asnaik -l localhost -a set -c capacity-scheduler -k
> "yarn.scheduler.capacity.resource-calculator" -v
> "org.apache.hadoop.yarn.util.resource.DefaultResourceCalculator" -b "Creating
> a new version with CPU scheduling off"
> {code}
> and the Help of the configs.py should be
> Please edit the help page :
> https://cwiki.apache.org/confluence/display/AMBARI/Modify+configurations#Modifyconfigurations-Editconfigurationusingconfigs.py
> {code:java}
> [root@pwd1 scripts]# /var/lib/ambari-server/resources/scripts/configs.py
> --help
> Usage: configs.py [options]
> Options:
> -h, --helpshow this help message and exit
> -t PORT, --port=PORT Optional port number for Ambari server. Default is
> '8080'. Provide empty string to not use port.
> -s PROTOCOL, --protocol=PROTOCOL
> Optional support of SSL. Default protocol is 'http'
> -a ACTION, --action=ACTION
> Script action: , ,
> -l HOST, --host=HOST Server external host name
> -n CLUSTER, --cluster=CLUSTER
> Name given to cluster. Ex: 'c1'
> -c CONFIG_TYPE, --config-type=CONFIG_TYPE
> One of the various configuration types in Ambari. Ex:
> core-site, hdfs-site, mapred-queue-acls, etc.
> -b VERSION_NOTE, --version-note=VERSION_NOTE
> Version change notes which will help to know what has
> been changed in this config , this value is optional
> and is used for action set
> To specify credentials please use "-e" OR "-u" and "-p'":
> -u USER, --user=USER
> Optional user ID to use for authentication. Default is
> 'admin'
> -p PASSWORD, --password=PASSWORD
> Optional password to use for authentication. Default
> is 'admin'
> -e CREDENTIALS_FILE, --credentials-file=CREDENTIALS_FILE
> Optional file with user credentials separated by new
> line.
> To specify property(s) please use "-f" OR "-k" and "-v'":
> -f FILE, --file=FILE
> File where entire configurations are saved to, or read
> from. Supported extensions (.xml, .json>)
> -k KEY, --key=KEY Key that has to be set or deleted. Not necessary for
> 'get' action.
> -v VALUE, --value=VALUE
> Optional value to be set. Not necessary for 'get' or
> 'delete' actions.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23336) Editing configurations usings configs.py doesnt have options to pass service config version note
[
https://issues.apache.org/jira/browse/AMBARI-23336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23336:
Labels: pull-request-available (was: )
> Editing configurations usings configs.py doesnt have options to pass service
> config version note
>
>
> Key: AMBARI-23336
> URL: https://issues.apache.org/jira/browse/AMBARI-23336
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
> Environment: Ambari -2.6.1
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
>
> Editing configurations usings configs.py doesnt have options to pass service
> config version note
> But we can pass service config version note via curl command and in ambari-ui
> This feature should be implemented for actions 'SET' and 'DELETE'
> Suggested give '-b' as option to give service config version note
> ex :
> {code:java}
> /var/lib/ambari-server/resources/scripts/configs.py -u admin -p admin -t 8080
> -n asnaik -l localhost -a set -c capacity-scheduler -k
> "yarn.scheduler.capacity.resource-calculator" -v
> "org.apache.hadoop.yarn.util.resource.DefaultResourceCalculator" -b "Creating
> a new version with CPU scheduling off"
> {code}
> and the Help of the configs.py should be
> Please edit the help page :
> https://cwiki.apache.org/confluence/display/AMBARI/Modify+configurations#Modifyconfigurations-Editconfigurationusingconfigs.py
> {code:java}
> [root@pwd1 scripts]# /var/lib/ambari-server/resources/scripts/configs.py
> --help
> Usage: configs.py [options]
> Options:
> -h, --helpshow this help message and exit
> -t PORT, --port=PORT Optional port number for Ambari server. Default is
> '8080'. Provide empty string to not use port.
> -s PROTOCOL, --protocol=PROTOCOL
> Optional support of SSL. Default protocol is 'http'
> -a ACTION, --action=ACTION
> Script action: , ,
> -l HOST, --host=HOST Server external host name
> -n CLUSTER, --cluster=CLUSTER
> Name given to cluster. Ex: 'c1'
> -c CONFIG_TYPE, --config-type=CONFIG_TYPE
> One of the various configuration types in Ambari. Ex:
> core-site, hdfs-site, mapred-queue-acls, etc.
> -b VERSION_NOTE, --version-note=VERSION_NOTE
> Version change notes which will help to know what has
> been changed in this config , this value is optional
> and is used for action set
> To specify credentials please use "-e" OR "-u" and "-p'":
> -u USER, --user=USER
> Optional user ID to use for authentication. Default is
> 'admin'
> -p PASSWORD, --password=PASSWORD
> Optional password to use for authentication. Default
> is 'admin'
> -e CREDENTIALS_FILE, --credentials-file=CREDENTIALS_FILE
> Optional file with user credentials separated by new
> line.
> To specify property(s) please use "-f" OR "-k" and "-v'":
> -f FILE, --file=FILE
> File where entire configurations are saved to, or read
> from. Supported extensions (.xml, .json>)
> -k KEY, --key=KEY Key that has to be set or deleted. Not necessary for
> 'get' action.
> -v VALUE, --value=VALUE
> Optional value to be set. Not necessary for 'get' or
> 'delete' actions.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23337) Remove python3 files from ws4py since they can cause build failure
[ https://issues.apache.org/jira/browse/AMBARI-23337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23337: Labels: pull-request-available (was: ) > Remove python3 files from ws4py since they can cause build failure > -- > > Key: AMBARI-23337 > URL: https://issues.apache.org/jira/browse/AMBARI-23337 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23337.patch > > > On some envs (not reproducible for me) it can result in failure like this: > > > 2018/03/22 23:49:21 INFO: [INFO] File > "/usr/lib/ambari-agent/lib/ambari_ws4py/async_websocket.py", line 85 > 2018/03/22 23:49:21 INFO: [INFO] yield from > self.proto.writer.drain() > 2018/03/22 23:49:21 INFO: [INFO] ^ > 2018/03/22 23:49:21 INFO: [INFO] SyntaxError: invalid syntax > 2018/03/22 23:49:21 INFO: [INFO] > 2018/03/22 23:49:21 INFO: [INFO] Compiling > /grid/0/jenkins/workspace/Zuul_Ambari_Build_Job/build-support/SOURCES/ambari/ambari-agent/target/rpm/ambari-agent/buildroot/usr/lib/ambari-agent/lib/ambari_ws4py/server/tulipserver.py > ... > 2018/03/22 23:49:21 INFO: [INFO] File > "/usr/lib/ambari-agent/lib/ambari_ws4py/server/tulipserver.py", line 101 > 2018/03/22 23:49:21 INFO: [INFO] request_line = yield from > self.next_line() > 2018/03/22 23:49:21 INFO: [INFO] ^ > 2018/03/22 23:49:21 INFO: [INFO] SyntaxError: invalid syntax > 2018/03/22 23:49:21 INFO: [INFO] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23324) Fix Zeppelin service dependency in HDP 3.0
[
https://issues.apache.org/jira/browse/AMBARI-23324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-23324:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Fix Zeppelin service dependency in HDP 3.0
> --
>
> Key: AMBARI-23324
> URL: https://issues.apache.org/jira/browse/AMBARI-23324
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.7.0
>
>
> As of now, in HDP 3.0 Zeppelin contain such dependency:
> {code}
>
> SPARK/SPARK_CLIENT
> host
>
> true
>
>
> {code}
> but stack HDP 3.0 doesn't have SPARK, only SPARK2 and SPARK2_CLIENT.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23337) Remove python3 files from ws4py since they can cause build failure
Andrew Onischuk created AMBARI-23337: Summary: Remove python3 files from ws4py since they can cause build failure Key: AMBARI-23337 URL: https://issues.apache.org/jira/browse/AMBARI-23337 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.7.0 Attachments: AMBARI-23337.patch On some envs (not reproducible for me) it can result in failure like this: 2018/03/22 23:49:21 INFO: [INFO] File "/usr/lib/ambari-agent/lib/ambari_ws4py/async_websocket.py", line 85 2018/03/22 23:49:21 INFO: [INFO] yield from self.proto.writer.drain() 2018/03/22 23:49:21 INFO: [INFO] ^ 2018/03/22 23:49:21 INFO: [INFO] SyntaxError: invalid syntax 2018/03/22 23:49:21 INFO: [INFO] 2018/03/22 23:49:21 INFO: [INFO] Compiling /grid/0/jenkins/workspace/Zuul_Ambari_Build_Job/build-support/SOURCES/ambari/ambari-agent/target/rpm/ambari-agent/buildroot/usr/lib/ambari-agent/lib/ambari_ws4py/server/tulipserver.py ... 2018/03/22 23:49:21 INFO: [INFO] File "/usr/lib/ambari-agent/lib/ambari_ws4py/server/tulipserver.py", line 101 2018/03/22 23:49:21 INFO: [INFO] request_line = yield from self.next_line() 2018/03/22 23:49:21 INFO: [INFO] ^ 2018/03/22 23:49:21 INFO: [INFO] SyntaxError: invalid syntax 2018/03/22 23:49:21 INFO: [INFO] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23337) Remove python3 files from ws4py since they can cause build failure
[ https://issues.apache.org/jira/browse/AMBARI-23337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23337: - Status: Patch Available (was: Open) > Remove python3 files from ws4py since they can cause build failure > -- > > Key: AMBARI-23337 > URL: https://issues.apache.org/jira/browse/AMBARI-23337 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-23337.patch > > > On some envs (not reproducible for me) it can result in failure like this: > > > 2018/03/22 23:49:21 INFO: [INFO] File > "/usr/lib/ambari-agent/lib/ambari_ws4py/async_websocket.py", line 85 > 2018/03/22 23:49:21 INFO: [INFO] yield from > self.proto.writer.drain() > 2018/03/22 23:49:21 INFO: [INFO] ^ > 2018/03/22 23:49:21 INFO: [INFO] SyntaxError: invalid syntax > 2018/03/22 23:49:21 INFO: [INFO] > 2018/03/22 23:49:21 INFO: [INFO] Compiling > /grid/0/jenkins/workspace/Zuul_Ambari_Build_Job/build-support/SOURCES/ambari/ambari-agent/target/rpm/ambari-agent/buildroot/usr/lib/ambari-agent/lib/ambari_ws4py/server/tulipserver.py > ... > 2018/03/22 23:49:21 INFO: [INFO] File > "/usr/lib/ambari-agent/lib/ambari_ws4py/server/tulipserver.py", line 101 > 2018/03/22 23:49:21 INFO: [INFO] request_line = yield from > self.next_line() > 2018/03/22 23:49:21 INFO: [INFO] ^ > 2018/03/22 23:49:21 INFO: [INFO] SyntaxError: invalid syntax > 2018/03/22 23:49:21 INFO: [INFO] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23337) Remove python3 files from ws4py since they can cause build failure
[ https://issues.apache.org/jira/browse/AMBARI-23337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-23337: - Attachment: AMBARI-23337.patch > Remove python3 files from ws4py since they can cause build failure > -- > > Key: AMBARI-23337 > URL: https://issues.apache.org/jira/browse/AMBARI-23337 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-23337.patch > > > On some envs (not reproducible for me) it can result in failure like this: > > > 2018/03/22 23:49:21 INFO: [INFO] File > "/usr/lib/ambari-agent/lib/ambari_ws4py/async_websocket.py", line 85 > 2018/03/22 23:49:21 INFO: [INFO] yield from > self.proto.writer.drain() > 2018/03/22 23:49:21 INFO: [INFO] ^ > 2018/03/22 23:49:21 INFO: [INFO] SyntaxError: invalid syntax > 2018/03/22 23:49:21 INFO: [INFO] > 2018/03/22 23:49:21 INFO: [INFO] Compiling > /grid/0/jenkins/workspace/Zuul_Ambari_Build_Job/build-support/SOURCES/ambari/ambari-agent/target/rpm/ambari-agent/buildroot/usr/lib/ambari-agent/lib/ambari_ws4py/server/tulipserver.py > ... > 2018/03/22 23:49:21 INFO: [INFO] File > "/usr/lib/ambari-agent/lib/ambari_ws4py/server/tulipserver.py", line 101 > 2018/03/22 23:49:21 INFO: [INFO] request_line = yield from > self.next_line() > 2018/03/22 23:49:21 INFO: [INFO] ^ > 2018/03/22 23:49:21 INFO: [INFO] SyntaxError: invalid syntax > 2018/03/22 23:49:21 INFO: [INFO] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23336) Editing configurations usings configs.py doesnt have options to pass service config version note
[
https://issues.apache.org/jira/browse/AMBARI-23336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil S Naik updated AMBARI-23336:
--
Description:
Editing configurations usings configs.py doesnt have options to pass service
config version note
But we can pass service config version note via curl command and in ambari-ui
This feature should be implemented for actions 'SET' and 'DELETE'
Suggested give '-b' as option to give service config version note
ex :
{code:java}
/var/lib/ambari-server/resources/scripts/configs.py -u admin -p admin -t 8080
-n asnaik -l localhost -a set -c capacity-scheduler -k
"yarn.scheduler.capacity.resource-calculator" -v
"org.apache.hadoop.yarn.util.resource.DefaultResourceCalculator" -b "Creating a
new version with CPU scheduling off"
{code}
and the Help of the configs.py should be
Please edit the help page :
https://cwiki.apache.org/confluence/display/AMBARI/Modify+configurations#Modifyconfigurations-Editconfigurationusingconfigs.py
{code:java}
[root@pwd1 scripts]# /var/lib/ambari-server/resources/scripts/configs.py --help
Usage: configs.py [options]
Options:
-h, --helpshow this help message and exit
-t PORT, --port=PORT Optional port number for Ambari server. Default is
'8080'. Provide empty string to not use port.
-s PROTOCOL, --protocol=PROTOCOL
Optional support of SSL. Default protocol is 'http'
-a ACTION, --action=ACTION
Script action: , ,
-l HOST, --host=HOST Server external host name
-n CLUSTER, --cluster=CLUSTER
Name given to cluster. Ex: 'c1'
-c CONFIG_TYPE, --config-type=CONFIG_TYPE
One of the various configuration types in Ambari. Ex:
core-site, hdfs-site, mapred-queue-acls, etc.
-b VERSION_NOTE, --version-note=VERSION_NOTE
Version change notes which will help to know what has
been changed in this config , this value is optional
and is used for action set
To specify credentials please use "-e" OR "-u" and "-p'":
-u USER, --user=USER
Optional user ID to use for authentication. Default is
'admin'
-p PASSWORD, --password=PASSWORD
Optional password to use for authentication. Default
is 'admin'
-e CREDENTIALS_FILE, --credentials-file=CREDENTIALS_FILE
Optional file with user credentials separated by new
line.
To specify property(s) please use "-f" OR "-k" and "-v'":
-f FILE, --file=FILE
File where entire configurations are saved to, or read
from. Supported extensions (.xml, .json>)
-k KEY, --key=KEY Key that has to be set or deleted. Not necessary for
'get' action.
-v VALUE, --value=VALUE
Optional value to be set. Not necessary for 'get' or
'delete' actions.
{code}
was:
Editing configurations usings configs.py doesnt have options to pass service
config version note
But we can pass service config version note via curl command and in ambari-ui
This feature should be implemented for actions 'SET' and 'DELETE'
Suggested give '-b' as option to give service config version note
ex :
{code:java}
/var/lib/ambari-server/resources/scripts/configs.py -u admin -p admin -t 8080
-n asnaik -l localhost -a set -c capacity-scheduler -k
"yarn.scheduler.capacity.resource-calculator" -v
"org.apache.hadoop.yarn.util.resource.DefaultResourceCalculator" -b "Creating a
new version with CPU scheduling off"
{code}
and the Help of the configs.py should be
{code:java}
[root@pwd1 scripts]# /var/lib/ambari-server/resources/scripts/configs.py --help
Usage: configs.py [options]
Options:
-h, --helpshow this help message and exit
-t PORT, --port=PORT Optional port number for Ambari server. Default is
'8080'. Provide empty string to not use port.
-s PROTOCOL, --protocol=PROTOCOL
Optional support of SSL. Default protocol is 'http'
-a ACTION, --action=ACTION
Script action: , ,
-l HOST, --host=HOST Server external host name
-n CLUSTER, --cluster=CLUSTER
Name given to cluster. Ex: 'c1'
-c CONFIG_TYPE, --config-type=CONFIG_TYPE
One of the various configuration types in Ambari. Ex:
core-site, hdfs-site, mapred-queue-acls, etc.
-b VERSION_NOTE, --version-note=VERSION_NOTE
Version change notes which will help to know what has
been changed in this config , this value is optional
and is used for action set
To specify credentials
[jira] [Updated] (AMBARI-23336) Editing configurations usings configs.py doesnt have options to pass service config version note
[
https://issues.apache.org/jira/browse/AMBARI-23336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil S Naik updated AMBARI-23336:
--
Description:
Editing configurations usings configs.py doesnt have options to pass service
config version note
But we can pass service config version note via curl command and in ambari-ui
This feature should be implemented for actions 'SET' and 'DELETE'
Suggested give '-b' as option to give service config version note
ex :
{code:java}
/var/lib/ambari-server/resources/scripts/configs.py -u admin -p admin -t 8080
-n asnaik -l localhost -a set -c capacity-scheduler -k
"yarn.scheduler.capacity.resource-calculator" -v
"org.apache.hadoop.yarn.util.resource.DefaultResourceCalculator" -b "Creating a
new version with CPU scheduling off"
{code}
and the Help of the configs.py should be
{code:java}
[root@pwd1 scripts]# /var/lib/ambari-server/resources/scripts/configs.py --help
Usage: configs.py [options]
Options:
-h, --helpshow this help message and exit
-t PORT, --port=PORT Optional port number for Ambari server. Default is
'8080'. Provide empty string to not use port.
-s PROTOCOL, --protocol=PROTOCOL
Optional support of SSL. Default protocol is 'http'
-a ACTION, --action=ACTION
Script action: , ,
-l HOST, --host=HOST Server external host name
-n CLUSTER, --cluster=CLUSTER
Name given to cluster. Ex: 'c1'
-c CONFIG_TYPE, --config-type=CONFIG_TYPE
One of the various configuration types in Ambari. Ex:
core-site, hdfs-site, mapred-queue-acls, etc.
-b VERSION_NOTE, --version-note=VERSION_NOTE
Version change notes which will help to know what has
been changed in this config , this value is optional
and is used for action set
To specify credentials please use "-e" OR "-u" and "-p'":
-u USER, --user=USER
Optional user ID to use for authentication. Default is
'admin'
-p PASSWORD, --password=PASSWORD
Optional password to use for authentication. Default
is 'admin'
-e CREDENTIALS_FILE, --credentials-file=CREDENTIALS_FILE
Optional file with user credentials separated by new
line.
To specify property(s) please use "-f" OR "-k" and "-v'":
-f FILE, --file=FILE
File where entire configurations are saved to, or read
from. Supported extensions (.xml, .json>)
-k KEY, --key=KEY Key that has to be set or deleted. Not necessary for
'get' action.
-v VALUE, --value=VALUE
Optional value to be set. Not necessary for 'get' or
'delete' actions.
{code}
was:
Editing configurations usings configs.py doesnt have options to pass service
config version note
But we can pass service config version note via curl command and in ambari-ui
This feature should be implemented for actions 'SET' and 'DELETE'
Suggested give '-b' as option to give service config version note
ex :
{code:java}
/var/lib/ambari-server/resources/scripts/configs.py -u admin -p admin -t 8080
-n asnaik -l localhost -a set -c capacity-scheduler -k
"yarn.scheduler.capacity.resource-calculator" -v
"org.apache.hadoop.yarn.util.resource.DefaultResourceCalculator" -b "Creating a
new version with CPU scheduling off"
{code}
and the Help of the configs.py should be
{code:java}
[root@pwd1 scripts]# /var/lib/ambari-server/resources/scripts/configs.py --help
Usage: configs.py [options]
Options:
-h, --helpshow this help message and exit
-t PORT, --port=PORT Optional port number for Ambari server. Default is
'8080'. Provide empty string to not use port.
-s PROTOCOL, --protocol=PROTOCOL
Optional support of SSL. Default protocol is 'http'
-a ACTION, --action=ACTION
Script action: , ,
-l HOST, --host=HOST Server external host name
-n CLUSTER, --cluster=CLUSTER
Name given to cluster. Ex: 'c1'
-c CONFIG_TYPE, --config-type=CONFIG_TYPE
One of the various configuration types in Ambari. Ex:
core-site, hdfs-site, mapred-queue-acls, etc.
* -b VERSION_NOTE, --version-note=VERSION_NOTE
Version change notes which will help to know what has
been changed in this config , this value is optional
and is used for action set*
To specify credentials please use "-e" OR "-u" and "-p'":
-u USER, --user=USER
Optional user ID to use for authentication. Default is
[jira] [Updated] (AMBARI-23336) Editing configurations usings configs.py doesnt have options to pass service config version note
[
https://issues.apache.org/jira/browse/AMBARI-23336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akhil S Naik updated AMBARI-23336:
--
Description:
Editing configurations usings configs.py doesnt have options to pass service
config version note
But we can pass service config version note via curl command and in ambari-ui
This feature should be implemented for actions 'SET' and 'DELETE'
Suggested give '-b' as option to give service config version note
ex :
{code:java}
/var/lib/ambari-server/resources/scripts/configs.py -u admin -p admin -t 8080
-n asnaik -l localhost -a set -c capacity-scheduler -k
"yarn.scheduler.capacity.resource-calculator" -v
"org.apache.hadoop.yarn.util.resource.DefaultResourceCalculator" -b "Creating a
new version with CPU scheduling off"
{code}
and the Help of the configs.py should be
{code:java}
[root@pwd1 scripts]# /var/lib/ambari-server/resources/scripts/configs.py --help
Usage: configs.py [options]
Options:
-h, --helpshow this help message and exit
-t PORT, --port=PORT Optional port number for Ambari server. Default is
'8080'. Provide empty string to not use port.
-s PROTOCOL, --protocol=PROTOCOL
Optional support of SSL. Default protocol is 'http'
-a ACTION, --action=ACTION
Script action: , ,
-l HOST, --host=HOST Server external host name
-n CLUSTER, --cluster=CLUSTER
Name given to cluster. Ex: 'c1'
-c CONFIG_TYPE, --config-type=CONFIG_TYPE
One of the various configuration types in Ambari. Ex:
core-site, hdfs-site, mapred-queue-acls, etc.
* -b VERSION_NOTE, --version-note=VERSION_NOTE
Version change notes which will help to know what has
been changed in this config , this value is optional
and is used for action set*
To specify credentials please use "-e" OR "-u" and "-p'":
-u USER, --user=USER
Optional user ID to use for authentication. Default is
'admin'
-p PASSWORD, --password=PASSWORD
Optional password to use for authentication. Default
is 'admin'
-e CREDENTIALS_FILE, --credentials-file=CREDENTIALS_FILE
Optional file with user credentials separated by new
line.
To specify property(s) please use "-f" OR "-k" and "-v'":
-f FILE, --file=FILE
File where entire configurations are saved to, or read
from. Supported extensions (.xml, .json>)
-k KEY, --key=KEY Key that has to be set or deleted. Not necessary for
'get' action.
-v VALUE, --value=VALUE
Optional value to be set. Not necessary for 'get' or
'delete' actions.
{code}
was:
Editing configurations usings configs.py doesnt have options to pass service
config version note
But we can pass service config version note via curl command and in ambari-ui
This feature should be implemented
> Editing configurations usings configs.py doesnt have options to pass service
> config version note
>
>
> Key: AMBARI-23336
> URL: https://issues.apache.org/jira/browse/AMBARI-23336
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
> Environment: Ambari -2.6.1
>Reporter: Akhil S Naik
>Assignee: Akhil S Naik
>Priority: Major
>
> Editing configurations usings configs.py doesnt have options to pass service
> config version note
> But we can pass service config version note via curl command and in ambari-ui
> This feature should be implemented for actions 'SET' and 'DELETE'
> Suggested give '-b' as option to give service config version note
> ex :
> {code:java}
> /var/lib/ambari-server/resources/scripts/configs.py -u admin -p admin -t 8080
> -n asnaik -l localhost -a set -c capacity-scheduler -k
> "yarn.scheduler.capacity.resource-calculator" -v
> "org.apache.hadoop.yarn.util.resource.DefaultResourceCalculator" -b "Creating
> a new version with CPU scheduling off"
> {code}
> and the Help of the configs.py should be
> {code:java}
> [root@pwd1 scripts]# /var/lib/ambari-server/resources/scripts/configs.py
> --help
> Usage: configs.py [options]
> Options:
> -h, --helpshow this help message and exit
> -t PORT, --port=PORT Optional port number for Ambari server. Default is
> '8080'. Provide empty string to not use port.
> -s PROTOCOL, --protocol=PROTOCOL
> Optional support of SSL. Default protocol is 'http'
> -a
[jira] [Created] (AMBARI-23336) Editing configurations usings configs.py doesnt have options to pass service config version note
Akhil S Naik created AMBARI-23336: - Summary: Editing configurations usings configs.py doesnt have options to pass service config version note Key: AMBARI-23336 URL: https://issues.apache.org/jira/browse/AMBARI-23336 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 2.6.1 Environment: Ambari -2.6.1 Reporter: Akhil S Naik Assignee: Akhil S Naik Editing configurations usings configs.py doesnt have options to pass service config version note But we can pass service config version note via curl command and in ambari-ui This feature should be implemented -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23335) 400 server error when Cluster Administrator tries to add service and move components
Srikanth Janardhan created AMBARI-23335:
---
Summary: 400 server error when Cluster Administrator tries to add
service and move components
Key: AMBARI-23335
URL: https://issues.apache.org/jira/browse/AMBARI-23335
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Srikanth Janardhan
Assignee: Attila Magyar
Fix For: 2.7.0
Attachments: screenshot.png
STR:
# Deploy a HDP-3.0 cluster
# Create a user with role as "Cluster Administrator"
# Login as the user
# Click Add Service from the dashboard
# Click Next button in the wizard
The same error occurs while trying the Move Components wizard too.
Issue also present for Cluster Operator Role while moving components.
The page is stuck at this stage even after dismissing the popup.
{code:java|title=ambari-server.log}
17 Mar 2018 16:13:51,740 WARN [ambari-client-thread-524]
StackAdvisorCommand:204 - Error occurred during retrieving ldap configuration,
status=403, response={
"status" : 403,
"message" : "The authenticated user does not have the appropriate
authorizations to get the requested resource(s)"
}
17 Mar 2018 16:13:51,741 WARN [ambari-client-thread-524]
StackAdvisorCommand:182 - Error parsing services.json file content: Error
occurred during retrieving ldap configuration, status=403, response={
"status" : 403,
"message" : "The authenticated user does not have the appropriate
authorizations to get the requested resource(s)"
}
org.apache.ambari.server.api.services.stackadvisor.StackAdvisorException: Error
occurred during retrieving ldap configuration, status=403, response={
"status" : 403,
"message" : "The authenticated user does not have the appropriate
authorizations to get the requested resource(s)"
}
at
org.apache.ambari.server.api.services.stackadvisor.commands.StackAdvisorCommand.populateLdapConfiguration(StackAdvisorCommand.java:205)
at
org.apache.ambari.server.api.services.stackadvisor.commands.StackAdvisorCommand.adjust(StackAdvisorCommand.java:177)
at
org.apache.ambari.server.api.services.stackadvisor.commands.StackAdvisorCommand.invoke(StackAdvisorCommand.java:352)
at
org.apache.ambari.server.api.services.stackadvisor.StackAdvisorHelper.recommend(StackAdvisorHelper.java:132)
at
org.apache.ambari.server.controller.internal.RecommendationResourceProvider.createResources(RecommendationResourceProvider.java:145)
at
org.apache.ambari.server.controller.internal.ClusterControllerImpl.createResources(ClusterControllerImpl.java:296)
at
org.apache.ambari.server.api.services.persistence.PersistenceManagerImpl.create(PersistenceManagerImpl.java:97)
at
org.apache.ambari.server.api.handlers.CreateHandler.persist(CreateHandler.java:50)
at
org.apache.ambari.server.api.handlers.BaseManagementHandler.handleRequest(BaseManagementHandler.java:68)
at
org.apache.ambari.server.api.services.BaseRequest.process(BaseRequest.java:144)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:163)
at
org.apache.ambari.server.api.services.BaseService.handleRequest(BaseService.java:127)
at
org.apache.ambari.server.api.services.RecommendationService.getRecommendation(RecommendationService.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at
[jira] [Updated] (AMBARI-23334) Provider URL validator incorrect when setting up SSO via Ambari CLI
[
https://issues.apache.org/jira/browse/AMBARI-23334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23334:
Labels: pull-request-available (was: )
> Provider URL validator incorrect when setting up SSO via Ambari CLI
> ---
>
> Key: AMBARI-23334
> URL: https://issues.apache.org/jira/browse/AMBARI-23334
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> When setting the URL for the SSO provider while running {{ambari-server
> setup-sso}}, valid URLs are rejected.
> {noformat}
> [root@c7402 ~]# ambari-server setup-sso
> Using python /usr/bin/python
> Setting up SSO authentication properties...
> Do you want to configure SSO authentication [y/n] (y)?y
> Provider URL [URL]
> (http://example.com):https://c7402.ambari.apache.org:8443/gateway/knoxsso/api/v1/websso
> Invalid provider URL
> Provider URL [URL] (http://example.com):c7402.ambari.apache.org:8443
> Public Certificate pem (empty) (empty line to finish input):
> {noformat}
> Cause:
> The RegEx validating the URL is only allowing hostname and port values, when
> it should allow for absolute URLs.
> {code:java|title=ambari_server/setupSso.py:72}
> provider_url = get_validated_string_input("Provider URL [URL]
> ({0}):".format(provider_url), provider_url, REGEX_HOSTNAME_PORT,
> "Invalid provider URL",
> False){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23243) Adding missing properties to OneFS mpack
[ https://issues.apache.org/jira/browse/AMBARI-23243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar resolved AMBARI-23243. Resolution: Fixed > Adding missing properties to OneFS mpack > > > Key: AMBARI-23243 > URL: https://issues.apache.org/jira/browse/AMBARI-23243 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 > Environment: > > >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Following properties should be added to the appropriate config > * hadoop.security.token.service.use_ip should be false when kerberos is > enabled > * dfs.checksum.type should always be null > * dfs.datanode.http.address/dfs.datanode.https.address = > 0.0.0.0:8082/0.0.0.0:8080 [?] > * -yarn.scheduler.capacity.node-locality-delay = 0- > * dfs.client-write-packet-size = 131072 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23243) Adding missing properties to OneFS mpack
[ https://issues.apache.org/jira/browse/AMBARI-23243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated AMBARI-23243: --- Description: Following properties should be added to the appropriate config * hadoop.security.token.service.use_ip should be false when kerberos is enabled * dfs.checksum.type should always be null * dfs.datanode.http.address/dfs.datanode.https.address = 0.0.0.0:8082/0.0.0.0:8080 [?] * -yarn.scheduler.capacity.node-locality-delay = 0- * dfs.client-write-packet-size = 131072 was: Following properties should be added to the appropriate config * hadoop.security.token.service.use_ip should be false when kerberos is enabled * dfs.checksum.type should always be null * dfs.datanode.http.address/dfs.datanode.https.address = 0.0.0.0:8082/0.0.0.0:8080 [?] * yarn.scheduler.capacity.node-locality-delay = 0 * dfs.client-write-packet-size = 131072 > Adding missing properties to OneFS mpack > > > Key: AMBARI-23243 > URL: https://issues.apache.org/jira/browse/AMBARI-23243 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 > Environment: > > >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Following properties should be added to the appropriate config > * hadoop.security.token.service.use_ip should be false when kerberos is > enabled > * dfs.checksum.type should always be null > * dfs.datanode.http.address/dfs.datanode.https.address = > 0.0.0.0:8082/0.0.0.0:8080 [?] > * -yarn.scheduler.capacity.node-locality-delay = 0- > * dfs.client-write-packet-size = 131072 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23334) Provider URL validator incorrect when setting up SSO via Ambari CLI
Sandor Molnar created AMBARI-23334:
--
Summary: Provider URL validator incorrect when setting up SSO via
Ambari CLI
Key: AMBARI-23334
URL: https://issues.apache.org/jira/browse/AMBARI-23334
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 2.7.0
When setting the URL for the SSO provider while running {{ambari-server
setup-sso}}, valid URLs are rejected.
{noformat}
[root@c7402 ~]# ambari-server setup-sso
Using python /usr/bin/python
Setting up SSO authentication properties...
Do you want to configure SSO authentication [y/n] (y)?y
Provider URL [URL]
(http://example.com):https://c7402.ambari.apache.org:8443/gateway/knoxsso/api/v1/websso
Invalid provider URL
Provider URL [URL] (http://example.com):c7402.ambari.apache.org:8443
Public Certificate pem (empty) (empty line to finish input):
{noformat}
Cause:
The RegEx validating the URL is only allowing hostname and port values, when it
should allow for absolute URLs.
{code:java|title=ambari_server/setupSso.py:72}
provider_url = get_validated_string_input("Provider URL [URL]
({0}):".format(provider_url), provider_url, REGEX_HOSTNAME_PORT,
"Invalid provider URL",
False){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23306) Ambari Upgrade: Start All Services fails after AU at MapReduce2 Client Install with error "Configuration parameter 'container-executor' was not found in configuratio
[
https://issues.apache.org/jira/browse/AMBARI-23306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16410966#comment-16410966
]
Hudson commented on AMBARI-23306:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8901 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8901/])
AMBARI-23306. Make sure we have container-executor after Ambari upgrade
(6454655+adoroszlai:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=75670a8b895319d7f0d4b7db95f870778af6d3c6])
* (edit)
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration/container-executor.xml
> Ambari Upgrade: Start All Services fails after AU at MapReduce2 Client
> Install with error "Configuration parameter 'container-executor' was not
> found in configurations dictionary!"
> -
>
> Key: AMBARI-23306
> URL: https://issues.apache.org/jira/browse/AMBARI-23306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Blocker
> Labels: pull-request-available, upgrade
> Fix For: 2.7.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> After Ambari Upgrade from 2.6.0.0 to 2.7.0.0 , start all services operation
> fails at MapReduce2 Client Install with below error.
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/mapreduce2_client.py",
> line 91, in
> MapReduce2Client().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 377, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/mapreduce2_client.py",
> line 41, in install
> self.configure(env)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 122, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/mapreduce2_client.py",
> line 50, in configure
> yarn(config_dir=config_dir)
> File "/usr/lib/ambari-agent/lib/ambari_commons/os_family_impl.py", line 89,
> in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/yarn.py",
> line 166, in yarn
> content=InlineTemplate(params.container_executor_cfg_template)
> File "/usr/lib/ambari-agent/lib/resource_management/core/source.py", line
> 150, in __init__
> super(InlineTemplate, self).__init__(name, extra_imports, **kwargs)
> File "/usr/lib/ambari-agent/lib/resource_management/core/source.py", line
> 137, in __init__
> self.template = self.template_env.get_template(self.name)
> File "/usr/lib/ambari-agent/lib/ambari_jinja2/environment.py", line 716, in
> get_template
> return self._load_template(name, self.make_globals(globals))
> File "/usr/lib/ambari-agent/lib/ambari_jinja2/environment.py", line 686, in
> _load_template
> template = self.cache.get(name)
> File "/usr/lib/ambari-agent/lib/ambari_jinja2/utils.py", line 405, in get
> return self[key]
> File "/usr/lib/ambari-agent/lib/ambari_jinja2/utils.py", line 448, in
> __getitem__
> rv = self._mapping[key]
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter
> 'container-executor' was not found in configurations dictionary!
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23306) Ambari Upgrade: Start All Services fails after AU at MapReduce2 Client Install with error "Configuration parameter 'container-executor' was not found in configurations
[
https://issues.apache.org/jira/browse/AMBARI-23306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated AMBARI-23306:
---
Status: Patch Available (was: In Progress)
> Ambari Upgrade: Start All Services fails after AU at MapReduce2 Client
> Install with error "Configuration parameter 'container-executor' was not
> found in configurations dictionary!"
> -
>
> Key: AMBARI-23306
> URL: https://issues.apache.org/jira/browse/AMBARI-23306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Blocker
> Labels: pull-request-available, upgrade
> Fix For: 2.7.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> After Ambari Upgrade from 2.6.0.0 to 2.7.0.0 , start all services operation
> fails at MapReduce2 Client Install with below error.
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/mapreduce2_client.py",
> line 91, in
> MapReduce2Client().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 377, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/mapreduce2_client.py",
> line 41, in install
> self.configure(env)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 122, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/mapreduce2_client.py",
> line 50, in configure
> yarn(config_dir=config_dir)
> File "/usr/lib/ambari-agent/lib/ambari_commons/os_family_impl.py", line 89,
> in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/yarn.py",
> line 166, in yarn
> content=InlineTemplate(params.container_executor_cfg_template)
> File "/usr/lib/ambari-agent/lib/resource_management/core/source.py", line
> 150, in __init__
> super(InlineTemplate, self).__init__(name, extra_imports, **kwargs)
> File "/usr/lib/ambari-agent/lib/resource_management/core/source.py", line
> 137, in __init__
> self.template = self.template_env.get_template(self.name)
> File "/usr/lib/ambari-agent/lib/ambari_jinja2/environment.py", line 716, in
> get_template
> return self._load_template(name, self.make_globals(globals))
> File "/usr/lib/ambari-agent/lib/ambari_jinja2/environment.py", line 686, in
> _load_template
> template = self.cache.get(name)
> File "/usr/lib/ambari-agent/lib/ambari_jinja2/utils.py", line 405, in get
> return self[key]
> File "/usr/lib/ambari-agent/lib/ambari_jinja2/utils.py", line 448, in
> __getitem__
> rv = self._mapping[key]
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/config_dictionary.py",
> line 73, in __getattr__
> raise Fail("Configuration parameter '" + self.name + "' was not found in
> configurations dictionary!")
> resource_management.core.exceptions.Fail: Configuration parameter
> 'container-executor' was not found in configurations dictionary!
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23333) Query should support wildcard or regexp
Xianghao Lu created AMBARI-2: Summary: Query should support wildcard or regexp Key: AMBARI-2 URL: https://issues.apache.org/jira/browse/AMBARI-2 Project: Ambari Issue Type: Task Components: ambari-logsearch Reporter: Xianghao Lu Solr supports wildcard and regular expression when query, refer to [Solr query wiki|https://wiki.apache.org/solr/SolrQuerySyntax] But both ambari-logsearch and spring-data-solr will escape special characters used in wildcard or regular expression, as a result, I only can use accurate match in Log search ui. Will ambari-logsearch support wildcard and regular expression in the future? Escaping special characters in spring-data-solr: function escapeCriteriaValue() in [QueryParserBase.java|https://github.com/spring-projects/spring-data-solr/blob/master/src/main/java/org/springframework/data/solr/core/QueryParserBase.java] Escaping special characters in ambari-logsearch: function escapeQueryChars() in [SolrUtil.java|https://github.com/apache/ambari/blob/trunk/ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/util/SolrUtil.java] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
