[jira] [Updated] (AMBARI-22422) Ambari Metrics does not work with DateTieredStoreEngine

[Zhanwei Wang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhanwei Wang updated AMBARI-22422:
--
Attachment: ambari-metrics-collector-log.tar.gz

attach all collector logs

> Ambari Metrics does not work with DateTieredStoreEngine
> ---
>
> Key: AMBARI-22422
> URL: https://issues.apache.org/jira/browse/AMBARI-22422
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.6.0
> Environment: centos7
>Reporter: Zhanwei Wang
> Attachments: ambari-metrics-collector-etc.tar.gz, 
> ambari-metrics-collector-log.tar.gz
>
>
> I build Ambari from source code with tag release-2.6.0 and setup a three node 
> centos7 cluster for test.
> With all default configurations, Ambari Metrics did not work and I found the 
> following from HBase logs.
> {noformat}
> 2017-11-11 15:07:56,478 INFO  
> [B.defaultRpcServer.handler=24,queue=0,port=40128] zookeeper.ZooKeeper: 
> Initiating client connection, connectString=test3:61181 sessionTimeout=12 
> watcher=hconnection-0x23f7d8350x0, quorum=test3:61181, 
> baseZNode=/ams-hbase-unsecure
> @ 
>@
> at 
> org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:129)
> at 
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:128)
> 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 load configured store engine 
> 'org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine'
> at 
> org.apache.hadoop.hbase.regionserver.StoreEngine.create(StoreEngine.java:128)
> at org.apache.hadoop.hbase.regionserver.HStore.(HStore.java:271)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:4958)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:905)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:902)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> ... 3 more
> Caused by: java.lang.UnsupportedOperationException: Unable to find 
> org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine
> at 
> org.apache.hadoop.hbase.util.ReflectionUtils.instantiateWithCustomCtor(ReflectionUtils.java:36)
> at 
> org.apache.hadoop.hbase.regionserver.StoreEngine.create(StoreEngine.java:123)
> ... 10 more
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at 
> org.apache.hadoop.hbase.util.ReflectionUtils.instantiateWithCustomCtor(ReflectionUtils.java:32)
> ... 11 more
> {noformat}
> After adding the following to ams-site.xml. Ambari Metrics work normally. And 
> no more Exception found in both collector and hbase logs.
> {noformat}
> 
>   
> timeline.metrics.hbase.aggregate.table.compaction.policy.class
>   org.apache.hadoop.hbase.regionserver.DefaultStoreEngine
> 
> {noformat}
> From HBASE-19223, Date Tiered Compaction is only available starting in the 
> 1.3 release.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22422) Ambari Metrics does not work with DateTieredStoreEngine

[Zhanwei Wang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhanwei Wang updated AMBARI-22422:
--
Attachment: ambari-metrics-collector-etc.tar.gz

attach collector configuration

> Ambari Metrics does not work with DateTieredStoreEngine
> ---
>
> Key: AMBARI-22422
> URL: https://issues.apache.org/jira/browse/AMBARI-22422
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics
>Affects Versions: 2.6.0
> Environment: centos7
>Reporter: Zhanwei Wang
> Attachments: ambari-metrics-collector-etc.tar.gz
>
>
> I build Ambari from source code with tag release-2.6.0 and setup a three node 
> centos7 cluster for test.
> With all default configurations, Ambari Metrics did not work and I found the 
> following from HBase logs.
> {noformat}
> 2017-11-11 15:07:56,478 INFO  
> [B.defaultRpcServer.handler=24,queue=0,port=40128] zookeeper.ZooKeeper: 
> Initiating client connection, connectString=test3:61181 sessionTimeout=12 
> watcher=hconnection-0x23f7d8350x0, quorum=test3:61181, 
> baseZNode=/ams-hbase-unsecure
> @ 
>@
> at 
> org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:129)
> at 
> org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:128)
> 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 load configured store engine 
> 'org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine'
> at 
> org.apache.hadoop.hbase.regionserver.StoreEngine.create(StoreEngine.java:128)
> at org.apache.hadoop.hbase.regionserver.HStore.(HStore.java:271)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:4958)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:905)
> at 
> org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:902)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> ... 3 more
> Caused by: java.lang.UnsupportedOperationException: Unable to find 
> org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine
> at 
> org.apache.hadoop.hbase.util.ReflectionUtils.instantiateWithCustomCtor(ReflectionUtils.java:36)
> at 
> org.apache.hadoop.hbase.regionserver.StoreEngine.create(StoreEngine.java:123)
> ... 10 more
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at 
> org.apache.hadoop.hbase.util.ReflectionUtils.instantiateWithCustomCtor(ReflectionUtils.java:32)
> ... 11 more
> {noformat}
> After adding the following to ams-site.xml. Ambari Metrics work normally. And 
> no more Exception found in both collector and hbase logs.
> {noformat}
> 
>   
> timeline.metrics.hbase.aggregate.table.compaction.policy.class
>   org.apache.hadoop.hbase.regionserver.DefaultStoreEngine
> 
> {noformat}
> From HBASE-19223, Date Tiered Compaction is only available starting in the 
> 1.3 release.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AMBARI-22422) Ambari Metrics does not work with DateTieredStoreEngine

[Zhanwei Wang (JIRA)]

Zhanwei Wang created AMBARI-22422:
-

 Summary: Ambari Metrics does not work with DateTieredStoreEngine
 Key: AMBARI-22422
 URL: https://issues.apache.org/jira/browse/AMBARI-22422
 Project: Ambari
  Issue Type: Bug
  Components: ambari-metrics
Affects Versions: 2.6.0
 Environment: centos7
Reporter: Zhanwei Wang


I build Ambari from source code with tag release-2.6.0 and setup a three node 
centos7 cluster for test.

With all default configurations, Ambari Metrics did not work and I found the 
following from HBase logs.

{noformat}

2017-11-11 15:07:56,478 INFO  
[B.defaultRpcServer.handler=24,queue=0,port=40128] zookeeper.ZooKeeper: 
Initiating client connection, connectString=test3:61181 sessionTimeout=12 
watcher=hconnection-0x23f7d8350x0, quorum=test3:61181, 
baseZNode=/ams-hbase-unsecure
@   
 @at 
org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:129)
at 
org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:128)
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 load configured store engine 
'org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine'
at 
org.apache.hadoop.hbase.regionserver.StoreEngine.create(StoreEngine.java:128)
at org.apache.hadoop.hbase.regionserver.HStore.(HStore.java:271)
at 
org.apache.hadoop.hbase.regionserver.HRegion.instantiateHStore(HRegion.java:4958)
at org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:905)
at org.apache.hadoop.hbase.regionserver.HRegion$1.call(HRegion.java:902)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
... 3 more
Caused by: java.lang.UnsupportedOperationException: Unable to find 
org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine
at 
org.apache.hadoop.hbase.util.ReflectionUtils.instantiateWithCustomCtor(ReflectionUtils.java:36)
at 
org.apache.hadoop.hbase.regionserver.StoreEngine.create(StoreEngine.java:123)
... 10 more
Caused by: java.lang.ClassNotFoundException: 
org.apache.hadoop.hbase.regionserver.DateTieredStoreEngine
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at 
org.apache.hadoop.hbase.util.ReflectionUtils.instantiateWithCustomCtor(ReflectionUtils.java:32)
... 11 more

{noformat}

After adding the following to ams-site.xml. Ambari Metrics work normally. And 
no more Exception found in both collector and hbase logs.

{noformat}

  
timeline.metrics.hbase.aggregate.table.compaction.policy.class
  org.apache.hadoop.hbase.regionserver.DefaultStoreEngine

{noformat}




>From HBASE-19223, Date Tiered Compaction is only available starting in the 1.3 
>release.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-13671) Ambari should check for duplicate config values

[Ted Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-13671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Yu updated AMBARI-13671:

Description: 
Using /#/main/services/HBASE/configs, I was able to save duplicate values for 
hbase.coprocessor.region.classes :

org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint,org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint

Ambari should check for duplicate config values.

  was:
Using /#/main/services/HBASE/configs, I was able to save duplicate values for 
hbase.coprocessor.region.classes :

org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint,org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint


Ambari should check for duplicate config values.


> Ambari should check for duplicate config values
> ---
>
> Key: AMBARI-13671
> URL: https://issues.apache.org/jira/browse/AMBARI-13671
> Project: Ambari
>  Issue Type: Bug
>Reporter: Ted Yu
>
> Using /#/main/services/HBASE/configs, I was able to save duplicate values for 
> hbase.coprocessor.region.classes :
> org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint,org.apache.hadoop.hbase.security.access.SecureBulkLoadEndpoint
> Ambari should check for duplicate config values.



--
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 $

[Ted Yu (JIRA)]

[ 
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 11/11/17 5:02 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-21822) Implement CodeCache related configuration change for HBase master

[Ted Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-21822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Yu updated AMBARI-21822:

Description: 
AMBARI-21326 applied the code cache directive to region server daemons.


This issue is to apply the same fix to hbase master.

  was:
AMBARI-21326 applied the code cache directive to region server daemons.

This issue is to apply the same fix to hbase master.


> Implement CodeCache related configuration change for HBase master
> -
>
> Key: AMBARI-21822
> URL: https://issues.apache.org/jira/browse/AMBARI-21822
> Project: Ambari
>  Issue Type: Task
>Reporter: Ted Yu
>
> AMBARI-21326 applied the code cache directive to region server daemons.
> This issue is to apply the same fix to hbase master.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22338) Add SAM StackFeatures to HDP StackFeatures

[Yolanda M. Davis (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yolanda M. Davis updated AMBARI-22338:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Patch was committed 

> Add SAM StackFeatures to HDP StackFeatures
> --
>
> Key: AMBARI-22338
> URL: https://issues.apache.org/jira/browse/AMBARI-22338
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.6.0
>Reporter: Yolanda M. Davis
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22338.patch
>
>
> {noformat}
> {
> "name": "sam_storage_core_in_registry",
> "description": "Storage core module moved to registry",
> "min_version": "2.6.0.0"
>  }
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-22416) Log Search UI: fixes for filtering form

[Hudson (JIRA)]

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

Hudson commented on AMBARI-22416:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8380 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8380/])
AMBARI-22416 Log Search UI: fixes for filtering form. (ababiichuk) (ababiichuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7c4a7e4c52e00282e5b8b901cef14c143fd3da2b])
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/time-range-picker/time-range-picker.component.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/filters-panel/filters-panel.component.html
* (edit) ambari-logsearch/ambari-logsearch-web/src/app/classes/models/store.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/logs-container/logs-container.component.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/filter-dropdown/filter-dropdown.component.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/logs-list/logs-list.component.spec.ts
* (edit) ambari-logsearch/ambari-logsearch-web/src/app/app.module.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/classes/models/app-state.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/logs-list/logs-list.component.html
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/search-box/search-box.component.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/services/component-generator.service.spec.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/services/logs-container.service.ts
* (edit) ambari-logsearch/ambari-logsearch-web/src/app/classes/models/tab.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/filters-panel/filters-panel.component.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/time-range-picker/time-range-picker.component.html
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/services/logs-container.service.spec.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/filters-panel/filters-panel.component.spec.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/services/component-actions.service.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/timezone-picker/timezone-picker.component.spec.ts
* (delete) ambari-logsearch/ambari-logsearch-web/src/app/classes/models/node.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/dropdown-list/dropdown-list.component.spec.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/logs-container/logs-container.component.spec.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/filter-button/filter-button.component.spec.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/app.component.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/dropdown-button/dropdown-button.component.html
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/filter-dropdown/filter-dropdown.component.spec.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/pagination/pagination.component.html
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/filter-button/filter-button.component.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/log-context/log-context.component.spec.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/services/component-actions.service.spec.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/pagination-controls/pagination-controls.component.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/time-range-picker/time-range-picker.component.spec.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/dropdown-button/dropdown-button.component.spec.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/logs-list/logs-list.component.ts
* (edit) ambari-logsearch/ambari-logsearch-web/src/app/services/utils.service.ts
* (add) 
ambari-logsearch/ambari-logsearch-web/src/app/classes/models/node-item.ts
* (edit) ambari-logsearch/ambari-logsearch-web/src/app/classes/filtering.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/menu-button/menu-button.component.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/services/utils.service.spec.ts
* (delete) 
ambari-logsearch/ambari-logsearch-web/src/app/services/filtering.service.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/dropdown-list/dropdown-list.component.html
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/pagination/pagination.component.ts
* (edit) 
ambari-logsearch/ambari-logsearch-web/src/app/components/dropdown-button/dropdown-button.component.ts
* (edit) 

[jira] [Commented] (AMBARI-22318) repositoryFile entity populating for wrong repository for RU

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-22318:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12897141/AMBARI-22318.patch
  against trunk revision .

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/12652//console

This message is automatically generated.

> repositoryFile entity populating for wrong repository for RU  
> --
>
> Key: AMBARI-22318
> URL: https://issues.apache.org/jira/browse/AMBARI-22318
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22318.patch, AMBARI-22318.v1.patch, 
> AMBARI-22318.v2.preview.patch
>
>
> In populating repositoryFile entity we relating to desired stack version, 
> what i correct for RU, as desired state switched there exactly at upgrade 
> creation time, while for RU we doing it later. 
> Due to entity populating far ahead of real upgrade, for RU it  populated for 
> source repository version instead of target.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-22420) Enable mpack version selection

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-22420:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12897145/AMBARI-22420.patch
  against trunk revision .

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/12651//console

This message is automatically generated.

> Enable mpack version selection
> --
>
> Key: AMBARI-22420
> URL: https://issues.apache.org/jira/browse/AMBARI-22420
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Jason Golieb
>Assignee: Jason Golieb
> Fix For: 3.0.0
>
> Attachments: AMBARI-22420.patch
>
>
> Implement the ability to change mpack version in the available mpacks list.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-22413) Fix tar_archive.py: 1. remove verbosity flags, 2. fix archive_dir() and archive_directory_dereference() methods

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-22413:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12897101/AMBARI-22413-fix-tar-trunk_v1.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/12650//console

This message is automatically generated.

> Fix tar_archive.py: 1. remove verbosity flags, 2. fix archive_dir() and 
> archive_directory_dereference() methods
> ---
>
> Key: AMBARI-22413
> URL: https://issues.apache.org/jira/browse/AMBARI-22413
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
>Priority: Critical
> Attachments: AMBARI-22413-fix-tar-trunk_v1.patch
>
>
> There are two issues with tar_archive.py which caused a HDP upgrade to fail 
> at a customer:
> # The verbose flag (-v) is switched on. This could result in long archival 
> time and timeouts
> # The full path of the files is preserverved in the archive without the 
> leading slash. This results in doubled paths when the archive is expanded. 
> E.g:
> The contents of _/hadoop/falcon/_ directory is archived.
> All files are archived with full path but no leading slash: 
> _hadoop/falcon//_
> After unpacking the unpacked file will look like: 
> _/hadoop/falcon/hadoop/falcon//_.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (AMBARI-22366) POST, GET and UPDATE API for cluster settings. (/clusters/{clusterName}/settings)

[Swapan Shridhar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapan Shridhar resolved AMBARI-22366.
--
Resolution: Fixed

> POST, GET and UPDATE API for cluster settings. 
> (/clusters/{clusterName}/settings)
> -
>
> Key: AMBARI-22366
> URL: https://issues.apache.org/jira/browse/AMBARI-22366
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 3.0.0
>
> Attachments: AMBARI-22366.1.patch, AMBARI-22366.2.patch, 
> AMBARI-22366.3.patch, AMBARI-22366.patch
>
>
> *Background:* AMBARI-22196 did the following : 
>  (1). Refactoring work of moving all cluster related configs/settings in 
> cluster-env to "cluster-settings" files.
>  (2). Implementing READ only API to access *cluster-settings* file 
> *setting(s)* : *http://:/api/v1/cluster_settings/ *
> - This was done to separate cluster related configs from stack related 
> configs.
> *This JIRA implements the following :*
> - POST, GET, UPDATE and DELETE APIs for cluster settings with endpoint : 
>   *http://:/api/v1/clusters/[[clusterName]]/settings*, where 
>-- the cluster settings would be initially read from the above mentioned 
> read-only API : *http://:/api/v1/cluster_settings/*. 
> - Further, added cluster *settings* as a sub-resource of *cluster* resource.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-22366) POST, GET and UPDATE API for cluster settings. (/clusters/{clusterName}/settings)

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar commented on AMBARI-22366:
--

{code:title=branch-feature-AMBARI-14714}
commit 4959206893da4060e66b6ece4cfba5136de79157
Author: Swapan Shridhar 
Date:   Fri Nov 10 14:07:40 2017 -0800

AMBARI-22366. POST, GET and UPDATE API for cluster settings. 
(/clusters/{clusterName}/settings).
{code}

> POST, GET and UPDATE API for cluster settings. 
> (/clusters/{clusterName}/settings)
> -
>
> Key: AMBARI-22366
> URL: https://issues.apache.org/jira/browse/AMBARI-22366
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 3.0.0
>
> Attachments: AMBARI-22366.1.patch, AMBARI-22366.2.patch, 
> AMBARI-22366.3.patch, AMBARI-22366.patch
>
>
> *Background:* AMBARI-22196 did the following : 
>  (1). Refactoring work of moving all cluster related configs/settings in 
> cluster-env to "cluster-settings" files.
>  (2). Implementing READ only API to access *cluster-settings* file 
> *setting(s)* : *http://:/api/v1/cluster_settings/ *
> - This was done to separate cluster related configs from stack related 
> configs.
> *This JIRA implements the following :*
> - POST, GET, UPDATE and DELETE APIs for cluster settings with endpoint : 
>   *http://:/api/v1/clusters/[[clusterName]]/settings*, where 
>-- the cluster settings would be initially read from the above mentioned 
> read-only API : *http://:/api/v1/cluster_settings/*. 
> - Further, added cluster *settings* as a sub-resource of *cluster* resource.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-22366) POST, GET and UPDATE API for cluster settings. (/clusters/{clusterName}/settings)

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar commented on AMBARI-22366:
--

[^AMBARI-22366.3.patch] rebased patch.

> POST, GET and UPDATE API for cluster settings. 
> (/clusters/{clusterName}/settings)
> -
>
> Key: AMBARI-22366
> URL: https://issues.apache.org/jira/browse/AMBARI-22366
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 3.0.0
>
> Attachments: AMBARI-22366.1.patch, AMBARI-22366.2.patch, 
> AMBARI-22366.3.patch, AMBARI-22366.patch
>
>
> *Background:* AMBARI-22196 did the following : 
>  (1). Refactoring work of moving all cluster related configs/settings in 
> cluster-env to "cluster-settings" files.
>  (2). Implementing READ only API to access *cluster-settings* file 
> *setting(s)* : *http://:/api/v1/cluster_settings/ *
> - This was done to separate cluster related configs from stack related 
> configs.
> *This JIRA implements the following :*
> - POST, GET, UPDATE and DELETE APIs for cluster settings with endpoint : 
>   *http://:/api/v1/clusters/[[clusterName]]/settings*, where 
>-- the cluster settings would be initially read from the above mentioned 
> read-only API : *http://:/api/v1/cluster_settings/*. 
> - Further, added cluster *settings* as a sub-resource of *cluster* resource.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-22355) New endpoint at ServiceLevel for configurations - POST, GET

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar commented on AMBARI-22355:
--

+1 for patch [^AMBARI-22355_addendum.patch]
CC [~mradhakrishnan]

> New endpoint at ServiceLevel for configurations - POST, GET
> ---
>
> Key: AMBARI-22355
> URL: https://issues.apache.org/jira/browse/AMBARI-22355
> Project: Ambari
>  Issue Type: Bug
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 3.0.0
>
> Attachments: AMBARI-22355_addendum.patch
>
>
> In a multi service instance scenario we could have more than one service 
> instance running in a cluster. 
> Two Zookeepers (ZK1, ZK2) running in a cluster. 
> We need to distinguish between configs for ZK1 and for ZK2 
> To support multi instance scenario, the configurations API endpoint will be 
> moved from cluster-level to service-level
> New API Endpoint
> api/v2/clusters//servicegroups//services//configurations



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-22355) New endpoint at ServiceLevel for configurations - POST, GET

[Madhuvanthi Radhakrishnan (JIRA)]

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

Madhuvanthi Radhakrishnan commented on AMBARI-22355:


[~swapanshridhar], [~jluniya],
Please review the attached patch. 
Due to addition of a new column service_id in clusterconfig table, it 
references the id in clusterservices. But there is no unique key constraint 
defined on the id column in clusterservices. Hence added it. Also, moved 
clusterconfig CREATE ddl to occur after clusterservices due to the foreign key 
reference.

> New endpoint at ServiceLevel for configurations - POST, GET
> ---
>
> Key: AMBARI-22355
> URL: https://issues.apache.org/jira/browse/AMBARI-22355
> Project: Ambari
>  Issue Type: Bug
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 3.0.0
>
> Attachments: AMBARI-22355_addendum.patch
>
>
> In a multi service instance scenario we could have more than one service 
> instance running in a cluster. 
> Two Zookeepers (ZK1, ZK2) running in a cluster. 
> We need to distinguish between configs for ZK1 and for ZK2 
> To support multi instance scenario, the configurations API endpoint will be 
> moved from cluster-level to service-level
> New API Endpoint
> api/v2/clusters//servicegroups//services//configurations



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22355) New endpoint at ServiceLevel for configurations - POST, GET

[Madhuvanthi Radhakrishnan (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Madhuvanthi Radhakrishnan updated AMBARI-22355:
---
Attachment: AMBARI-22355_addendum.patch

> New endpoint at ServiceLevel for configurations - POST, GET
> ---
>
> Key: AMBARI-22355
> URL: https://issues.apache.org/jira/browse/AMBARI-22355
> Project: Ambari
>  Issue Type: Bug
>Reporter: Madhuvanthi Radhakrishnan
>Assignee: Madhuvanthi Radhakrishnan
> Fix For: 3.0.0
>
> Attachments: AMBARI-22355_addendum.patch
>
>
> In a multi service instance scenario we could have more than one service 
> instance running in a cluster. 
> Two Zookeepers (ZK1, ZK2) running in a cluster. 
> We need to distinguish between configs for ZK1 and for ZK2 
> To support multi instance scenario, the configurations API endpoint will be 
> moved from cluster-level to service-level
> New API Endpoint
> api/v2/clusters//servicegroups//services//configurations



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-22417) Ambari checks fail with FIPS mode is activated on the OS

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-22417:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12897110/AMBARI-22417_branch-2.6_01.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in .

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/12649//console

This message is automatically generated.

> Ambari checks fail with FIPS mode is activated on the OS
> 
>
> Key: AMBARI-22417
> URL: https://issues.apache.org/jira/browse/AMBARI-22417
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent, ambari-server
>Affects Versions: 2.5.1
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22417_branch-2.6_01.patch, 
> AMBARI-22417_trunk_01.patch
>
>
> Ambari checks fail with FIPS mode is activated on the OS (Rhel7). FIPS mode 
> disables weak ciphers (such as MD5). 
> Ambari code is doing 
> {code}
> ccache_file_name = _md5("
> {0}|{1}".format(principal, keytab)).hexdigest(). MD5 is disabled on the OS 
> (RHEL7) so ambari throws errors.
> {code}
> - All service checks fail, Ranger KMS start fails via ambari. 
> - However all the services are actually running and fine. 
> - Also Ranger KMS succesfully started from command Line
> Here is the stack trace from Ambari
> {code}
> service_check
> params.kinit_path_local, False, None, params.smoke_user)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/curl_krb_request.py",
>  line 109, in curl_krb_request
> ccache_file_name = _md5("{0}
> |
> {1}
> ".format(principal, keytab)).hexdigest()
> ValueError: error:060800A3:digital envelope 
> routines:EVP_DigestInit_ex:disabled for fips
> {code}
> Fix: 
> MD5 is disabled on the OS, Code needs to be updated to use SHA?
> This is required when FIPS mode is enabled on the RHEL OS



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22345) Add service dependencies

[Vitaly Brodetskyi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vitaly Brodetskyi updated AMBARI-22345:
---
Attachment: AMBARI-22345_part2.patch

> Add service dependencies
> 
>
> Key: AMBARI-22345
> URL: https://issues.apache.org/jira/browse/AMBARI-22345
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
> Fix For: 3.0.0
>
> Attachments: AMBARI-22345.patch, AMBARI-22345_part2.patch
>
>
> API:
> {code}
> POST 
> http://SERVER:8080/api/v2/clusters/{cluster-id}/servicegroups/{sgId}/services
> Request
> {
>   "ServiceInfo" : {
> "service_name" : "{service-name}",
> "service_display_name" : "{service-display-name}",
> "service_version" : "{service-version}",
> "stack_id" : "{stack-id}",
> "hosting_platform" : "Ambari|Yarn"
>   }
>   "dependencies" : [
>   {
> "ServiceInfo" : {
>   "service_id" : "{dependent-service-id}",
>   "cluster_id" : "{dependent-cluster-id}",
>   "service_group_id" : "{dependent-service-group-id}",
>}
>   }
> ]
> }
> {code}
> DB:
> Add table {{servicedependencies}}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-22366) POST, GET and UPDATE API for cluster settings. (/clusters/{clusterName}/settings)

[Swapan Shridhar (JIRA)]

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

Swapan Shridhar commented on AMBARI-22366:
--

[^AMBARI-22366.2.patch] fixes review comments.

> POST, GET and UPDATE API for cluster settings. 
> (/clusters/{clusterName}/settings)
> -
>
> Key: AMBARI-22366
> URL: https://issues.apache.org/jira/browse/AMBARI-22366
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 3.0.0
>
> Attachments: AMBARI-22366.1.patch, AMBARI-22366.2.patch, 
> AMBARI-22366.3.patch, AMBARI-22366.patch
>
>
> *Background:* AMBARI-22196 did the following : 
>  (1). Refactoring work of moving all cluster related configs/settings in 
> cluster-env to "cluster-settings" files.
>  (2). Implementing READ only API to access *cluster-settings* file 
> *setting(s)* : *http://:/api/v1/cluster_settings/ *
> - This was done to separate cluster related configs from stack related 
> configs.
> *This JIRA implements the following :*
> - POST, GET, UPDATE and DELETE APIs for cluster settings with endpoint : 
>   *http://:/api/v1/clusters/[[clusterName]]/settings*, where 
>-- the cluster settings would be initially read from the above mentioned 
> read-only API : *http://:/api/v1/cluster_settings/*. 
> - Further, added cluster *settings* as a sub-resource of *cluster* resource.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22366) POST, GET and UPDATE API for cluster settings. (/clusters/{clusterName}/settings)

[Swapan Shridhar (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Swapan Shridhar updated AMBARI-22366:
-
Attachment: AMBARI-22366.2.patch
AMBARI-22366.3.patch

> POST, GET and UPDATE API for cluster settings. 
> (/clusters/{clusterName}/settings)
> -
>
> Key: AMBARI-22366
> URL: https://issues.apache.org/jira/browse/AMBARI-22366
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Swapan Shridhar
>Assignee: Swapan Shridhar
> Fix For: 3.0.0
>
> Attachments: AMBARI-22366.1.patch, AMBARI-22366.2.patch, 
> AMBARI-22366.3.patch, AMBARI-22366.patch
>
>
> *Background:* AMBARI-22196 did the following : 
>  (1). Refactoring work of moving all cluster related configs/settings in 
> cluster-env to "cluster-settings" files.
>  (2). Implementing READ only API to access *cluster-settings* file 
> *setting(s)* : *http://:/api/v1/cluster_settings/ *
> - This was done to separate cluster related configs from stack related 
> configs.
> *This JIRA implements the following :*
> - POST, GET, UPDATE and DELETE APIs for cluster settings with endpoint : 
>   *http://:/api/v1/clusters/[[clusterName]]/settings*, where 
>-- the cluster settings would be initially read from the above mentioned 
> read-only API : *http://:/api/v1/cluster_settings/*. 
> - Further, added cluster *settings* as a sub-resource of *cluster* resource.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22416) Log Search UI: fixes for filtering form

[Andrii Babiichuk (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrii Babiichuk updated AMBARI-22416:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk

> Log Search UI: fixes for filtering form
> ---
>
> Key: AMBARI-22416
> URL: https://issues.apache.org/jira/browse/AMBARI-22416
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22416.patch
>
>
> # Checkboxes in multiselect, labels of dropdown filter buttons etc. should 
> pick up currently selected value even if it's set from outside the form
> # All the tabs should have their own isolated filtering options, so that 
> filters application on one tab doesn't affect other tab



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AMBARI-22421) Ambari upgrade is not idempotent if it fails with service not found error

[amarnath reddy pappu (JIRA)]

amarnath reddy pappu created AMBARI-22421:
-

 Summary: Ambari upgrade is not idempotent if it fails with service 
not found error
 Key: AMBARI-22421
 URL: https://issues.apache.org/jira/browse/AMBARI-22421
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.6.0
Reporter: amarnath reddy pappu


If Upgrade is failed with below exception and try to upgrade from that point 
after correcting the service not found issue.


{noformat}
06 Nov 2017 04:31:26,823 ERROR [main] SchemaUpgradeHelper:233 - Upgrade failed. 
org.apache.ambari.server.ServiceNotFoundException: Service not found, 
clusterName=, serviceName=NIFI
at 
org.apache.ambari.server.state.cluster.ClusterImpl.getService(ClusterImpl.java:864)
at 
org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1240)
at 
org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
at 
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938)
at 
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:231)
at 
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
06 Nov 2017 04:31:26,826 ERROR [main] SchemaUpgradeHelper:437 - Exception 
occurred during upgrade, failed
org.apache.ambari.server.AmbariException: Service not found, 
clusterName=usldwdevhdp, serviceName=NIFI
at 
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:234)
at 
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
Caused by: org.apache.ambari.server.ServiceNotFoundException: Service not 
found, clusterName=usldwdevhdp, serviceName=NIFI
at 
org.apache.ambari.server.state.cluster.ClusterImpl.getService(ClusterImpl.java:864)
at 
org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1240)
at 
org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
at 
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938)
at 
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:231)
{noformat}


Upgrade fails with below exception

{noformat}
INFO: Updating Ambari Server properties in ambari.properties ...
WARNING: Can not find ambari.properties.rpmsave file from previous version, 
skipping import of settings
INFO: Updating Ambari Server properties in ambari-env.sh ...
INFO: Can not find ambari-env.sh.rpmsave file from previous version, skipping 
restore of environment settings. ambari-env.sh may not include any user 
customization.
INFO: Fixing database objects owner
Ambari Server configured for MySQL. Confirm you have made a backup of the 
Ambari Server database [y/n] (y)?
INFO: Upgrading database schema
INFO: Return code from schema upgrade command, retcode = 1
ERROR: Error executing schema upgrade, please check the server logs.
ERROR: Error output from schema upgrade command:
ERROR: Exception in thread "main" org.apache.ambari.server.AmbariException: 
cluster_version table does not contain repo_version_id column
at 
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:203)
at 
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:418)
Caused by: java.lang.IllegalArgumentException: cluster_version table does not 
contain repo_version_id column
at 
org.apache.ambari.server.orm.DBAccessorImpl.getIntColumnValues(DBAccessorImpl.java:1536)
at 
org.apache.ambari.server.upgrade.UpgradeCatalog260.getCurrentVersionID(UpgradeCatalog260.java:507)
at 
org.apache.ambari.server.upgrade.UpgradeCatalog260.executeDDLUpdates(UpgradeCatalog260.java:194)
at 
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:923)
at 
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:200)
... 1 more


ERROR: Ambari server upgrade failed. Please look at 
/var/log/ambari-server/ambari-server.log, for more details.
ERROR: Exiting with exit code 11.
REASON: Schema upgrade failed.
{noformat}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22420) Enable mpack version selection

[Jason Golieb (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Golieb updated AMBARI-22420:
--
Status: Patch Available  (was: In Progress)

> Enable mpack version selection
> --
>
> Key: AMBARI-22420
> URL: https://issues.apache.org/jira/browse/AMBARI-22420
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Jason Golieb
>Assignee: Jason Golieb
> Fix For: 3.0.0
>
> Attachments: AMBARI-22420.patch
>
>
> Implement the ability to change mpack version in the available mpacks list.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22420) Enable mpack version selection

[Jason Golieb (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Golieb updated AMBARI-22420:
--
Attachment: AMBARI-22420.patch

> Enable mpack version selection
> --
>
> Key: AMBARI-22420
> URL: https://issues.apache.org/jira/browse/AMBARI-22420
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Jason Golieb
>Assignee: Jason Golieb
> Fix For: 3.0.0
>
> Attachments: AMBARI-22420.patch
>
>
> Implement the ability to change mpack version in the available mpacks list.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AMBARI-22420) Enable mpack version selection

[Jason Golieb (JIRA)]

Jason Golieb created AMBARI-22420:
-

 Summary: Enable mpack version selection
 Key: AMBARI-22420
 URL: https://issues.apache.org/jira/browse/AMBARI-22420
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 3.0.0
Reporter: Jason Golieb
Assignee: Jason Golieb
 Fix For: 3.0.0


Implement the ability to change mpack version in the available mpacks list.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AMBARI-22419) Ambari upgrade failed

[amarnath reddy pappu (JIRA)]

amarnath reddy pappu created AMBARI-22419:
-

 Summary: Ambari upgrade failed
 Key: AMBARI-22419
 URL: https://issues.apache.org/jira/browse/AMBARI-22419
 Project: Ambari
  Issue Type: Bug
  Components: ambari-sever
Affects Versions: 2.6.0
Reporter: amarnath reddy pappu


Ambari upgrade would fail during the DMLStatements execution if there is no 
service definition in the stacks.
For example: Customer database has entry for GANGLIA in alert_definition table 
but there is no stack definition - hence its getting failed with below 
exception.

{noformat}
org.apache.ambari.server.AmbariException: Service not found, 
clusterName=comcastdrcluster, serviceName=GANGLIA 
at 
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:234)
 
at 
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:424)
 
Caused by: org.apache.ambari.server.ServiceNotFoundException: Service not 
found, clusterName=comcastdrcluster, serviceName=GANGLIA 
at 
org.apache.ambari.server.state.cluster.ClusterImpl.getService(ClusterImpl.java:864)
 
at 
org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1240)
 
at 
org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
 
at 
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:938)
 
at 
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:231)
 
... 1 more
{noformat}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-22416) Log Search UI: fixes for filtering form

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-22416:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12897107/AMBARI-22416.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/12648//console

This message is automatically generated.

> Log Search UI: fixes for filtering form
> ---
>
> Key: AMBARI-22416
> URL: https://issues.apache.org/jira/browse/AMBARI-22416
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22416.patch
>
>
> # Checkboxes in multiselect, labels of dropdown filter buttons etc. should 
> pick up currently selected value even if it's set from outside the form
> # All the tabs should have their own isolated filtering options, so that 
> filters application on one tab doesn't affect other tab



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22318) repositoryFile entity populating for wrong repository for RU

[Dmytro Grinenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmytro Grinenko updated AMBARI-22318:
-
Attachment: AMBARI-22318.patch

> repositoryFile entity populating for wrong repository for RU  
> --
>
> Key: AMBARI-22318
> URL: https://issues.apache.org/jira/browse/AMBARI-22318
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22318.patch, AMBARI-22318.v1.patch, 
> AMBARI-22318.v2.preview.patch
>
>
> In populating repositoryFile entity we relating to desired stack version, 
> what i correct for RU, as desired state switched there exactly at upgrade 
> creation time, while for RU we doing it later. 
> Due to entity populating far ahead of real upgrade, for RU it  populated for 
> source repository version instead of target.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22318) repositoryFile entity populating for wrong repository for RU

[Dmytro Grinenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmytro Grinenko updated AMBARI-22318:
-
Attachment: (was: AMBARI-22318.patch)

> repositoryFile entity populating for wrong repository for RU  
> --
>
> Key: AMBARI-22318
> URL: https://issues.apache.org/jira/browse/AMBARI-22318
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22318.patch, AMBARI-22318.v1.patch, 
> AMBARI-22318.v2.preview.patch
>
>
> In populating repositoryFile entity we relating to desired stack version, 
> what i correct for RU, as desired state switched there exactly at upgrade 
> creation time, while for RU we doing it later. 
> Due to entity populating far ahead of real upgrade, for RU it  populated for 
> source repository version instead of target.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22318) repositoryFile entity populating for wrong repository for RU

[Dmytro Grinenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmytro Grinenko updated AMBARI-22318:
-
Attachment: AMBARI-22318.patch

> repositoryFile entity populating for wrong repository for RU  
> --
>
> Key: AMBARI-22318
> URL: https://issues.apache.org/jira/browse/AMBARI-22318
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22318.patch, AMBARI-22318.v1.patch, 
> AMBARI-22318.v2.preview.patch
>
>
> In populating repositoryFile entity we relating to desired stack version, 
> what i correct for RU, as desired state switched there exactly at upgrade 
> creation time, while for RU we doing it later. 
> Due to entity populating far ahead of real upgrade, for RU it  populated for 
> source repository version instead of target.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22318) repositoryFile entity populating for wrong repository for RU

[Dmytro Grinenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmytro Grinenko updated AMBARI-22318:
-
Attachment: (was: AMBARI-22318.patch)

> repositoryFile entity populating for wrong repository for RU  
> --
>
> Key: AMBARI-22318
> URL: https://issues.apache.org/jira/browse/AMBARI-22318
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22318.v1.patch, AMBARI-22318.v2.preview.patch
>
>
> In populating repositoryFile entity we relating to desired stack version, 
> what i correct for RU, as desired state switched there exactly at upgrade 
> creation time, while for RU we doing it later. 
> Due to entity populating far ahead of real upgrade, for RU it  populated for 
> source repository version instead of target.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-22411) Restart all required services failed when running cluster with several patch upgrades applied

[Hudson (JIRA)]

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

Hudson commented on AMBARI-22411:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8379 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8379/])
AMBARI-22411. Restart all required services failed when running cluster (ncole: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=068d82f700432cf5cfa75d20924443e998d8fe87])
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerImplTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_packages.json
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java


> Restart all required services failed when running cluster with several patch 
> upgrades applied
> -
>
> Key: AMBARI-22411
> URL: https://issues.apache.org/jira/browse/AMBARI-22411
> Project: Ambari
>  Issue Type: Bug
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22411.patch
>
>
> - Deploy Ambari 2.6 with  HDP 2.6.1
> - Select Oozie and rest related to oozie services
> - make 3 patch upgrades (xml files would be attached)
> - before last patch upgrade enable LZO.
> - Select actions below services list and press restart all related



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22318) repositoryFile entity populating for wrong repository for RU

[Dmytro Grinenko (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmytro Grinenko updated AMBARI-22318:
-
Attachment: AMBARI-22318.patch

> repositoryFile entity populating for wrong repository for RU  
> --
>
> Key: AMBARI-22318
> URL: https://issues.apache.org/jira/browse/AMBARI-22318
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22318.patch, AMBARI-22318.v1.patch, 
> AMBARI-22318.v2.preview.patch
>
>
> In populating repositoryFile entity we relating to desired stack version, 
> what i correct for RU, as desired state switched there exactly at upgrade 
> creation time, while for RU we doing it later. 
> Due to entity populating far ahead of real upgrade, for RU it  populated for 
> source repository version instead of target.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-22411) Restart all required services failed when running cluster with several patch upgrades applied

[Hudson (JIRA)]

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

Hudson commented on AMBARI-22411:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #445 (See 
[https://builds.apache.org/job/Ambari-branch-2.6/445/])
AMBARI-22411. Restart all required services failed when running cluster (ncole: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=23cd02e59f01b52817884a0572ad34edfe5b7167])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.0.6/properties/stack_packages.json
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerImplTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java


> Restart all required services failed when running cluster with several patch 
> upgrades applied
> -
>
> Key: AMBARI-22411
> URL: https://issues.apache.org/jira/browse/AMBARI-22411
> Project: Ambari
>  Issue Type: Bug
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22411.patch
>
>
> - Deploy Ambari 2.6 with  HDP 2.6.1
> - Select Oozie and rest related to oozie services
> - make 3 patch upgrades (xml files would be attached)
> - before last patch upgrade enable LZO.
> - Select actions below services list and press restart all related



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-22412) Remove IPA integration from experimental status

[Hudson (JIRA)]

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

Hudson commented on AMBARI-22412:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8378 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8378/])
AMBARI-22412. Remove IPA integration from experimental status (rlevas) (rlevas: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=22b2d55f646ebd965834e43536056c5f229e236e])
* (edit) ambari-web/app/config.js
* (edit) ambari-web/app/controllers/main/admin/kerberos/step1_controller.js
* (edit) ambari-web/app/messages.js
* (edit) 
ambari-web/test/controllers/main/admin/kerberos/step1_controller_test.js


> Remove IPA integration from experimental status
> ---
>
> Key: AMBARI-22412
> URL: https://issues.apache.org/jira/browse/AMBARI-22412
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22412_trunk_01.patch
>
>
> Remove IPA integration from experimental status so that users can select 
> FreeIPA when enabling Kerberos via the Enable Kerberos Wizard without having 
> to explicitly enable it via the Experimental page. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-22415) Blueprint deploys failing with missing smoke user keytab file

[Hudson (JIRA)]

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

Hudson commented on AMBARI-22415:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8378 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8378/])
AMBARI-22415. Blueprint deploys failing with missing smoke user keytab 
(echekanskiy: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ec02a14c02529ec7fec647e6fed7c8c401f10e6d])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/serveraction/kerberos/CreateKeytabFilesServerAction.java


> Blueprint deploys failing with missing smoke user keytab file
> -
>
> Key: AMBARI-22415
> URL: https://issues.apache.org/jira/browse/AMBARI-22415
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Eugene Chekanskiy
>Assignee: Eugene Chekanskiy
> Fix For: 3.0.0
>
> Attachments: AMBARI-22415.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AMBARI-22418) Make Ambari configuration API consistent with existing API.

[Robert Levas (JIRA)]

Robert Levas created AMBARI-22418:
-

 Summary: Make Ambari configuration API consistent with existing 
API.
 Key: AMBARI-22418
 URL: https://issues.apache.org/jira/browse/AMBARI-22418
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 3.0.0
Reporter: Robert Levas
Assignee: Robert Levas
 Fix For: 3.0.0


Make Ambari configuration API consistent with existing API. 

The current API entry point (as of AMBARI-21307) is {{/api/v1/ambariconfigs}}. 
This should be more inline with the existing entry point for Ambari server 
related data...  {{/api/v1/services/AMBARI/components/AMBARI_SERVER}}.  

The new API entry point for Ambari server related configuration data should be 
{{/api/v1/services/AMBARI/components/AMBARI_SERVER/configurations}}.






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22411) Restart all required services failed when running cluster with several patch upgrades applied

[Nate Cole (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nate Cole updated AMBARI-22411:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Restart all required services failed when running cluster with several patch 
> upgrades applied
> -
>
> Key: AMBARI-22411
> URL: https://issues.apache.org/jira/browse/AMBARI-22411
> Project: Ambari
>  Issue Type: Bug
>Reporter: Nate Cole
>Assignee: Nate Cole
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22411.patch
>
>
> - Deploy Ambari 2.6 with  HDP 2.6.1
> - Select Oozie and rest related to oozie services
> - make 3 patch upgrades (xml files would be attached)
> - before last patch upgrade enable LZO.
> - Select actions below services list and press restart all related



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22417) Ambari checks fail with FIPS mode is activated on the OS

[Robert Levas (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Levas updated AMBARI-22417:
--
Status: Patch Available  (was: In Progress)

> Ambari checks fail with FIPS mode is activated on the OS
> 
>
> Key: AMBARI-22417
> URL: https://issues.apache.org/jira/browse/AMBARI-22417
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent, ambari-server
>Affects Versions: 2.5.1
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22417_branch-2.6_01.patch, 
> AMBARI-22417_trunk_01.patch
>
>
> Ambari checks fail with FIPS mode is activated on the OS (Rhel7). FIPS mode 
> disables weak ciphers (such as MD5). 
> Ambari code is doing 
> {code}
> ccache_file_name = _md5("
> {0}|{1}".format(principal, keytab)).hexdigest(). MD5 is disabled on the OS 
> (RHEL7) so ambari throws errors.
> {code}
> - All service checks fail, Ranger KMS start fails via ambari. 
> - However all the services are actually running and fine. 
> - Also Ranger KMS succesfully started from command Line
> Here is the stack trace from Ambari
> {code}
> service_check
> params.kinit_path_local, False, None, params.smoke_user)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/curl_krb_request.py",
>  line 109, in curl_krb_request
> ccache_file_name = _md5("{0}
> |
> {1}
> ".format(principal, keytab)).hexdigest()
> ValueError: error:060800A3:digital envelope 
> routines:EVP_DigestInit_ex:disabled for fips
> {code}
> Fix: 
> MD5 is disabled on the OS, Code needs to be updated to use SHA?
> This is required when FIPS mode is enabled on the RHEL OS



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22417) Ambari checks fail with FIPS mode is activated on the OS

[Robert Levas (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Levas updated AMBARI-22417:
--
Attachment: AMBARI-22417_branch-2.6_01.patch
AMBARI-22417_trunk_01.patch

> Ambari checks fail with FIPS mode is activated on the OS
> 
>
> Key: AMBARI-22417
> URL: https://issues.apache.org/jira/browse/AMBARI-22417
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent, ambari-server
>Affects Versions: 2.5.1
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 2.6.1
>
> Attachments: AMBARI-22417_branch-2.6_01.patch, 
> AMBARI-22417_trunk_01.patch
>
>
> Ambari checks fail with FIPS mode is activated on the OS (Rhel7). FIPS mode 
> disables weak ciphers (such as MD5). 
> Ambari code is doing 
> {code}
> ccache_file_name = _md5("
> {0}|{1}".format(principal, keytab)).hexdigest(). MD5 is disabled on the OS 
> (RHEL7) so ambari throws errors.
> {code}
> - All service checks fail, Ranger KMS start fails via ambari. 
> - However all the services are actually running and fine. 
> - Also Ranger KMS succesfully started from command Line
> Here is the stack trace from Ambari
> {code}
> service_check
> params.kinit_path_local, False, None, params.smoke_user)
> File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/functions/curl_krb_request.py",
>  line 109, in curl_krb_request
> ccache_file_name = _md5("{0}
> |
> {1}
> ".format(principal, keytab)).hexdigest()
> ValueError: error:060800A3:digital envelope 
> routines:EVP_DigestInit_ex:disabled for fips
> {code}
> Fix: 
> MD5 is disabled on the OS, Code needs to be updated to use SHA?
> This is required when FIPS mode is enabled on the RHEL OS



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22415) Blueprint deploys failing with missing smoke user keytab file

[Eugene Chekanskiy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eugene Chekanskiy updated AMBARI-22415:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Blueprint deploys failing with missing smoke user keytab file
> -
>
> Key: AMBARI-22415
> URL: https://issues.apache.org/jira/browse/AMBARI-22415
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Eugene Chekanskiy
>Assignee: Eugene Chekanskiy
> Fix For: 3.0.0
>
> Attachments: AMBARI-22415.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-22415) Blueprint deploys failing with missing smoke user keytab file

[Eugene Chekanskiy (JIRA)]

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

Eugene Chekanskiy commented on AMBARI-22415:


22b2d55f64..ec02a14c02  trunk -> trunk


> Blueprint deploys failing with missing smoke user keytab file
> -
>
> Key: AMBARI-22415
> URL: https://issues.apache.org/jira/browse/AMBARI-22415
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Eugene Chekanskiy
>Assignee: Eugene Chekanskiy
> Fix For: 3.0.0
>
> Attachments: AMBARI-22415.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AMBARI-22417) Ambari checks fail with FIPS mode is activated on the OS

[Robert Levas (JIRA)]

Robert Levas created AMBARI-22417:
-

 Summary: Ambari checks fail with FIPS mode is activated on the OS
 Key: AMBARI-22417
 URL: https://issues.apache.org/jira/browse/AMBARI-22417
 Project: Ambari
  Issue Type: Bug
  Components: ambari-agent, ambari-server
Affects Versions: 2.5.1
Reporter: Robert Levas
Assignee: Robert Levas
Priority: Critical
 Fix For: 2.6.1


Ambari checks fail with FIPS mode is activated on the OS (Rhel7). FIPS mode 
disables weak ciphers (such as MD5). 
Ambari code is doing 

{code}
ccache_file_name = _md5("
{0}|{1}".format(principal, keytab)).hexdigest(). MD5 is disabled on the OS 
(RHEL7) so ambari throws errors.
{code}

- All service checks fail, Ranger KMS start fails via ambari. 
- However all the services are actually running and fine. 

- Also Ranger KMS succesfully started from command Line

Here is the stack trace from Ambari

{code}
service_check
params.kinit_path_local, False, None, params.smoke_user)
File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/curl_krb_request.py",
 line 109, in curl_krb_request
ccache_file_name = _md5("{0}
|
{1}
".format(principal, keytab)).hexdigest()
ValueError: error:060800A3:digital envelope routines:EVP_DigestInit_ex:disabled 
for fips
{code}

Fix: 
MD5 is disabled on the OS, Code needs to be updated to use SHA?

This is required when FIPS mode is enabled on the RHEL OS




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22416) Log Search UI: fixes for filtering form

[Andrii Babiichuk (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrii Babiichuk updated AMBARI-22416:
--
Status: Patch Available  (was: Open)

> Log Search UI: fixes for filtering form
> ---
>
> Key: AMBARI-22416
> URL: https://issues.apache.org/jira/browse/AMBARI-22416
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22416.patch
>
>
> # Checkboxes in multiselect, labels of dropdown filter buttons etc. should 
> pick up currently selected value even if it's set from outside the form
> # All the tabs should have their own isolated filtering options, so that 
> filters application on one tab doesn't affect other tab



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22416) Log Search UI: fixes for filtering form

[Andrii Babiichuk (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrii Babiichuk updated AMBARI-22416:
--
Attachment: AMBARI-22416.patch

> Log Search UI: fixes for filtering form
> ---
>
> Key: AMBARI-22416
> URL: https://issues.apache.org/jira/browse/AMBARI-22416
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-22416.patch
>
>
> # Checkboxes in multiselect, labels of dropdown filter buttons etc. should 
> pick up currently selected value even if it's set from outside the form
> # All the tabs should have their own isolated filtering options, so that 
> filters application on one tab doesn't affect other tab



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AMBARI-22416) Log Search UI: fixes for filtering form

[Andrii Babiichuk (JIRA)]

Andrii Babiichuk created AMBARI-22416:
-

 Summary: Log Search UI: fixes for filtering form
 Key: AMBARI-22416
 URL: https://issues.apache.org/jira/browse/AMBARI-22416
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch
Affects Versions: 3.0.0
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
 Fix For: 3.0.0


# Checkboxes in multiselect, labels of dropdown filter buttons etc. should pick 
up currently selected value even if it's set from outside the form
# All the tabs should have their own isolated filtering options, so that 
filters application on one tab doesn't affect other tab



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22412) Remove IPA integration from experimental status

[Robert Levas (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Levas updated AMBARI-22412:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk
{noformat}
commit 22b2d55f646ebd965834e43536056c5f229e236e
Author: Robert Levas 
Date:   Fri Nov 10 10:46:01 2017 -0500
{noformat}


> Remove IPA integration from experimental status
> ---
>
> Key: AMBARI-22412
> URL: https://issues.apache.org/jira/browse/AMBARI-22412
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22412_trunk_01.patch
>
>
> Remove IPA integration from experimental status so that users can select 
> FreeIPA when enabling Kerberos via the Enable Kerberos Wizard without having 
> to explicitly enable it via the Experimental page. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22413) Fix tar_archive.py: 1. remove verbosity flags, 2. fix archive_dir() and archive_directory_dereference() methods

[JIRA]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Balázs Bence Sári updated AMBARI-22413:
---
Attachment: AMBARI-22413-fix-tar-trunk_v1.patch

> Fix tar_archive.py: 1. remove verbosity flags, 2. fix archive_dir() and 
> archive_directory_dereference() methods
> ---
>
> Key: AMBARI-22413
> URL: https://issues.apache.org/jira/browse/AMBARI-22413
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
>Priority: Critical
> Attachments: AMBARI-22413-fix-tar-trunk_v1.patch
>
>
> There are two issues with tar_archive.py which caused a HDP upgrade to fail 
> at a customer:
> # The verbose flag (-v) is switched on. This could result in long archival 
> time and timeouts
> # The full path of the files is preserverved in the archive without the 
> leading slash. This results in doubled paths when the archive is expanded. 
> E.g:
> The contents of _/hadoop/falcon/_ directory is archived.
> All files are archived with full path but no leading slash: 
> _hadoop/falcon//_
> After unpacking the unpacked file will look like: 
> _/hadoop/falcon/hadoop/falcon//_.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22413) Fix tar_archive.py: 1. remove verbosity flags, 2. fix archive_dir() and archive_directory_dereference() methods

[JIRA]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Balázs Bence Sári updated AMBARI-22413:
---
Status: Patch Available  (was: In Progress)

> Fix tar_archive.py: 1. remove verbosity flags, 2. fix archive_dir() and 
> archive_directory_dereference() methods
> ---
>
> Key: AMBARI-22413
> URL: https://issues.apache.org/jira/browse/AMBARI-22413
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
>Priority: Critical
> Attachments: AMBARI-22413-fix-tar-trunk_v1.patch
>
>
> There are two issues with tar_archive.py which caused a HDP upgrade to fail 
> at a customer:
> # The verbose flag (-v) is switched on. This could result in long archival 
> time and timeouts
> # The full path of the files is preserverved in the archive without the 
> leading slash. This results in doubled paths when the archive is expanded. 
> E.g:
> The contents of _/hadoop/falcon/_ directory is archived.
> All files are archived with full path but no leading slash: 
> _hadoop/falcon//_
> After unpacking the unpacked file will look like: 
> _/hadoop/falcon/hadoop/falcon//_.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (AMBARI-22412) Remove IPA integration from experimental status

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-22412:


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12897064/AMBARI-22412_trunk_01.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/12647//console

This message is automatically generated.

> Remove IPA integration from experimental status
> ---
>
> Key: AMBARI-22412
> URL: https://issues.apache.org/jira/browse/AMBARI-22412
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22412_trunk_01.patch
>
>
> Remove IPA integration from experimental status so that users can select 
> FreeIPA when enabling Kerberos via the Enable Kerberos Wizard without having 
> to explicitly enable it via the Experimental page. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22415) Blueprint deploys failing with missing smoke user keytab file

[Eugene Chekanskiy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eugene Chekanskiy updated AMBARI-22415:
---
Attachment: AMBARI-22415.patch

> Blueprint deploys failing with missing smoke user keytab file
> -
>
> Key: AMBARI-22415
> URL: https://issues.apache.org/jira/browse/AMBARI-22415
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Eugene Chekanskiy
>Assignee: Eugene Chekanskiy
> Fix For: 3.0.0
>
> Attachments: AMBARI-22415.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22415) Blueprint deploys failing with missing smoke user keytab file

[Eugene Chekanskiy (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eugene Chekanskiy updated AMBARI-22415:
---
Status: Patch Available  (was: Open)

> Blueprint deploys failing with missing smoke user keytab file
> -
>
> Key: AMBARI-22415
> URL: https://issues.apache.org/jira/browse/AMBARI-22415
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 3.0.0
>Reporter: Eugene Chekanskiy
>Assignee: Eugene Chekanskiy
> Fix For: 3.0.0
>
> Attachments: AMBARI-22415.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AMBARI-22415) Blueprint deploys failing with missing smoke user keytab file

[Eugene Chekanskiy (JIRA)]

Eugene Chekanskiy created AMBARI-22415:
--

 Summary: Blueprint deploys failing with missing smoke user keytab 
file
 Key: AMBARI-22415
 URL: https://issues.apache.org/jira/browse/AMBARI-22415
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 3.0.0
Reporter: Eugene Chekanskiy
Assignee: Eugene Chekanskiy
 Fix For: 3.0.0






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22414) Support # hash prefix comment lines in Hadoop auth_to_local mapping rules

[Hari Sekhon (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hari Sekhon updated AMBARI-22414:
-
Summary: Support # hash prefix comment lines in Hadoop auth_to_local 
mapping rules  (was: Support # hash prefix comment lines in auth_to_local 
mapping rules)

> Support # hash prefix comment lines in Hadoop auth_to_local mapping rules
> -
>
> Key: AMBARI-22414
> URL: https://issues.apache.org/jira/browse/AMBARI-22414
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.5.1
> Environment: HDP 2.6.1 + Kerberos
>Reporter: Hari Sekhon
>
> Request to add support for # hash prefixed comment lines in Hadoop's 
> auth_to_local mappings rules config box so I can comment what rules I've 
> added and why inline to the rules like with code (useful when supporting 
> multi-directory mappings).
> It should be fairly easy to implement, just string strip all lines from # to 
> end, trim whitespace and then exclude all blank / whitespace lines, I do this 
> in tools I write all the time.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22414) Support # hash prefix comment lines in Hadoop auth_to_local mapping rules

[Hari Sekhon (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hari Sekhon updated AMBARI-22414:
-
Priority: Minor  (was: Major)

> Support # hash prefix comment lines in Hadoop auth_to_local mapping rules
> -
>
> Key: AMBARI-22414
> URL: https://issues.apache.org/jira/browse/AMBARI-22414
> Project: Ambari
>  Issue Type: Improvement
>  Components: ambari-server
>Affects Versions: 2.5.1
> Environment: HDP 2.6.1 + Kerberos
>Reporter: Hari Sekhon
>Priority: Minor
>
> Request to add support for # hash prefixed comment lines in Hadoop's 
> auth_to_local mappings rules config box so I can comment what rules I've 
> added and why inline to the rules like with code (useful when supporting 
> multi-directory mappings).
> It should be fairly easy to implement, just string strip all lines from # to 
> end, trim whitespace and then exclude all blank / whitespace lines, I do this 
> in tools I write all the time.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AMBARI-22414) Support # hash prefix comment lines in auth_to_local mapping rules

[Hari Sekhon (JIRA)]

Hari Sekhon created AMBARI-22414:


 Summary: Support # hash prefix comment lines in auth_to_local 
mapping rules
 Key: AMBARI-22414
 URL: https://issues.apache.org/jira/browse/AMBARI-22414
 Project: Ambari
  Issue Type: Improvement
  Components: ambari-server
Affects Versions: 2.5.1
 Environment: HDP 2.6.1 + Kerberos
Reporter: Hari Sekhon


Request to add support for # hash prefixed comment lines in Hadoop's 
auth_to_local mappings rules config box so I can comment what rules I've added 
and why inline to the rules like with code (useful when supporting 
multi-directory mappings).

It should be fairly easy to implement, just string strip all lines from # to 
end, trim whitespace and then exclude all blank / whitespace lines, I do this 
in tools I write all the time.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22413) Fix tar_archive.py: 1. remove verbosity flags, 2. fix archive_dir() and archive_directory_dereference() methods

[JIRA]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Balázs Bence Sári updated AMBARI-22413:
---
Description: 
There are two issues with tar_archive.py which caused a HDP upgrade to fail at 
a customer:

# The verbose flag (-v) is switched on. This could result in long archival time 
and timeouts
# The full path of the files is preserverved in the archive without the leading 
slash. This results in doubled paths when the archive is expanded. 

E.g:
The contents of _/hadoop/falcon/_ directory is archived.
All files are archived with full path but no leading slash: 
_hadoop/falcon//_
After unpacking the unpacked file will look like: 
_/hadoop/falcon/hadoop/falcon//_.


  was:
There are two issues with tar_archive.py which caused a HDP upgrade to fail at 
a customer:

# The verbose flag (-v) is switched on. This could result in long archival time 
and timeouts
# The full path of the files is preserverved in the archive without the leading 
slash. This results in doubled paths when the archive is expanded. 

E.g:
The contents of _/hadoop/falcon/_ directory is archived.
All files are archived with full path but no leading slash: 
_hadoop/falcon//_
When unpacking the unpacked file will look like: 
_/hadoop/falcon/hadoop/falcon//.



> Fix tar_archive.py: 1. remove verbosity flags, 2. fix archive_dir() and 
> archive_directory_dereference() methods
> ---
>
> Key: AMBARI-22413
> URL: https://issues.apache.org/jira/browse/AMBARI-22413
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Balázs Bence Sári
>Assignee: Balázs Bence Sári
>Priority: Critical
>
> There are two issues with tar_archive.py which caused a HDP upgrade to fail 
> at a customer:
> # The verbose flag (-v) is switched on. This could result in long archival 
> time and timeouts
> # The full path of the files is preserverved in the archive without the 
> leading slash. This results in doubled paths when the archive is expanded. 
> E.g:
> The contents of _/hadoop/falcon/_ directory is archived.
> All files are archived with full path but no leading slash: 
> _hadoop/falcon//_
> After unpacking the unpacked file will look like: 
> _/hadoop/falcon/hadoop/falcon//_.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AMBARI-22413) Fix tar_archive.py: 1. remove verbosity flags, 2. fix archive_dir() and archive_directory_dereference() methods

[JIRA]

Balázs Bence Sári created AMBARI-22413:
--

 Summary: Fix tar_archive.py: 1. remove verbosity flags, 2. fix 
archive_dir() and archive_directory_dereference() methods
 Key: AMBARI-22413
 URL: https://issues.apache.org/jira/browse/AMBARI-22413
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.5.2
Reporter: Balázs Bence Sári
Assignee: Balázs Bence Sári
Priority: Critical


There are two issues with tar_archive.py which caused a HDP upgrade to fail at 
a customer:

# The verbose flag (-v) is switched on. This could result in long archival time 
and timeouts
# The full path of the files is preserverved in the archive without the leading 
slash. This results in doubled paths when the archive is expanded. 

E.g:
The contents of _/hadoop/falcon/_ directory is archived.
All files are archived with full path but no leading slash: 
_hadoop/falcon//_
When unpacking the unpacked file will look like: 
_/hadoop/falcon/hadoop/falcon//.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22346) Beeline connection hangs for longer time when connection to HS2 with metastore DB down

[Andrew Onischuk (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Onischuk updated AMBARI-22346:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2.6

> Beeline connection hangs for longer time when connection to HS2 with 
> metastore DB down
> --
>
> Key: AMBARI-22346
> URL: https://issues.apache.org/jira/browse/AMBARI-22346
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
>Priority: Trivial
> Fix For: 2.6.1
>
> Attachments: AMBARI-22346.patch
>
>
> PROBLEM:  
> beeline connection to HS2 hangs when hive metastore Database is down.  
> Issue seen on HDP 2.5.3 and 2.6 version clusters, same test on HDP 2.4.2
> beeline doesn't hangs.
> BUSINESS IMPACT:  
> Ambari spawning multiple beeline processes thats hanging causes unnecessary
> memory usage, resulting in master service failures.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22412) Remove IPA integration from experimental status

[Robert Levas (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Levas updated AMBARI-22412:
--
Status: Patch Available  (was: In Progress)

> Remove IPA integration from experimental status
> ---
>
> Key: AMBARI-22412
> URL: https://issues.apache.org/jira/browse/AMBARI-22412
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22412_trunk_01.patch
>
>
> Remove IPA integration from experimental status so that users can select 
> FreeIPA when enabling Kerberos via the Enable Kerberos Wizard without having 
> to explicitly enable it via the Experimental page. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22412) Remove IPA integration from experimental status

[Robert Levas (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Levas updated AMBARI-22412:
--
Attachment: AMBARI-22412_trunk_01.patch

> Remove IPA integration from experimental status
> ---
>
> Key: AMBARI-22412
> URL: https://issues.apache.org/jira/browse/AMBARI-22412
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22412_trunk_01.patch
>
>
> Remove IPA integration from experimental status so that users can select 
> FreeIPA when enabling Kerberos via the Enable Kerberos Wizard without having 
> to explicitly enable it via the Experimental page. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (AMBARI-22303) Spark history server is stopped (with umask 027 and custom spark log/pid dir)

[Andrew Onischuk (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMBARI-22303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Onischuk updated AMBARI-22303:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to branch-2.6 and trunk

> Spark history server is stopped (with umask 027 and custom spark log/pid dir)
> -
>
> Key: AMBARI-22303
> URL: https://issues.apache.org/jira/browse/AMBARI-22303
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.6.1
>
> Attachments: AMBARI-22303.patch
>
>
> STR:
>   1. Deploy HDP 2.4.3.0-227 on Ambari 2.5.2.0 without Spark
>   2. Enable NN HA
>   3. Upgrade Ambari to 2.6.0.0
>   4. Register install and perform RU to 2.6.3.0-220
>   5. Add Spark service
>   6. Wait for some time.  
> Result: Spark History server is stopped.
> Cluster: 172.27.62.82:8080 - nat-yc-r6-pgos-ambari-hv-r-upg-1 - 48h.
> Artifacts:  /ambari-hv-r-upg/split-1/nat-yc-r6-pgos-ambari-
> hv-r-upg-1/artifacts/ctr-e134-1499953498516-250582-01-14.hwx.site/artifacts/screenshots/com.hw.ambari.ui.tests.monitoring.admin_page.rolling_express_upgrade.TestRegisterAndInstallNewStackVersion/test130_AddService/_24_10_27_28_Component__Spark_History_Server__not_started_on_host_ctr_e134_1499953498516_250582_01_0/>
> Spark logs:  /ambari-hv-r-upg/split-1/nat-yc-r6-pgos-ambari-hv-r-upg-1/var-
> logs/spark/ctr-e134-1499953498516-250582-01-02.hwx.site/>
> From Spark.out
> 
> 
> 
> The reported blocks 1677 has reached the threshold 0.9900 of total blocks 
> 1677. The number of live datanodes 5 has reached the minimum number 0. In 
> safe mode extension. Safe mode will be turned off automatically in 18 seconds.
>   at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkNameNodeSafeMode(FSNamesystem.java:1422)
>   at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFileInt(FSNamesystem.java:2693)
>   at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.startFile(FSNamesystem.java:2582)
>   at 
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.create(NameNodeRpcServer.java:736)
>   at 
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.create(ClientNamenodeProtocolServerSideTranslatorPB.java:409)
>   at 
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
>   at 
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:640)
>   at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:982)
>   at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2351)
>   at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2347)
>   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.hadoop.ipc.Server$Handler.run(Server.java:2347)
> Caused by: org.apache.hadoop.hdfs.server.namenode.SafeModeException: 
> Cannot create file/spark-history/.342200c3-6e9e-485c-8f08-d998cd9d92aa. Name 
> node is in safe mode.
> The reported blocks 1677 has reached the threshold 0.9900 of total blocks 
> 1677. The number of live datanodes 5 has reached the minimum number 0. In 
> safe mode extension. Safe mode will be turned off automatically in 18 seconds.
>   at 
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkNameNodeSafeMode(FSNamesystem.java:1418)
>   ... 13 more
> , while invoking ClientNamenodeProtocolTranslatorPB.create over 
> ctr-e134-1499953498516-250582-01-02.hwx.site/172.27.56.143:8020. Retrying 
> after sleeping for 22256ms.
> 
> However, the NN is not in safemode state:
> 
> 
> 
> [root@ctr-e134-1499953498516-250582-01-02 ~]# hdfs dfsadmin -safemode 
> get
> Safe mode is OFF in 
> ctr-e134-1499953498516-250582-01-13.hwx.site/172.27.69.83:8020
> Safe mode is OFF in 
> ctr-e134-1499953498516-250582-01-02.hwx.site/172.27.56.143:8020
> 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (AMBARI-22412) Remove IPA integration from experimental status

[Robert Levas (JIRA)]

Robert Levas created AMBARI-22412:
-

 Summary: Remove IPA integration from experimental status
 Key: AMBARI-22412
 URL: https://issues.apache.org/jira/browse/AMBARI-22412
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 3.0.0
Reporter: Robert Levas
Assignee: Robert Levas
Priority: Critical
 Fix For: 3.0.0


Remove IPA integration from experimental status so that users can select 
FreeIPA when enabling Kerberos via the Enable Kerberos Wizard without having to 
explicitly enable it via the Experimental page. 




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)