[jira] [Resolved] (AMBARI-23307) Rename AMBARI_INFRA to AMBARI_INFRA_SOLR in upgrade helper script
[ https://issues.apache.org/jira/browse/AMBARI-23307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-23307. --- Resolution: Fixed > Rename AMBARI_INFRA to AMBARI_INFRA_SOLR in upgrade helper script > - > > Key: AMBARI-23307 > URL: https://issues.apache.org/jira/browse/AMBARI-23307 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23316) Infra Solr - migrationHelper script should work in unsecure mode
[ https://issues.apache.org/jira/browse/AMBARI-23316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-23316. --- Resolution: Fixed > Infra Solr - migrationHelper script should work in unsecure mode > > > Key: AMBARI-23316 > URL: https://issues.apache.org/jira/browse/AMBARI-23316 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23276) Maven cleanup
[
https://issues.apache.org/jira/browse/AMBARI-23276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila resolved AMBARI-23276.
Resolution: Fixed
> Maven cleanup
> -
>
> Key: AMBARI-23276
> URL: https://issues.apache.org/jira/browse/AMBARI-23276
> Project: Ambari
> Issue Type: Task
>Affects Versions: trunk
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Major
> Labels: pull-request-available
> Fix For: trunk
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Clean up some of the duplications in {{pom.xml}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23296) Python UT failure
[ https://issues.apache.org/jira/browse/AMBARI-23296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila updated AMBARI-23296: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Python UT failure > - > > Key: AMBARI-23296 > URL: https://issues.apache.org/jira/browse/AMBARI-23296 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-23296.patch > > Time Spent: 40m > Remaining Estimate: 0h > > ERROR: test_get_service_base_dir (TestFileCache.TestFileCache) > -- > ERROR 2018-03-20 06:58:54,744 - Python unit tests failed > Traceback (most recent call last): > File > "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-common/src/test/python/mock/mock.py", > line 1199, in patched > return func(*args, **keywargs) > File > "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-agent/src/test/python/ambari_agent/TestFileCache.py", > line 72, in test_get_service_base_dir > res = fileCache.get_service_base_dir(command, "server_url_pref") > File > "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-agent/src/main/python/ambari_agent/FileCache.py", > line 77, in get_service_base_dir > if 'service_package_folder' in command['commandParams']: > KeyError: 'commandParams' > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23295) Python UT failure
[ https://issues.apache.org/jira/browse/AMBARI-23295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doroszlai, Attila resolved AMBARI-23295. Resolution: Duplicate > Python UT failure > - > > Key: AMBARI-23295 > URL: https://issues.apache.org/jira/browse/AMBARI-23295 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.0 > > > ERROR: test_get_service_base_dir (TestFileCache.TestFileCache) > -- > ERROR 2018-03-20 06:58:54,744 - Python unit tests failed > Traceback (most recent call last): > File > "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-common/src/test/python/mock/mock.py", > line 1199, in patched > return func(*args, **keywargs) > File > "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-agent/src/test/python/ambari_agent/TestFileCache.py", > line 72, in test_get_service_base_dir > res = fileCache.get_service_base_dir(command, "server_url_pref") > File > "/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-agent/src/main/python/ambari_agent/FileCache.py", > line 77, in get_service_base_dir > if 'service_package_folder' in command['commandParams']: > KeyError: 'commandParams' > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23263) hdfs-site.xml is not getting updated after config change and restart via Ambari
[ https://issues.apache.org/jira/browse/AMBARI-23263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16408649#comment-16408649 ] Hudson commented on AMBARI-23263: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8891 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8891/]) AMBARI-23263. hdfs-site.xml is not getting updated after config change (mpapirkovskyy: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=2caa282fdd0ed47167a459b86d1358ef0d26c39f]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/dao/ClusterDAO.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Cluster.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterConfigEntity.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java > hdfs-site.xml is not getting updated after config change and restart via > Ambari > --- > > Key: AMBARI-23263 > URL: https://issues.apache.org/jira/browse/AMBARI-23263 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > 1. Changed 'dfs.datanode.data.dir' in hdfs-site.xml to new value. > 2. Restarted HDFS service. > 3. The value of 'dfs.datanode.data.dir' is not updated in hdfs-site.xml. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23320) Replace calls to Class#newInstance
Ted Yu created AMBARI-23320: --- Summary: Replace calls to Class#newInstance Key: AMBARI-23320 URL: https://issues.apache.org/jira/browse/AMBARI-23320 Project: Ambari Issue Type: Improvement Reporter: Ted Yu Class#newInstance is deprecated starting in Java 9 - https://bugs.openjdk.java.net/browse/JDK-6850612 - because it may throw undeclared checked exceptions. The suggested replacement is getDeclaredConstructor().newInstance(), which wraps the checked exceptions in InvocationException. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22943) Wrong condition in FixCapacitySchedulerOrderingPolicy#execute()
[
https://issues.apache.org/jira/browse/AMBARI-22943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated AMBARI-22943:
Description:
{code}
} else if (!orderingPolicyValue.equals(UTILIZATION) ||
!orderingPolicyValue.equals(PRIORITY_UTILIZATION)) {
{code}
Regardless of the value for orderingPolicyValue, the condition would be true.
was:
{code}
} else if (!orderingPolicyValue.equals(UTILIZATION) ||
!orderingPolicyValue.equals(PRIORITY_UTILIZATION)) {
{code}
Regardless of the value for orderingPolicyValue, the condition would be true.
> Wrong condition in FixCapacitySchedulerOrderingPolicy#execute()
> ---
>
> Key: AMBARI-22943
> URL: https://issues.apache.org/jira/browse/AMBARI-22943
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Major
>
> {code}
> } else if (!orderingPolicyValue.equals(UTILIZATION) ||
> !orderingPolicyValue.equals(PRIORITY_UTILIZATION)) {
> {code}
> Regardless of the value for orderingPolicyValue, the condition would be true.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23319) Provide for mpack definition tarballs crc32 or md5 checksums, to validate downloaded files
Scott Duan created AMBARI-23319: --- Summary: Provide for mpack definition tarballs crc32 or md5 checksums, to validate downloaded files Key: AMBARI-23319 URL: https://issues.apache.org/jira/browse/AMBARI-23319 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Scott Duan Assignee: Scott Duan Fix For: 3.0.0 from the start, not fully downloaded or become broken after some hardware failure. The idea is, to provide crc32 or md5 checksum to verify them before start working with them, as it happen with rpm files and yum. Checksum could be provided as separate file: definition_name.tar.gz.crc32 or inside mpack.json -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23263) hdfs-site.xml is not getting updated after config change and restart via Ambari
[ https://issues.apache.org/jira/browse/AMBARI-23263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23263: Labels: pull-request-available (was: ) > hdfs-site.xml is not getting updated after config change and restart via > Ambari > --- > > Key: AMBARI-23263 > URL: https://issues.apache.org/jira/browse/AMBARI-23263 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.7.0 >Reporter: Myroslav Papirkovskyi >Assignee: Myroslav Papirkovskyi >Priority: Blocker > Labels: pull-request-available > Fix For: 2.7.0 > > > 1. Changed 'dfs.datanode.data.dir' in hdfs-site.xml to new value. > 2. Restarted HDFS service. > 3. The value of 'dfs.datanode.data.dir' is not updated in hdfs-site.xml. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23315) Incorrect text for Druid and Superset kerberos property names
[ https://issues.apache.org/jira/browse/AMBARI-23315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16408333#comment-16408333 ] Hudson commented on AMBARI-23315: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8890 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8890/]) AMBARI-23315 Incorrect text for Druid and Superset kerberos property (mgergely: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=e751205fb089deffd7fb0253752f140891213f43]) * (edit) ambari-web/app/data/configs/wizards/kerberos_identities.js > Incorrect text for Druid and Superset kerberos property names > - > > Key: AMBARI-23315 > URL: https://issues.apache.org/jira/browse/AMBARI-23315 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Minor > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23293) Fix the following : 1. Host Component deletes are broken 2. Use resource Type in for getting resources from Mpack Modules.
[
https://issues.apache.org/jira/browse/AMBARI-23293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar resolved AMBARI-23293.
--
Resolution: Fixed
> Fix the following : 1. Host Component deletes are broken 2. Use resource Type
> in for getting resources from Mpack Modules.
> --
>
> Key: AMBARI-23293
> URL: https://issues.apache.org/jira/browse/AMBARI-23293
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
>Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> After Fix:
> *1. Host Component Delete*:
> {code:title=DELETE
> http://:8080/api/v1/clusters/c1/hosts//host_components/13}
> {
> "deleteResult" : [
> {
> "deleted" : {
> "key" : "component_id: 13"
> }
> }
> ]
> }
> {code}
> *2. Use resource Type in for getting resources from Mpack Modules.*
> *Reason:* When we are creating a Service, Host Component and Service
> Component when *name* provided is not same as the *type*, we need to use the
> ResourceType to refer the mpack to get the resource component from stack.
> Eg:
> {code}
> {
> "ServiceInfo":{
> "service_group_name":"dev",
> "service_type":"ZOOKEEPER",
> "service_name":"ZOOKEEPER_dev"
> }
>}
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-14163) zookeeper session timeout for hbase should take zookeeper tickTime into account
[ https://issues.apache.org/jira/browse/AMBARI-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-14163: Description: With tickTime=2000 in zoo.cfg, I tried to set zookeeper.session.timeout value of 1 min 40 seconds. The change was accepted. However, such timeout is not reachable (it is > 20 times tickTime). Ambari should detect such scenario and warn user. was: With tickTime=2000 in zoo.cfg, I tried to set zookeeper.session.timeout value of 1 min 40 seconds. The change was accepted. However, such timeout is not reachable (it is > 20 times tickTime). Ambari should detect such scenario and warn user. > zookeeper session timeout for hbase should take zookeeper tickTime into > account > --- > > Key: AMBARI-14163 > URL: https://issues.apache.org/jira/browse/AMBARI-14163 > Project: Ambari > Issue Type: Bug >Reporter: Ted Yu >Priority: Major > > With tickTime=2000 in zoo.cfg, I tried to set zookeeper.session.timeout value > of 1 min 40 seconds. > The change was accepted. > However, such timeout is not reachable (it is > 20 times tickTime). > Ambari should detect such scenario and warn user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (AMBARI-18528) Need a way to escape config values that contain $
[
https://issues.apache.org/jira/browse/AMBARI-18528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15603928#comment-15603928
]
Ted Yu edited comment on AMBARI-18528 at 3/21/18 5:33 PM:
--
Escaping the dollar sign automatically is a desirable solution.
was (Author: yuzhih...@gmail.com):
Escaping the dollar sign automatically is a desirable solution .
> Need a way to escape config values that contain $
> -
>
> Key: AMBARI-18528
> URL: https://issues.apache.org/jira/browse/AMBARI-18528
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>Priority: Major
> Labels: zookeeper
>
> We tried specifying auth_to_local in zookeeper env input box:
> {code}
> export SERVER_JVMFLAGS="$SERVER_JVMFLAGS
> -Dzookeeper.security.auth_to_local=RULE:[2:$1@$0](hb...@c.net)s/.*/hbase/
> -Djava.security.auth.login.config={{zk_server_jaas_file}}"
> {code}
> However, when zookeeper quorum starts, the rule got interrupted with
> zkServer.sh
> We should add the capability of specifying auth_to_local in Ambari UI
--
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 ] ASF GitHub Bot updated AMBARI-23243: Labels: pull-request-available (was: ) > 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 > > > 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] [Commented] (AMBARI-23307) Rename AMBARI_INFRA to AMBARI_INFRA_SOLR in upgrade helper script
[ https://issues.apache.org/jira/browse/AMBARI-23307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16408145#comment-16408145 ] Hudson commented on AMBARI-23307: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8889 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8889/]) AMBARI-23307. Rename AMBARI_INFRA to AMBARI_INFRA_SOLR in upgrade helper (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=77f358a76ee3b2fdfcc5a24ec5fde3a9d49b35a9]) * (edit) ambari-infra/ambari-infra-solr-client/src/main/python/migrationHelper.py > Rename AMBARI_INFRA to AMBARI_INFRA_SOLR in upgrade helper script > - > > Key: AMBARI-23307 > URL: https://issues.apache.org/jira/browse/AMBARI-23307 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23318) API Addition for Upgrade Plan
Nate Cole created AMBARI-23318: -- Summary: API Addition for Upgrade Plan Key: AMBARI-23318 URL: https://issues.apache.org/jira/browse/AMBARI-23318 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 3.0.0 Add an endpoint to create upgrade plans. An upgrade plan holds all the "configuration" settings for an upgrade, as well as the service groups and target mpacks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23317) Management Packs: Upgrade Orchestration
Nate Cole created AMBARI-23317: -- Summary: Management Packs: Upgrade Orchestration Key: AMBARI-23317 URL: https://issues.apache.org/jira/browse/AMBARI-23317 Project: Ambari Issue Type: Epic Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 3.0.0 This Epic covers work items need for changes to upgrade orchestration based on the mpack model. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23316) Infra Solr - migrationHelper script should work in unsecure mode
[ https://issues.apache.org/jira/browse/AMBARI-23316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23316: Labels: pull-request-available (was: ) > Infra Solr - migrationHelper script should work in unsecure mode > > > Key: AMBARI-23316 > URL: https://issues.apache.org/jira/browse/AMBARI-23316 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-23097) Log Search: knox proxy support
[ https://issues.apache.org/jira/browse/AMBARI-23097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-23097. --- Resolution: Fixed > Log Search: knox proxy support > -- > > Key: AMBARI-23097 > URL: https://issues.apache.org/jira/browse/AMBARI-23097 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Add knox proxy support and update knox docker env with that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23316) Infra Solr - migrationHelper script should work in unsecure mode
Olivér Szabó created AMBARI-23316: - Summary: Infra Solr - migrationHelper script should work in unsecure mode Key: AMBARI-23316 URL: https://issues.apache.org/jira/browse/AMBARI-23316 Project: Ambari Issue Type: Bug Components: ambari-infra Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23097) Log Search: knox proxy support
[ https://issues.apache.org/jira/browse/AMBARI-23097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16408050#comment-16408050 ] Hudson commented on AMBARI-23097: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit # (See [https://builds.apache.org/job/Ambari-trunk-Commit//]) AMBARI-23097. Log Search: knox proxy support (#733) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=b149d123531909db322c5cc12dd545199585211d]) * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/web/security/LogsearchAuthenticationProvider.java * (edit) ambari-logsearch/docker/knox/logsearch/1.0.0/service.xml * (edit) ambari-logsearch/docker/knox/logsearch/1.0.0/rewrite.xml * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/web/filters/LogsearchAuthenticationEntryPoint.java * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/auth/filter/AbstractJWTFilter.java * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/SecurityConfig.java > Log Search: knox proxy support > -- > > Key: AMBARI-23097 > URL: https://issues.apache.org/jira/browse/AMBARI-23097 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Add knox proxy support and update knox docker env with that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23315) Incorrect text for Druid and Superset kerberos property names
[ https://issues.apache.org/jira/browse/AMBARI-23315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23315: Labels: pull-request-available (was: ) > Incorrect text for Druid and Superset kerberos property names > - > > Key: AMBARI-23315 > URL: https://issues.apache.org/jira/browse/AMBARI-23315 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Reporter: Miklos Gergely >Assignee: Miklos Gergely >Priority: Minor > Labels: pull-request-available > Fix For: 2.7.0 > > -- 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
]
Jonathan Hurley updated AMBARI-23314:
-
Description:
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.
was:
The operating systems endpoint allows for creation and deletion of repositories
which are associated with a single management pack:
{code:title=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.
> 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
> 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-23315) Incorrect text for Druid and Superset kerberos property names
Miklos Gergely created AMBARI-23315: --- Summary: Incorrect text for Druid and Superset kerberos property names Key: AMBARI-23315 URL: https://issues.apache.org/jira/browse/AMBARI-23315 Project: Ambari Issue Type: Bug Components: ambari-web Reporter: Miklos Gergely Assignee: Miklos Gergely Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23314) Prevent Multiple OS Entries For a Single Mpack
Jonathan Hurley created AMBARI-23314:
Summary: 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
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:title=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] [Updated] (AMBARI-23313) JS error on service stop/restart after config changes
[
https://issues.apache.org/jira/browse/AMBARI-23313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-23313:
Labels: pull-request-available (was: )
> JS error on service stop/restart after config changes
> -
>
> Key: AMBARI-23313
> URL: https://issues.apache.org/jira/browse/AMBARI-23313
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.7.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> Steps:
> # Change the value of fs.trash.interval for HDFS service.
> # Save configs
> # Notice Restart required icon
> # Try to apply 'Restart All Affected'
> No op was triggered. Could see js error error in console:
> {noformat}
> Uncaught TypeError: Cannot read property 'get' of undefined
> pullNnCheckPointTime @ app.js:27950
> checkNnLastCheckpointTime @ app.js:27905
> restartAllStaleConfigComponents @ app.js:26478
> ActionHelper.registeredActions.(anonymous function).handler @ vendor.js:31554
> (anonymous function) @ vendor.js:23346
> jQuery.event.dispatch @ vendor.js:3178
> elemData.handle @ vendor.js:2854
> app.js:56248
> {noformat}
> Also for 'Stop' service operation:
> {noformat}
> Uncaught TypeError: Cannot read property 'get' of undefined
> pullNnCheckPointTime @ app.js:27950
> checkNnLastCheckpointTime @ app.js:27905
> startStopPopup @ app.js:27842
> stopService @ app.js:28176
> doAction @ app.js:28662
> ActionHelper.registeredActions.(anonymous function).handler @ vendor.js:31554
> (anonymous function) @ vendor.js:23346
> jQuery.event.dispatch @ vendor.js:3178
> elemData.handle @ vendor.js:2854
> app.js:56248
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23313) JS error on service stop/restart after config changes
Andrii Babiichuk created AMBARI-23313:
-
Summary: JS error on service stop/restart after config changes
Key: AMBARI-23313
URL: https://issues.apache.org/jira/browse/AMBARI-23313
Project: Ambari
Issue Type: Bug
Components: ambari-web
Affects Versions: 2.7.0
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
Fix For: 2.7.0
Steps:
# Change the value of fs.trash.interval for HDFS service.
# Save configs
# Notice Restart required icon
# Try to apply 'Restart All Affected'
No op was triggered. Could see js error error in console:
{noformat}
Uncaught TypeError: Cannot read property 'get' of undefined
pullNnCheckPointTime @ app.js:27950
checkNnLastCheckpointTime @ app.js:27905
restartAllStaleConfigComponents @ app.js:26478
ActionHelper.registeredActions.(anonymous function).handler @ vendor.js:31554
(anonymous function) @ vendor.js:23346
jQuery.event.dispatch @ vendor.js:3178
elemData.handle @ vendor.js:2854
app.js:56248
{noformat}
Also for 'Stop' service operation:
{noformat}
Uncaught TypeError: Cannot read property 'get' of undefined
pullNnCheckPointTime @ app.js:27950
checkNnLastCheckpointTime @ app.js:27905
startStopPopup @ app.js:27842
stopService @ app.js:28176
doAction @ app.js:28662
ActionHelper.registeredActions.(anonymous function).handler @ vendor.js:31554
(anonymous function) @ vendor.js:23346
jQuery.event.dispatch @ vendor.js:3178
elemData.handle @ vendor.js:2854
app.js:56248
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23312) Regression : Adding Atlas Metadata server' for HA on an host takes forever.
[ https://issues.apache.org/jira/browse/AMBARI-23312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23312: Labels: pull-request-available (was: ) > Regression : Adding Atlas Metadata server' for HA on an host takes forever. > --- > > Key: AMBARI-23312 > URL: https://issues.apache.org/jira/browse/AMBARI-23312 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Labels: pull-request-available > Fix For: 2.6.2, 2.7.0 > > Attachments: Ambari-issue.png > > > Atlas is already installed in the cluster. To make Atlas HA , tried to add a > new instance of Atlas Metadata server on host summary page. if Atlas Metadata > server is added, "Confirmation" window keeps buffering forever. > refer to screenshot provided > Workaround : > 1. Inspect on the Confirm button > 2. Remove the "disabled" attribute (Now Confirm button is enabled) > 3. Submit the confirm button -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23312) Regression : Adding Atlas Metadata server' for HA on an host takes forever.
[ https://issues.apache.org/jira/browse/AMBARI-23312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-23312: -- Attachment: Ambari-issue.png > Regression : Adding Atlas Metadata server' for HA on an host takes forever. > --- > > Key: AMBARI-23312 > URL: https://issues.apache.org/jira/browse/AMBARI-23312 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Fix For: 2.6.2, 2.7.0 > > Attachments: Ambari-issue.png > > > Atlas is already installed in the cluster. To make Atlas HA , tried to add a > new instance of Atlas Metadata server on host summary page. if Atlas Metadata > server is added, "Confirmation" window keeps buffering forever. > refer to screenshot provided > Workaround : > 1. Inspect on the Confirm button > 2. Remove the "disabled" attribute (Now Confirm button is enabled) > 3. Submit the confirm button -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23312) Regression : Adding Atlas Metadata server' for HA on an host takes forever.
Andrii Tkach created AMBARI-23312: - Summary: Regression : Adding Atlas Metadata server' for HA on an host takes forever. Key: AMBARI-23312 URL: https://issues.apache.org/jira/browse/AMBARI-23312 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.2 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.6.2, 2.7.0 Atlas is already installed in the cluster. To make Atlas HA , tried to add a new instance of Atlas Metadata server on host summary page. if Atlas Metadata server is added, "Confirmation" window keeps buffering forever. refer to screenshot provided Workaround : 1. Inspect on the Confirm button 2. Remove the "disabled" attribute (Now Confirm button is enabled) 3. Submit the confirm button -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23309) YARN cluster memory graph is not loading in Ambari 2.6
[ https://issues.apache.org/jira/browse/AMBARI-23309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Tkach updated AMBARI-23309: -- Attachment: Screen Shot 2018-03-16 at 1.14.34 PM.png > YARN cluster memory graph is not loading in Ambari 2.6 > -- > > Key: AMBARI-23309 > URL: https://issues.apache.org/jira/browse/AMBARI-23309 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: Screen Shot 2018-03-16 at 1.14.34 PM.png > > Time Spent: 10m > Remaining Estimate: 0h > > Users are not able to see cluster memory graph under YARN. This was working > before upgrade. > We were able to reproduce this internally on Ambari 2.6. We checked across 5 > clusters and all of them exhibited same behaviour. > Seems like problem with the compute : mem_total._sum - mem_free._sum fails > but mem_total._sum + mem_free._sum succeeds. > Also if we load mem_total._sum AND mem_free._sum individually, they come up > fine. > Seems like issue when we do a 'subtract'. > Attaching UI Screenshot -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23311) Use Ambari CLI to specify which services should be setup for SSO integration
Sandor Molnar created AMBARI-23311:
--
Summary: 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
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] [Commented] (AMBARI-23284) Add Ambari configuration data to stack/service advisor input data
[
https://issues.apache.org/jira/browse/AMBARI-23284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407825#comment-16407825
]
Hudson commented on AMBARI-23284:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8887 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8887/])
AMBARI-23284. Add Ambari configuration data to stack/service advisor
(m.magyar3:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=62d14a016156719c1c873809adc2ca2601a0d10c])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/api/services/stackadvisor/commands/StackAdvisorCommand.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/api/services/stackadvisor/commands/StackAdvisorCommandTest.java
> Add Ambari configuration data to stack/service advisor input data
> -
>
> Key: AMBARI-23284
> URL: https://issues.apache.org/jira/browse/AMBARI-23284
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Add Ambari configuration data to stack/service advisor input data. Currently
> the {{ldap-configuration}} data is passed in to the stack/service advisor.
> However, generically all Ambari configuration data should be passed in.
> For example, the current data set (in service.json) contains
> {code:java}
> {
> ... "services" : [],
> ... "configurations" : \{ ... }, "ambari-server-properties" : \{ ... },
> ... "ldap-configurations" : \{ ... }
> }
>
> {code}
>
> "\{{ldap-configurations}}" may or may not exist depending on if LDAP
> authentication/sync was setup. This should be treated generically and part of
> a larger block of data named "\{{ambari-server-configuration}}". For example:
> {code:java}
> {
> ...
> "services" : [],
> ...
> "configurations" :
> { ... },
> "ambari-server-properties" : { ... }
> ,
> ...
> "ambari-server-configuration" : {
> "ldap-configurations" :
> { ... }
> ,
> ...
> }
> }
>
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-23310) Add SSO-related configuration recommendations to the stack advisor
Robert Levas created AMBARI-23310:
-
Summary: 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
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] [Commented] (AMBARI-23283) Install Wizard > Select Version page: the user cannot proceed with Redhat Satellite option
[ https://issues.apache.org/jira/browse/AMBARI-23283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407791#comment-16407791 ] Hudson commented on AMBARI-23283: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #662 (See [https://builds.apache.org/job/Ambari-branch-2.6/662/]) AMBARI-23283 Install Wizard > Select Version page: the user cannot (1963907+atkach: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=63cfebb176bca5e204f9fdc84a34e2cc03ffbc02]) * (edit) ambari-web/app/views/wizard/step1_view.js * (edit) ambari-web/test/views/wizard/step1_view_test.js > Install Wizard > Select Version page: the user cannot proceed with Redhat > Satellite option > -- > > Key: AMBARI-23283 > URL: https://issues.apache.org/jira/browse/AMBARI-23283 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.2, 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Labels: pull-request-available > Fix For: 2.6.2, 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > STR: > * Launch Install Wizard > * On Select Version page, select "Use Local Repository" and then "Use RedHat > Satellite/Spacewalk" > * The Next button is disabled. The Next button must be enabled in this > scenario. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23309) YARN cluster memory graph is not loading in Ambari 2.6
[ https://issues.apache.org/jira/browse/AMBARI-23309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23309: Labels: pull-request-available (was: ) > YARN cluster memory graph is not loading in Ambari 2.6 > -- > > Key: AMBARI-23309 > URL: https://issues.apache.org/jira/browse/AMBARI-23309 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.2 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Critical > Labels: pull-request-available > Fix For: 2.7.0 > > > Users are not able to see cluster memory graph under YARN. This was working > before upgrade. > We were able to reproduce this internally on Ambari 2.6. We checked across 5 > clusters and all of them exhibited same behaviour. > Seems like problem with the compute : mem_total._sum - mem_free._sum fails > but mem_total._sum + mem_free._sum succeeds. > Also if we load mem_total._sum AND mem_free._sum individually, they come up > fine. > Seems like issue when we do a 'subtract'. > Attaching UI Screenshot -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23309) YARN cluster memory graph is not loading in Ambari 2.6
Andrii Tkach created AMBARI-23309: - Summary: YARN cluster memory graph is not loading in Ambari 2.6 Key: AMBARI-23309 URL: https://issues.apache.org/jira/browse/AMBARI-23309 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.6.2 Reporter: Andrii Tkach Assignee: Andrii Tkach Fix For: 2.7.0 Users are not able to see cluster memory graph under YARN. This was working before upgrade. We were able to reproduce this internally on Ambari 2.6. We checked across 5 clusters and all of them exhibited same behaviour. Seems like problem with the compute : mem_total._sum - mem_free._sum fails but mem_total._sum + mem_free._sum succeeds. Also if we load mem_total._sum AND mem_free._sum individually, they come up fine. Seems like issue when we do a 'subtract'. Attaching UI Screenshot -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23289) Add SSO integration support information to service information via Ambari's REST API
[
https://issues.apache.org/jira/browse/AMBARI-23289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar updated AMBARI-23289:
---
Status: Patch Available (was: In Progress)
> Add SSO integration support information to service information via Ambari's
> REST API
>
>
> Key: AMBARI-23289
> URL: https://issues.apache.org/jira/browse/AMBARI-23289
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Add SSO integration support information to service information via Ambari's
> REST API. This information should be usable by Ambari's search predicate
> feature.
> New _read-only_ properties for (stack) services should be:
> * *{{sso_integration_supported}}* - Indicates whether the service supports
> SSO integration or not
> ** Information is expected to be determined by service's meta info (see
> BUG-98626)
> New _read-only_ properties for installed services should be:
> * *{{sso_integration_supported}}* - Indicates whether the service supports
> SSO integration or not
> ** Information is expected to be determined by the service's meta info (see
> BUG-98626)
> * *{{sso_integration_enabled}}* - Indicates whether the service is configured
> for SSO integration or not
> ** Information is expected to be determined by a value indicated in the
> service's meta info (see BUG-98626)
> * *{{sso_integration_desired}}* - Indicates whether the service is chosen for
> SSO integration or not
> ** Information is expected to be in {{cluster-env/sso_enabled_services}} (see
> BUG-98451)
> Examples:
> {noformat:title=Get stack service details}
> GET /api/v1/stacks/:STACK_NAME/versions/:VERSION/services/:SERVICE_NAME",
> {
> "href" : ":URL",
> "StackServices" : {
> ...
> "sso_integration_supported": "false",
> ...
> },
> ...
> {noformat}
> {noformat:title=Get installed service information}
> GET /api/v1/clusters/:CLUSTER_NAME/services/:SERVICE_NAME
> {
> "href" : ":URL",
> "ServiceInfo" : {
> "cluster_name" : ":CLUSTER_NAME",
> ...
> "sso_integration_supported": "true",
> "sso_integration_enabled": "false",
> "sso_integration_desired": "false",
> ...
> },
> ...
> {noformat}
> {noformat:title=List installed services that support SSO integration}
> GET
> /api/v1/clusters/:CLUSTER_NAME/services?ServiceInfo/sso_integration_supported=true
> {
> "href" : ":URL",
> "items" : [
> ...
>]
> }
> {noformat}
> {noformat:title=List stack services that support SSO integration}
> GET
> /api/v1/stacks/:STACK_NAME/versions/:VERSION/services?StackServices/credential_store_enabled=false
> {
> "href" : ":URL",
> "items" : [
> ...
>]
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AMBARI-23284) Add Ambari configuration data to stack/service advisor input data
[
https://issues.apache.org/jira/browse/AMBARI-23284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar resolved AMBARI-23284.
Resolution: Fixed
> Add Ambari configuration data to stack/service advisor input data
> -
>
> Key: AMBARI-23284
> URL: https://issues.apache.org/jira/browse/AMBARI-23284
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Attila Magyar
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Add Ambari configuration data to stack/service advisor input data. Currently
> the {{ldap-configuration}} data is passed in to the stack/service advisor.
> However, generically all Ambari configuration data should be passed in.
> For example, the current data set (in service.json) contains
> {code:java}
> {
> ... "services" : [],
> ... "configurations" : \{ ... }, "ambari-server-properties" : \{ ... },
> ... "ldap-configurations" : \{ ... }
> }
>
> {code}
>
> "\{{ldap-configurations}}" may or may not exist depending on if LDAP
> authentication/sync was setup. This should be treated generically and part of
> a larger block of data named "\{{ambari-server-configuration}}". For example:
> {code:java}
> {
> ...
> "services" : [],
> ...
> "configurations" :
> { ... },
> "ambari-server-properties" : { ... }
> ,
> ...
> "ambari-server-configuration" : {
> "ldap-configurations" :
> { ... }
> ,
> ...
> }
> }
>
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (AMBARI-23289) Add SSO integration support information to service information via Ambari's REST API
[
https://issues.apache.org/jira/browse/AMBARI-23289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Magyar reassigned AMBARI-23289:
--
Assignee: Attila Magyar (was: Robert Levas)
> Add SSO integration support information to service information via Ambari's
> REST API
>
>
> Key: AMBARI-23289
> URL: https://issues.apache.org/jira/browse/AMBARI-23289
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Robert Levas
>Assignee: Attila Magyar
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Add SSO integration support information to service information via Ambari's
> REST API. This information should be usable by Ambari's search predicate
> feature.
> New _read-only_ properties for (stack) services should be:
> * *{{sso_integration_supported}}* - Indicates whether the service supports
> SSO integration or not
> ** Information is expected to be determined by service's meta info (see
> BUG-98626)
> New _read-only_ properties for installed services should be:
> * *{{sso_integration_supported}}* - Indicates whether the service supports
> SSO integration or not
> ** Information is expected to be determined by the service's meta info (see
> BUG-98626)
> * *{{sso_integration_enabled}}* - Indicates whether the service is configured
> for SSO integration or not
> ** Information is expected to be determined by a value indicated in the
> service's meta info (see BUG-98626)
> * *{{sso_integration_desired}}* - Indicates whether the service is chosen for
> SSO integration or not
> ** Information is expected to be in {{cluster-env/sso_enabled_services}} (see
> BUG-98451)
> Examples:
> {noformat:title=Get stack service details}
> GET /api/v1/stacks/:STACK_NAME/versions/:VERSION/services/:SERVICE_NAME",
> {
> "href" : ":URL",
> "StackServices" : {
> ...
> "sso_integration_supported": "false",
> ...
> },
> ...
> {noformat}
> {noformat:title=Get installed service information}
> GET /api/v1/clusters/:CLUSTER_NAME/services/:SERVICE_NAME
> {
> "href" : ":URL",
> "ServiceInfo" : {
> "cluster_name" : ":CLUSTER_NAME",
> ...
> "sso_integration_supported": "true",
> "sso_integration_enabled": "false",
> "sso_integration_desired": "false",
> ...
> },
> ...
> {noformat}
> {noformat:title=List installed services that support SSO integration}
> GET
> /api/v1/clusters/:CLUSTER_NAME/services?ServiceInfo/sso_integration_supported=true
> {
> "href" : ":URL",
> "items" : [
> ...
>]
> }
> {noformat}
> {noformat:title=List stack services that support SSO integration}
> GET
> /api/v1/stacks/:STACK_NAME/versions/:VERSION/services?StackServices/credential_store_enabled=false
> {
> "href" : ":URL",
> "items" : [
> ...
>]
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-23308) Ticket cache file is delete before balancer access it during rebalance HDFS operation
[ https://issues.apache.org/jira/browse/AMBARI-23308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen updated AMBARI-23308: Summary: Ticket cache file is delete before balancer access it during rebalance HDFS operation (was: Tgt cache file is delete before balancer access it during rebalance HDFS operation) > Ticket cache file is delete before balancer access it during rebalance HDFS > operation > - > > Key: AMBARI-23308 > URL: https://issues.apache.org/jira/browse/AMBARI-23308 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.6.2 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 20m > Remaining Estimate: 0h > > Since the rebalance command is run into background without waiting for > finish, delete tgt cache file is executed right after subprocess start. > The subprocess fails due to missing tgt cache file because the file is > deleted before the subprocess access it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23283) Install Wizard > Select Version page: the user cannot proceed with Redhat Satellite option
[ https://issues.apache.org/jira/browse/AMBARI-23283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407765#comment-16407765 ] Andrii Tkach commented on AMBARI-23283: --- committed to branch-2.6 > Install Wizard > Select Version page: the user cannot proceed with Redhat > Satellite option > -- > > Key: AMBARI-23283 > URL: https://issues.apache.org/jira/browse/AMBARI-23283 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.6.2, 2.7.0 >Reporter: Andrii Tkach >Assignee: Andrii Tkach >Priority: Blocker > Labels: pull-request-available > Fix For: 2.6.2, 2.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > STR: > * Launch Install Wizard > * On Select Version page, select "Use Local Repository" and then "Use RedHat > Satellite/Spacewalk" > * The Next button is disabled. The Next button must be enabled in this > scenario. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23308) Tgt cache file is delete before balancer access it during rebalance HDFS operation
[ https://issues.apache.org/jira/browse/AMBARI-23308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23308: Labels: pull-request-available (was: ) > Tgt cache file is delete before balancer access it during rebalance HDFS > operation > -- > > Key: AMBARI-23308 > URL: https://issues.apache.org/jira/browse/AMBARI-23308 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.6.2 >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Blocker > Labels: pull-request-available > Fix For: 2.6.2 > > > Since the rebalance command is run into background without waiting for > finish, delete tgt cache file is executed right after subprocess start. > The subprocess fails due to missing tgt cache file because the file is > deleted before the subprocess access it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23308) Tgt cache file is delete before balancer access it during rebalance HDFS operation
Dmytro Sen created AMBARI-23308: --- Summary: Tgt cache file is delete before balancer access it during rebalance HDFS operation Key: AMBARI-23308 URL: https://issues.apache.org/jira/browse/AMBARI-23308 Project: Ambari Issue Type: Task Components: ambari-server Affects Versions: 2.6.2 Reporter: Dmytro Sen Assignee: Dmytro Sen Fix For: 2.6.2 Since the rebalance command is run into background without waiting for finish, delete tgt cache file is executed right after subprocess start. The subprocess fails due to missing tgt cache file because the file is deleted before the subprocess access it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-23299) Intermittent failure in TestAgentStompResponses
[
https://issues.apache.org/jira/browse/AMBARI-23299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407644#comment-16407644
]
Doroszlai, Attila commented on AMBARI-23299:
Similar intermittent problem in the same test class:
{noformat}
FAIL: test_mock_server_can_start
(TestAgentStompResponses.TestAgentStompResponses)
--
Traceback (most recent call last):
File
"/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-common/src/test/python/mock/mock.py",
line 1199, in patched
return func(*args, **keywargs)
File
"/home/jenkins/jenkins-slave/workspace/Ambari-Github-PullRequest-Builder/ambari-agent/src/test/python/ambari_agent/TestAgentStompResponses.py",
line 151, in test_mock_server_can_start
ERROR 2018-03-21 09:01:14,737 - Python unit tests failed
self.assertTrue('mounts' in host_status_report)
AssertionError: False is not true
{noformat}
https://builds.apache.org/job/Ambari-trunk-Commit/8884/
https://builds.apache.org/job/Ambari-trunk-Commit/8875/
https://builds.apache.org/job/Ambari-trunk-Commit/8872/
https://builds.apache.org/job/Ambari-trunk-Commit/8865/
> Intermittent failure in TestAgentStompResponses
> ---
>
> Key: AMBARI-23299
> URL: https://issues.apache.org/jira/browse/AMBARI-23299
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent
>Affects Versions: 2.7.0
>Reporter: Doroszlai, Attila
>Priority: Major
> Fix For: 2.7.0
>
>
> Intermittent unit test failure, probably due to use of threads:
> {noformat}
> FAIL: test_alert_definitions_update_and_delete
> (TestAgentStompResponses.TestAgentStompResponses)
> ...
> -u'uuid':
> u'69ff4c8f-8e98-4cfd-b90f-6914e2f147ff'}],
> ?
> -
> +u'uuid':
> u'69ff4c8f-8e98-4cfd-b90f-6914e2f147ff'},
> + {u'clusterId': 2,
> +u'componentName': u'HBASE_MASTER',
> +u'definitionId': 1,
> +u'description': u'This alert is triggered if
> the HBase master processes cannot be confirmed to be up and listening on the
> network for the configured critical threshold, given in seconds.',
> +u'enabled': True,
> +u'ignore_host': False,
> +u'interval': 1,
> +u'label': u'HBase Master Process',
> +u'name': u'hbase_master_process',
> +u'scope': u'ANY',
> +u'serviceName': u'HBASE',
> +u'source': {u'default_port': 6,
> +u'reporting': {u'critical':
> {u'text': u'Connection failed: {0} to {1}:{2}',
> +
> u'value': 5.0},
> + u'ok': {u'text':
> u'TCP OK - {0:.3f}s response on port {1}'},
> + u'warning':
> {u'text': u'TCP OK - {0:.3f}s response on port {1}',
> +
> u'value': 1.5}},
> +u'type': u'PORT',
> +u'uri':
> u'{{hbase-site/hbase.master.port}}'},
> +u'uuid':
> u'ff73ead7-13b4-43ea-a747-d230f17bf230'}],
> u'clusterName': u'cl1',
> ...
> {noformat}
> https://builds.apache.org/job/Ambari-trunk-Commit/8872/
> https://builds.apache.org/job/Ambari-trunk-Commit/8863/
> https://builds.apache.org/job/Ambari-trunk-Commit/8862/
> https://builds.apache.org/job/Ambari-trunk-Commit/8858/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-23230) Upgrade Solr configuration while upgrading Ambari 2.6.1 -> 2.7.0
[ https://issues.apache.org/jira/browse/AMBARI-23230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407556#comment-16407556 ] Hudson commented on AMBARI-23230: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8886 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8886/]) AMBARI-23230 Upgrade Solr configuration while upgrading Ambari 2.6.1 -> (oleewere: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=d1c547dba32475ff2bdecd68ed434edc93cc3d0a]) * (delete) ambari-logsearch/ambari-logsearch-assembly/src/main/package/rpm/portal/postremove.sh~HEAD * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/LogFeederSecurityConfig.java * (add) ambari-server/src/test/resources/org/apache/ambari/server/upgrade/solrconfig-v500.xml.j2 * (edit) ambari-server/src/main/resources/common-services/AMBARI_INFRA_SOLR/0.1.0/package/scripts/setup_infra_solr.py * (edit) ambari-logsearch/ambari-logsearch-logfeeder/src/main/java/org/apache/ambari/logfeeder/conf/LogFeederProps.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog270.java * (edit) ambari-logsearch/ambari-logsearch-assembly/src/main/package/rpm/portal/postinstall.sh * (edit) ambari-logsearch/ambari-logsearch-assembly/src/main/package/deb/logfeeder/postinst * (edit) ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog270Test.java * (edit) ambari-logsearch/ambari-logsearch-assembly/src/main/package/deb/portal/postinst * (delete) ambari-logsearch/ambari-logsearch-assembly/src/main/package/rpm/logfeeder/postremove.sh~trunk * (edit) ambari-logsearch/ambari-logsearch-assembly/src/main/package/rpm/logfeeder/postinstall.sh * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/SolrAuditLogPropsConfig.java * (delete) ambari-logsearch/ambari-logsearch-assembly/src/main/package/rpm/logfeeder/postremove.sh~HEAD * (delete) ambari-logsearch/ambari-logsearch-assembly/src/main/package/rpm/portal/postremove.sh~trunk * (edit) ambari-logsearch/ambari-logsearch-server/src/main/java/org/apache/ambari/logsearch/conf/SolrConnectionPropsConfig.java > Upgrade Solr configuration while upgrading Ambari 2.6.1 -> 2.7.0 > > > Key: AMBARI-23230 > URL: https://issues.apache.org/jira/browse/AMBARI-23230 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23307) Rename AMBARI_INFRA to AMBARI_INFRA_SOLR in upgrade helper script
[ https://issues.apache.org/jira/browse/AMBARI-23307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-23307: Labels: pull-request-available (was: ) > Rename AMBARI_INFRA to AMBARI_INFRA_SOLR in upgrade helper script > - > > Key: AMBARI-23307 > URL: https://issues.apache.org/jira/browse/AMBARI-23307 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-23307) Rename AMBARI_INFRA to AMBARI_INFRA_SOLR in upgrade helper script
Olivér Szabó created AMBARI-23307: - Summary: Rename AMBARI_INFRA to AMBARI_INFRA_SOLR in upgrade helper script Key: AMBARI-23307 URL: https://issues.apache.org/jira/browse/AMBARI-23307 Project: Ambari Issue Type: Bug Components: ambari-infra Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23230) Upgrade Solr configuration while upgrading Ambari 2.6.1 -> 2.7.0
[ https://issues.apache.org/jira/browse/AMBARI-23230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa updated AMBARI-23230: Status: Patch Available (was: In Progress) > Upgrade Solr configuration while upgrading Ambari 2.6.1 -> 2.7.0 > > > Key: AMBARI-23230 > URL: https://issues.apache.org/jira/browse/AMBARI-23230 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-23230) Upgrade Solr configuration while upgrading Ambari 2.6.1 -> 2.7.0
[ https://issues.apache.org/jira/browse/AMBARI-23230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krisztian Kasa updated AMBARI-23230: Resolution: Fixed Status: Resolved (was: Patch Available) > Upgrade Solr configuration while upgrading Ambari 2.6.1 -> 2.7.0 > > > Key: AMBARI-23230 > URL: https://issues.apache.org/jira/browse/AMBARI-23230 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Krisztian Kasa >Assignee: Krisztian Kasa >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
