[jira] [Comment Edited] (AMBARI-13109) Verify that max logs parameter wouldn't cause premature region flush
[ https://issues.apache.org/jira/browse/AMBARI-13109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16120333#comment-16120333 ] Ted Yu edited comment on AMBARI-13109 at 12/9/17 5:16 AM: -- The max logs parameter plays an important role in preventing fragmentation in memstore . was (Author: yuzhih...@gmail.com): The max logs parameter plays an important role in preventing fragmentation in memstore. > Verify that max logs parameter wouldn't cause premature region flush > > > Key: AMBARI-13109 > URL: https://issues.apache.org/jira/browse/AMBARI-13109 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu > > For hbase, the following relationship should be maintained: > dfs.blocksize * 0.95 * hbase.regionserver.maxlogs (default 32) > > hbase.regionserver.global.memstore.upperLimit * HBASE_HEAPSIZE > The rationale is to avoid premature region flush due to log roll which is > triggered by insufficiently high max logs. > When user changes the values for max logs, memstore upper limit or max heap > size, we should verify that the above relationship is satisfied. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[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 > > 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 (v6.4.14#64029)
[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 12/9/17 5:15 AM:
--
Escaping the dollar sign automatically is the desirable solution .
was (Author: yuzhih...@gmail.com):
Escaping the dollar sign automatically is the 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
> 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
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22620) Ambari page takes too long to load after deleting services
[ https://issues.apache.org/jira/browse/AMBARI-22620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yesha Vora updated AMBARI-22620: Attachment: Screen Shot 2017-12-08 at 2.00.59 PM.png > Ambari page takes too long to load after deleting services > -- > > Key: AMBARI-22620 > URL: https://issues.apache.org/jira/browse/AMBARI-22620 > Project: Ambari > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Yesha Vora > Attachments: Screen Shot 2017-12-08 at 2.00.59 PM.png > > > Scenario: > 1) Install HDFS, Yarn, Mapreduce2 > 2) Stop Yarn and Mapreduce2 services > 3) Delete Yarn and Mapreduce2 service > After prompting to confirm delete operation, ambari page tries to load. At > this time, page takes too long to load. It shows attached stacktrace in > console. ( Look at screenshots) > "TypeError: null is not an object" > User have to load page manually to workaround this issue -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22620) Ambari page takes too long to load after deleting services
Yesha Vora created AMBARI-22620: --- Summary: Ambari page takes too long to load after deleting services Key: AMBARI-22620 URL: https://issues.apache.org/jira/browse/AMBARI-22620 Project: Ambari Issue Type: Bug Affects Versions: 3.0.0 Reporter: Yesha Vora Scenario: 1) Install HDFS, Yarn, Mapreduce2 2) Stop Yarn and Mapreduce2 services 3) Delete Yarn and Mapreduce2 service After prompting to confirm delete operation, ambari page tries to load. At this time, page takes too long to load. It shows attached stacktrace in console. ( Look at screenshots) "TypeError: null is not an object" User have to load page manually to workaround this issue -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22619) Add service check for Yarn Registry DNS
Yesha Vora created AMBARI-22619: --- Summary: Add service check for Yarn Registry DNS Key: AMBARI-22619 URL: https://issues.apache.org/jira/browse/AMBARI-22619 Project: Ambari Issue Type: Bug Affects Versions: 3.0.0 Reporter: Yesha Vora Add service check for Yarn Registry DNS. 1) Check if service is up 2) Sanity check for Yarn Registry DNS -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21232) Determination of defaultFS with WebHDFS enabled
[ https://issues.apache.org/jira/browse/AMBARI-21232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-21232: - Fix Version/s: (was: 2.6.1) 3.0.0 > Determination of defaultFS with WebHDFS enabled > --- > > Key: AMBARI-21232 > URL: https://issues.apache.org/jira/browse/AMBARI-21232 > Project: Ambari > Issue Type: Improvement > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Sridhar Sailappan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 3.0.0 > > Attachments: Patch_AmbariViewUtils_WebHDFS.txt > > > In Ambari View Utils , the determination logic for the value of defaultFS > when WebHDFS is enabled, needs to consider the current property value of > defaultFS. Please see attached patch for the context. > If the existing configuration for the defaultFS URI already has the protocol > specified as webhdfs or swebhdfs, the URI should be used as provided and a > new value should not be constructed. Constructing a new value in a such a > scenario may lead to unexpected behavior if the Namenode has different > host-port settings for the HTTP and WebHDFS access. > The patch also addresses the following code cleanup: > 1)Fix variable names httpAddr and httpsAddr (current implementation has > the naming interchanged) > 2)Add null value check for httpAddr before assignment to hostWithPort > 3)Fix typo in variable names - DFS_NAMENODE_HTTP_ADDRESS and > DFS_NAMENODE_HTTPS_ADDRESS -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-21232) Determination of defaultFS with WebHDFS enabled
[ https://issues.apache.org/jira/browse/AMBARI-21232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284325#comment-16284325 ] Swapan Shridhar edited comment on AMBARI-21232 at 12/8/17 10:17 PM: Moved it to 3.0 as I am starting the 2.6.1 release process. CC [~jluniya] | [~mradhakrishnan] was (Author: swapanshridhar): Moved it to 3.0 as I am started the 2.6.1 release process. CC [~jluniya] | [~mradhakrishnan] > Determination of defaultFS with WebHDFS enabled > --- > > Key: AMBARI-21232 > URL: https://issues.apache.org/jira/browse/AMBARI-21232 > Project: Ambari > Issue Type: Improvement > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Sridhar Sailappan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.6.1 > > Attachments: Patch_AmbariViewUtils_WebHDFS.txt > > > In Ambari View Utils , the determination logic for the value of defaultFS > when WebHDFS is enabled, needs to consider the current property value of > defaultFS. Please see attached patch for the context. > If the existing configuration for the defaultFS URI already has the protocol > specified as webhdfs or swebhdfs, the URI should be used as provided and a > new value should not be constructed. Constructing a new value in a such a > scenario may lead to unexpected behavior if the Namenode has different > host-port settings for the HTTP and WebHDFS access. > The patch also addresses the following code cleanup: > 1)Fix variable names httpAddr and httpsAddr (current implementation has > the naming interchanged) > 2)Add null value check for httpAddr before assignment to hostWithPort > 3)Fix typo in variable names - DFS_NAMENODE_HTTP_ADDRESS and > DFS_NAMENODE_HTTPS_ADDRESS -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-21232) Determination of defaultFS with WebHDFS enabled
[ https://issues.apache.org/jira/browse/AMBARI-21232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284325#comment-16284325 ] Swapan Shridhar commented on AMBARI-21232: -- Moved it to 3.0 as I am started the 2.6.1 release process. CC [~jluniya] | [~mradhakrishnan] > Determination of defaultFS with WebHDFS enabled > --- > > Key: AMBARI-21232 > URL: https://issues.apache.org/jira/browse/AMBARI-21232 > Project: Ambari > Issue Type: Improvement > Components: ambari-views >Affects Versions: 2.4.0 >Reporter: Sridhar Sailappan >Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.6.1 > > Attachments: Patch_AmbariViewUtils_WebHDFS.txt > > > In Ambari View Utils , the determination logic for the value of defaultFS > when WebHDFS is enabled, needs to consider the current property value of > defaultFS. Please see attached patch for the context. > If the existing configuration for the defaultFS URI already has the protocol > specified as webhdfs or swebhdfs, the URI should be used as provided and a > new value should not be constructed. Constructing a new value in a such a > scenario may lead to unexpected behavior if the Namenode has different > host-port settings for the HTTP and WebHDFS access. > The patch also addresses the following code cleanup: > 1)Fix variable names httpAddr and httpsAddr (current implementation has > the naming interchanged) > 2)Add null value check for httpAddr before assignment to hostWithPort > 3)Fix typo in variable names - DFS_NAMENODE_HTTP_ADDRESS and > DFS_NAMENODE_HTTPS_ADDRESS -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-20534) Enable Ambari builds on ARM64 and PPC
[ https://issues.apache.org/jira/browse/AMBARI-20534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-20534: - Fix Version/s: (was: 2.6.1) 3.0.0 > Enable Ambari builds on ARM64 and PPC > - > > Key: AMBARI-20534 > URL: https://issues.apache.org/jira/browse/AMBARI-20534 > Project: Ambari > Issue Type: Improvement > Components: ambari-admin, ambari-web >Affects Versions: 2.4.2 >Reporter: Roman Shaposhnik >Assignee: Roman Shaposhnik > Fix For: 3.0.0 > > Attachments: AMBARI-20534.patch.txt > > > Currently Ambari fails to build on ARM64 and PPC in big part because of > dependency on the old version of com.github.eirslett:frontend-maven-plugin > Bumping the version to 1.3 solves this issue and doesn't seem to affect the > build in any other way. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-20534) Enable Ambari builds on ARM64 and PPC
[ https://issues.apache.org/jira/browse/AMBARI-20534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284298#comment-16284298 ] Swapan Shridhar commented on AMBARI-20534: -- Moved it to 3.0 as I am started the 2.6.1 release process. > Enable Ambari builds on ARM64 and PPC > - > > Key: AMBARI-20534 > URL: https://issues.apache.org/jira/browse/AMBARI-20534 > Project: Ambari > Issue Type: Improvement > Components: ambari-admin, ambari-web >Affects Versions: 2.4.2 >Reporter: Roman Shaposhnik >Assignee: Roman Shaposhnik > Fix For: 3.0.0 > > Attachments: AMBARI-20534.patch.txt > > > Currently Ambari fails to build on ARM64 and PPC in big part because of > dependency on the old version of com.github.eirslett:frontend-maven-plugin > Bumping the version to 1.3 solves this issue and doesn't seem to affect the > build in any other way. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22016) changeToSecureUid.sh might collide with existing user if it is not a local user but a network managed user
[
https://issues.apache.org/jira/browse/AMBARI-22016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-22016:
-
Fix Version/s: (was: 2.6.1)
3.0.0
> changeToSecureUid.sh might collide with existing user if it is not a local
> user but a network managed user
> --
>
> Key: AMBARI-22016
> URL: https://issues.apache.org/jira/browse/AMBARI-22016
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
> Environment: Using Centos as the test bed
>Reporter: Aman Poonia
>Assignee: Aman Poonia
> Fix For: 3.0.0
>
> Attachments: AMBARI-22016.patch, AMBARI-22016_branch-2.6.patch
>
>
> changeToSecureUid.sh might collide with existing user if it is not a local
> user but a network managed user
> Currently we are doing
> {code:java}
> function find_available_uid() {
> for ((i=1001; i<=2000; i++))
> do
>grep -q $i /etc/passwd
>if [ "$?" -ne 0 ]
>then
> newUid=$i
> break
>fi
> done
> }
> {code}
> This will only check local user. Network manged users are not directly
> present inside passwd file.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22016) changeToSecureUid.sh might collide with existing user if it is not a local user but a network managed user
[
https://issues.apache.org/jira/browse/AMBARI-22016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284297#comment-16284297
]
Swapan Shridhar commented on AMBARI-22016:
--
Moved it to 3.0 as I am started the 2.6.1 release process.
> changeToSecureUid.sh might collide with existing user if it is not a local
> user but a network managed user
> --
>
> Key: AMBARI-22016
> URL: https://issues.apache.org/jira/browse/AMBARI-22016
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.5.2
> Environment: Using Centos as the test bed
>Reporter: Aman Poonia
>Assignee: Aman Poonia
> Fix For: 3.0.0
>
> Attachments: AMBARI-22016.patch, AMBARI-22016_branch-2.6.patch
>
>
> changeToSecureUid.sh might collide with existing user if it is not a local
> user but a network managed user
> Currently we are doing
> {code:java}
> function find_available_uid() {
> for ((i=1001; i<=2000; i++))
> do
>grep -q $i /etc/passwd
>if [ "$?" -ne 0 ]
>then
> newUid=$i
> break
>fi
> done
> }
> {code}
> This will only check local user. Network manged users are not directly
> present inside passwd file.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22152) Service check failures for Yarn and MR after patch upgrade
[ https://issues.apache.org/jira/browse/AMBARI-22152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284296#comment-16284296 ] Swapan Shridhar commented on AMBARI-22152: -- Moved it to 3.0 as I am started the 2.6.1 release process. > Service check failures for Yarn and MR after patch upgrade > -- > > Key: AMBARI-22152 > URL: https://issues.apache.org/jira/browse/AMBARI-22152 > Project: Ambari > Issue Type: Bug > Components: ambari-upgrade >Affects Versions: 2.6.0 >Reporter: Supreeth Sharma >Priority: Critical > Fix For: 3.0.0 > > Attachments: mr.err, yarn.err > > > Test steps : > 1) Perform ambari upgrade from 2.5.2.0 tp 2.6.3.0 > 2) Perform stack upgrade from 2.6.2.0-205 to 2.6.3.0-163 > Service checks for Yarn and MR are failing with below errors : > attaching the error log for Yarn and MR failures. > Service logs could be found here : > http://logserver.eng.hortonworks.com/?prefix=qelogs/nat/67526/ambaripu-thirddigit-r7/split-1/pu-third-r7--shavi71/service-logs/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21858) Not able to enable hive "Interactive Query"
[
https://issues.apache.org/jira/browse/AMBARI-21858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-21858:
-
Fix Version/s: (was: 2.6.1)
3.0.0
> Not able to enable hive "Interactive Query"
> ---
>
> Key: AMBARI-21858
> URL: https://issues.apache.org/jira/browse/AMBARI-21858
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: amarnath reddy pappu
>Priority: Critical
> Fix For: 3.0.0
>
>
> when try to enable Hive interactive query it fails with below JS error and
> Save button does not get activated and does not start any wizard.
> {noformat}
> app.js:42734 Uncaught TypeError: Cannot read property 'forEach' of
> undefined(…)(anonymous function) @
> app.js:42734pendingBatchRequestsAjaxSuccess @ app.js:42733opt.success @
> app.js:175507o @ vendor.js:106fireWith @ vendor.js:106w @ vendor.js:108d @
> vendor.js:108
> {noformat}
> Workaround: Update requestschedule table to mark the entry as "COMPLETED" to
> resolve the issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21858) Not able to enable hive "Interactive Query"
[
https://issues.apache.org/jira/browse/AMBARI-21858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284295#comment-16284295
]
Swapan Shridhar commented on AMBARI-21858:
--
Moved it to 3.0 as I am started the 2.6.1 release process.
> Not able to enable hive "Interactive Query"
> ---
>
> Key: AMBARI-21858
> URL: https://issues.apache.org/jira/browse/AMBARI-21858
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.1
>Reporter: amarnath reddy pappu
>Priority: Critical
> Fix For: 3.0.0
>
>
> when try to enable Hive interactive query it fails with below JS error and
> Save button does not get activated and does not start any wizard.
> {noformat}
> app.js:42734 Uncaught TypeError: Cannot read property 'forEach' of
> undefined(…)(anonymous function) @
> app.js:42734pendingBatchRequestsAjaxSuccess @ app.js:42733opt.success @
> app.js:175507o @ vendor.js:106fireWith @ vendor.js:106w @ vendor.js:108d @
> vendor.js:108
> {noformat}
> Workaround: Update requestschedule table to mark the entry as "COMPLETED" to
> resolve the issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21644) Cannot delete file using ambari files view when proxied through Knox
[
https://issues.apache.org/jira/browse/AMBARI-21644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-21644:
-
Fix Version/s: (was: 2.6.1)
3.0.0
> Cannot delete file using ambari files view when proxied through Knox
>
>
> Key: AMBARI-21644
> URL: https://issues.apache.org/jira/browse/AMBARI-21644
> Project: Ambari
> Issue Type: Bug
> Components: contrib
>Affects Versions: 2.5.1
>Reporter: Tan Pham
> Fix For: 3.0.0
>
>
> The problem is with the deleting file in Ambari Files view when proxied
> through Knox.
> Ambari Files view using: method: *DELETE*, path:
> *resources/files/fileops/moveToTrash*, body payload: {path: "path_to_delete",
> recursive: true}
> Knox using Apache HttpClient. HttpClient implementation does not support
> request body and the the request body is dropped (see
> org.apache.http.client.methods.HttpDelete).
> To fix this issue, change from DELETE method to POST or PUT method in Ambari
> Files view.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22152) Service check failures for Yarn and MR after patch upgrade
[ https://issues.apache.org/jira/browse/AMBARI-22152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-22152: - Fix Version/s: (was: 2.6.1) 3.0.0 > Service check failures for Yarn and MR after patch upgrade > -- > > Key: AMBARI-22152 > URL: https://issues.apache.org/jira/browse/AMBARI-22152 > Project: Ambari > Issue Type: Bug > Components: ambari-upgrade >Affects Versions: 2.6.0 >Reporter: Supreeth Sharma >Priority: Critical > Fix For: 3.0.0 > > Attachments: mr.err, yarn.err > > > Test steps : > 1) Perform ambari upgrade from 2.5.2.0 tp 2.6.3.0 > 2) Perform stack upgrade from 2.6.2.0-205 to 2.6.3.0-163 > Service checks for Yarn and MR are failing with below errors : > attaching the error log for Yarn and MR failures. > Service logs could be found here : > http://logserver.eng.hortonworks.com/?prefix=qelogs/nat/67526/ambaripu-thirddigit-r7/split-1/pu-third-r7--shavi71/service-logs/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21225) Support for macro based property definitions in Ambari Views
[
https://issues.apache.org/jira/browse/AMBARI-21225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-21225:
-
Fix Version/s: (was: 2.6.1)
3.0.0
> Support for macro based property definitions in Ambari Views
>
>
> Key: AMBARI-21225
> URL: https://issues.apache.org/jira/browse/AMBARI-21225
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Sridhar Sailappan
> Fix For: 3.0.0
>
> Attachments: Patch_AmbariViewUtils_Macro.txt
>
>
> The attached patch for Ambari Views provides support for property
> configurations with macro based definitions (relying on variable expansion of
> Hadoop Configuration).
> e.g., Consider the following definition of properties for HDFS.
> 1) In Advanced core-site, property "fs.defaultFS" is defined to have value
> "${fs.defaultFS.dev}"
> 2) In Custom core-site, property "fs.defaultFS.dev" is defined to have value
> "hdfs://dev-sandbox.hortonworks.com:8020"
> Now, when referencing the property "fs.defaultFS", the value should be
> resolved to "hdfs://dev-sandbox.hortonworks.com:8020".
> This is typical variable expansion that is expected in Hadoop Configuration.
> Refer:
> https://hadoop.apache.org/docs/r2.6.0/api/org/apache/hadoop/conf/Configuration.html
> This functionality of variable expansion is not available with Ambari Views.
> The attached patch (on branch-2.4.0) addresses this need.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21644) Cannot delete file using ambari files view when proxied through Knox
[
https://issues.apache.org/jira/browse/AMBARI-21644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284294#comment-16284294
]
Swapan Shridhar commented on AMBARI-21644:
--
Moved it to 3.0 as I am started the 2.6.1 release process.
> Cannot delete file using ambari files view when proxied through Knox
>
>
> Key: AMBARI-21644
> URL: https://issues.apache.org/jira/browse/AMBARI-21644
> Project: Ambari
> Issue Type: Bug
> Components: contrib
>Affects Versions: 2.5.1
>Reporter: Tan Pham
> Fix For: 2.6.1
>
>
> The problem is with the deleting file in Ambari Files view when proxied
> through Knox.
> Ambari Files view using: method: *DELETE*, path:
> *resources/files/fileops/moveToTrash*, body payload: {path: "path_to_delete",
> recursive: true}
> Knox using Apache HttpClient. HttpClient implementation does not support
> request body and the the request body is dropped (see
> org.apache.http.client.methods.HttpDelete).
> To fix this issue, change from DELETE method to POST or PUT method in Ambari
> Files view.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21225) Support for macro based property definitions in Ambari Views
[
https://issues.apache.org/jira/browse/AMBARI-21225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284293#comment-16284293
]
Swapan Shridhar commented on AMBARI-21225:
--
Moved it to 3.0 as I am started the 2.6.1 release process.
> Support for macro based property definitions in Ambari Views
>
>
> Key: AMBARI-21225
> URL: https://issues.apache.org/jira/browse/AMBARI-21225
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Sridhar Sailappan
> Fix For: 3.0.0
>
> Attachments: Patch_AmbariViewUtils_Macro.txt
>
>
> The attached patch for Ambari Views provides support for property
> configurations with macro based definitions (relying on variable expansion of
> Hadoop Configuration).
> e.g., Consider the following definition of properties for HDFS.
> 1) In Advanced core-site, property "fs.defaultFS" is defined to have value
> "${fs.defaultFS.dev}"
> 2) In Custom core-site, property "fs.defaultFS.dev" is defined to have value
> "hdfs://dev-sandbox.hortonworks.com:8020"
> Now, when referencing the property "fs.defaultFS", the value should be
> resolved to "hdfs://dev-sandbox.hortonworks.com:8020".
> This is typical variable expansion that is expected in Hadoop Configuration.
> Refer:
> https://hadoop.apache.org/docs/r2.6.0/api/org/apache/hadoop/conf/Configuration.html
> This functionality of variable expansion is not available with Ambari Views.
> The attached patch (on branch-2.4.0) addresses this need.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21816) test_kms_server timing issue
[
https://issues.apache.org/jira/browse/AMBARI-21816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-21816:
-
Fix Version/s: (was: 2.6.1)
> test_kms_server timing issue
>
>
> Key: AMBARI-21816
> URL: https://issues.apache.org/jira/browse/AMBARI-21816
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0
>
>
> Python unit test in {{test_kms_server}} occasionally fails due to timing.
> Expected and actual output use two separate calls to get current time, which
> may be different if happens to be executed around the turn of a second.
> {noformat}
> FAIL: test_start_secured (test_kms_server.TestRangerKMS)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/stacks/2.5/RANGER_KMS/test_kms_server.py",
> line 522, in test_start_secured
> mode = 0644
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
> line 330, in assertResourceCalled
> self.assertEquals(kwargs, resource.arguments)
> AssertionError: {'owner': 'kms', 'content': '\n2017-08-25
> 11:02:46\n< [truncated]... != {'content':
> '\n2017-08-25 11:02:45\n', 'owne
> [truncated]...
> - {'content': '\n2017-08-25 11:02:46\n',
> ? ^
> + {'content': '\n2017-08-25 11:02:45\n',
> ? ^
> - 'group': 'kms',
> + 'group': u'kms',
> ? +
>'mode': 420,
> - 'owner': 'kms'}
> + 'owner': u'kms'}
> ? +
> {noformat}
> Affected code: {{test_start_default}} and {{test_start_secured}} in
> {{ambari-server/src/test/python/stacks/2.5/RANGER_KMS/test_kms_server.py}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21816) test_kms_server timing issue
[
https://issues.apache.org/jira/browse/AMBARI-21816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284292#comment-16284292
]
Swapan Shridhar commented on AMBARI-21816:
--
Moved it to 3.0 as I am started the 2.6.1 release process.
> test_kms_server timing issue
>
>
> Key: AMBARI-21816
> URL: https://issues.apache.org/jira/browse/AMBARI-21816
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Priority: Minor
> Fix For: 3.0.0, 2.6.1
>
>
> Python unit test in {{test_kms_server}} occasionally fails due to timing.
> Expected and actual output use two separate calls to get current time, which
> may be different if happens to be executed around the turn of a second.
> {noformat}
> FAIL: test_start_secured (test_kms_server.TestRangerKMS)
> --
> Traceback (most recent call last):
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-common/src/test/python/mock/mock.py",
> line 1199, in patched
> return func(*args, **keywargs)
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/stacks/2.5/RANGER_KMS/test_kms_server.py",
> line 522, in test_start_secured
> mode = 0644
> File
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-Commit/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
> line 330, in assertResourceCalled
> self.assertEquals(kwargs, resource.arguments)
> AssertionError: {'owner': 'kms', 'content': '\n2017-08-25
> 11:02:46\n< [truncated]... != {'content':
> '\n2017-08-25 11:02:45\n', 'owne
> [truncated]...
> - {'content': '\n2017-08-25 11:02:46\n',
> ? ^
> + {'content': '\n2017-08-25 11:02:45\n',
> ? ^
> - 'group': 'kms',
> + 'group': u'kms',
> ? +
>'mode': 420,
> - 'owner': 'kms'}
> + 'owner': u'kms'}
> ? +
> {noformat}
> Affected code: {{test_start_default}} and {{test_start_secured}} in
> {{ambari-server/src/test/python/stacks/2.5/RANGER_KMS/test_kms_server.py}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-21775) [Druid] Wrong logrotate configuration for generating an excess of cron email messages
[
https://issues.apache.org/jira/browse/AMBARI-21775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-21775:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> [Druid] Wrong logrotate configuration for generating an excess of cron email
> messages
> -
>
> Key: AMBARI-21775
> URL: https://issues.apache.org/jira/browse/AMBARI-21775
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: slim bouguerra
>Assignee: slim bouguerra
> Fix For: trunk, 2.6.1
>
>
> Druid related configuration is generating the following corn email
> {code}
> /etc/cron.daily/logrotate:
> error: druid:12 unknown unit 'B'
> error: found error in /var/log/druid/*.log , skipping
> {code}
> This is due to wrong logrotate config
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22140) Patch upgrade failure for oozie service
[
https://issues.apache.org/jira/browse/AMBARI-22140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-22140:
-
Fix Version/s: (was: 2.6.1)
3.0.0
> Patch upgrade failure for oozie service
>
>
> Key: AMBARI-22140
> URL: https://issues.apache.org/jira/browse/AMBARI-22140
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.6.0
> Environment: ambari-server --version 2.6.0.0-178
>Reporter: Supreeth Sharma
>Priority: Blocker
> Labels: patch-upgrade
> Fix For: 3.0.0
>
>
> Patch upgrade is failing while performing the upgrade for oozie service.
> Upgrade is failing with below error :
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 150, in
> OozieServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 350, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 119, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 70, in configure
> oozie(is_server=True, upgrade_type=upgrade_type)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py",
> line 193, in oozie
> oozie_server_specific(upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py",
> line 313, in oozie_server_specific
> not_if = no_op_test,
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 166, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> 'ambari-sudo.sh cp /usr/hdp/2.6.3.0-158/hadoop/lib/hadoop-lzo*.jar
> /usr/hdp/current/oozie-server' returned 1. cp: cannot stat
> `/usr/hdp/2.6.3.0-158/hadoop/lib/hadoop-lzo*.jar': No such file or directory
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22087) Druid start component via ambari doesn't wait to check if the component is successfully started
[
https://issues.apache.org/jira/browse/AMBARI-22087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-22087:
-
Fix Version/s: (was: 2.6.1)
3.0.0
> Druid start component via ambari doesn't wait to check if the component is
> successfully started
> ---
>
> Key: AMBARI-22087
> URL: https://issues.apache.org/jira/browse/AMBARI-22087
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Dileep Kumar Chiguruvada
>Assignee: Nishant Bangarwa
> Labels: druid
> Fix For: trunk, 3.0.0
>
>
> Druid start component via ambari doesn't wait to check if the component is
> successfully started.
> Any component start for Druid service will just execute the start command
> and comes out with exit status 0. It will not further check if the process is
> running, or any port if its listening.
> say for example Druid Coordinator
> {code}
> 2017-09-19 18:48:47,076 - Execute['/usr/lib/jvm/java-openjdk/bin/java -cp
> /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/druid-coordinator/extensions/mysql-metadata-storage/mysql-connector-java.jar
> org.apache.ambari.server.DBConnectionVerification
> 'jdbc:mysql://ctr-e134-1499953498516-160569-01-07.hwx.site:3306/druid?createDatabaseIfNotExist=true'
> druid [PROTECTED] com.mysql.jdbc.Driver'] {'tries': 5, 'user': 'druid',
> 'try_sleep': 10}
> 2017-09-19 18:48:47,554 - Execute['source
> /usr/hdp/current/druid-coordinator/conf/druid-env.sh ;
> /usr/hdp/current/druid-coordinator/bin/node.sh coordinator start'] {'user':
> 'druid'}
> Command completed successfully!
> {code}
> The start command via Ambari-UI shows as passed on Ambari-ops even if the
> component fails to start. this gives false impression to check the service.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22140) Patch upgrade failure for oozie service
[
https://issues.apache.org/jira/browse/AMBARI-22140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284285#comment-16284285
]
Swapan Shridhar commented on AMBARI-22140:
--
Moved it to 3.0 as I am started the 2.6.1 release process.
> Patch upgrade failure for oozie service
>
>
> Key: AMBARI-22140
> URL: https://issues.apache.org/jira/browse/AMBARI-22140
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
>Affects Versions: 2.6.0
> Environment: ambari-server --version 2.6.0.0-178
>Reporter: Supreeth Sharma
>Priority: Blocker
> Labels: patch-upgrade
> Fix For: 3.0.0
>
>
> Patch upgrade is failing while performing the upgrade for oozie service.
> Upgrade is failing with below error :
> {code}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 150, in
> OozieServer().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 350, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 119, in locking_configure
> original_configure(obj, *args, **kw)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
> line 70, in configure
> oozie(is_server=True, upgrade_type=upgrade_type)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py",
> line 193, in oozie
> oozie_server_specific(upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie.py",
> line 313, in oozie_server_specific
> not_if = no_op_test,
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 166, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> 'ambari-sudo.sh cp /usr/hdp/2.6.3.0-158/hadoop/lib/hadoop-lzo*.jar
> /usr/hdp/current/oozie-server' returned 1. cp: cannot stat
> `/usr/hdp/2.6.3.0-158/hadoop/lib/hadoop-lzo*.jar': No such file or directory
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22087) Druid start component via ambari doesn't wait to check if the component is successfully started
[
https://issues.apache.org/jira/browse/AMBARI-22087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284287#comment-16284287
]
Swapan Shridhar commented on AMBARI-22087:
--
Moved it to 3.0 as I am started the 2.6.1 release process.
> Druid start component via ambari doesn't wait to check if the component is
> successfully started
> ---
>
> Key: AMBARI-22087
> URL: https://issues.apache.org/jira/browse/AMBARI-22087
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Dileep Kumar Chiguruvada
>Assignee: Nishant Bangarwa
> Labels: druid
> Fix For: trunk, 3.0.0
>
>
> Druid start component via ambari doesn't wait to check if the component is
> successfully started.
> Any component start for Druid service will just execute the start command
> and comes out with exit status 0. It will not further check if the process is
> running, or any port if its listening.
> say for example Druid Coordinator
> {code}
> 2017-09-19 18:48:47,076 - Execute['/usr/lib/jvm/java-openjdk/bin/java -cp
> /usr/lib/ambari-agent/DBConnectionVerification.jar:/usr/hdp/current/druid-coordinator/extensions/mysql-metadata-storage/mysql-connector-java.jar
> org.apache.ambari.server.DBConnectionVerification
> 'jdbc:mysql://ctr-e134-1499953498516-160569-01-07.hwx.site:3306/druid?createDatabaseIfNotExist=true'
> druid [PROTECTED] com.mysql.jdbc.Driver'] {'tries': 5, 'user': 'druid',
> 'try_sleep': 10}
> 2017-09-19 18:48:47,554 - Execute['source
> /usr/hdp/current/druid-coordinator/conf/druid-env.sh ;
> /usr/hdp/current/druid-coordinator/bin/node.sh coordinator start'] {'user':
> 'druid'}
> Command completed successfully!
> {code}
> The start command via Ambari-UI shows as passed on Ambari-ops even if the
> component fails to start. this gives false impression to check the service.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22182) In order to achieve internationalization, provide multi-language version support, such as Chinese support
[ https://issues.apache.org/jira/browse/AMBARI-22182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-22182: - Fix Version/s: (was: 2.6.1) 3.0.0 > In order to achieve internationalization, provide multi-language version > support, such as Chinese support > - > > Key: AMBARI-22182 > URL: https://issues.apache.org/jira/browse/AMBARI-22182 > Project: Ambari > Issue Type: New Feature > Components: ambari-web >Affects Versions: 2.5.0, 2.4.2, 2.5.2 >Reporter: rila kwan > Labels: newbie, performance, usability > Fix For: 3.0.0 > > Original Estimate: 672h > Remaining Estimate: 672h > > With the development of the community, the use of ambari is becoming more and > more popular, and more and more developers of different languages are also > involved.At present, only the English version has been unable to meet the > requirements of users.For example, in China, many companies face the problem > of localization. > So the next version, hoping to add new language support features,users can > switch to other languages, such as Chinese, Japanese, and so on. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22175) Host check operation is being performed on all hosts during host add
[ https://issues.apache.org/jira/browse/AMBARI-22175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-22175: - Fix Version/s: (was: 2.6.1) 3.0.0 > Host check operation is being performed on all hosts during host add > > > Key: AMBARI-22175 > URL: https://issues.apache.org/jira/browse/AMBARI-22175 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.1 >Reporter: amarnath reddy pappu >Priority: Critical > Fix For: 3.0.0 > > > Steps to reproduce: > 1. Have a cluster with 2/3 hosts > 2. now try to add a new host from UI > 3. Ambari initiates host check for all the hosts in the cluster instead of > doing it for new host alone. if there is any issues with other hosts then > host add will get hung and will not be able to proceed further. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22222) Switch druid to use /var/druid directory instead of /apps/druid on local disk
[ https://issues.apache.org/jira/browse/AMBARI-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284281#comment-16284281 ] Swapan Shridhar commented on AMBARI-2: -- Moved it to 3.0 as I am started the 2.6.1 release process. [~nishantbangarwa] > Switch druid to use /var/druid directory instead of /apps/druid on local disk > - > > Key: AMBARI-2 > URL: https://issues.apache.org/jira/browse/AMBARI-2 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: 3.0.0 > > Attachments: AMBARI-2.patch > > > Druid requires directories be created at /apps/druid. If the /apps directory > is read only, Druid installation will fail. Since /apps directory does not > have any industry wide standards, use a more standard location such as /var > or /usr. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22175) Host check operation is being performed on all hosts during host add
[ https://issues.apache.org/jira/browse/AMBARI-22175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284283#comment-16284283 ] Swapan Shridhar commented on AMBARI-22175: -- Moved it to 3.0 as I am started the 2.6.1 release process. > Host check operation is being performed on all hosts during host add > > > Key: AMBARI-22175 > URL: https://issues.apache.org/jira/browse/AMBARI-22175 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.1 >Reporter: amarnath reddy pappu >Priority: Critical > Fix For: 3.0.0 > > > Steps to reproduce: > 1. Have a cluster with 2/3 hosts > 2. now try to add a new host from UI > 3. Ambari initiates host check for all the hosts in the cluster instead of > doing it for new host alone. if there is any issues with other hosts then > host add will get hung and will not be able to proceed further. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22182) In order to achieve internationalization, provide multi-language version support, such as Chinese support
[ https://issues.apache.org/jira/browse/AMBARI-22182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284282#comment-16284282 ] Swapan Shridhar commented on AMBARI-22182: -- Moved it to 3.0 as I am started the 2.6.1 release process. > In order to achieve internationalization, provide multi-language version > support, such as Chinese support > - > > Key: AMBARI-22182 > URL: https://issues.apache.org/jira/browse/AMBARI-22182 > Project: Ambari > Issue Type: New Feature > Components: ambari-web >Affects Versions: 2.5.0, 2.4.2, 2.5.2 >Reporter: rila kwan > Labels: newbie, performance, usability > Fix For: 3.0.0 > > Original Estimate: 672h > Remaining Estimate: 672h > > With the development of the community, the use of ambari is becoming more and > more popular, and more and more developers of different languages are also > involved.At present, only the English version has been unable to meet the > requirements of users.For example, in China, many companies face the problem > of localization. > So the next version, hoping to add new language support features,users can > switch to other languages, such as Chinese, Japanese, and so on. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22222) Switch druid to use /var/druid directory instead of /apps/druid on local disk
[ https://issues.apache.org/jira/browse/AMBARI-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-2: - Fix Version/s: (was: 2.6.1) 3.0.0 > Switch druid to use /var/druid directory instead of /apps/druid on local disk > - > > Key: AMBARI-2 > URL: https://issues.apache.org/jira/browse/AMBARI-2 > Project: Ambari > Issue Type: Bug >Reporter: Nishant Bangarwa >Assignee: Nishant Bangarwa > Fix For: 3.0.0 > > Attachments: AMBARI-2.patch > > > Druid requires directories be created at /apps/druid. If the /apps directory > is read only, Druid installation will fail. Since /apps directory does not > have any industry wide standards, use a more standard location such as /var > or /usr. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-21282) Support for macro based property definitions in Pig View
[
https://issues.apache.org/jira/browse/AMBARI-21282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-21282:
-
Fix Version/s: (was: 2.6.1)
3.0.0
> Support for macro based property definitions in Pig View
>
>
> Key: AMBARI-21282
> URL: https://issues.apache.org/jira/browse/AMBARI-21282
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Sridhar Sailappan
> Fix For: 3.0.0
>
> Attachments: Patch_AmbariPigView_Macro_20170619.txt
>
>
> The attached patch for Pig View provides support for property configurations
> with macro based definitions (relying on variable expansion of Hadoop
> Configuration).
>
> e.g., Consider the following definition of properties for HDFS.
> 1) In Advanced core-site, property "fs.defaultFS" is defined to have value
> "${fs.defaultFS.dev}"
> 2) In Custom core-site, property "fs.defaultFS.dev" is defined to have value
> "hdfs://dev-sandbox.hortonworks.com:8020"
>
> Now, when referencing the property "fs.defaultFS", the value should be
> resolved to "hdfs://dev-sandbox.hortonworks.com:8020".
>
> This is typical variable expansion that is expected in Hadoop Configuration.
> Refer:
> https://hadoop.apache.org/docs/r2.6.0/api/org/apache/hadoop/conf/Configuration.html
> This functionality of variable expansion is not available with Pig View. The
> attached patch (on branch-2.4.0) addresses this need.
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-21282) Support for macro based property definitions in Pig View
[
https://issues.apache.org/jira/browse/AMBARI-21282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284276#comment-16284276
]
Swapan Shridhar commented on AMBARI-21282:
--
Moved it to 3.0 as I am started the 2.6.1 release process.
> Support for macro based property definitions in Pig View
>
>
> Key: AMBARI-21282
> URL: https://issues.apache.org/jira/browse/AMBARI-21282
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-views
>Affects Versions: 2.4.0
>Reporter: Sridhar Sailappan
> Fix For: 3.0.0
>
> Attachments: Patch_AmbariPigView_Macro_20170619.txt
>
>
> The attached patch for Pig View provides support for property configurations
> with macro based definitions (relying on variable expansion of Hadoop
> Configuration).
>
> e.g., Consider the following definition of properties for HDFS.
> 1) In Advanced core-site, property "fs.defaultFS" is defined to have value
> "${fs.defaultFS.dev}"
> 2) In Custom core-site, property "fs.defaultFS.dev" is defined to have value
> "hdfs://dev-sandbox.hortonworks.com:8020"
>
> Now, when referencing the property "fs.defaultFS", the value should be
> resolved to "hdfs://dev-sandbox.hortonworks.com:8020".
>
> This is typical variable expansion that is expected in Hadoop Configuration.
> Refer:
> https://hadoop.apache.org/docs/r2.6.0/api/org/apache/hadoop/conf/Configuration.html
> This functionality of variable expansion is not available with Pig View. The
> attached patch (on branch-2.4.0) addresses this need.
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22306) Cluster state is out of sync after HDP installation with Superset
[
https://issues.apache.org/jira/browse/AMBARI-22306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284273#comment-16284273
]
Swapan Shridhar commented on AMBARI-22306:
--
Moved it to 3.0 as I am started the 2.6.1 release process.
CC [~nishantbangarwa]
> Cluster state is out of sync after HDP installation with Superset
> -
>
> Key: AMBARI-22306
> URL: https://issues.apache.org/jira/browse/AMBARI-22306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
> Environment: ambari-server --version 2.6.0.0-256
>Reporter: Supreeth Sharma
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: trunk, 3.0.0
>
> Attachments: AMBARI-22306.patch, out_of_sync.png
>
>
> Live cluster : http://172.27.26.136:8080/#/main/admin/stack/versions
> Cluster is going out of sync after HDP installation with superset. Attaching
> the screenshot.
> Issue looks similar to https://hortonworks.jira.com/browse/BUG-90028.
> Checked
> https://github.com/hortonworks/ambari/blob/AMBARI-2.6.0.0/ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/metainfo.xml
> and
> 'versionAdvertised' is true
> {code}
> true
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22306) Cluster state is out of sync after HDP installation with Superset
[
https://issues.apache.org/jira/browse/AMBARI-22306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-22306:
-
Fix Version/s: (was: 2.6.1)
3.0.0
> Cluster state is out of sync after HDP installation with Superset
> -
>
> Key: AMBARI-22306
> URL: https://issues.apache.org/jira/browse/AMBARI-22306
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
> Environment: ambari-server --version 2.6.0.0-256
>Reporter: Supreeth Sharma
>Assignee: Nishant Bangarwa
>Priority: Blocker
> Fix For: trunk, 3.0.0
>
> Attachments: AMBARI-22306.patch, out_of_sync.png
>
>
> Live cluster : http://172.27.26.136:8080/#/main/admin/stack/versions
> Cluster is going out of sync after HDP installation with superset. Attaching
> the screenshot.
> Issue looks similar to https://hortonworks.jira.com/browse/BUG-90028.
> Checked
> https://github.com/hortonworks/ambari/blob/AMBARI-2.6.0.0/ambari-server/src/main/resources/common-services/SUPERSET/0.15.0/metainfo.xml
> and
> 'versionAdvertised' is true
> {code}
> true
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22321) Add Registry StackFeatures to HDP StackFeatures
[
https://issues.apache.org/jira/browse/AMBARI-22321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar resolved AMBARI-22321.
--
Resolution: Fixed
Marking it resolved as I am starting the 2.6.1 release work.
> Add Registry StackFeatures to HDP StackFeatures
> ---
>
> Key: AMBARI-22321
> URL: https://issues.apache.org/jira/browse/AMBARI-22321
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.0
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.6.1
>
>
> {code}
> {
> "name": "registry_remove_rootpath",
> "description": "Registry remove root path setting",
> "min_version": "2.6.0.0"
> },
> {
> "name": "registry_allowed_resources_support",
> "description": "Registry allowed resources",
> "min_version": "2.6.0.0"
> },
> {
> "name": "registry_rewriteuri_filter_support",
> "description": "Registry RewriteUri servlet filter",
> "min_version": "2.6.0.0"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22607) Design and implement an AD job scheduler.
[ https://issues.apache.org/jira/browse/AMBARI-22607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan updated AMBARI-22607: --- Attachment: AMBARI-22607-2.patch > Design and implement an AD job scheduler. > -- > > Key: AMBARI-22607 > URL: https://issues.apache.org/jira/browse/AMBARI-22607 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Attachments: AMBARI-22607-2.patch > > > Design and implement a scheduler for starting and managing AD jobs on Spark. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22607) Design and implement an AD job scheduler.
[ https://issues.apache.org/jira/browse/AMBARI-22607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-22607. Resolution: Fixed Pushed to feature branch. > Design and implement an AD job scheduler. > -- > > Key: AMBARI-22607 > URL: https://issues.apache.org/jira/browse/AMBARI-22607 > Project: Ambari > Issue Type: Task > Components: ambari-metrics >Affects Versions: 3.0.0 >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan > Attachments: AMBARI-22607-2.patch > > > Design and implement a scheduler for starting and managing AD jobs on Spark. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22483) Add SAM StackFeatures to HDP StackFeatures - DB Storage Support
[
https://issues.apache.org/jira/browse/AMBARI-22483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284236#comment-16284236
]
Swapan Shridhar commented on AMBARI-22483:
--
Moved it to 3.0 as I am started the 2.6.1 release process.
[~YolandaMDavis]
> Add SAM StackFeatures to HDP StackFeatures - DB Storage Support
> ---
>
> Key: AMBARI-22483
> URL: https://issues.apache.org/jira/browse/AMBARI-22483
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
> Fix For: 3.0.0
>
>
> {
> "name": "sam_db_file_storage",
> "description": "DB based file storage in SAM",
> "min_version": "2.6.3.0"
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22483) Add SAM StackFeatures to HDP StackFeatures - DB Storage Support
[
https://issues.apache.org/jira/browse/AMBARI-22483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-22483:
-
Fix Version/s: (was: 2.6.1)
3.0.0
> Add SAM StackFeatures to HDP StackFeatures - DB Storage Support
> ---
>
> Key: AMBARI-22483
> URL: https://issues.apache.org/jira/browse/AMBARI-22483
> Project: Ambari
> Issue Type: Bug
> Components: stacks
>Affects Versions: 2.6.0
>Reporter: Yolanda M. Davis
>Assignee: Yolanda M. Davis
> Fix For: 3.0.0
>
>
> {
> "name": "sam_db_file_storage",
> "description": "DB based file storage in SAM",
> "min_version": "2.6.3.0"
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22491) Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
[ https://issues.apache.org/jira/browse/AMBARI-22491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-22491: - Resolution: Fixed Status: Resolved (was: Patch Available) Marking it resolved as I am starting the 2.6.1 release work. CC [~aantonenko] > Moving Metrics Collector Forces ZooKeeper Server Install on Target Host > --- > > Key: AMBARI-22491 > URL: https://issues.apache.org/jira/browse/AMBARI-22491 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22491.patch > > > When moving a Metrics Collector, a ZooKeeper Server is installed on the > target host along with the Metrics Collector. This ZooKeeper Server is added > and quorum can be upset in large clusters, and the customer was not intending > to have a ZooKeeper server on the target directory. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (AMBARI-22457) Conditionally Install LZO packages through Ambari
[ https://issues.apache.org/jira/browse/AMBARI-22457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284210#comment-16284210 ] Swapan Shridhar edited comment on AMBARI-22457 at 12/8/17 9:13 PM: --- [~swagle] Marking it resolved as I am starting the 2.6.1 release work. was (Author: swapanshridhar): Marking it resolved as I am starting the 2.6.1 release work. > Conditionally Install LZO packages through Ambari > - > > Key: AMBARI-22457 > URL: https://issues.apache.org/jira/browse/AMBARI-22457 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server >Affects Versions: 2.6.1 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.6.1 > > Attachments: GPL Use Cases.jpg > > > LZO should only be installed if the user has met the requirements to allow > Ambari to download and install them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22539) Cannot add host with host_name in request body
[
https://issues.apache.org/jira/browse/AMBARI-22539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-22539:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Marking it resolved as I am starting the 2.6.1 release work.
> Cannot add host with host_name in request body
> --
>
> Key: AMBARI-22539
> URL: https://issues.apache.org/jira/browse/AMBARI-22539
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22539.branch-2.6.patch
>
>
> STR:
> # Create cluster via blueprints
> # Add a new node to one of the host groups specifying {{host_name}} in the
> request body according to the "multiple hosts" [example in
> wiki|https://cwiki.apache.org/confluence/display/AMBARI/Blueprints#Blueprints-AddHostRequest]
> Expected result: host is added
> Actual result: request is rejected with "Must specify either host_name or
> host_count" error
> {noformat}
> $ curl -X POST -d '[ { "blueprint": "blue", "host_group": "node",
> "host_name": "c6402.ambari.apache.org" } ]'
> http://c6401.ambari.apache.org:8080/api/v1/clusters/TEST/hosts
> HTTP/1.1 400 Bad Request
> {noformat}
> Similar request with host name under {{Hosts/host_name}} is accepted:
> {noformat}
> $ curl -X POST -d '[ { "blueprint": "blue", "host_group": "node", "Hosts": {
> "host_name": "c6403.ambari.apache.org" } } ]'
> http://c6401.ambari.apache.org:8080/api/v1/clusters/TEST/hosts
> HTTP/1.1 202 Accepted
> {noformat}
> Also, request with host name specified path is accepted:
> {noformat}
> $ curl -X POST -d '[ { "blueprint": "blue", "host_group": "node" } ]'
> http://c6401.ambari.apache.org:8080/api/v1/clusters/TEST/hosts/c6404.ambari.apache.org
> HTTP/1.1 202 Accepted
> {noformat}
> All three requests work fine in Ambari 2.5.2.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22457) Conditionally Install LZO packages through Ambari
[ https://issues.apache.org/jira/browse/AMBARI-22457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar resolved AMBARI-22457. -- Resolution: Fixed > Conditionally Install LZO packages through Ambari > - > > Key: AMBARI-22457 > URL: https://issues.apache.org/jira/browse/AMBARI-22457 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server >Affects Versions: 2.6.1 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.6.1 > > Attachments: GPL Use Cases.jpg > > > LZO should only be installed if the user has met the requirements to allow > Ambari to download and install them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22457) Conditionally Install LZO packages through Ambari
[ https://issues.apache.org/jira/browse/AMBARI-22457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284210#comment-16284210 ] Swapan Shridhar commented on AMBARI-22457: -- Marking it resolved as I am starting the 2.6.1 release work. > Conditionally Install LZO packages through Ambari > - > > Key: AMBARI-22457 > URL: https://issues.apache.org/jira/browse/AMBARI-22457 > Project: Ambari > Issue Type: Epic > Components: ambari-agent, ambari-server >Affects Versions: 2.6.1 >Reporter: Siddharth Wagle >Assignee: Siddharth Wagle >Priority: Critical > Fix For: 2.6.1 > > Attachments: GPL Use Cases.jpg > > > LZO should only be installed if the user has met the requirements to allow > Ambari to download and install them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22618) User should be able to install Yarn DNS server using "+Add" utility from Host page
Yesha Vora created AMBARI-22618: --- Summary: User should be able to install Yarn DNS server using "+Add" utility from Host page Key: AMBARI-22618 URL: https://issues.apache.org/jira/browse/AMBARI-22618 Project: Ambari Issue Type: Bug Affects Versions: 3.0.0 Reporter: Yesha Vora Priority: Critical Scenario: Install Yarn component without selecting "Yarn DNS registry" After installation, go to Host page and click on +ADD. Yarn DNS registry service option should be present to allow the user to add the service to host. Currently, Yarn DNS registry service can not be ADDED to host directly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22561) Need to address HDP-GPL repo update after user accepts license in post-install scenario
[ https://issues.apache.org/jira/browse/AMBARI-22561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284208#comment-16284208 ] Swapan Shridhar commented on AMBARI-22561: -- Moved it to 3.0 as I am started the 2.6.1 release process. > Need to address HDP-GPL repo update after user accepts license in > post-install scenario > --- > > Key: AMBARI-22561 > URL: https://issues.apache.org/jira/browse/AMBARI-22561 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-22561.patch > > > * User denies the GPL license agreement, UI will still issue PUT call to > create the repo > * Ambari should not write HDP-GPL repo info to the ambari-hdp-1.repo > because it will break yum in local repo world. > * Then the user accepts the license by running ambari-server setup > * The repo file does not get updated on existing hosts > * We need to push the HDP-GPL repo to the repo files on existing hosts only > when the license is accepted -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22561) Need to address HDP-GPL repo update after user accepts license in post-install scenario
[ https://issues.apache.org/jira/browse/AMBARI-22561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-22561: - Fix Version/s: 3.0.0 > Need to address HDP-GPL repo update after user accepts license in > post-install scenario > --- > > Key: AMBARI-22561 > URL: https://issues.apache.org/jira/browse/AMBARI-22561 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Fix For: 3.0.0 > > Attachments: AMBARI-22561.patch > > > * User denies the GPL license agreement, UI will still issue PUT call to > create the repo > * Ambari should not write HDP-GPL repo info to the ambari-hdp-1.repo > because it will break yum in local repo world. > * Then the user accepts the license by running ambari-server setup > * The repo file does not get updated on existing hosts > * We need to push the HDP-GPL repo to the repo files on existing hosts only > when the license is accepted -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22561) Need to address HDP-GPL repo update after user accepts license in post-install scenario
[ https://issues.apache.org/jira/browse/AMBARI-22561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-22561: - Fix Version/s: (was: 2.6.1) > Need to address HDP-GPL repo update after user accepts license in > post-install scenario > --- > > Key: AMBARI-22561 > URL: https://issues.apache.org/jira/browse/AMBARI-22561 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk > Attachments: AMBARI-22561.patch > > > * User denies the GPL license agreement, UI will still issue PUT call to > create the repo > * Ambari should not write HDP-GPL repo info to the ambari-hdp-1.repo > because it will break yum in local repo world. > * Then the user accepts the license by running ambari-server setup > * The repo file does not get updated on existing hosts > * We need to push the HDP-GPL repo to the repo files on existing hosts only > when the license is accepted -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22527) Error while viewing topology details - Storm View
[
https://issues.apache.org/jira/browse/AMBARI-22527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapan Shridhar updated AMBARI-22527:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Error while viewing topology details - Storm View
> -
>
> Key: AMBARI-22527
> URL: https://issues.apache.org/jira/browse/AMBARI-22527
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
> Environment: ambari-server --version
> 2.6.1.0-59
>Reporter: Sanket Shah
>Assignee: Sanket Shah
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22527.patch
>
>
> {noformat}
> Uncaught Error: Minified React error #130; visit
> http://facebook.github.io/react/docs/error-decoder.html?invariant=130[]=object[]=%20Check%20the%20render%20method%20of%20%60e%60.
> for the full message or use the non-minified dev environment for full errors
> and additional helpful warnings.
> at n (vendor.bundle.js:4)
> at a (vendor.bundle.js:6)
> at Object.updateChildren (vendor.bundle.js:2)
> at v._reconcilerUpdateChildren (vendor.bundle.js:3)
> at v._updateChildren (vendor.bundle.js:3)
> at v.updateChildren (vendor.bundle.js:3)
> at v._updateDOMChildren (vendor.bundle.js:2)
> at v.updateComponent (vendor.bundle.js:2)
> at v.receiveComponent (vendor.bundle.js:2)
> at Object.receiveComponent (vendor.bundle.js:2)
> {noformat}
> On the latest build, due to few npm packages being updated dynamically, Storm
> view is running into above mentioned error.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22615) Log Search UI: improve histogram display
[ https://issues.apache.org/jira/browse/AMBARI-22615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283965#comment-16283965 ] Hudson commented on AMBARI-22615: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8511 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8511/]) AMBARI-22615 Log Search UI: improve histogram display. (Istvan Tobias (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b1fd131f78feda8f9fef6f33dbc8c67e3fdf539f]) * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/time-histogram/time-histogram.component.html * (edit) ambari-logsearch/ambari-logsearch-web/src/assets/i18n/en.json * (edit) ambari-logsearch/ambari-logsearch-web/src/app/classes/histogram-options.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/mixins.less * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/time-histogram/time-histogram.component.less * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/time-histogram/time-histogram.component.spec.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/time-histogram/time-histogram.component.ts * (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/logs-container.service.ts > Log Search UI: improve histogram display > > > Key: AMBARI-22615 > URL: https://issues.apache.org/jira/browse/AMBARI-22615 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Istvan Tobias > Fix For: 3.0.0 > > Attachments: AMBARI-22615.patch > > > # Add tooltip over columns > # Add legend > # Add display of selected time interval length > # Reduce the height of the histogram > # When narrowing in on time in the histogram we need to make the bars wider > to fill more of the gap > # Also when zooming in we should have text to tell you the gap > # The amount of space between the y axis and the bars needs to be increased -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22617) Install Wizard Customize Services step has no vertical scroll
[ https://issues.apache.org/jira/browse/AMBARI-22617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283883#comment-16283883 ] Hudson commented on AMBARI-22617: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8510 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8510/]) AMBARI-22617. Install Wizard Customize Services step has no vertical (akovalenko: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ee506295d3d911c4bc9b00233481a1db97cd9289]) * (edit) ambari-web/app/templates/main/host/configs_service.hbs * (edit) ambari-web/app/templates/main/service/info/configs.hbs * (edit) ambari-web/app/styles/application.less * (edit) ambari-web/app/templates/common/configs/service_config_wizard.hbs > Install Wizard Customize Services step has no vertical scroll > - > > Key: AMBARI-22617 > URL: https://issues.apache.org/jira/browse/AMBARI-22617 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22617.patch > > > it it unable to scroll down step content -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22617) Install Wizard Customize Services step has no vertical scroll
[
https://issues.apache.org/jira/browse/AMBARI-22617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283868#comment-16283868
]
Hadoop QA commented on AMBARI-22617:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12901251/AMBARI-22617.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12818//console
This message is automatically generated.
> Install Wizard Customize Services step has no vertical scroll
> -
>
> Key: AMBARI-22617
> URL: https://issues.apache.org/jira/browse/AMBARI-22617
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22617.patch
>
>
> it it unable to scroll down step content
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22615) Log Search UI: improve histogram display
[ https://issues.apache.org/jira/browse/AMBARI-22615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-22615: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Log Search UI: improve histogram display > > > Key: AMBARI-22615 > URL: https://issues.apache.org/jira/browse/AMBARI-22615 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Istvan Tobias > Fix For: 3.0.0 > > Attachments: AMBARI-22615.patch > > > # Add tooltip over columns > # Add legend > # Add display of selected time interval length > # Reduce the height of the histogram > # When narrowing in on time in the histogram we need to make the bars wider > to fill more of the gap > # Also when zooming in we should have text to tell you the gap > # The amount of space between the y axis and the bars needs to be increased -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22617) Install Wizard Customize Services step has no vertical scroll
[ https://issues.apache.org/jira/browse/AMBARI-22617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-22617: - Resolution: Fixed Status: Resolved (was: Patch Available) > Install Wizard Customize Services step has no vertical scroll > - > > Key: AMBARI-22617 > URL: https://issues.apache.org/jira/browse/AMBARI-22617 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22617.patch > > > it it unable to scroll down step content -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22617) Install Wizard Customize Services step has no vertical scroll
[ https://issues.apache.org/jira/browse/AMBARI-22617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283829#comment-16283829 ] Aleksandr Kovalenko commented on AMBARI-22617: -- committed to trunk > Install Wizard Customize Services step has no vertical scroll > - > > Key: AMBARI-22617 > URL: https://issues.apache.org/jira/browse/AMBARI-22617 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22617.patch > > > it it unable to scroll down step content -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22615) Log Search UI: improve histogram display
[
https://issues.apache.org/jira/browse/AMBARI-22615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283826#comment-16283826
]
Hadoop QA commented on AMBARI-22615:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12901235/AMBARI-22615.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-logsearch/ambari-logsearch-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12817//console
This message is automatically generated.
> Log Search UI: improve histogram display
>
>
> Key: AMBARI-22615
> URL: https://issues.apache.org/jira/browse/AMBARI-22615
> Project: Ambari
> Issue Type: Task
> Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Istvan Tobias
> Fix For: 3.0.0
>
> Attachments: AMBARI-22615.patch
>
>
> # Add tooltip over columns
> # Add legend
> # Add display of selected time interval length
> # Reduce the height of the histogram
> # When narrowing in on time in the histogram we need to make the bars wider
> to fill more of the gap
> # Also when zooming in we should have text to tell you the gap
> # The amount of space between the y axis and the bars needs to be increased
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22617) Install Wizard Customize Services step has no vertical scroll
[ https://issues.apache.org/jira/browse/AMBARI-22617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283824#comment-16283824 ] Aleksandr Kovalenko commented on AMBARI-22617: -- patch doesn't have changes in javascript files > Install Wizard Customize Services step has no vertical scroll > - > > Key: AMBARI-22617 > URL: https://issues.apache.org/jira/browse/AMBARI-22617 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22617.patch > > > it it unable to scroll down step content -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22612) Log Search UI: Fixes for Top-Level Buttons
[ https://issues.apache.org/jira/browse/AMBARI-22612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283813#comment-16283813 ] Hudson commented on AMBARI-22612: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8509 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8509/]) AMBARI-22612 Log Search UI: Fixes for Top-Level Buttons. (Istvan Tobias (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2b285dac1667e80b89c8719f1746cb433bf0d4dc]) * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-container/logs-container.component.less * (edit) ambari-logsearch/ambari-logsearch-web/src/app/components/logs-container/logs-container.component.html > Log Search UI: Fixes for Top-Level Buttons > -- > > Key: AMBARI-22612 > URL: https://issues.apache.org/jira/browse/AMBARI-22612 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Istvan Tobias > Fix For: 3.0.0 > > Attachments: AMBARI-22612.patch > > > Recently, the top-level "Undo/Redo/Refresh/History" buttons have been moved > from the top bar to lower in the UI. Buttons should be centered in the bar > vertically. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22616) noplugins switch should not be used for yum repos backed by RedHat Satellite/Spacewalk
[
https://issues.apache.org/jira/browse/AMBARI-22616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283816#comment-16283816
]
Hudson commented on AMBARI-22616:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8509 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8509/])
AMBARI-22616 noplugins switch should not be used for yum repos backed by
(hapylestat:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1ed7c086e4d417b47de8a2a7b80e28956cf01d47])
* (edit)
ambari-common/src/main/python/resource_management/core/providers/package/yumrpm.py
> noplugins switch should not be used for yum repos backed by RedHat
> Satellite/Spacewalk
> --
>
> Key: AMBARI-22616
> URL: https://issues.apache.org/jira/browse/AMBARI-22616
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-22616.patch
>
>
> {{--noplugins}} flag intended to hide unwanted output from plugins to make
> parser get proper yum output, however Satellite/Spacewalk repositories r
> powered by plugins and disabling them leads to excluding those repos from the
> search result
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22613) Hive Queries Failing with Missing SnappyCodec Compression Type Due to Hive's Use of MapReduce Admin Env Property
[
https://issues.apache.org/jira/browse/AMBARI-22613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283815#comment-16283815
]
Hudson commented on AMBARI-22613:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8509 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8509/])
AMBARI-22613 - Hive Queries Failing with Missing SnappyCodec Compression
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=348bdd668ecf6964e2c021aeddf547b3f9bb23bf])
* (edit)
ambari-server/src/main/resources/common-services/HIVE/2.1.0.3.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/common-services/YARN/3.0.0.3.0/configuration-mapred/mapred-site.xml
* (edit)
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration-mapred/mapred-site.xml
* (edit)
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/params_linux.py
* (edit)
ambari-server/src/main/resources/stacks/HDP/2.6/upgrades/config-upgrade.xml
> Hive Queries Failing with Missing SnappyCodec Compression Type Due to Hive's
> Use of MapReduce Admin Env Property
>
>
> Key: AMBARI-22613
> URL: https://issues.apache.org/jira/browse/AMBARI-22613
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Dileep Kumar Chiguruvada
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22613.patch
>
>
> Many queries, similar to the below {{InsertOverwrite}}, are failing after
> performing an HDP->HDP upgrade. The cause is that Hive does not localize the
> Tez TAR file, but instead uses the MapReduce2 property
> {{mapreduce.admin.user.env}}
> {code}
> >>> analyze table studenttab10k compute statistics for columns age ;
> INFO : Session is already open
> INFO : Dag name: analyze table studenttab10k compute st...age(Stage-0)
> INFO : Status: Running (Executing on YARN cluster with App id
> application_1512568339263_0003)
> [2K
> [2K[36;1mVERTICES STATUS TOTAL COMPLETED RUNNING PENDING
> FAILED KILLED
> [22;0m[2K
> [2KMap 1RUNNING 1 010 2
> 0
> Reducer 2 INITED 1 001 0
> 0
> [2K
> [2K[31;1mVERTICES: 00/02 [>>--] 0%ELAPSED
> TIME: 9.38 s
> [22;0m[2K
> [8A[2K
> [2K[36;1mVERTICES STATUS TOTAL COMPLETED RUNNING PENDING
> FAILED KILLED
> [22;0m[2K
> [2KMap 1RUNNING 1 001 4
> 0
> Reducer 2 INITED 1 001 0
> 0
> [2K
> [2K[31;1mVERTICES: 00/02 [>>--] 0%ELAPSED
> TIME: 14.37 s
> [22;0m[2K
> ERROR : Status: Failed
> ERROR : Vertex failed, vertexName=Map 1,
> vertexId=vertex_1512568339263_0003_2_00, diagnostics=[Task failed,
> taskId=task_1512568339263_0003_2_00_00, diagnostics=[TaskAttempt 0
> failed, info=[Error: Failure while running task:java.lang.RuntimeException:
> java.io.IOException: Unable to get CompressorType for codec
> (org.apache.hadoop.io.compress.SnappyCodec). This is most likely due to
> missing native libraries for the codec.
> at
> org.apache.hadoop.hive.ql.exec.tez.TezProcessor.initializeAndRunProcessor(TezProcessor.java:173)
> at
> org.apache.hadoop.hive.ql.exec.tez.TezProcessor.run(TezProcessor.java:139)
> at
> org.apache.tez.runtime.LogicalIOProcessorRuntimeTask.run(LogicalIOProcessorRuntimeTask.java:347)
> at
> org.apache.tez.runtime.task.TezTaskRunner$TaskRunnerCallable$1.run(TezTaskRunner.java:194)
> at
> org.apache.tez.runtime.task.TezTaskRunner$TaskRunnerCallable$1.run(TezTaskRunner.java:185)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866)
> at
>
[jira] [Commented] (AMBARI-22609) Install wizard stacks on select version step
[
https://issues.apache.org/jira/browse/AMBARI-22609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283814#comment-16283814
]
Hudson commented on AMBARI-22609:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8509 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8509/])
AMBARI-22609. Install wizard stacks on select version step (aantonenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ed327bd53eb140789b548044ebd207b3c47ccf3b])
* (edit) ambari-web/app/models/repository.js
> Install wizard stacks on select version step
>
>
> Key: AMBARI-22609
> URL: https://issues.apache.org/jira/browse/AMBARI-22609
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-22609.patch
>
>
> Ambari stacks on install wizard in 2nd step, cause of error:
> {code}
> Cannot read property 'contains' of undefined
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22617) Install Wizard Customize Services step has no vertical scroll
[
https://issues.apache.org/jira/browse/AMBARI-22617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283801#comment-16283801
]
Hadoop QA commented on AMBARI-22617:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12901251/AMBARI-22617.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12816//console
This message is automatically generated.
> Install Wizard Customize Services step has no vertical scroll
> -
>
> Key: AMBARI-22617
> URL: https://issues.apache.org/jira/browse/AMBARI-22617
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22617.patch
>
>
> it it unable to scroll down step content
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AMBARI-22617) Install Wizard Customize Services step has no vertical scroll
[ https://issues.apache.org/jira/browse/AMBARI-22617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283747#comment-16283747 ] Andrii Tkach commented on AMBARI-22617: --- +1 for the patch > Install Wizard Customize Services step has no vertical scroll > - > > Key: AMBARI-22617 > URL: https://issues.apache.org/jira/browse/AMBARI-22617 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22617.patch > > > it it unable to scroll down step content -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22617) Install Wizard Customize Services step has no vertical scroll
[ https://issues.apache.org/jira/browse/AMBARI-22617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-22617: - Attachment: AMBARI-22617.patch > Install Wizard Customize Services step has no vertical scroll > - > > Key: AMBARI-22617 > URL: https://issues.apache.org/jira/browse/AMBARI-22617 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22617.patch > > > it it unable to scroll down step content -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22617) Install Wizard Customize Services step has no vertical scroll
[ https://issues.apache.org/jira/browse/AMBARI-22617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Kovalenko updated AMBARI-22617: - Status: Patch Available (was: Open) > Install Wizard Customize Services step has no vertical scroll > - > > Key: AMBARI-22617 > URL: https://issues.apache.org/jira/browse/AMBARI-22617 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Aleksandr Kovalenko >Assignee: Aleksandr Kovalenko >Priority: Critical > Fix For: 3.0.0 > > Attachments: AMBARI-22617.patch > > > it it unable to scroll down step content -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22617) Install Wizard Customize Services step has no vertical scroll
Aleksandr Kovalenko created AMBARI-22617: Summary: Install Wizard Customize Services step has no vertical scroll Key: AMBARI-22617 URL: https://issues.apache.org/jira/browse/AMBARI-22617 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Priority: Critical Fix For: 3.0.0 it it unable to scroll down step content -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22614) Fix unit tests in feature branch to make them workable
[
https://issues.apache.org/jira/browse/AMBARI-22614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doroszlai, Attila updated AMBARI-22614:
---
Attachment: AMBARI-22614.branch-feature-AMBARI-14714.002.patch
More fixes for {{ServiceGroup}}-related tests in
{{AmbariManagementControllerTest}}:
{noformat}
Tests run: 122, Failures: 3, Errors: 64, Skipped: 4
vs.
Tests run: 122, Failures: 1, Errors: 18, Skipped: 4
{noformat}
> Fix unit tests in feature branch to make them workable
> --
>
> Key: AMBARI-22614
> URL: https://issues.apache.org/jira/browse/AMBARI-22614
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22614.branch-feature-AMBARI-14714.002.patch,
> AMBARI-22614.patch
>
>
> Fix unit tests in feature branch to make them workable
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22616) noplugins switch should not be used for yum repos backed by RedHat Satellite/Spacewalk
[
https://issues.apache.org/jira/browse/AMBARI-22616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-22616:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed:
348bdd668e..1ed7c086e4 trunk -> trunk
> noplugins switch should not be used for yum repos backed by RedHat
> Satellite/Spacewalk
> --
>
> Key: AMBARI-22616
> URL: https://issues.apache.org/jira/browse/AMBARI-22616
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-22616.patch
>
>
> {{--noplugins}} flag intended to hide unwanted output from plugins to make
> parser get proper yum output, however Satellite/Spacewalk repositories r
> powered by plugins and disabling them leads to excluding those repos from the
> search result
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22604) Fix hostConfigMappingEntity cluster_id, concurrency in ClusterImpl and serviceConfigTypes initialization
[ https://issues.apache.org/jira/browse/AMBARI-22604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-22604. - Resolution: Fixed Committed to branch-feature-AMBARI-14714 > Fix hostConfigMappingEntity cluster_id, concurrency in ClusterImpl and > serviceConfigTypes initialization > > > Key: AMBARI-22604 > URL: https://issues.apache.org/jira/browse/AMBARI-22604 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: ambari-server >Reporter: Dmytro Sen >Assignee: Dmytro Sen >Priority: Critical > Fix For: 3.0.0 > > > 1) HostConfigMappingEntity is not correct. You can't use same field > cluster_id for current entity and for joined columns. Use > ClusterTest.testDesiredConfig() to see this issue. > 2) As you can see in ClusterImpl we are using concurrent maps/lists and locks > in methods. Please do the same for your code chnages. > 3) Initialize map serviceConfigTypes, it will prevent many NPE and additional > check for NULL. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22591) MD interpreter fails with NPE (Zeppelin)
[ https://issues.apache.org/jira/browse/AMBARI-22591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhjyot Singh updated AMBARI-22591: - Resolution: Fixed Fix Version/s: 2.6.1 3.0.0 Status: Resolved (was: Patch Available) > MD interpreter fails with NPE (Zeppelin) > > > Key: AMBARI-22591 > URL: https://issues.apache.org/jira/browse/AMBARI-22591 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.6.0 >Reporter: Prabhjyot Singh >Assignee: Prabhjyot Singh > Fix For: 3.0.0, 2.6.1 > > Attachments: AMBARI-22591_trunk_v1.patch > > > While trying to run multiple MarkDown paragraph at once since pegdown-parser > is not thread safe, it fails to render HTLM. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22613) Hive Queries Failing with Missing SnappyCodec Compression Type Due to Hive's Use of MapReduce Admin Env Property
[
https://issues.apache.org/jira/browse/AMBARI-22613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-22613:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Hive Queries Failing with Missing SnappyCodec Compression Type Due to Hive's
> Use of MapReduce Admin Env Property
>
>
> Key: AMBARI-22613
> URL: https://issues.apache.org/jira/browse/AMBARI-22613
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.1
>Reporter: Dileep Kumar Chiguruvada
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22613.patch
>
>
> Many queries, similar to the below {{InsertOverwrite}}, are failing after
> performing an HDP->HDP upgrade. The cause is that Hive does not localize the
> Tez TAR file, but instead uses the MapReduce2 property
> {{mapreduce.admin.user.env}}
> {code}
> >>> analyze table studenttab10k compute statistics for columns age ;
> INFO : Session is already open
> INFO : Dag name: analyze table studenttab10k compute st...age(Stage-0)
> INFO : Status: Running (Executing on YARN cluster with App id
> application_1512568339263_0003)
> [2K
> [2K[36;1mVERTICES STATUS TOTAL COMPLETED RUNNING PENDING
> FAILED KILLED
> [22;0m[2K
> [2KMap 1RUNNING 1 010 2
> 0
> Reducer 2 INITED 1 001 0
> 0
> [2K
> [2K[31;1mVERTICES: 00/02 [>>--] 0%ELAPSED
> TIME: 9.38 s
> [22;0m[2K
> [8A[2K
> [2K[36;1mVERTICES STATUS TOTAL COMPLETED RUNNING PENDING
> FAILED KILLED
> [22;0m[2K
> [2KMap 1RUNNING 1 001 4
> 0
> Reducer 2 INITED 1 001 0
> 0
> [2K
> [2K[31;1mVERTICES: 00/02 [>>--] 0%ELAPSED
> TIME: 14.37 s
> [22;0m[2K
> ERROR : Status: Failed
> ERROR : Vertex failed, vertexName=Map 1,
> vertexId=vertex_1512568339263_0003_2_00, diagnostics=[Task failed,
> taskId=task_1512568339263_0003_2_00_00, diagnostics=[TaskAttempt 0
> failed, info=[Error: Failure while running task:java.lang.RuntimeException:
> java.io.IOException: Unable to get CompressorType for codec
> (org.apache.hadoop.io.compress.SnappyCodec). This is most likely due to
> missing native libraries for the codec.
> at
> org.apache.hadoop.hive.ql.exec.tez.TezProcessor.initializeAndRunProcessor(TezProcessor.java:173)
> at
> org.apache.hadoop.hive.ql.exec.tez.TezProcessor.run(TezProcessor.java:139)
> at
> org.apache.tez.runtime.LogicalIOProcessorRuntimeTask.run(LogicalIOProcessorRuntimeTask.java:347)
> at
> org.apache.tez.runtime.task.TezTaskRunner$TaskRunnerCallable$1.run(TezTaskRunner.java:194)
> at
> org.apache.tez.runtime.task.TezTaskRunner$TaskRunnerCallable$1.run(TezTaskRunner.java:185)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866)
> at
> org.apache.tez.runtime.task.TezTaskRunner$TaskRunnerCallable.callInternal(TezTaskRunner.java:185)
> at
> org.apache.tez.runtime.task.TezTaskRunner$TaskRunnerCallable.callInternal(TezTaskRunner.java:181)
> at org.apache.tez.common.CallableWithNdc.call(CallableWithNdc.java:36)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.io.IOException: Unable to get CompressorType for codec
> (org.apache.hadoop.io.compress.SnappyCodec). This is most likely due to
> missing native libraries for the codec.
> at
>
[jira] [Commented] (AMBARI-22609) Install wizard stacks on select version step
[
https://issues.apache.org/jira/browse/AMBARI-22609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283417#comment-16283417
]
Antonenko Alexander commented on AMBARI-22609:
--
Committed to master
> Install wizard stacks on select version step
>
>
> Key: AMBARI-22609
> URL: https://issues.apache.org/jira/browse/AMBARI-22609
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-22609.patch
>
>
> Ambari stacks on install wizard in 2nd step, cause of error:
> {code}
> Cannot read property 'contains' of undefined
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22609) Install wizard stacks on select version step
[
https://issues.apache.org/jira/browse/AMBARI-22609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander updated AMBARI-22609:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Install wizard stacks on select version step
>
>
> Key: AMBARI-22609
> URL: https://issues.apache.org/jira/browse/AMBARI-22609
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-22609.patch
>
>
> Ambari stacks on install wizard in 2nd step, cause of error:
> {code}
> Cannot read property 'contains' of undefined
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22615) Log Search UI: improve histogram display
[ https://issues.apache.org/jira/browse/AMBARI-22615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-22615: -- Attachment: AMBARI-22615.patch > Log Search UI: improve histogram display > > > Key: AMBARI-22615 > URL: https://issues.apache.org/jira/browse/AMBARI-22615 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Istvan Tobias > Fix For: 3.0.0 > > Attachments: AMBARI-22615.patch > > > # Add tooltip over columns > # Add legend > # Add display of selected time interval length > # Reduce the height of the histogram > # When narrowing in on time in the histogram we need to make the bars wider > to fill more of the gap > # Also when zooming in we should have text to tell you the gap > # The amount of space between the y axis and the bars needs to be increased -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-22615) Log Search UI: improve histogram display
[ https://issues.apache.org/jira/browse/AMBARI-22615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-22615: -- Status: Patch Available (was: Open) > Log Search UI: improve histogram display > > > Key: AMBARI-22615 > URL: https://issues.apache.org/jira/browse/AMBARI-22615 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Istvan Tobias > Fix For: 3.0.0 > > Attachments: AMBARI-22615.patch > > > # Add tooltip over columns > # Add legend > # Add display of selected time interval length > # Reduce the height of the histogram > # When narrowing in on time in the histogram we need to make the bars wider > to fill more of the gap > # Also when zooming in we should have text to tell you the gap > # The amount of space between the y axis and the bars needs to be increased -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22609) Install wizard stacks on select version step
[
https://issues.apache.org/jira/browse/AMBARI-22609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283402#comment-16283402
]
Andrii Tkach commented on AMBARI-22609:
---
+1 for the patch
> Install wizard stacks on select version step
>
>
> Key: AMBARI-22609
> URL: https://issues.apache.org/jira/browse/AMBARI-22609
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 3.0.0
>
> Attachments: AMBARI-22609.patch
>
>
> Ambari stacks on install wizard in 2nd step, cause of error:
> {code}
> Cannot read property 'contains' of undefined
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22616) noplugins switch should not be used for yum repos backed by RedHat Satellite/Spacewalk
[
https://issues.apache.org/jira/browse/AMBARI-22616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-22616:
-
Attachment: AMBARI-22616.patch
> noplugins switch should not be used for yum repos backed by RedHat
> Satellite/Spacewalk
> --
>
> Key: AMBARI-22616
> URL: https://issues.apache.org/jira/browse/AMBARI-22616
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-22616.patch
>
>
> {{--noplugins}} flag intended to hide unwanted output from plugins to make
> parser get proper yum output, however Satellite/Spacewalk repositories r
> powered by plugins and disabling them leads to excluding those repos from the
> search result
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22616) noplugins switch should not be used for yum repos backed by RedHat Satellite/Spacewalk
[
https://issues.apache.org/jira/browse/AMBARI-22616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmytro Grinenko updated AMBARI-22616:
-
Status: Patch Available (was: In Progress)
> noplugins switch should not be used for yum repos backed by RedHat
> Satellite/Spacewalk
> --
>
> Key: AMBARI-22616
> URL: https://issues.apache.org/jira/browse/AMBARI-22616
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: trunk
>
> Attachments: AMBARI-22616.patch
>
>
> {{--noplugins}} flag intended to hide unwanted output from plugins to make
> parser get proper yum output, however Satellite/Spacewalk repositories r
> powered by plugins and disabling them leads to excluding those repos from the
> search result
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22610) Log Search UI: fixes for search box autocomplete
[ https://issues.apache.org/jira/browse/AMBARI-22610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-22610: -- Issue Type: Task (was: Bug) > Log Search UI: fixes for search box autocomplete > > > Key: AMBARI-22610 > URL: https://issues.apache.org/jira/browse/AMBARI-22610 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-22610.patch > > > # Search box typeahead shouldn't display dropdown with 'No Results Found' > text if there are no matches. > # Filtering by parameters from search box should be applied by pressing Enter > as well as by Search button click. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22616) noplugins switch should not be used for yum repos backed by RedHat Satellite/Spacewalk
Dmytro Grinenko created AMBARI-22616:
Summary: noplugins switch should not be used for yum repos backed
by RedHat Satellite/Spacewalk
Key: AMBARI-22616
URL: https://issues.apache.org/jira/browse/AMBARI-22616
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: trunk
Reporter: Dmytro Grinenko
Assignee: Dmytro Grinenko
Priority: Critical
Fix For: trunk
{{--noplugins}} flag intended to hide unwanted output from plugins to make
parser get proper yum output, however Satellite/Spacewalk repositories r
powered by plugins and disabling them leads to excluding those repos from the
search result
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22612) Log Search UI: Fixes for Top-Level Buttons
[ https://issues.apache.org/jira/browse/AMBARI-22612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-22612: -- Issue Type: Task (was: Bug) > Log Search UI: Fixes for Top-Level Buttons > -- > > Key: AMBARI-22612 > URL: https://issues.apache.org/jira/browse/AMBARI-22612 > Project: Ambari > Issue Type: Task > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Istvan Tobias > Fix For: 3.0.0 > > Attachments: AMBARI-22612.patch > > > Recently, the top-level "Undo/Redo/Refresh/History" buttons have been moved > from the top bar to lower in the UI. Buttons should be centered in the bar > vertically. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (AMBARI-22615) Log Search UI: improve histogram display
Andrii Babiichuk created AMBARI-22615: - Summary: Log Search UI: improve histogram display Key: AMBARI-22615 URL: https://issues.apache.org/jira/browse/AMBARI-22615 Project: Ambari Issue Type: Task Components: ambari-logsearch Affects Versions: 3.0.0 Reporter: Andrii Babiichuk Assignee: Istvan Tobias Fix For: 3.0.0 # Add tooltip over columns # Add legend # Add display of selected time interval length # Reduce the height of the histogram # When narrowing in on time in the histogram we need to make the bars wider to fill more of the gap # Also when zooming in we should have text to tell you the gap # The amount of space between the y axis and the bars needs to be increased -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AMBARI-22611) Log Search IT: Expose the right port for Selenium in docker-compose file
[ https://issues.apache.org/jira/browse/AMBARI-22611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó resolved AMBARI-22611. --- Resolution: Fixed > Log Search IT: Expose the right port for Selenium in docker-compose file > > > Key: AMBARI-22611 > URL: https://issues.apache.org/jira/browse/AMBARI-22611 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Issue Comment Deleted] (AMBARI-22606) Service actions for R4ML not loaded
[
https://issues.apache.org/jira/browse/AMBARI-22606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan updated AMBARI-22606:
Comment: was deleted
(was: Reopening as issue occurs in ambari-113)
> Service actions for R4ML not loaded
> ---
>
> Key: AMBARI-22606
> URL: https://issues.apache.org/jira/browse/AMBARI-22606
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22606.patch, AMBARI-22606_branch-2.6.patch
>
>
> While trying to delete R4ML service, the Service actions menu doesn't load
> with next js error:
> {code}
> app.js:180350 Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.createServiceConfig (app.js:180350)
> at app.js:30065
> at Array.forEach ()
> at Object. (app.js:30060)
> at o (vendor.js:106)
> at Object.add [as done] (vendor.js:106)
> at Object. (app.js:30054)
> at o (vendor.js:106)
> at Object.fireWith (vendor.js:106)
> at Object.fire [as resolve] (vendor.js:106)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AMBARI-22606) Service actions for R4ML not loaded
[
https://issues.apache.org/jira/browse/AMBARI-22606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan resolved AMBARI-22606.
-
Resolution: Fixed
> Service actions for R4ML not loaded
> ---
>
> Key: AMBARI-22606
> URL: https://issues.apache.org/jira/browse/AMBARI-22606
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22606.patch, AMBARI-22606_branch-2.6.patch
>
>
> While trying to delete R4ML service, the Service actions menu doesn't load
> with next js error:
> {code}
> app.js:180350 Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.createServiceConfig (app.js:180350)
> at app.js:30065
> at Array.forEach ()
> at Object. (app.js:30060)
> at o (vendor.js:106)
> at Object.add [as done] (vendor.js:106)
> at Object. (app.js:30054)
> at o (vendor.js:106)
> at Object.fireWith (vendor.js:106)
> at Object.fire [as resolve] (vendor.js:106)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-22612) Log Search UI: Fixes for Top-Level Buttons
[ https://issues.apache.org/jira/browse/AMBARI-22612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-22612: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk > Log Search UI: Fixes for Top-Level Buttons > -- > > Key: AMBARI-22612 > URL: https://issues.apache.org/jira/browse/AMBARI-22612 > Project: Ambari > Issue Type: Bug > Components: ambari-logsearch >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Istvan Tobias > Fix For: 3.0.0 > > Attachments: AMBARI-22612.patch > > > Recently, the top-level "Undo/Redo/Refresh/History" buttons have been moved > from the top bar to lower in the UI. Buttons should be centered in the bar > vertically. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (AMBARI-22606) Service actions for R4ML not loaded
[
https://issues.apache.org/jira/browse/AMBARI-22606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Janardhan reopened AMBARI-22606:
-
Reopening as issue occurs in ambari-113
> Service actions for R4ML not loaded
> ---
>
> Key: AMBARI-22606
> URL: https://issues.apache.org/jira/browse/AMBARI-22606
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.6.1
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22606.patch, AMBARI-22606_branch-2.6.patch
>
>
> While trying to delete R4ML service, the Service actions menu doesn't load
> with next js error:
> {code}
> app.js:180350 Uncaught TypeError: Cannot read property 'get' of undefined
> at Class.createServiceConfig (app.js:180350)
> at app.js:30065
> at Array.forEach ()
> at Object. (app.js:30060)
> at o (vendor.js:106)
> at Object.add [as done] (vendor.js:106)
> at Object. (app.js:30054)
> at o (vendor.js:106)
> at Object.fireWith (vendor.js:106)
> at Object.fire [as resolve] (vendor.js:106)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
