[jira] [Commented] (AMBARI-18521) Stack upgrade fix for Ranger in secure env

[Mugdha Varadkar (JIRA)]

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

Mugdha Varadkar commented on AMBARI-18521:
--

Committed to branch-2.4: 
https://github.com/apache/ambari/commit/960d60ff4584f35fe5aa4908eb27ed4cd97cfe23

> Stack upgrade fix for Ranger in secure env
> --
>
> Key: AMBARI-18521
> URL: https://issues.apache.org/jira/browse/AMBARI-18521
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0, 2.4.1
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-18521.1.patch, AMBARI-18521.patch
>
>
> Stack changes required while upgrading to 2.5 in secure env
> * Remove adding spnego principal value to 
> ranger-admin-site/ranger.spnego.kerberos.principal
> * Get storm principal bare name and update it accordingly to 
> ranger-admin-site.xml/ranger.plugins.storm.serviceuser



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18521) Stack upgrade fix for Ranger in secure env

[Mugdha Varadkar (JIRA)]

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

Mugdha Varadkar updated AMBARI-18521:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Stack upgrade fix for Ranger in secure env
> --
>
> Key: AMBARI-18521
> URL: https://issues.apache.org/jira/browse/AMBARI-18521
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0, 2.4.1
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-18521.1.patch, AMBARI-18521.patch
>
>
> Stack changes required while upgrading to 2.5 in secure env
> * Remove adding spnego principal value to 
> ranger-admin-site/ranger.spnego.kerberos.principal
> * Get storm principal bare name and update it accordingly to 
> ranger-admin-site.xml/ranger.plugins.storm.serviceuser



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18551) Enhance falcon integration to call falcon-config to make sure WEB-INF/lib is present in all cases

[Venkat Ranganathan (JIRA)]

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

Venkat Ranganathan commented on AMBARI-18551:
-

Test failures unrelated to changes in the patch
{quote}
--
Traceback (most recent call last):
  File 
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-common/src/test/python/mock/mock.py",
 line 1199, in patched
return func(*args, **keywargs)
  File 
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_server.py",
 line 577, in test_stop_default
target = RMFTestCase.TARGET_COMMON_SERVICES
  File 
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
 line 155, in executeScript
method(RMFTestCase.env, *command_args)
  File 
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
 line 100, in stop
oozie_service(action='stop', upgrade_type=upgrade_type)
  File 
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-common/src/main/python/ambari_commons/os_family_impl.py",
 line 89, in thunk
return fn(*args, **kwargs)
  File 
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
 line 173, in oozie_service
Directory(params.oozie_tmp_dir,
NameError: global name 'Directory' is not defined

ERROR: test_stop_secured (test_oozie_server.TestOozieServer)
--
Traceback (most recent call last):
  File 
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-common/src/test/python/mock/mock.py",
 line 1199, in patched
return func(*args, **keywargs)
  File 
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_server.py",
 line 711, in test_stop_secured
target = RMFTestCase.TARGET_COMMON_SERVICES
  File 
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
 line 155, in executeScript
method(RMFTestCase.env, *command_args)
  File 
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/test/python/stacks/utils/../../../../main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
 line 100, in stop
oozie_service(action='stop', upgrade_type=upgrade_type)
  File 
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-common/src/main/python/ambari_commons/os_family_impl.py",
 line 89, in thunk
return fn(*args, **kwargs)
  File 
"/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
 line 173, in oozie_service
Directory(params.oozie_tmp_dir,
NameError: global name 'Directory' is not defined
{quote}


> Enhance falcon integration to call falcon-config to make sure WEB-INF/lib is 
> present in all cases
> -
>
> Key: AMBARI-18551
> URL: https://issues.apache.org/jira/browse/AMBARI-18551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.4.2
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
> Fix For: trunk
>
> Attachments: AMBARI-18551.patch
>
>
> There are scenarios where when falcon is started for the first time the 
> enhancements of AMBARI-17955 needs an explicit falcon-config.sh call to 
> create the needed WEB-INF directories so that the customer provisioned jars 
> can be placed in the right directories



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[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.3.4#6332)

[jira] [Updated] (AMBARI-13135) Provide recommendation w.r.t. CMSInitiatingOccupancy for HBase

[Ted Yu (JIRA)]

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

Ted Yu updated AMBARI-13135:

Description: 
The following options are recommended for HBase when ConcMarkSweepGC is used:
{code}
-XX:CMSInitiatingOccupancyFraction=50
-XX:+UseCMSInitiatingOccupancyOnly
{code}

The band for CMSInitiatingOccupancyFraction is [40, 60], depending on workload.
This should be reflected in stack_advisor.py

  was:
The following options are recommended for HBase when ConcMarkSweepGC is used:
{code}
-XX:CMSInitiatingOccupancyFraction=50
-XX:+UseCMSInitiatingOccupancyOnly
{code}
The band for CMSInitiatingOccupancyFraction is [40, 60], depending on workload.
This should be reflected in stack_advisor.py


> Provide recommendation w.r.t. CMSInitiatingOccupancy for HBase
> --
>
> Key: AMBARI-13135
> URL: https://issues.apache.org/jira/browse/AMBARI-13135
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Ted Yu
>
> The following options are recommended for HBase when ConcMarkSweepGC is used:
> {code}
> -XX:CMSInitiatingOccupancyFraction=50
> -XX:+UseCMSInitiatingOccupancyOnly
> {code}
> The band for CMSInitiatingOccupancyFraction is [40, 60], depending on 
> workload.
> This should be reflected in stack_advisor.py



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-13109) Verify that max logs parameter wouldn't cause premature region flush

[Ted Yu (JIRA)]

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

Ted Yu updated AMBARI-13109:

Description: 
For hbase, the following relationship should be maintained:

dfs.blocksize * 0.95 *  hbase.regionserver.maxlogs (default 32) > 
hbase.regionserver.global.memstore.upperLimit * HBASE_HEAPSIZE

The rationale is to avoid premature region flush due to log roll which is 
triggered by insufficiently high max logs.

When user changes the values for max logs, memstore upper limit or max heap 
size, we should verify that the above relationship is satisfied.

  was:
For hbase, the following relationship should be maintained:

dfs.blocksize * 0.95 *  hbase.regionserver.maxlogs (default 32) > 
hbase.regionserver.global.memstore.upperLimit * HBASE_HEAPSIZE

The rationale is to avoid premature region flush due to log roll which is 
triggered by insufficiently high max logs.


When user changes the values for max logs, memstore upper limit or max heap 
size, we should verify that the above relationship is satisfied.


> Verify that max logs parameter wouldn't cause premature region flush
> 
>
> Key: AMBARI-13109
> URL: https://issues.apache.org/jira/browse/AMBARI-13109
> Project: Ambari
>  Issue Type: Improvement
>Reporter: Ted Yu
>
> For hbase, the following relationship should be maintained:
> dfs.blocksize * 0.95 *  hbase.regionserver.maxlogs (default 32) > 
> hbase.regionserver.global.memstore.upperLimit * HBASE_HEAPSIZE
> The rationale is to avoid premature region flush due to log roll which is 
> triggered by insufficiently high max logs.
> When user changes the values for max logs, memstore upper limit or max heap 
> size, we should verify that the above relationship is satisfied.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18550) Views build failure

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18550:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #123 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/123/])
AMBARI-18550. Views build failure. (yusaku) (yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=77019f781dafb528eb274e781cd37e2da9b58c00])
* (edit) 
contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/package.json
* (edit) contrib/views/wfmanager/src/main/resources/ui/package.json


> Views build failure 
> 
>
> Key: AMBARI-18550
> URL: https://issues.apache.org/jira/browse/AMBARI-18550
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Yusaku Sako
>Assignee: Yusaku Sako
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18550.patch
>
>
> Views build fails due to missing dependencies on ember-data:
> {noformat}
> util.py::run_cmd  231 - INFO: Missing npm packages: 
> util.py::run_cmd  231 - INFO: Package: ember-data
> util.py::run_cmd  231 - INFO:   * Specified: ^2.4.2
> util.py::run_cmd  231 - INFO:   * Installed: 2.9.0-beta.2
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18550) Views build failure

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18550:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5772 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5772/])
AMBARI-18550. Views build failure. (yusaku) (yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b81deb0e5dea0c4f1ed56567d03e0e04049372ba])
* (edit) contrib/views/wfmanager/src/main/resources/ui/package.json
* (edit) 
contrib/views/hueambarimigration/src/main/resources/ui/hueambarimigration-view/package.json


> Views build failure 
> 
>
> Key: AMBARI-18550
> URL: https://issues.apache.org/jira/browse/AMBARI-18550
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Yusaku Sako
>Assignee: Yusaku Sako
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18550.patch
>
>
> Views build fails due to missing dependencies on ember-data:
> {noformat}
> util.py::run_cmd  231 - INFO: Missing npm packages: 
> util.py::run_cmd  231 - INFO: Package: ember-data
> util.py::run_cmd  231 - INFO:   * Specified: ^2.4.2
> util.py::run_cmd  231 - INFO:   * Installed: 2.9.0-beta.2
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18546) BP format does not generate property oozie.service.JPAService.jdbc.url

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18546:


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

This message is automatically generated.

> BP format does not generate property oozie.service.JPAService.jdbc.url
> --
>
> Key: AMBARI-18546
> URL: https://issues.apache.org/jira/browse/AMBARI-18546
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18546.patch
>
>
> STR:
> * Install Ambari 2.4.0.1 with HDP 2.5 and Oozie (using existing MySQL DB).
> * Notice that oozie-site has config,
> {code}
> oozie.service.JPAService.jdbc.url=jdbc:mysql://$SERVER/$oozie.db.schema.name
> {code}
> E.g.,
> jdbc:mysql://c6401.ambari.apache.org/oozie
> * Export the BP,
> api/v1/clusters/c1?format=blueprint
> It doesn't generate the "oozie.service.JPAService.jdbc.url" property, so a 
> user trying to use that blueprint will run into errors.
> Further, setting the value of that property to 
> "jdbc:mysql://%HOSTGROUP::host_group_1%/oozie" does not actually replace it 
> with the hostname, and it should also dynamically replace the Oozie DB name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18551) Enhance falcon integration to call falcon-config to make sure WEB-INF/lib is present in all cases

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18551:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12832016/AMBARI-18551.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 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

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

{color:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8826//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8826//console

This message is automatically generated.

> Enhance falcon integration to call falcon-config to make sure WEB-INF/lib is 
> present in all cases
> -
>
> Key: AMBARI-18551
> URL: https://issues.apache.org/jira/browse/AMBARI-18551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.4.2
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
> Fix For: trunk
>
> Attachments: AMBARI-18551.patch
>
>
> There are scenarios where when falcon is started for the first time the 
> enhancements of AMBARI-17955 needs an explicit falcon-config.sh call to 
> create the needed WEB-INF directories so that the customer provisioned jars 
> can be placed in the right directories



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-18552) Migrate to Bootstrap 3

[Yusaku Sako (JIRA)]

Yusaku Sako created AMBARI-18552:


 Summary: Migrate to Bootstrap 3
 Key: AMBARI-18552
 URL: https://issues.apache.org/jira/browse/AMBARI-18552
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 3.0.0
Reporter: Yusaku Sako
Assignee: Yusaku Sako
 Fix For: 3.0.0


Migrate from Bootstrap 2 to Bootstrap 3.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18550) Views build failure

[Yusaku Sako (JIRA)]

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

Yusaku Sako commented on AMBARI-18550:
--

Committed to trunk, branch-2.5, and branch-2.4.

> Views build failure 
> 
>
> Key: AMBARI-18550
> URL: https://issues.apache.org/jira/browse/AMBARI-18550
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Yusaku Sako
>Assignee: Yusaku Sako
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18550.patch
>
>
> Views build fails due to missing dependencies on ember-data:
> {noformat}
> util.py::run_cmd  231 - INFO: Missing npm packages: 
> util.py::run_cmd  231 - INFO: Package: ember-data
> util.py::run_cmd  231 - INFO:   * Specified: ^2.4.2
> util.py::run_cmd  231 - INFO:   * Installed: 2.9.0-beta.2
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18550) Views build failure

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18550:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Views build failure 
> 
>
> Key: AMBARI-18550
> URL: https://issues.apache.org/jira/browse/AMBARI-18550
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Yusaku Sako
>Assignee: Yusaku Sako
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18550.patch
>
>
> Views build fails due to missing dependencies on ember-data:
> {noformat}
> util.py::run_cmd  231 - INFO: Missing npm packages: 
> util.py::run_cmd  231 - INFO: Package: ember-data
> util.py::run_cmd  231 - INFO:   * Specified: ^2.4.2
> util.py::run_cmd  231 - INFO:   * Installed: 2.9.0-beta.2
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18550) Views build failure

[Jaimin D Jetly (JIRA)]

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

Jaimin D Jetly commented on AMBARI-18550:
-

+1 for the patch.

> Views build failure 
> 
>
> Key: AMBARI-18550
> URL: https://issues.apache.org/jira/browse/AMBARI-18550
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Yusaku Sako
>Assignee: Yusaku Sako
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18550.patch
>
>
> Views build fails due to missing dependencies on ember-data:
> {noformat}
> util.py::run_cmd  231 - INFO: Missing npm packages: 
> util.py::run_cmd  231 - INFO: Package: ember-data
> util.py::run_cmd  231 - INFO:   * Specified: ^2.4.2
> util.py::run_cmd  231 - INFO:   * Installed: 2.9.0-beta.2
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18550) Views build failure

[Yusaku Sako (JIRA)]

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

Yusaku Sako commented on AMBARI-18550:
--

After the patch:
{noformat}
[INFO] 
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Ambari Project POM .. SUCCESS [  3.348 s]
[INFO] Ambari Web . SUCCESS [ 37.863 s]
[INFO] Ambari Views ... SUCCESS [  1.449 s]
[INFO] Ambari Admin View .. SUCCESS [ 19.154 s]
[INFO] Ambari View Utils .. SUCCESS [  1.260 s]
[INFO] Ambari View Commons  SUCCESS [  0.557 s]
[INFO] Files .. SUCCESS [01:09 min]
[INFO] Pig  SUCCESS [ 18.644 s]
[INFO] Slider . SUCCESS [ 18.373 s]
[INFO] Capacity Scheduler . SUCCESS [ 36.462 s]
[INFO] Tez  SUCCESS [  6.527 s]
[INFO] Storm_Monitoring ... SUCCESS [  1.017 s]
[INFO] Zeppelin ... SUCCESS [  4.742 s]
[INFO] hueambarimigration . SUCCESS [ 44.216 s]
[INFO] Hive Jdbc .. SUCCESS [ 49.027 s]
[INFO] WF Manager View  SUCCESS [02:07 min]
[INFO] Hive ... SUCCESS [03:18 min]
[INFO] Ambari Metrics Common .. SUCCESS [  3.342 s]
[INFO] Ambari Server .. SUCCESS [11:01 min]
[INFO] Ambari Agent ... SUCCESS [01:37 min]
[INFO] Ambari Client .. SUCCESS [  0.434 s]
[INFO] Ambari Shell ... SUCCESS [  0.397 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 23:24 min
[INFO] Finished at: 2016-10-05T10:35:05+00:00
[INFO] Final Memory: 147M/634M
[INFO] 
{noformat}

> Views build failure 
> 
>
> Key: AMBARI-18550
> URL: https://issues.apache.org/jira/browse/AMBARI-18550
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Yusaku Sako
>Assignee: Yusaku Sako
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18550.patch
>
>
> Views build fails due to missing dependencies on ember-data:
> {noformat}
> util.py::run_cmd  231 - INFO: Missing npm packages: 
> util.py::run_cmd  231 - INFO: Package: ember-data
> util.py::run_cmd  231 - INFO:   * Specified: ^2.4.2
> util.py::run_cmd  231 - INFO:   * Installed: 2.9.0-beta.2
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18551) Enhance falcon integration to call falcon-config to make sure WEB-INF/lib is present in all cases

[Venkat Ranganathan (JIRA)]

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

Venkat Ranganathan commented on AMBARI-18551:
-

[~afernandez]  yes.   It also applies to 2.5.

Thanks

> Enhance falcon integration to call falcon-config to make sure WEB-INF/lib is 
> present in all cases
> -
>
> Key: AMBARI-18551
> URL: https://issues.apache.org/jira/browse/AMBARI-18551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.4.2
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
> Fix For: trunk
>
> Attachments: AMBARI-18551.patch
>
>
> There are scenarios where when falcon is started for the first time the 
> enhancements of AMBARI-17955 needs an explicit falcon-config.sh call to 
> create the needed WEB-INF directories so that the customer provisioned jars 
> can be placed in the right directories



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18551) Enhance falcon integration to call falcon-config to make sure WEB-INF/lib is present in all cases

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez commented on AMBARI-18551:
--

+1, is this also intended for Ambari 2.5?

> Enhance falcon integration to call falcon-config to make sure WEB-INF/lib is 
> present in all cases
> -
>
> Key: AMBARI-18551
> URL: https://issues.apache.org/jira/browse/AMBARI-18551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.4.2
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
> Fix For: trunk
>
> Attachments: AMBARI-18551.patch
>
>
> There are scenarios where when falcon is started for the first time the 
> enhancements of AMBARI-17955 needs an explicit falcon-config.sh call to 
> create the needed WEB-INF directories so that the customer provisioned jars 
> can be placed in the right directories



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (AMBARI-18551) Enhance falcon integration to call falcon-config to make sure WEB-INF/lib is present in all cases

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez edited comment on AMBARI-18551 at 10/6/16 10:08 PM:


+1, is this also intended for Ambari 2.5?
[~venkatnrangan]


was (Author: afernandez):
+1, is this also intended for Ambari 2.5?

> Enhance falcon integration to call falcon-config to make sure WEB-INF/lib is 
> present in all cases
> -
>
> Key: AMBARI-18551
> URL: https://issues.apache.org/jira/browse/AMBARI-18551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.4.2
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
> Fix For: trunk
>
> Attachments: AMBARI-18551.patch
>
>
> There are scenarios where when falcon is started for the first time the 
> enhancements of AMBARI-17955 needs an explicit falcon-config.sh call to 
> create the needed WEB-INF directories so that the customer provisioned jars 
> can be placed in the right directories



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18546) BP format does not generate property oozie.service.JPAService.jdbc.url

[Vitaly Brodetskyi (JIRA)]

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

Vitaly Brodetskyi updated AMBARI-18546:
---
Attachment: (was: AMBARI-18546.patch)

> BP format does not generate property oozie.service.JPAService.jdbc.url
> --
>
> Key: AMBARI-18546
> URL: https://issues.apache.org/jira/browse/AMBARI-18546
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18546.patch
>
>
> STR:
> * Install Ambari 2.4.0.1 with HDP 2.5 and Oozie (using existing MySQL DB).
> * Notice that oozie-site has config,
> {code}
> oozie.service.JPAService.jdbc.url=jdbc:mysql://$SERVER/$oozie.db.schema.name
> {code}
> E.g.,
> jdbc:mysql://c6401.ambari.apache.org/oozie
> * Export the BP,
> api/v1/clusters/c1?format=blueprint
> It doesn't generate the "oozie.service.JPAService.jdbc.url" property, so a 
> user trying to use that blueprint will run into errors.
> Further, setting the value of that property to 
> "jdbc:mysql://%HOSTGROUP::host_group_1%/oozie" does not actually replace it 
> with the hostname, and it should also dynamically replace the Oozie DB name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18549) oozie server start fails post upgrade to Ambari 2.4.1

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18549:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5771 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5771/])
AMBARI-18549. oozie server start fails post upgrade to Ambari 2.4.1 (aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=49c9660c39c379b5568f9cff2d0fad44bde03222])
* (edit) ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_server.py
* (edit) 
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py


> oozie server start fails post upgrade to Ambari 2.4.1
> -
>
> Key: AMBARI-18549
> URL: https://issues.apache.org/jira/browse/AMBARI-18549
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.2
>
> Attachments: AMBARI-18549.patch
>
>
>   
> **Info**  
> This cluster has gone through below upgrade.  
> Ambari 2.2.2.0 - Ambari 2.4.1  
> Cluster Details :   
> Please login with okta credential to these cluster machines  
> 
> On restarting Oozie web server from Ambari below error was thrown.
> 
> 
> 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 215, in 
> OozieServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 280, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 100, in stop
> oozie_service(action='stop', upgrade_type=upgrade_type)
>   File 
> "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89, 
> in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
>  line 164, in oozie_service
> user = params.oozie_user)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 
> 155, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 71, in inner
> result = function(command, **kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 93, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'cd /var/tmp/oozie 
> && /usr/hdp/current/oozie-server/bin/oozied.sh stop 60 -force' returned 1. 
> -bash: line 0: cd: /var/tmp/oozie: No such file or directory
> 
> We had to workaround this problem by running oozie stop manual as below
> 
> 
> 
> /usr/hdp/2.4.3.0-207/oozie/bin/oozied.sh stop
> 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18516) Add ability to have services declare itself as tech-preview or mandatory

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18516:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5771 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5771/])
AMBARI-18516. Add ability to have services declare itself as (vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=56e00acdc8d7357ba811fcd4dca4fbb23bad33be])
* (edit) ambari-server/src/main/resources/properties.json
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackServiceResourceProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/StackServiceResponse.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceInfo.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/ServiceInfoTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/stack/ServiceModuleTest.java


> Add ability to have services declare itself as tech-preview or mandatory
> 
>
> Key: AMBARI-18516
> URL: https://issues.apache.org/jira/browse/AMBARI-18516
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18516.patch
>
>
> When a service is added to a stack, it should be identified as:
> default/regular - service is optional on the cluster, UI usually shows it as
> tech-preview - service may be deployed, UI will not auto-select these 
> services and mark them as TechPreview
> mandatory - service need to be deployed and all deployment should fail is the 
> service is not selected during deployment
> Lets create a proposal of what changes are needed in the services' 
> metainfo.xml? Note that a service can change its attribute between stack 
> versions - e.g. move from "tech-preview" to "mandatory".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18547) No validation errors recieved for empty or removed hadoop.proxyuser.* properties

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18547:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5771 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5771/])
AMBARI-18547. No validation errors recieved for empty or removed (dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=55c1dc5cb8015e3d114c186792dacd883b7aa820])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py
* (add) 
ambari-common/src/main/python/resource_management/libraries/functions/data_structure_utils.py
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/services/stack_advisor.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/common/test_stack_advisor.py
* (add) 
ambari-agent/src/test/python/resource_management/TestDataStructureUtils.py


> No validation errors recieved for empty or removed hadoop.proxyuser.* 
> properties
> 
>
> Key: AMBARI-18547
> URL: https://issues.apache.org/jira/browse/AMBARI-18547
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-18547.patch
>
>
> Steps to reproduce:
> 1) Start install wizard
> 2) Select HDFS, Yarn, Zookeeper
> 3) Navigate to Customize Service page
> 4) Select HDFS and open *Custom core-site* category
> 4) Remove any/all hadoop.proxyuser.* properties , e.g. 
> hadoop.proxyuser.hdfs.groups
> 5) Set empty value for any/all hadoop.proxyuser.*
> 6) Click next
> AR: Validation succeed, {{/api/v1/stacks/HDP/versions/2.5/validations}} 
> request returns no errors or warnings regarding mentioned properties
> ER: Validation error/warning regarding empty and removed hadoop.proxyuser.* 
> properties



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18526) Ambari breaks sudo and user access if Ambari Agent misconfigured

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18526:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5771 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5771/])
AMBARI-18526. Ambari breaks sudo and user access if Ambari Agent (dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=cceb7d2d3eb8359e3a25a7c9eec5c92516f28097])
* (edit) ambari-agent/conf/unix/ambari-agent


> Ambari breaks sudo and user access if Ambari Agent misconfigured
> 
>
> Key: AMBARI-18526
> URL: https://issues.apache.org/jira/browse/AMBARI-18526
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.2
>
> Attachments: AMBARI-18526.patch
>
>
> While working on Ambari installation using Vagrant I found following issues 
> that can be potentially dangerous and destroy sudo and /home permissions
> Steps to reproduce:
> Remove or misconfigure following configs from ambari-agent.ini file:
> {code}
> [agent]
> logdir=/var/log/ambari-agent
> piddir=/var/run/ambari-agent
> {code}
> Start ambari agent.  Note that log, pid, and out want to be written to /.  
> Everything fails and sudo is destroyed as well as /home for all users.  Sudo 
> user will not be able to connect to cluster using private key due to 
> permissions and folder ownership switch to root.
> {code}
> [root@ambari-slave1 vagrant]# id
> uid=0(root) gid=0(root) groups=0(root)
> [root@ambari-slave1 vagrant]# ambari-agent start
> chown: changing ownership of `/proc/12937': Operation not permitted
> chown: changing ownership of `/proc/12938/task/12938': Operation not permitted
> chown: changing ownership of `/proc/12938': Operation not permitted
> chown: changing ownership of `/proc/12941/task/12941': Operation not permitted
> chown: changing ownership of `/proc/12941': Operation not permitted
> chown: changing ownership of `/proc/12942/task/12942/fd/4': No such file or 
> directory
> chown: changing ownership of `/proc/12942/task/12942/fdinfo/4': No such file 
> or directory
> chown: changing ownership of `/proc/12942/task/12942': Operation not permitted
> chown: changing ownership of `/proc/12942/fd/4': No such file or directory
> chown: changing ownership of `/proc/12942/fdinfo/4': No such file or directory
> chown: changing ownership of `/proc/12942': Operation not permitted
> Starting ambari-agent
> Verifying ambari-agent process status...
> Ambari Agent successfully started
> Agent PID at: /ambari-agent.pid
> Agent out at: /ambari-agent.out
> Agent log at: /ambari-agent.log
> {code}
> Sticky bit is removed from sudo as result of it
> {code}
> [root@ambari-slave1 vagrant]# ls -l /usr/bin/sudo
> ---x--x--x. 1 root root 123832 Oct 15  2014 /usr/bin/sudo
> {code}
> it should be:
> {code}
> [root@ambari-slave2 vagrant]# ls -l /usr/bin/sudo
> ---s--x--x. 1 root root 123832 Oct 15  2014 /usr/bin/sudo
> {code}
> All user folder is messed up as owned by root
> {code}
> [root@ambari-slave1 vagrant]# ls -ld /home/
> drwxr-xr-x. 3 root root 4096 Mar  9  2016 /home/
> [root@ambari-slave1 vagrant]# ls -ld /home/vagrant
> drwx-- 3 root root 4096 Sep 27 22:16 /home/vagrant
> {code}
> sudo is broken:
> {code}
> [root@ambari-slave1 vagrant]# id
> uid=0(root) gid=0(root) groups=0(root)
> [root@ambari-slave1 vagrant]# exit
> exit
> [vagrant@ambari-slave1 ~]$ sudo su
> sudo: effective uid is not 0, is sudo installed setuid root?
> {code}
> this is caused due to by function in /usr/sbin/ambari-agent
> {code}
> get_agent_property() {
> property_name="$1"
> value=$(awk -F "=" "/$property_name/ {print \$2}" 
> /etc/ambari-agent/conf/ambari-agent.ini)
> echo $value
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18549) oozie server start fails post upgrade to Ambari 2.4.1

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18549:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #122 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/122/])
AMBARI-18549. oozie server start fails post upgrade to Ambari 2.4.1 (aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8678f46d945c20ad9555a50bf2bf68a0edac3c6a])
* (edit) 
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py
* (edit) ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_server.py


> oozie server start fails post upgrade to Ambari 2.4.1
> -
>
> Key: AMBARI-18549
> URL: https://issues.apache.org/jira/browse/AMBARI-18549
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.2
>
> Attachments: AMBARI-18549.patch
>
>
>   
> **Info**  
> This cluster has gone through below upgrade.  
> Ambari 2.2.2.0 - Ambari 2.4.1  
> Cluster Details :   
> Please login with okta credential to these cluster machines  
> 
> On restarting Oozie web server from Ambari below error was thrown.
> 
> 
> 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 215, in 
> OozieServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 280, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 100, in stop
> oozie_service(action='stop', upgrade_type=upgrade_type)
>   File 
> "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89, 
> in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
>  line 164, in oozie_service
> user = params.oozie_user)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 
> 155, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 71, in inner
> result = function(command, **kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 93, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'cd /var/tmp/oozie 
> && /usr/hdp/current/oozie-server/bin/oozied.sh stop 60 -force' returned 1. 
> -bash: line 0: cd: /var/tmp/oozie: No such file or directory
> 
> We had to workaround this problem by running oozie stop manual as below
> 
> 
> 
> /usr/hdp/2.4.3.0-207/oozie/bin/oozied.sh stop
> 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18526) Ambari breaks sudo and user access if Ambari Agent misconfigured

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18526:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #122 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/122/])
AMBARI-18526. Ambari breaks sudo and user access if Ambari Agent (dlysnichenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=351b8f1954db7edf8523698bbb33cc480afc6096])
* (edit) ambari-agent/conf/unix/ambari-agent


> Ambari breaks sudo and user access if Ambari Agent misconfigured
> 
>
> Key: AMBARI-18526
> URL: https://issues.apache.org/jira/browse/AMBARI-18526
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.2
>
> Attachments: AMBARI-18526.patch
>
>
> While working on Ambari installation using Vagrant I found following issues 
> that can be potentially dangerous and destroy sudo and /home permissions
> Steps to reproduce:
> Remove or misconfigure following configs from ambari-agent.ini file:
> {code}
> [agent]
> logdir=/var/log/ambari-agent
> piddir=/var/run/ambari-agent
> {code}
> Start ambari agent.  Note that log, pid, and out want to be written to /.  
> Everything fails and sudo is destroyed as well as /home for all users.  Sudo 
> user will not be able to connect to cluster using private key due to 
> permissions and folder ownership switch to root.
> {code}
> [root@ambari-slave1 vagrant]# id
> uid=0(root) gid=0(root) groups=0(root)
> [root@ambari-slave1 vagrant]# ambari-agent start
> chown: changing ownership of `/proc/12937': Operation not permitted
> chown: changing ownership of `/proc/12938/task/12938': Operation not permitted
> chown: changing ownership of `/proc/12938': Operation not permitted
> chown: changing ownership of `/proc/12941/task/12941': Operation not permitted
> chown: changing ownership of `/proc/12941': Operation not permitted
> chown: changing ownership of `/proc/12942/task/12942/fd/4': No such file or 
> directory
> chown: changing ownership of `/proc/12942/task/12942/fdinfo/4': No such file 
> or directory
> chown: changing ownership of `/proc/12942/task/12942': Operation not permitted
> chown: changing ownership of `/proc/12942/fd/4': No such file or directory
> chown: changing ownership of `/proc/12942/fdinfo/4': No such file or directory
> chown: changing ownership of `/proc/12942': Operation not permitted
> Starting ambari-agent
> Verifying ambari-agent process status...
> Ambari Agent successfully started
> Agent PID at: /ambari-agent.pid
> Agent out at: /ambari-agent.out
> Agent log at: /ambari-agent.log
> {code}
> Sticky bit is removed from sudo as result of it
> {code}
> [root@ambari-slave1 vagrant]# ls -l /usr/bin/sudo
> ---x--x--x. 1 root root 123832 Oct 15  2014 /usr/bin/sudo
> {code}
> it should be:
> {code}
> [root@ambari-slave2 vagrant]# ls -l /usr/bin/sudo
> ---s--x--x. 1 root root 123832 Oct 15  2014 /usr/bin/sudo
> {code}
> All user folder is messed up as owned by root
> {code}
> [root@ambari-slave1 vagrant]# ls -ld /home/
> drwxr-xr-x. 3 root root 4096 Mar  9  2016 /home/
> [root@ambari-slave1 vagrant]# ls -ld /home/vagrant
> drwx-- 3 root root 4096 Sep 27 22:16 /home/vagrant
> {code}
> sudo is broken:
> {code}
> [root@ambari-slave1 vagrant]# id
> uid=0(root) gid=0(root) groups=0(root)
> [root@ambari-slave1 vagrant]# exit
> exit
> [vagrant@ambari-slave1 ~]$ sudo su
> sudo: effective uid is not 0, is sudo installed setuid root?
> {code}
> this is caused due to by function in /usr/sbin/ambari-agent
> {code}
> get_agent_property() {
> property_name="$1"
> value=$(awk -F "=" "/$property_name/ {print \$2}" 
> /etc/ambari-agent/conf/ambari-agent.ini)
> echo $value
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18551) Enhance falcon integration to call falcon-config to make sure WEB-INF/lib is present in all cases

[Venkat Ranganathan (JIRA)]

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

Venkat Ranganathan updated AMBARI-18551:

Fix Version/s: trunk
   Status: Patch Available  (was: Open)

> Enhance falcon integration to call falcon-config to make sure WEB-INF/lib is 
> present in all cases
> -
>
> Key: AMBARI-18551
> URL: https://issues.apache.org/jira/browse/AMBARI-18551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.4.2
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
> Fix For: trunk
>
> Attachments: AMBARI-18551.patch
>
>
> There are scenarios where when falcon is started for the first time the 
> enhancements of AMBARI-17955 needs an explicit falcon-config.sh call to 
> create the needed WEB-INF directories so that the customer provisioned jars 
> can be placed in the right directories



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18551) Enhance falcon integration to call falcon-config to make sure WEB-INF/lib is present in all cases

[Venkat Ranganathan (JIRA)]

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

Venkat Ranganathan commented on AMBARI-18551:
-

[~afernandez]/[~sumitmohanty]  Can you please take a look?

> Enhance falcon integration to call falcon-config to make sure WEB-INF/lib is 
> present in all cases
> -
>
> Key: AMBARI-18551
> URL: https://issues.apache.org/jira/browse/AMBARI-18551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.4.2
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
> Fix For: trunk
>
> Attachments: AMBARI-18551.patch
>
>
> There are scenarios where when falcon is started for the first time the 
> enhancements of AMBARI-17955 needs an explicit falcon-config.sh call to 
> create the needed WEB-INF directories so that the customer provisioned jars 
> can be placed in the right directories



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18551) Enhance falcon integration to call falcon-config to make sure WEB-INF/lib is present in all cases

[Venkat Ranganathan (JIRA)]

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

Venkat Ranganathan updated AMBARI-18551:

Attachment: AMBARI-18551.patch

Bypassing RB as it is a very simple change

> Enhance falcon integration to call falcon-config to make sure WEB-INF/lib is 
> present in all cases
> -
>
> Key: AMBARI-18551
> URL: https://issues.apache.org/jira/browse/AMBARI-18551
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-agent
>Affects Versions: 2.4.2
>Reporter: Venkat Ranganathan
>Assignee: Venkat Ranganathan
> Attachments: AMBARI-18551.patch
>
>
> There are scenarios where when falcon is started for the first time the 
> enhancements of AMBARI-17955 needs an explicit falcon-config.sh call to 
> create the needed WEB-INF directories so that the customer provisioned jars 
> can be placed in the right directories



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-18551) Enhance falcon integration to call falcon-config to make sure WEB-INF/lib is present in all cases

[Venkat Ranganathan (JIRA)]

Venkat Ranganathan created AMBARI-18551:
---

 Summary: Enhance falcon integration to call falcon-config to make 
sure WEB-INF/lib is present in all cases
 Key: AMBARI-18551
 URL: https://issues.apache.org/jira/browse/AMBARI-18551
 Project: Ambari
  Issue Type: Bug
  Components: ambari-agent
Affects Versions: 2.4.2
Reporter: Venkat Ranganathan
Assignee: Venkat Ranganathan


There are scenarios where when falcon is started for the first time the 
enhancements of AMBARI-17955 needs an explicit falcon-config.sh call to create 
the needed WEB-INF directories so that the customer provisioned jars can be 
placed in the right directories



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18532) Getting errors with max length 1000byte, when using Mysql db with charset UTF8

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18532:
-

ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #5770 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5770/])
AMBARI-18532. Getting errors with max length 1000byte, when using Mysql 
(vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=46cb40233d3e9762c2b44c1b43f3a0c1cf5c96c2])
* (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql


> Getting errors with max length 1000byte, when using Mysql db with charset UTF8
> --
>
> Key: AMBARI-18532
> URL: https://issues.apache.org/jira/browse/AMBARI-18532
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, ambari-upgrade
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18532.patch
>
>
> ERROR 1071 (42000): Specified key was too long; max key length is 1000 bytes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18550) Views build failure

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18550:
-
Description: 
Views build fails due to missing dependencies on ember-data:
{noformat}
util.py::run_cmd  231 - INFO: Missing npm packages: 
util.py::run_cmd  231 - INFO: Package: ember-data
util.py::run_cmd  231 - INFO:   * Specified: ^2.4.2
util.py::run_cmd  231 - INFO:   * Installed: 2.9.0-beta.2
{noformat}

  was:Views build fails due to missing dependencies on ember-data.


> Views build failure 
> 
>
> Key: AMBARI-18550
> URL: https://issues.apache.org/jira/browse/AMBARI-18550
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Yusaku Sako
>Assignee: Yusaku Sako
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18550.patch
>
>
> Views build fails due to missing dependencies on ember-data:
> {noformat}
> util.py::run_cmd  231 - INFO: Missing npm packages: 
> util.py::run_cmd  231 - INFO: Package: ember-data
> util.py::run_cmd  231 - INFO:   * Specified: ^2.4.2
> util.py::run_cmd  231 - INFO:   * Installed: 2.9.0-beta.2
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18550) Views build failure

[Yusaku Sako (JIRA)]

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

Yusaku Sako updated AMBARI-18550:
-
Status: Patch Available  (was: Open)

> Views build failure 
> 
>
> Key: AMBARI-18550
> URL: https://issues.apache.org/jira/browse/AMBARI-18550
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.5.0
>Reporter: Yusaku Sako
>Assignee: Yusaku Sako
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18550.patch
>
>
> Views build fails due to missing dependencies on ember-data:
> {noformat}
> util.py::run_cmd  231 - INFO: Missing npm packages: 
> util.py::run_cmd  231 - INFO: Package: ember-data
> util.py::run_cmd  231 - INFO:   * Specified: ^2.4.2
> util.py::run_cmd  231 - INFO:   * Installed: 2.9.0-beta.2
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18516) Add ability to have services declare itself as tech-preview or mandatory

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18516:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #121 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/121/])
AMBARI-18516. Add ability to have services declare itself as (vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8ef3088fe0d1305aceae0f9039a0d0429e572fe4])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/stack/ServiceModule.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackServiceResourceProvider.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/state/ServiceInfo.java
* (edit) ambari-server/src/main/resources/properties.json
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/ServiceInfoTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/stack/ServiceModuleTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/controller/StackServiceResponse.java


> Add ability to have services declare itself as tech-preview or mandatory
> 
>
> Key: AMBARI-18516
> URL: https://issues.apache.org/jira/browse/AMBARI-18516
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18516.patch
>
>
> When a service is added to a stack, it should be identified as:
> default/regular - service is optional on the cluster, UI usually shows it as
> tech-preview - service may be deployed, UI will not auto-select these 
> services and mark them as TechPreview
> mandatory - service need to be deployed and all deployment should fail is the 
> service is not selected during deployment
> Lets create a proposal of what changes are needed in the services' 
> metainfo.xml? Note that a service can change its attribute between stack 
> versions - e.g. move from "tech-preview" to "mandatory".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18548) Declarative Logsearch/Logfeeder Component Metadata for Stack Component

[JIRA]

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

Olivér Szabó updated AMBARI-18548:
--
Summary: Declarative Logsearch/Logfeeder Component Metadata for Stack 
Component  (was: Declarative Component Log Search Pattern Metadata for Stack 
Components)

> Declarative Logsearch/Logfeeder Component Metadata for Stack Component
> --
>
> Key: AMBARI-18548
> URL: https://issues.apache.org/jira/browse/AMBARI-18548
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18547) No validation errors recieved for empty or removed hadoop.proxyuser.* properties

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-18547:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed
   49c9660..55c1dc5  trunk -> trunk


> No validation errors recieved for empty or removed hadoop.proxyuser.* 
> properties
> 
>
> Key: AMBARI-18547
> URL: https://issues.apache.org/jira/browse/AMBARI-18547
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-18547.patch
>
>
> Steps to reproduce:
> 1) Start install wizard
> 2) Select HDFS, Yarn, Zookeeper
> 3) Navigate to Customize Service page
> 4) Select HDFS and open *Custom core-site* category
> 4) Remove any/all hadoop.proxyuser.* properties , e.g. 
> hadoop.proxyuser.hdfs.groups
> 5) Set empty value for any/all hadoop.proxyuser.*
> 6) Click next
> AR: Validation succeed, {{/api/v1/stacks/HDP/versions/2.5/validations}} 
> request returns no errors or warnings regarding mentioned properties
> ER: Validation error/warning regarding empty and removed hadoop.proxyuser.* 
> properties



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18526) Ambari breaks sudo and user access if Ambari Agent misconfigured

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-18526:

Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed
To https://git-wip-us.apache.org/repos/asf/ambari.git
   9373517..ffa1bbf  branch-2.4 -> branch-2.4
   8678f46..351b8f1  branch-2.5 -> branch-2.5
   49c9660..55c1dc5  trunk -> trunk


> Ambari breaks sudo and user access if Ambari Agent misconfigured
> 
>
> Key: AMBARI-18526
> URL: https://issues.apache.org/jira/browse/AMBARI-18526
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.2
>
> Attachments: AMBARI-18526.patch
>
>
> While working on Ambari installation using Vagrant I found following issues 
> that can be potentially dangerous and destroy sudo and /home permissions
> Steps to reproduce:
> Remove or misconfigure following configs from ambari-agent.ini file:
> {code}
> [agent]
> logdir=/var/log/ambari-agent
> piddir=/var/run/ambari-agent
> {code}
> Start ambari agent.  Note that log, pid, and out want to be written to /.  
> Everything fails and sudo is destroyed as well as /home for all users.  Sudo 
> user will not be able to connect to cluster using private key due to 
> permissions and folder ownership switch to root.
> {code}
> [root@ambari-slave1 vagrant]# id
> uid=0(root) gid=0(root) groups=0(root)
> [root@ambari-slave1 vagrant]# ambari-agent start
> chown: changing ownership of `/proc/12937': Operation not permitted
> chown: changing ownership of `/proc/12938/task/12938': Operation not permitted
> chown: changing ownership of `/proc/12938': Operation not permitted
> chown: changing ownership of `/proc/12941/task/12941': Operation not permitted
> chown: changing ownership of `/proc/12941': Operation not permitted
> chown: changing ownership of `/proc/12942/task/12942/fd/4': No such file or 
> directory
> chown: changing ownership of `/proc/12942/task/12942/fdinfo/4': No such file 
> or directory
> chown: changing ownership of `/proc/12942/task/12942': Operation not permitted
> chown: changing ownership of `/proc/12942/fd/4': No such file or directory
> chown: changing ownership of `/proc/12942/fdinfo/4': No such file or directory
> chown: changing ownership of `/proc/12942': Operation not permitted
> Starting ambari-agent
> Verifying ambari-agent process status...
> Ambari Agent successfully started
> Agent PID at: /ambari-agent.pid
> Agent out at: /ambari-agent.out
> Agent log at: /ambari-agent.log
> {code}
> Sticky bit is removed from sudo as result of it
> {code}
> [root@ambari-slave1 vagrant]# ls -l /usr/bin/sudo
> ---x--x--x. 1 root root 123832 Oct 15  2014 /usr/bin/sudo
> {code}
> it should be:
> {code}
> [root@ambari-slave2 vagrant]# ls -l /usr/bin/sudo
> ---s--x--x. 1 root root 123832 Oct 15  2014 /usr/bin/sudo
> {code}
> All user folder is messed up as owned by root
> {code}
> [root@ambari-slave1 vagrant]# ls -ld /home/
> drwxr-xr-x. 3 root root 4096 Mar  9  2016 /home/
> [root@ambari-slave1 vagrant]# ls -ld /home/vagrant
> drwx-- 3 root root 4096 Sep 27 22:16 /home/vagrant
> {code}
> sudo is broken:
> {code}
> [root@ambari-slave1 vagrant]# id
> uid=0(root) gid=0(root) groups=0(root)
> [root@ambari-slave1 vagrant]# exit
> exit
> [vagrant@ambari-slave1 ~]$ sudo su
> sudo: effective uid is not 0, is sudo installed setuid root?
> {code}
> this is caused due to by function in /usr/sbin/ambari-agent
> {code}
> get_agent_property() {
> property_name="$1"
> value=$(awk -F "=" "/$property_name/ {print \$2}" 
> /etc/ambari-agent/conf/ambari-agent.ini)
> echo $value
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18547) No validation errors recieved for empty or removed hadoop.proxyuser.* properties

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18547:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12831979/AMBARI-18547.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 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

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

{color:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8825//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8825//console

This message is automatically generated.

> No validation errors recieved for empty or removed hadoop.proxyuser.* 
> properties
> 
>
> Key: AMBARI-18547
> URL: https://issues.apache.org/jira/browse/AMBARI-18547
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-18547.patch
>
>
> Steps to reproduce:
> 1) Start install wizard
> 2) Select HDFS, Yarn, Zookeeper
> 3) Navigate to Customize Service page
> 4) Select HDFS and open *Custom core-site* category
> 4) Remove any/all hadoop.proxyuser.* properties , e.g. 
> hadoop.proxyuser.hdfs.groups
> 5) Set empty value for any/all hadoop.proxyuser.*
> 6) Click next
> AR: Validation succeed, {{/api/v1/stacks/HDP/versions/2.5/validations}} 
> request returns no errors or warnings regarding mentioned properties
> ER: Validation error/warning regarding empty and removed hadoop.proxyuser.* 
> properties



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18526) Ambari breaks sudo and user access if Ambari Agent misconfigured

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-18526:

Fix Version/s: (was: 2.5.0)
   2.4.2

> Ambari breaks sudo and user access if Ambari Agent misconfigured
> 
>
> Key: AMBARI-18526
> URL: https://issues.apache.org/jira/browse/AMBARI-18526
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 2.4.2
>
> Attachments: AMBARI-18526.patch
>
>
> While working on Ambari installation using Vagrant I found following issues 
> that can be potentially dangerous and destroy sudo and /home permissions
> Steps to reproduce:
> Remove or misconfigure following configs from ambari-agent.ini file:
> {code}
> [agent]
> logdir=/var/log/ambari-agent
> piddir=/var/run/ambari-agent
> {code}
> Start ambari agent.  Note that log, pid, and out want to be written to /.  
> Everything fails and sudo is destroyed as well as /home for all users.  Sudo 
> user will not be able to connect to cluster using private key due to 
> permissions and folder ownership switch to root.
> {code}
> [root@ambari-slave1 vagrant]# id
> uid=0(root) gid=0(root) groups=0(root)
> [root@ambari-slave1 vagrant]# ambari-agent start
> chown: changing ownership of `/proc/12937': Operation not permitted
> chown: changing ownership of `/proc/12938/task/12938': Operation not permitted
> chown: changing ownership of `/proc/12938': Operation not permitted
> chown: changing ownership of `/proc/12941/task/12941': Operation not permitted
> chown: changing ownership of `/proc/12941': Operation not permitted
> chown: changing ownership of `/proc/12942/task/12942/fd/4': No such file or 
> directory
> chown: changing ownership of `/proc/12942/task/12942/fdinfo/4': No such file 
> or directory
> chown: changing ownership of `/proc/12942/task/12942': Operation not permitted
> chown: changing ownership of `/proc/12942/fd/4': No such file or directory
> chown: changing ownership of `/proc/12942/fdinfo/4': No such file or directory
> chown: changing ownership of `/proc/12942': Operation not permitted
> Starting ambari-agent
> Verifying ambari-agent process status...
> Ambari Agent successfully started
> Agent PID at: /ambari-agent.pid
> Agent out at: /ambari-agent.out
> Agent log at: /ambari-agent.log
> {code}
> Sticky bit is removed from sudo as result of it
> {code}
> [root@ambari-slave1 vagrant]# ls -l /usr/bin/sudo
> ---x--x--x. 1 root root 123832 Oct 15  2014 /usr/bin/sudo
> {code}
> it should be:
> {code}
> [root@ambari-slave2 vagrant]# ls -l /usr/bin/sudo
> ---s--x--x. 1 root root 123832 Oct 15  2014 /usr/bin/sudo
> {code}
> All user folder is messed up as owned by root
> {code}
> [root@ambari-slave1 vagrant]# ls -ld /home/
> drwxr-xr-x. 3 root root 4096 Mar  9  2016 /home/
> [root@ambari-slave1 vagrant]# ls -ld /home/vagrant
> drwx-- 3 root root 4096 Sep 27 22:16 /home/vagrant
> {code}
> sudo is broken:
> {code}
> [root@ambari-slave1 vagrant]# id
> uid=0(root) gid=0(root) groups=0(root)
> [root@ambari-slave1 vagrant]# exit
> exit
> [vagrant@ambari-slave1 ~]$ sudo su
> sudo: effective uid is not 0, is sudo installed setuid root?
> {code}
> this is caused due to by function in /usr/sbin/ambari-agent
> {code}
> get_agent_property() {
> property_name="$1"
> value=$(awk -F "=" "/$property_name/ {print \$2}" 
> /etc/ambari-agent/conf/ambari-agent.ini)
> echo $value
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18549) oozie server start fails post upgrade to Ambari 2.4.1

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18549:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12831985/AMBARI-18549.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 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

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

{color:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8824//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8824//console

This message is automatically generated.

> oozie server start fails post upgrade to Ambari 2.4.1
> -
>
> Key: AMBARI-18549
> URL: https://issues.apache.org/jira/browse/AMBARI-18549
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.2
>
> Attachments: AMBARI-18549.patch
>
>
>   
> **Info**  
> This cluster has gone through below upgrade.  
> Ambari 2.2.2.0 - Ambari 2.4.1  
> Cluster Details :   
> Please login with okta credential to these cluster machines  
> 
> On restarting Oozie web server from Ambari below error was thrown.
> 
> 
> 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 215, in 
> OozieServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 280, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 100, in stop
> oozie_service(action='stop', upgrade_type=upgrade_type)
>   File 
> "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89, 
> in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
>  line 164, in oozie_service
> user = params.oozie_user)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 
> 155, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 71, in inner
> result = function(command, **kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 93, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'cd /var/tmp/oozie 
> && /usr/hdp/current/oozie-server/bin/oozied.sh stop 60 -force' returned 1. 
> -bash: line 0: cd: /var/tmp/oozie: No such file or directory
> 
> We had to workaround this problem by running oozie stop manual as below
> 
> 
> 
> /usr/hdp/2.4.3.0-207/oozie/bin/oozied.sh stop
> 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18548) Declarative Component Log Search Pattern Metadata for Stack Components

[JIRA]

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

Olivér Szabó updated AMBARI-18548:
--
Summary: Declarative Component Log Search Pattern Metadata for Stack 
Components  (was: Declarative Logsearch/Logfeeder Component Metadata for Stack 
Services)

> Declarative Component Log Search Pattern Metadata for Stack Components
> --
>
> Key: AMBARI-18548
> URL: https://issues.apache.org/jira/browse/AMBARI-18548
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18548) Declarative Logsearch/Logfeeder Component Metadata for Stack Services

[JIRA]

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

Olivér Szabó updated AMBARI-18548:
--
Summary: Declarative Logsearch/Logfeeder Component Metadata for Stack 
Services  (was: Use LogSearch metadata inside service stacks instead of on 
LogSearch side)

> Declarative Logsearch/Logfeeder Component Metadata for Stack Services
> -
>
> Key: AMBARI-18548
> URL: https://issues.apache.org/jira/browse/AMBARI-18548
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-logsearch
>Affects Versions: 2.4.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.5.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18549) oozie server start fails post upgrade to Ambari 2.4.1

[Andrew Onischuk (JIRA)]

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

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

Committed to trunk and branch-2.4 and branch-2.5

> oozie server start fails post upgrade to Ambari 2.4.1
> -
>
> Key: AMBARI-18549
> URL: https://issues.apache.org/jira/browse/AMBARI-18549
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.2
>
> Attachments: AMBARI-18549.patch
>
>
>   
> **Info**  
> This cluster has gone through below upgrade.  
> Ambari 2.2.2.0 - Ambari 2.4.1  
> Cluster Details :   
> Please login with okta credential to these cluster machines  
> 
> On restarting Oozie web server from Ambari below error was thrown.
> 
> 
> 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 215, in 
> OozieServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 280, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 100, in stop
> oozie_service(action='stop', upgrade_type=upgrade_type)
>   File 
> "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89, 
> in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
>  line 164, in oozie_service
> user = params.oozie_user)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 
> 155, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 71, in inner
> result = function(command, **kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 93, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'cd /var/tmp/oozie 
> && /usr/hdp/current/oozie-server/bin/oozied.sh stop 60 -force' returned 1. 
> -bash: line 0: cd: /var/tmp/oozie: No such file or directory
> 
> We had to workaround this problem by running oozie stop manual as below
> 
> 
> 
> /usr/hdp/2.4.3.0-207/oozie/bin/oozied.sh stop
> 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18546) BP format does not generate property oozie.service.JPAService.jdbc.url

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18546:


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

This message is automatically generated.

> BP format does not generate property oozie.service.JPAService.jdbc.url
> --
>
> Key: AMBARI-18546
> URL: https://issues.apache.org/jira/browse/AMBARI-18546
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18546.patch
>
>
> STR:
> * Install Ambari 2.4.0.1 with HDP 2.5 and Oozie (using existing MySQL DB).
> * Notice that oozie-site has config,
> {code}
> oozie.service.JPAService.jdbc.url=jdbc:mysql://$SERVER/$oozie.db.schema.name
> {code}
> E.g.,
> jdbc:mysql://c6401.ambari.apache.org/oozie
> * Export the BP,
> api/v1/clusters/c1?format=blueprint
> It doesn't generate the "oozie.service.JPAService.jdbc.url" property, so a 
> user trying to use that blueprint will run into errors.
> Further, setting the value of that property to 
> "jdbc:mysql://%HOSTGROUP::host_group_1%/oozie" does not actually replace it 
> with the hostname, and it should also dynamically replace the Oozie DB name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18545) Kerberos server actions should not timeout in minutes as specified in configuration

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-18545:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12831971/AMBARI-18545_trunk_02.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 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

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

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

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8822//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8822//console

This message is automatically generated.

> Kerberos server actions should not timeout in minutes as specified in 
> configuration
> ---
>
> Key: AMBARI-18545
> URL: https://issues.apache.org/jira/browse/AMBARI-18545
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: kerberos
> Fix For: 2.5.0
>
> Attachments: AMBARI-18545_branch-2.4_01.patch, 
> AMBARI-18545_branch-2.4_02.patch, AMBARI-18545_branch-2.5_01.patch, 
> AMBARI-18545_branch-2.5_02.patch, AMBARI-18545_trunk_01.patch, 
> AMBARI-18545_trunk_02.patch
>
>
> Kerberos related server-side actions should not time out in minutes as 
> specified in configuration.  Some Kerberos-related task can potentially take 
> a much longer time based on number of hosts and components installed in the 
> cluster. 
> The {{Create Principals}} and {{Create Keytab Files}} stages need to be set 
> to a rather large timeout value such that
> {noformat}
> if  server.task.timeout < X 
>   timeout = X;
> else 
>   timeout =  server.task.timeout
> Where X is set to something like 10 hours. 
> {noformat}
> 10 hours seems to be a reasonable timeout value since it is not possible to 
> specified an unlimited amount of time give Ambari's current task processing 
> infrastructure. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18549) oozie server start fails post upgrade to Ambari 2.4.1

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-18549:
-
Attachment: AMBARI-18549.patch

> oozie server start fails post upgrade to Ambari 2.4.1
> -
>
> Key: AMBARI-18549
> URL: https://issues.apache.org/jira/browse/AMBARI-18549
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.2
>
> Attachments: AMBARI-18549.patch
>
>
>   
> **Info**  
> This cluster has gone through below upgrade.  
> Ambari 2.2.2.0 - Ambari 2.4.1  
> Cluster Details :   
> Please login with okta credential to these cluster machines  
> 
> On restarting Oozie web server from Ambari below error was thrown.
> 
> 
> 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 215, in 
> OozieServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 280, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 100, in stop
> oozie_service(action='stop', upgrade_type=upgrade_type)
>   File 
> "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89, 
> in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
>  line 164, in oozie_service
> user = params.oozie_user)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 
> 155, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 71, in inner
> result = function(command, **kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 93, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'cd /var/tmp/oozie 
> && /usr/hdp/current/oozie-server/bin/oozied.sh stop 60 -force' returned 1. 
> -bash: line 0: cd: /var/tmp/oozie: No such file or directory
> 
> We had to workaround this problem by running oozie stop manual as below
> 
> 
> 
> /usr/hdp/2.4.3.0-207/oozie/bin/oozied.sh stop
> 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18549) oozie server start fails post upgrade to Ambari 2.4.1

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk updated AMBARI-18549:
-
Status: Patch Available  (was: Open)

> oozie server start fails post upgrade to Ambari 2.4.1
> -
>
> Key: AMBARI-18549
> URL: https://issues.apache.org/jira/browse/AMBARI-18549
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.2
>
> Attachments: AMBARI-18549.patch
>
>
>   
> **Info**  
> This cluster has gone through below upgrade.  
> Ambari 2.2.2.0 - Ambari 2.4.1  
> Cluster Details :   
> Please login with okta credential to these cluster machines  
> 
> On restarting Oozie web server from Ambari below error was thrown.
> 
> 
> 
> Traceback (most recent call last):
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 215, in 
> OozieServer().execute()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
>  line 280, in execute
> method(env)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
>  line 100, in stop
> oozie_service(action='stop', upgrade_type=upgrade_type)
>   File 
> "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", line 89, 
> in thunk
> return fn(*args, **kwargs)
>   File 
> "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
>  line 164, in oozie_service
> user = params.oozie_user)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 
> 155, in __init__
> self.env.run()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 160, in run
> self.run_action(resource, action)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
> line 124, in run_action
> provider_action()
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
>  line 273, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 71, in inner
> result = function(command, **kwargs)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 93, in checked_call
> tries=tries, try_sleep=try_sleep)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 141, in _call_wrapper
> result = _call(command, **kwargs_copy)
>   File 
> "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 
> 294, in _call
> raise Fail(err_msg)
> resource_management.core.exceptions.Fail: Execution of 'cd /var/tmp/oozie 
> && /usr/hdp/current/oozie-server/bin/oozied.sh stop 60 -force' returned 1. 
> -bash: line 0: cd: /var/tmp/oozie: No such file or directory
> 
> We had to workaround this problem by running oozie stop manual as below
> 
> 
> 
> /usr/hdp/2.4.3.0-207/oozie/bin/oozied.sh stop
> 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-18549) oozie server start fails post upgrade to Ambari 2.4.1

[Andrew Onischuk (JIRA)]

Andrew Onischuk created AMBARI-18549:


 Summary: oozie server start fails post upgrade to Ambari 2.4.1
 Key: AMBARI-18549
 URL: https://issues.apache.org/jira/browse/AMBARI-18549
 Project: Ambari
  Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
 Fix For: 2.4.2
 Attachments: AMBARI-18549.patch

  
**Info**  
This cluster has gone through below upgrade.  
Ambari 2.2.2.0 - Ambari 2.4.1  
Cluster Details :   
Please login with okta credential to these cluster machines  


On restarting Oozie web server from Ambari below error was thrown.




Traceback (most recent call last):
  File 
"/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
 line 215, in 
OozieServer().execute()
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 280, in execute
method(env)
  File 
"/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py",
 line 100, in stop
oozie_service(action='stop', upgrade_type=upgrade_type)
  File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py", 
line 89, in thunk
return fn(*args, **kwargs)
  File 
"/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_service.py",
 line 164, in oozie_service
user = params.oozie_user)
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
line 155, in __init__
self.env.run()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 160, in run
self.run_action(resource, action)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 124, in run_action
provider_action()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
 line 273, in action_run
tries=self.resource.tries, try_sleep=self.resource.try_sleep)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 71, 
in inner
result = function(command, **kwargs)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 93, 
in checked_call
tries=tries, try_sleep=try_sleep)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 141, 
in _call_wrapper
result = _call(command, **kwargs_copy)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/shell.py", line 294, 
in _call
raise Fail(err_msg)
resource_management.core.exceptions.Fail: Execution of 'cd /var/tmp/oozie 
&& /usr/hdp/current/oozie-server/bin/oozied.sh stop 60 -force' returned 1. 
-bash: line 0: cd: /var/tmp/oozie: No such file or directory


We had to workaround this problem by running oozie stop manual as below




/usr/hdp/2.4.3.0-207/oozie/bin/oozied.sh stop






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18532) Getting errors with max length 1000byte, when using Mysql db with charset UTF8

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18532:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #120 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/120/])
AMBARI-18532. Getting errors with max length 1000byte, when using Mysql 
(vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=03cd231f5d212fe7f9152f96a584521e60487bb6])
* (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql


> Getting errors with max length 1000byte, when using Mysql db with charset UTF8
> --
>
> Key: AMBARI-18532
> URL: https://issues.apache.org/jira/browse/AMBARI-18532
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, ambari-upgrade
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18532.patch
>
>
> ERROR 1071 (42000): Specified key was too long; max key length is 1000 bytes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-18548) Use LogSearch metadata inside service stacks instead of on LogSearch side

[JIRA]

Olivér Szabó created AMBARI-18548:
-

 Summary: Use LogSearch metadata inside service stacks instead of 
on LogSearch side
 Key: AMBARI-18548
 URL: https://issues.apache.org/jira/browse/AMBARI-18548
 Project: Ambari
  Issue Type: Bug
  Components: ambari-logsearch
Affects Versions: 2.4.0
Reporter: Olivér Szabó
Assignee: Olivér Szabó
 Fix For: 2.5.0






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18539) Remove Unnecessary Locks Inside Of Host Business Object Implementations

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-18539:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Remove Unnecessary Locks Inside Of Host Business Object Implementations
> ---
>
> Key: AMBARI-18539
> URL: https://issues.apache.org/jira/browse/AMBARI-18539
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18539.patch
>
>
> Many of the business object implementations include needless locks which 
> simply add the overhead and contention in larger clusters. Some examples of 
> these are :
> - HostImpl
> -- get/set DisksInfo()
> -- get/set TotalMemBytes()
> - ServiceComponentHostImpl
> -- get/set MaintenanceState()
> -- get/set LastOpLastUpdateTime()
> These types of methods are found on other business classes as well, like 
> {{ClusterImpl}} and {{ServiceImpl}}. Additionally, methods like 
> {{convertToResponse()}} and {{debugDump()}} need not acquire locks since they 
> are used mostly for serialization of data to the web client where the data 
> will then immediately become stale anyway.
> The {{Host}} business object should have the following work performed:
> - Remove locking around areas where its no longer required
> - Replace collections with thread-safe concurrent versions
> - Remove some reliance on state-full business objects (caches)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18539) Remove Unnecessary Locks Inside Of Host Business Object Implementations

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-18539:
-
Status: Patch Available  (was: Open)

> Remove Unnecessary Locks Inside Of Host Business Object Implementations
> ---
>
> Key: AMBARI-18539
> URL: https://issues.apache.org/jira/browse/AMBARI-18539
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18539.patch
>
>
> Many of the business object implementations include needless locks which 
> simply add the overhead and contention in larger clusters. Some examples of 
> these are :
> - HostImpl
> -- get/set DisksInfo()
> -- get/set TotalMemBytes()
> - ServiceComponentHostImpl
> -- get/set MaintenanceState()
> -- get/set LastOpLastUpdateTime()
> These types of methods are found on other business classes as well, like 
> {{ClusterImpl}} and {{ServiceImpl}}. Additionally, methods like 
> {{convertToResponse()}} and {{debugDump()}} need not acquire locks since they 
> are used mostly for serialization of data to the web client where the data 
> will then immediately become stale anyway.
> The {{Host}} business object should have the following work performed:
> - Remove locking around areas where its no longer required
> - Replace collections with thread-safe concurrent versions
> - Remove some reliance on state-full business objects (caches)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18539) Remove Unnecessary Locks Inside Of Host Business Object Implementations

[Jonathan Hurley (JIRA)]

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

Jonathan Hurley updated AMBARI-18539:
-
Attachment: AMBARI-18539.patch

> Remove Unnecessary Locks Inside Of Host Business Object Implementations
> ---
>
> Key: AMBARI-18539
> URL: https://issues.apache.org/jira/browse/AMBARI-18539
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18539.patch
>
>
> Many of the business object implementations include needless locks which 
> simply add the overhead and contention in larger clusters. Some examples of 
> these are :
> - HostImpl
> -- get/set DisksInfo()
> -- get/set TotalMemBytes()
> - ServiceComponentHostImpl
> -- get/set MaintenanceState()
> -- get/set LastOpLastUpdateTime()
> These types of methods are found on other business classes as well, like 
> {{ClusterImpl}} and {{ServiceImpl}}. Additionally, methods like 
> {{convertToResponse()}} and {{debugDump()}} need not acquire locks since they 
> are used mostly for serialization of data to the web client where the data 
> will then immediately become stale anyway.
> The {{Host}} business object should have the following work performed:
> - Remove locking around areas where its no longer required
> - Replace collections with thread-safe concurrent versions
> - Remove some reliance on state-full business objects (caches)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18547) No validation errors recieved for empty or removed hadoop.proxyuser.* properties

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-18547:

Affects Version/s: 2.4.0

> No validation errors recieved for empty or removed hadoop.proxyuser.* 
> properties
> 
>
> Key: AMBARI-18547
> URL: https://issues.apache.org/jira/browse/AMBARI-18547
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-18547.patch
>
>
> Steps to reproduce:
> 1) Start install wizard
> 2) Select HDFS, Yarn, Zookeeper
> 3) Navigate to Customize Service page
> 4) Select HDFS and open *Custom core-site* category
> 4) Remove any/all hadoop.proxyuser.* properties , e.g. 
> hadoop.proxyuser.hdfs.groups
> 5) Set empty value for any/all hadoop.proxyuser.*
> 6) Click next
> AR: Validation succeed, {{/api/v1/stacks/HDP/versions/2.5/validations}} 
> request returns no errors or warnings regarding mentioned properties
> ER: Validation error/warning regarding empty and removed hadoop.proxyuser.* 
> properties



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18547) No validation errors recieved for empty or removed hadoop.proxyuser.* properties

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-18547:

Fix Version/s: 3.0.0

> No validation errors recieved for empty or removed hadoop.proxyuser.* 
> properties
> 
>
> Key: AMBARI-18547
> URL: https://issues.apache.org/jira/browse/AMBARI-18547
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Fix For: 3.0.0
>
> Attachments: AMBARI-18547.patch
>
>
> Steps to reproduce:
> 1) Start install wizard
> 2) Select HDFS, Yarn, Zookeeper
> 3) Navigate to Customize Service page
> 4) Select HDFS and open *Custom core-site* category
> 4) Remove any/all hadoop.proxyuser.* properties , e.g. 
> hadoop.proxyuser.hdfs.groups
> 5) Set empty value for any/all hadoop.proxyuser.*
> 6) Click next
> AR: Validation succeed, {{/api/v1/stacks/HDP/versions/2.5/validations}} 
> request returns no errors or warnings regarding mentioned properties
> ER: Validation error/warning regarding empty and removed hadoop.proxyuser.* 
> properties



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18547) No validation errors recieved for empty or removed hadoop.proxyuser.* properties

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-18547:

Attachment: AMBARI-18547.patch

> No validation errors recieved for empty or removed hadoop.proxyuser.* 
> properties
> 
>
> Key: AMBARI-18547
> URL: https://issues.apache.org/jira/browse/AMBARI-18547
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-18547.patch
>
>
> Steps to reproduce:
> 1) Start install wizard
> 2) Select HDFS, Yarn, Zookeeper
> 3) Navigate to Customize Service page
> 4) Select HDFS and open *Custom core-site* category
> 4) Remove any/all hadoop.proxyuser.* properties , e.g. 
> hadoop.proxyuser.hdfs.groups
> 5) Set empty value for any/all hadoop.proxyuser.*
> 6) Click next
> AR: Validation succeed, {{/api/v1/stacks/HDP/versions/2.5/validations}} 
> request returns no errors or warnings regarding mentioned properties
> ER: Validation error/warning regarding empty and removed hadoop.proxyuser.* 
> properties



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18547) No validation errors recieved for empty or removed hadoop.proxyuser.* properties

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-18547:

Component/s: ambari-server

> No validation errors recieved for empty or removed hadoop.proxyuser.* 
> properties
> 
>
> Key: AMBARI-18547
> URL: https://issues.apache.org/jira/browse/AMBARI-18547
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-18547.patch
>
>
> Steps to reproduce:
> 1) Start install wizard
> 2) Select HDFS, Yarn, Zookeeper
> 3) Navigate to Customize Service page
> 4) Select HDFS and open *Custom core-site* category
> 4) Remove any/all hadoop.proxyuser.* properties , e.g. 
> hadoop.proxyuser.hdfs.groups
> 5) Set empty value for any/all hadoop.proxyuser.*
> 6) Click next
> AR: Validation succeed, {{/api/v1/stacks/HDP/versions/2.5/validations}} 
> request returns no errors or warnings regarding mentioned properties
> ER: Validation error/warning regarding empty and removed hadoop.proxyuser.* 
> properties



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18547) No validation errors recieved for empty or removed hadoop.proxyuser.* properties

[Dmitry Lysnichenko (JIRA)]

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

Dmitry Lysnichenko updated AMBARI-18547:

Status: Patch Available  (was: Open)

> No validation errors recieved for empty or removed hadoop.proxyuser.* 
> properties
> 
>
> Key: AMBARI-18547
> URL: https://issues.apache.org/jira/browse/AMBARI-18547
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Dmitry Lysnichenko
>Assignee: Dmitry Lysnichenko
> Attachments: AMBARI-18547.patch
>
>
> Steps to reproduce:
> 1) Start install wizard
> 2) Select HDFS, Yarn, Zookeeper
> 3) Navigate to Customize Service page
> 4) Select HDFS and open *Custom core-site* category
> 4) Remove any/all hadoop.proxyuser.* properties , e.g. 
> hadoop.proxyuser.hdfs.groups
> 5) Set empty value for any/all hadoop.proxyuser.*
> 6) Click next
> AR: Validation succeed, {{/api/v1/stacks/HDP/versions/2.5/validations}} 
> request returns no errors or warnings regarding mentioned properties
> ER: Validation error/warning regarding empty and removed hadoop.proxyuser.* 
> properties



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-18547) No validation errors recieved for empty or removed hadoop.proxyuser.* properties

[Dmitry Lysnichenko (JIRA)]

Dmitry Lysnichenko created AMBARI-18547:
---

 Summary: No validation errors recieved for empty or removed 
hadoop.proxyuser.* properties
 Key: AMBARI-18547
 URL: https://issues.apache.org/jira/browse/AMBARI-18547
 Project: Ambari
  Issue Type: Bug
Reporter: Dmitry Lysnichenko
Assignee: Dmitry Lysnichenko
 Attachments: AMBARI-18547.patch


Steps to reproduce:
1) Start install wizard
2) Select HDFS, Yarn, Zookeeper
3) Navigate to Customize Service page
4) Select HDFS and open *Custom core-site* category
4) Remove any/all hadoop.proxyuser.* properties , e.g. 
hadoop.proxyuser.hdfs.groups
5) Set empty value for any/all hadoop.proxyuser.*
6) Click next

AR: Validation succeed, {{/api/v1/stacks/HDP/versions/2.5/validations}} request 
returns no errors or warnings regarding mentioned properties
ER: Validation error/warning regarding empty and removed hadoop.proxyuser.* 
properties




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18540) Unit test cases required for verifying Ambari username case sensitivity

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-18540:
---
Status: Patch Available  (was: Open)

> Unit test cases required for verifying Ambari username case sensitivity
> ---
>
> Key: AMBARI-18540
> URL: https://issues.apache.org/jira/browse/AMBARI-18540
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0, 2.4.2
>
> Attachments: rb52586.patch
>
>
> Unit Tests are required to cover these scenarios:
> 1. Ensure that usernames are persisted as provided by verifying that PUT and 
> GET match.
> 2. Usernames that differ only by case should match



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18540) Unit test cases required for verifying Ambari username case sensitivity

[Nahappan Somasundaram (JIRA)]

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

Nahappan Somasundaram updated AMBARI-18540:
---
Status: Open  (was: Patch Available)

> Unit test cases required for verifying Ambari username case sensitivity
> ---
>
> Key: AMBARI-18540
> URL: https://issues.apache.org/jira/browse/AMBARI-18540
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0, 2.4.2
>
> Attachments: rb52586.patch
>
>
> Unit Tests are required to cover these scenarios:
> 1. Ensure that usernames are persisted as provided by verifying that PUT and 
> GET match.
> 2. Usernames that differ only by case should match



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AMBARI-18544) Update repo base urls for HDP-2.6 stack

[Sumit Mohanty (JIRA)]

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

Sumit Mohanty resolved AMBARI-18544.

Resolution: Fixed

> Update repo base urls for HDP-2.6 stack
> ---
>
> Key: AMBARI-18544
> URL: https://issues.apache.org/jira/browse/AMBARI-18544
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.5.0
>Reporter: Sumit Mohanty
>Assignee: Sumit Mohanty
> Fix For: 2.5.0
>
> Attachments: AMBARI-18544.patch
>
>
> Update repo base urls for HDP-2.6 stack



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18516) Add ability to have services declare itself as tech-preview or mandatory

[Vitaly Brodetskyi (JIRA)]

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

Vitaly Brodetskyi updated AMBARI-18516:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2.5

> Add ability to have services declare itself as tech-preview or mandatory
> 
>
> Key: AMBARI-18516
> URL: https://issues.apache.org/jira/browse/AMBARI-18516
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18516.patch
>
>
> When a service is added to a stack, it should be identified as:
> default/regular - service is optional on the cluster, UI usually shows it as
> tech-preview - service may be deployed, UI will not auto-select these 
> services and mark them as TechPreview
> mandatory - service need to be deployed and all deployment should fail is the 
> service is not selected during deployment
> Lets create a proposal of what changes are needed in the services' 
> metainfo.xml? Note that a service can change its attribute between stack 
> versions - e.g. move from "tech-preview" to "mandatory".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18545) Kerberos server actions should not timeout in minutes as specified in configuration

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-18545:
--
Attachment: AMBARI-18545_trunk_02.patch
AMBARI-18545_branch-2.5_02.patch
AMBARI-18545_branch-2.4_02.patch

> Kerberos server actions should not timeout in minutes as specified in 
> configuration
> ---
>
> Key: AMBARI-18545
> URL: https://issues.apache.org/jira/browse/AMBARI-18545
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: kerberos
> Fix For: 2.5.0
>
> Attachments: AMBARI-18545_branch-2.4_01.patch, 
> AMBARI-18545_branch-2.4_02.patch, AMBARI-18545_branch-2.5_01.patch, 
> AMBARI-18545_branch-2.5_02.patch, AMBARI-18545_trunk_01.patch, 
> AMBARI-18545_trunk_02.patch
>
>
> Kerberos related server-side actions should not time out in minutes as 
> specified in configuration.  Some Kerberos-related task can potentially take 
> a much longer time based on number of hosts and components installed in the 
> cluster. 
> The {{Create Principals}} and {{Create Keytab Files}} stages need to be set 
> to a rather large timeout value such that
> {noformat}
> if  server.task.timeout < X 
>   timeout = X;
> else 
>   timeout =  server.task.timeout
> Where X is set to something like 10 hours. 
> {noformat}
> 10 hours seems to be a reasonable timeout value since it is not possible to 
> specified an unlimited amount of time give Ambari's current task processing 
> infrastructure. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18532) Getting errors with max length 1000byte, when using Mysql db with charset UTF8

[Vitaly Brodetskyi (JIRA)]

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

Vitaly Brodetskyi updated AMBARI-18532:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

Committed to trunk, branch-2.5, branch-2.4

> Getting errors with max length 1000byte, when using Mysql db with charset UTF8
> --
>
> Key: AMBARI-18532
> URL: https://issues.apache.org/jira/browse/AMBARI-18532
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, ambari-upgrade
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18532.patch
>
>
> ERROR 1071 (42000): Specified key was too long; max key length is 1000 bytes



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18546) BP format does not generate property oozie.service.JPAService.jdbc.url

[Vitaly Brodetskyi (JIRA)]

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

Vitaly Brodetskyi updated AMBARI-18546:
---
Attachment: AMBARI-18546.patch

> BP format does not generate property oozie.service.JPAService.jdbc.url
> --
>
> Key: AMBARI-18546
> URL: https://issues.apache.org/jira/browse/AMBARI-18546
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18546.patch
>
>
> STR:
> * Install Ambari 2.4.0.1 with HDP 2.5 and Oozie (using existing MySQL DB).
> * Notice that oozie-site has config,
> {code}
> oozie.service.JPAService.jdbc.url=jdbc:mysql://$SERVER/$oozie.db.schema.name
> {code}
> E.g.,
> jdbc:mysql://c6401.ambari.apache.org/oozie
> * Export the BP,
> api/v1/clusters/c1?format=blueprint
> It doesn't generate the "oozie.service.JPAService.jdbc.url" property, so a 
> user trying to use that blueprint will run into errors.
> Further, setting the value of that property to 
> "jdbc:mysql://%HOSTGROUP::host_group_1%/oozie" does not actually replace it 
> with the hostname, and it should also dynamically replace the Oozie DB name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18545) Kerberos server actions should not timeout in minutes as specified in configuration

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-18545:
--
Attachment: AMBARI-18545_trunk_01.patch
AMBARI-18545_branch-2.5_01.patch
AMBARI-18545_branch-2.4_01.patch

> Kerberos server actions should not timeout in minutes as specified in 
> configuration
> ---
>
> Key: AMBARI-18545
> URL: https://issues.apache.org/jira/browse/AMBARI-18545
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: kerberos
> Fix For: 2.5.0
>
> Attachments: AMBARI-18545_branch-2.4_01.patch, 
> AMBARI-18545_branch-2.5_01.patch, AMBARI-18545_trunk_01.patch
>
>
> Kerberos related server-side actions should not time out in minutes as 
> specified in configuration.  Some Kerberos-related task can potentially take 
> a much longer time based on number of hosts and components installed in the 
> cluster. 
> The {{Create Principals}} and {{Create Keytab Files}} stages need to be set 
> to a rather large timeout value such that
> {noformat}
> if  server.task.timeout < X 
>   timeout = X;
> else 
>   timeout =  server.task.timeout
> Where X is set to something like 10 hours. 
> {noformat}
> 10 hours seems to be a reasonable timeout value since it is not possible to 
> specified an unlimited amount of time give Ambari's current task processing 
> infrastructure. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18546) BP format does not generate property oozie.service.JPAService.jdbc.url

[Vitaly Brodetskyi (JIRA)]

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

Vitaly Brodetskyi updated AMBARI-18546:
---
Status: Patch Available  (was: Open)

> BP format does not generate property oozie.service.JPAService.jdbc.url
> --
>
> Key: AMBARI-18546
> URL: https://issues.apache.org/jira/browse/AMBARI-18546
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18546.patch
>
>
> STR:
> * Install Ambari 2.4.0.1 with HDP 2.5 and Oozie (using existing MySQL DB).
> * Notice that oozie-site has config,
> {code}
> oozie.service.JPAService.jdbc.url=jdbc:mysql://$SERVER/$oozie.db.schema.name
> {code}
> E.g.,
> jdbc:mysql://c6401.ambari.apache.org/oozie
> * Export the BP,
> api/v1/clusters/c1?format=blueprint
> It doesn't generate the "oozie.service.JPAService.jdbc.url" property, so a 
> user trying to use that blueprint will run into errors.
> Further, setting the value of that property to 
> "jdbc:mysql://%HOSTGROUP::host_group_1%/oozie" does not actually replace it 
> with the hostname, and it should also dynamically replace the Oozie DB name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18545) Kerberos server actions should not timeout in minutes as specified in configuration

[Robert Levas (JIRA)]

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

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

> Kerberos server actions should not timeout in minutes as specified in 
> configuration
> ---
>
> Key: AMBARI-18545
> URL: https://issues.apache.org/jira/browse/AMBARI-18545
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.2
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: kerberos
> Fix For: 2.5.0
>
> Attachments: AMBARI-18545_branch-2.4_01.patch, 
> AMBARI-18545_branch-2.5_01.patch, AMBARI-18545_trunk_01.patch
>
>
> Kerberos related server-side actions should not time out in minutes as 
> specified in configuration.  Some Kerberos-related task can potentially take 
> a much longer time based on number of hosts and components installed in the 
> cluster. 
> The {{Create Principals}} and {{Create Keytab Files}} stages need to be set 
> to a rather large timeout value such that
> {noformat}
> if  server.task.timeout < X 
>   timeout = X;
> else 
>   timeout =  server.task.timeout
> Where X is set to something like 10 hours. 
> {noformat}
> 10 hours seems to be a reasonable timeout value since it is not possible to 
> specified an unlimited amount of time give Ambari's current task processing 
> infrastructure. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-18546) BP format does not generate property oozie.service.JPAService.jdbc.url

[Vitaly Brodetskyi (JIRA)]

Vitaly Brodetskyi created AMBARI-18546:
--

 Summary: BP format does not generate property 
oozie.service.JPAService.jdbc.url
 Key: AMBARI-18546
 URL: https://issues.apache.org/jira/browse/AMBARI-18546
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Critical
 Fix For: 2.5.0


STR:
* Install Ambari 2.4.0.1 with HDP 2.5 and Oozie (using existing MySQL DB).
* Notice that oozie-site has config,
{code}
oozie.service.JPAService.jdbc.url=jdbc:mysql://$SERVER/$oozie.db.schema.name
{code}
E.g.,
jdbc:mysql://c6401.ambari.apache.org/oozie
* Export the BP,
api/v1/clusters/c1?format=blueprint

It doesn't generate the "oozie.service.JPAService.jdbc.url" property, so a user 
trying to use that blueprint will run into errors.
Further, setting the value of that property to 
"jdbc:mysql://%HOSTGROUP::host_group_1%/oozie" does not actually replace it 
with the hostname, and it should also dynamically replace the Oozie DB name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (AMBARI-18545) Kerberos server actions should not timeout in minutes as specified in configuration

[Robert Levas (JIRA)]

Robert Levas created AMBARI-18545:
-

 Summary: Kerberos server actions should not timeout in minutes as 
specified in configuration
 Key: AMBARI-18545
 URL: https://issues.apache.org/jira/browse/AMBARI-18545
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.2.2
Reporter: Robert Levas
Assignee: Robert Levas
 Fix For: 2.5.0


Kerberos related server-side actions should not time out in minutes as 
specified in configuration.  Some Kerberos-related task can potentially take a 
much longer time based on number of hosts and components installed in the 
cluster. 

The {{Create Principals}} and {{Create Keytab Files}} stages need to be set to 
a rather large timeout value such that

{noformat}
if  server.task.timeout < X 
  timeout = X;
else 
  timeout =  server.task.timeout

Where X is set to something like 10 hours. 
{noformat}

10 hours seems to be a reasonable timeout value since it is not possible to 
specified an unlimited amount of time give Ambari's current task processing 
infrastructure. 





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18521) Stack upgrade fix for Ranger in secure env

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18521:
-

ABORTED: Integrated in Jenkins build Ambari-trunk-Commit #5769 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5769/])
AMBARI-18521. Stack upgrade fix for Ranger in secure env (mugdha) (mugdha: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=bce5dbe3eacda9d35e645a776f1f9aa3edf06e9c])
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/RangerKerberosConfigCalculation.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/RangerKerberosConfigCalculationTest.java


> Stack upgrade fix for Ranger in secure env
> --
>
> Key: AMBARI-18521
> URL: https://issues.apache.org/jira/browse/AMBARI-18521
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0, 2.4.1
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-18521.1.patch, AMBARI-18521.patch
>
>
> Stack changes required while upgrading to 2.5 in secure env
> * Remove adding spnego principal value to 
> ranger-admin-site/ranger.spnego.kerberos.principal
> * Get storm principal bare name and update it accordingly to 
> ranger-admin-site.xml/ranger.plugins.storm.serviceuser



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18515) Write unittests for configs.py

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18515:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #119 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/119/])
AMBARI-18515. Write unittests for configs.py (aonishuk) (aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=801526f7d6ec137d7fea60ce71fb3be49043f9a5])
* (edit) ambari-server/src/test/python/TestConfigs.py
* (add) ambari-server/src/test/resources/TestConfigs-content.xml
* (edit) ambari-server/src/main/resources/scripts/configs.py


> Write unittests for configs.py
> --
>
> Key: AMBARI-18515
> URL: https://issues.apache.org/jira/browse/AMBARI-18515
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-18515.patch
>
>
> Write/update unittests for configs.py script.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (AMBARI-18515) Write unittests for configs.py

[Andrew Onischuk (JIRA)]

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

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

Committed to branch-2.5

> Write unittests for configs.py
> --
>
> Key: AMBARI-18515
> URL: https://issues.apache.org/jira/browse/AMBARI-18515
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-18515.patch
>
>
> Write/update unittests for configs.py script.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18515) Write unittests for configs.py

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk commented on AMBARI-18515:
--

This patch is only meant for branch-2.5, not trunk. That's why Hadoop QA failed 
here.
For me it was fine:
{noformat}
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 
approved: 148 licence.
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Ambari Views .. SUCCESS [1.999s]
[INFO] Ambari Metrics Common . SUCCESS [1.241s]
[INFO] Ambari Server . SUCCESS [1:12.578s]
[INFO] Ambari Agent .. SUCCESS [12.108s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 1:28.761s
[INFO] Finished at: Thu Oct 06 09:42:03 EEST 2016
[INFO] Final Memory: 65M/1173M
[INFO] 
{noformat}

> Write unittests for configs.py
> --
>
> Key: AMBARI-18515
> URL: https://issues.apache.org/jira/browse/AMBARI-18515
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-18515.patch
>
>
> Write/update unittests for configs.py script.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18521) Stack upgrade fix for Ranger in secure env

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18521:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #118 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/118/])
AMBARI-18521. Stack upgrade fix for Ranger in secure env (mugdha) (mugdha: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c4918d2b1f6c3884e8900ccc6352b5f861dd5253])
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/serveraction/upgrades/RangerKerberosConfigCalculationTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/RangerKerberosConfigCalculation.java


> Stack upgrade fix for Ranger in secure env
> --
>
> Key: AMBARI-18521
> URL: https://issues.apache.org/jira/browse/AMBARI-18521
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0, 2.4.1
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-18521.1.patch, AMBARI-18521.patch
>
>
> Stack changes required while upgrading to 2.5 in secure env
> * Remove adding spnego principal value to 
> ranger-admin-site/ranger.spnego.kerberos.principal
> * Get storm principal bare name and update it accordingly to 
> ranger-admin-site.xml/ranger.plugins.storm.serviceuser



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMBARI-18536) Components can't be started because of failed webhdfs request

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18536:
-

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5768 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5768/])
AMBARI-18536. Components can't be started because of failed webhdfs (aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=8b6e45e6220bd0304f3ce1cda1b7245ebb322669])
* (edit) 
ambari-common/src/main/python/resource_management/libraries/providers/hdfs_resource.py


> Components can't be started because of failed webhdfs request
> -
>
> Key: AMBARI-18536
> URL: https://issues.apache.org/jira/browse/AMBARI-18536
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-18536.patch
>
>
> Different components fail to start, for instance:
> 
> 
> 
> Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py\",
>  line 182, in \nHistoryServer().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 219, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py\",
>  line 100, in start\nhost_sys_prepped=params.host_sys_prepped)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/copy_tarball.py\",
>  line 204, in copy_to_hdfs\n
> replace_existing_files=replace_existing_files,\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line 
> 154, in __init__\nself.env.run()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 160, in run\nself.run_action(resource, action)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 124, in run_action\nprovider_action()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py\",
>  line 463, in action_create_on_execute\nself.action_delayed(\"create\")\n 
>  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py\",
>  line 460, in action_delayed\n
> self.get_hdfs_resource_executor().action_delayed(action_name, self)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py\",
>  line 258, in action_delayed\nself._create_resource()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py\",
>  line 272, in _create_resource\n
> self._create_file(self.main_resource.resource.target, 
> source=self.main_resource.resource.source, mode=self.mode)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py\",
>  line 325, in _create_file\nself.util.run_command(target, 'CREATE', 
> method='PUT', overwrite=True, assertable_result=False, file_to_put=source, 
> **kwargs)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py\",
>  line 182, in run_command\n_, out, err = get_user_call_output(cmd, 
> user=self.run_user, logoutput=self.logoutput, quiet=False)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py\",
>  line 61, in get_user_call_output\nraise 
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of 'curl 
> -sS -L -w '%{http_code}' -X PUT --data-binary 
> @/usr/hdp/2.4.3.0-227/hadoop/mapreduce.tar.gz --negotiate -u : 
> 'http://nat-r6-tzrs-ambari-alerts-1.openstacklocal:50070/webhdfs/v1/hdp/apps/2.4.3.0-227/mapreduce/mapreduce.tar.gz?op=CREATE=cstm-hdfs=True=444'
>  1>/tmp/tmpNxSlRa 2>/tmp/tmpXlLRgB' returned 52. curl: (52) Empty reply from 
> server\n100
> 
> 
> 
> Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_server.py\",
>  line 165, in \nFalconServer().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 219, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_server.py\",
>  line 46, in start\nself.configure(env, upgrade_type=upgrade_type)\n  
> File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_server.py\",
>  line 41, in configure\nfalcon('server', action='config', 
> upgrade_type=upgrade_type)\n  File 
> 

[jira] [Commented] (AMBARI-18536) Components can't be started because of failed webhdfs request

[Hudson (JIRA)]

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

Hudson commented on AMBARI-18536:
-

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #117 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/117/])
AMBARI-18536. Components can't be started because of failed webhdfs (aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=be9ae725c1687ef04eecf1c228c822cab709d97a])
* (edit) 
ambari-common/src/main/python/resource_management/libraries/providers/hdfs_resource.py


> Components can't be started because of failed webhdfs request
> -
>
> Key: AMBARI-18536
> URL: https://issues.apache.org/jira/browse/AMBARI-18536
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-18536.patch
>
>
> Different components fail to start, for instance:
> 
> 
> 
> Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py\",
>  line 182, in \nHistoryServer().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 219, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/YARN/2.1.0.2.0/package/scripts/historyserver.py\",
>  line 100, in start\nhost_sys_prepped=params.host_sys_prepped)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/copy_tarball.py\",
>  line 204, in copy_to_hdfs\n
> replace_existing_files=replace_existing_files,\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/base.py\", line 
> 154, in __init__\nself.env.run()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 160, in run\nself.run_action(resource, action)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 124, in run_action\nprovider_action()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py\",
>  line 463, in action_create_on_execute\nself.action_delayed(\"create\")\n 
>  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py\",
>  line 460, in action_delayed\n
> self.get_hdfs_resource_executor().action_delayed(action_name, self)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py\",
>  line 258, in action_delayed\nself._create_resource()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py\",
>  line 272, in _create_resource\n
> self._create_file(self.main_resource.resource.target, 
> source=self.main_resource.resource.source, mode=self.mode)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py\",
>  line 325, in _create_file\nself.util.run_command(target, 'CREATE', 
> method='PUT', overwrite=True, assertable_result=False, file_to_put=source, 
> **kwargs)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/providers/hdfs_resource.py\",
>  line 182, in run_command\n_, out, err = get_user_call_output(cmd, 
> user=self.run_user, logoutput=self.logoutput, quiet=False)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/functions/get_user_call_output.py\",
>  line 61, in get_user_call_output\nraise 
> Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of 'curl 
> -sS -L -w '%{http_code}' -X PUT --data-binary 
> @/usr/hdp/2.4.3.0-227/hadoop/mapreduce.tar.gz --negotiate -u : 
> 'http://nat-r6-tzrs-ambari-alerts-1.openstacklocal:50070/webhdfs/v1/hdp/apps/2.4.3.0-227/mapreduce/mapreduce.tar.gz?op=CREATE=cstm-hdfs=True=444'
>  1>/tmp/tmpNxSlRa 2>/tmp/tmpXlLRgB' returned 52. curl: (52) Empty reply from 
> server\n100
> 
> 
> 
> Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_server.py\",
>  line 165, in \nFalconServer().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 219, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_server.py\",
>  line 46, in start\nself.configure(env, upgrade_type=upgrade_type)\n  
> File 
> \"/var/lib/ambari-agent/cache/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_server.py\",
>  line 41, in configure\nfalcon('server', action='config', 
> upgrade_type=upgrade_type)\n  File 
> 

[jira] [Commented] (AMBARI-18521) Stack upgrade fix for Ranger in secure env

[Mugdha Varadkar (JIRA)]

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

Mugdha Varadkar commented on AMBARI-18521:
--

Committed to trunk: 
https://github.com/apache/ambari/commit/bce5dbe3eacda9d35e645a776f1f9aa3edf06e9c
branch-2.5: 
https://github.com/apache/ambari/commit/c4918d2b1f6c3884e8900ccc6352b5f861dd5253

> Stack upgrade fix for Ranger in secure env
> --
>
> Key: AMBARI-18521
> URL: https://issues.apache.org/jira/browse/AMBARI-18521
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0, 2.4.1
>Reporter: Mugdha Varadkar
>Assignee: Mugdha Varadkar
>Priority: Critical
> Fix For: 2.5.0, 2.4.2
>
> Attachments: AMBARI-18521.1.patch, AMBARI-18521.patch
>
>
> Stack changes required while upgrading to 2.5 in secure env
> * Remove adding spnego principal value to 
> ranger-admin-site/ranger.spnego.kerberos.principal
> * Get storm principal bare name and update it accordingly to 
> ranger-admin-site.xml/ranger.plugins.storm.serviceuser



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)