You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by Robert Levas <rl...@hortonworks.com> on 2015/01/04 14:21:03 UTC
Review Request 29568: MapReduce service components should indicate
security state
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/29568/
-----------------------------------------------------------
Review request for Ambari, Alejandro Fernandez, Andrew Onischuk, Jaimin Jetly, and Yusaku Sako.
Bugs: AMBARI-8795
https://issues.apache.org/jira/browse/AMBARI-8795
Repository: ambari
Description
-------
The MAPREDUCE2 service components should indicate security state when queried by Ambari Agent via STATUS_COMMAND.
Diffs
-----
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/YARN/package/scripts/historyserver.py d2b6ee3
ambari-server/src/main/resources/stacks/HDP/2.0.6/services/YARN/package/scripts/status_params.py 498a885
ambari-server/src/test/python/stacks/2.0.6/YARN/test_historyserver.py b759de6
Diff: https://reviews.apache.org/r/29568/diff/
Testing
-------
Manual testing in test cluster
Added unit test
#Jenkins test results:
OK
Running tests for stack:2.0.6 service:YARN
test_configure_default (test_mapreduce2_client.TestMapReduce2Client) ... ok
test_configure_secured (test_mapreduce2_client.TestMapReduce2Client) ... ok
test_upgrade (test_mapreduce2_client.TestMapReduce2Client) ... ok
test_service_check_default (test_mapreduce2_service_check.TestServiceCheck) ... ok
test_service_check_secured (test_mapreduce2_service_check.TestServiceCheck) ... ok
test_configure_default (test_historyserver.TestHistoryServer) ... ok
test_configure_secured (test_historyserver.TestHistoryServer) ... ok
**test_security_status (test_historyserver.TestHistoryServer) ... ok**
test_start_default (test_historyserver.TestHistoryServer) ... 2015-01-04 03:18:11,142 - Did not find mapreduce tar source file and destination folder properties in cluster-env.xml
2015-01-04 03:18:11,143 - Could not retrieve properties for tarball with prefix: mapreduce
ok
test_start_secured (test_historyserver.TestHistoryServer) ... 2015-01-04 03:18:11,182 - Did not find mapreduce tar source file and destination folder properties in cluster-env.xml
2015-01-04 03:18:11,182 - Could not retrieve properties for tarball with prefix: mapreduce
ok
test_stop_default (test_historyserver.TestHistoryServer) ... ok
test_stop_secured (test_historyserver.TestHistoryServer) ... ok
test_service_check_default (test_yarn_service_check.TestServiceCheck) ... ok
test_service_check_secured (test_yarn_service_check.TestServiceCheck) ... ok
test_configure_default (test_yarn_client.TestYarnClient) ... ok
test_configure_secured (test_yarn_client.TestYarnClient) ... ok
test_restart_client (test_yarn_client.TestYarnClient) ... ok
test_upgrade (test_yarn_client.TestYarnClient) ... ok
test_configure_default (test_nodemanager.TestNodeManager) ... ok
test_configure_secured (test_nodemanager.TestNodeManager) ... ok
test_post_rolling_restart (test_nodemanager.TestNodeManager) ... 2015-01-04 03:18:11,463 - Executing NodeManager Rolling Upgrade post-restart
2015-01-04 03:18:11,467 - NodeManager executing "yarn node -list -states=RUNNING" to verify the node has rejoined the cluster...
2015-01-04 03:18:11,467 - NodeManager with ID c6401.ambari.apache.org:45454 has rejoined the cluster.
ok
test_post_rolling_restart_nodemanager_not_ready (test_nodemanager.TestNodeManager) ... 2015-01-04 03:18:11,472 - Executing NodeManager Rolling Upgrade post-restart
2015-01-04 03:18:11,477 - NodeManager executing "yarn node -list -states=RUNNING" to verify the node has rejoined the cluster...
2015-01-04 03:18:11,477 - Will retry 11 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
2015-01-04 03:18:11,477 - Will retry 10 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
2015-01-04 03:18:11,477 - Will retry 9 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
2015-01-04 03:18:11,478 - Will retry 8 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
2015-01-04 03:18:11,478 - Will retry 7 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
2015-01-04 03:18:11,478 - Will retry 6 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
2015-01-04 03:18:11,478 - Will retry 5 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
2015-01-04 03:18:11,478 - Will retry 4 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
2015-01-04 03:18:11,478 - Will retry 3 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
2015-01-04 03:18:11,479 - Will retry 2 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
2015-01-04 03:18:11,479 - Will retry 1 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
ok
test_start_default (test_nodemanager.TestNodeManager) ... ok
test_start_secured (test_nodemanager.TestNodeManager) ... ok
test_stop_default (test_nodemanager.TestNodeManager) ... ok
test_stop_secured (test_nodemanager.TestNodeManager) ... ok
test_configure_default (test_resourcemanager.TestResourceManager) ... ok
test_configure_secured (test_resourcemanager.TestResourceManager) ... ok
test_decommission_default (test_resourcemanager.TestResourceManager) ... ok
test_decommission_secured (test_resourcemanager.TestResourceManager) ... ok
test_start_default (test_resourcemanager.TestResourceManager) ... ok
test_start_secured (test_resourcemanager.TestResourceManager) ... ok
test_stop_default (test_resourcemanager.TestResourceManager) ... ok
test_stop_secured (test_resourcemanager.TestResourceManager) ... ok
----------------------------------------------------------------------
Ran 34 tests in 0.883s
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:08 h
[INFO] Finished at: 2015-01-04T03:20:24+00:00
[INFO] Final Memory: 44M/536M
[INFO] ------------------------------------------------------------------------
Thanks,
Robert Levas
Re: Review Request 29568: MapReduce service components should indicate
security state
Posted by Jaimin Jetly <ja...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/29568/#review66771
-----------------------------------------------------------
Ship it!
Ship It!
- Jaimin Jetly
On Jan. 4, 2015, 1:21 p.m., Robert Levas wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/29568/
> -----------------------------------------------------------
>
> (Updated Jan. 4, 2015, 1:21 p.m.)
>
>
> Review request for Ambari, Alejandro Fernandez, Andrew Onischuk, Jaimin Jetly, and Yusaku Sako.
>
>
> Bugs: AMBARI-8795
> https://issues.apache.org/jira/browse/AMBARI-8795
>
>
> Repository: ambari
>
>
> Description
> -------
>
> The MAPREDUCE2 service components should indicate security state when queried by Ambari Agent via STATUS_COMMAND.
>
>
> Diffs
> -----
>
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/YARN/package/scripts/historyserver.py d2b6ee3
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/YARN/package/scripts/status_params.py 498a885
> ambari-server/src/test/python/stacks/2.0.6/YARN/test_historyserver.py b759de6
>
> Diff: https://reviews.apache.org/r/29568/diff/
>
>
> Testing
> -------
>
> Manual testing in test cluster
> Added unit test
>
> #Jenkins test results:
>
> OK
> Running tests for stack:2.0.6 service:YARN
> test_configure_default (test_mapreduce2_client.TestMapReduce2Client) ... ok
> test_configure_secured (test_mapreduce2_client.TestMapReduce2Client) ... ok
> test_upgrade (test_mapreduce2_client.TestMapReduce2Client) ... ok
> test_service_check_default (test_mapreduce2_service_check.TestServiceCheck) ... ok
> test_service_check_secured (test_mapreduce2_service_check.TestServiceCheck) ... ok
> test_configure_default (test_historyserver.TestHistoryServer) ... ok
> test_configure_secured (test_historyserver.TestHistoryServer) ... ok
> **test_security_status (test_historyserver.TestHistoryServer) ... ok**
> test_start_default (test_historyserver.TestHistoryServer) ... 2015-01-04 03:18:11,142 - Did not find mapreduce tar source file and destination folder properties in cluster-env.xml
> 2015-01-04 03:18:11,143 - Could not retrieve properties for tarball with prefix: mapreduce
> ok
> test_start_secured (test_historyserver.TestHistoryServer) ... 2015-01-04 03:18:11,182 - Did not find mapreduce tar source file and destination folder properties in cluster-env.xml
> 2015-01-04 03:18:11,182 - Could not retrieve properties for tarball with prefix: mapreduce
> ok
> test_stop_default (test_historyserver.TestHistoryServer) ... ok
> test_stop_secured (test_historyserver.TestHistoryServer) ... ok
> test_service_check_default (test_yarn_service_check.TestServiceCheck) ... ok
> test_service_check_secured (test_yarn_service_check.TestServiceCheck) ... ok
> test_configure_default (test_yarn_client.TestYarnClient) ... ok
> test_configure_secured (test_yarn_client.TestYarnClient) ... ok
> test_restart_client (test_yarn_client.TestYarnClient) ... ok
> test_upgrade (test_yarn_client.TestYarnClient) ... ok
> test_configure_default (test_nodemanager.TestNodeManager) ... ok
> test_configure_secured (test_nodemanager.TestNodeManager) ... ok
> test_post_rolling_restart (test_nodemanager.TestNodeManager) ... 2015-01-04 03:18:11,463 - Executing NodeManager Rolling Upgrade post-restart
> 2015-01-04 03:18:11,467 - NodeManager executing "yarn node -list -states=RUNNING" to verify the node has rejoined the cluster...
> 2015-01-04 03:18:11,467 - NodeManager with ID c6401.ambari.apache.org:45454 has rejoined the cluster.
> ok
> test_post_rolling_restart_nodemanager_not_ready (test_nodemanager.TestNodeManager) ... 2015-01-04 03:18:11,472 - Executing NodeManager Rolling Upgrade post-restart
> 2015-01-04 03:18:11,477 - NodeManager executing "yarn node -list -states=RUNNING" to verify the node has rejoined the cluster...
> 2015-01-04 03:18:11,477 - Will retry 11 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> 2015-01-04 03:18:11,477 - Will retry 10 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> 2015-01-04 03:18:11,477 - Will retry 9 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> 2015-01-04 03:18:11,478 - Will retry 8 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> 2015-01-04 03:18:11,478 - Will retry 7 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> 2015-01-04 03:18:11,478 - Will retry 6 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> 2015-01-04 03:18:11,478 - Will retry 5 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> 2015-01-04 03:18:11,478 - Will retry 4 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> 2015-01-04 03:18:11,478 - Will retry 3 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> 2015-01-04 03:18:11,479 - Will retry 2 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> 2015-01-04 03:18:11,479 - Will retry 1 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> ok
> test_start_default (test_nodemanager.TestNodeManager) ... ok
> test_start_secured (test_nodemanager.TestNodeManager) ... ok
> test_stop_default (test_nodemanager.TestNodeManager) ... ok
> test_stop_secured (test_nodemanager.TestNodeManager) ... ok
> test_configure_default (test_resourcemanager.TestResourceManager) ... ok
> test_configure_secured (test_resourcemanager.TestResourceManager) ... ok
> test_decommission_default (test_resourcemanager.TestResourceManager) ... ok
> test_decommission_secured (test_resourcemanager.TestResourceManager) ... ok
> test_start_default (test_resourcemanager.TestResourceManager) ... ok
> test_start_secured (test_resourcemanager.TestResourceManager) ... ok
> test_stop_default (test_resourcemanager.TestResourceManager) ... ok
> test_stop_secured (test_resourcemanager.TestResourceManager) ... ok
>
> ----------------------------------------------------------------------
> Ran 34 tests in 0.883s
>
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 01:08 h
> [INFO] Finished at: 2015-01-04T03:20:24+00:00
> [INFO] Final Memory: 44M/536M
> [INFO] ------------------------------------------------------------------------
>
>
> Thanks,
>
> Robert Levas
>
>
Re: Review Request 29568: MapReduce service components should indicate
security state
Posted by Alejandro Fernandez <af...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/29568/#review66681
-----------------------------------------------------------
Ship it!
Ship It!
- Alejandro Fernandez
On Jan. 4, 2015, 1:21 p.m., Robert Levas wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/29568/
> -----------------------------------------------------------
>
> (Updated Jan. 4, 2015, 1:21 p.m.)
>
>
> Review request for Ambari, Alejandro Fernandez, Andrew Onischuk, Jaimin Jetly, and Yusaku Sako.
>
>
> Bugs: AMBARI-8795
> https://issues.apache.org/jira/browse/AMBARI-8795
>
>
> Repository: ambari
>
>
> Description
> -------
>
> The MAPREDUCE2 service components should indicate security state when queried by Ambari Agent via STATUS_COMMAND.
>
>
> Diffs
> -----
>
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/YARN/package/scripts/historyserver.py d2b6ee3
> ambari-server/src/main/resources/stacks/HDP/2.0.6/services/YARN/package/scripts/status_params.py 498a885
> ambari-server/src/test/python/stacks/2.0.6/YARN/test_historyserver.py b759de6
>
> Diff: https://reviews.apache.org/r/29568/diff/
>
>
> Testing
> -------
>
> Manual testing in test cluster
> Added unit test
>
> #Jenkins test results:
>
> OK
> Running tests for stack:2.0.6 service:YARN
> test_configure_default (test_mapreduce2_client.TestMapReduce2Client) ... ok
> test_configure_secured (test_mapreduce2_client.TestMapReduce2Client) ... ok
> test_upgrade (test_mapreduce2_client.TestMapReduce2Client) ... ok
> test_service_check_default (test_mapreduce2_service_check.TestServiceCheck) ... ok
> test_service_check_secured (test_mapreduce2_service_check.TestServiceCheck) ... ok
> test_configure_default (test_historyserver.TestHistoryServer) ... ok
> test_configure_secured (test_historyserver.TestHistoryServer) ... ok
> **test_security_status (test_historyserver.TestHistoryServer) ... ok**
> test_start_default (test_historyserver.TestHistoryServer) ... 2015-01-04 03:18:11,142 - Did not find mapreduce tar source file and destination folder properties in cluster-env.xml
> 2015-01-04 03:18:11,143 - Could not retrieve properties for tarball with prefix: mapreduce
> ok
> test_start_secured (test_historyserver.TestHistoryServer) ... 2015-01-04 03:18:11,182 - Did not find mapreduce tar source file and destination folder properties in cluster-env.xml
> 2015-01-04 03:18:11,182 - Could not retrieve properties for tarball with prefix: mapreduce
> ok
> test_stop_default (test_historyserver.TestHistoryServer) ... ok
> test_stop_secured (test_historyserver.TestHistoryServer) ... ok
> test_service_check_default (test_yarn_service_check.TestServiceCheck) ... ok
> test_service_check_secured (test_yarn_service_check.TestServiceCheck) ... ok
> test_configure_default (test_yarn_client.TestYarnClient) ... ok
> test_configure_secured (test_yarn_client.TestYarnClient) ... ok
> test_restart_client (test_yarn_client.TestYarnClient) ... ok
> test_upgrade (test_yarn_client.TestYarnClient) ... ok
> test_configure_default (test_nodemanager.TestNodeManager) ... ok
> test_configure_secured (test_nodemanager.TestNodeManager) ... ok
> test_post_rolling_restart (test_nodemanager.TestNodeManager) ... 2015-01-04 03:18:11,463 - Executing NodeManager Rolling Upgrade post-restart
> 2015-01-04 03:18:11,467 - NodeManager executing "yarn node -list -states=RUNNING" to verify the node has rejoined the cluster...
> 2015-01-04 03:18:11,467 - NodeManager with ID c6401.ambari.apache.org:45454 has rejoined the cluster.
> ok
> test_post_rolling_restart_nodemanager_not_ready (test_nodemanager.TestNodeManager) ... 2015-01-04 03:18:11,472 - Executing NodeManager Rolling Upgrade post-restart
> 2015-01-04 03:18:11,477 - NodeManager executing "yarn node -list -states=RUNNING" to verify the node has rejoined the cluster...
> 2015-01-04 03:18:11,477 - Will retry 11 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> 2015-01-04 03:18:11,477 - Will retry 10 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> 2015-01-04 03:18:11,477 - Will retry 9 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> 2015-01-04 03:18:11,478 - Will retry 8 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> 2015-01-04 03:18:11,478 - Will retry 7 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> 2015-01-04 03:18:11,478 - Will retry 6 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> 2015-01-04 03:18:11,478 - Will retry 5 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> 2015-01-04 03:18:11,478 - Will retry 4 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> 2015-01-04 03:18:11,478 - Will retry 3 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> 2015-01-04 03:18:11,479 - Will retry 2 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> 2015-01-04 03:18:11,479 - Will retry 1 time(s), caught exception: Unable to determine if the NodeManager has started after upgrade (result code 999). Sleeping for 10 sec(s)
> ok
> test_start_default (test_nodemanager.TestNodeManager) ... ok
> test_start_secured (test_nodemanager.TestNodeManager) ... ok
> test_stop_default (test_nodemanager.TestNodeManager) ... ok
> test_stop_secured (test_nodemanager.TestNodeManager) ... ok
> test_configure_default (test_resourcemanager.TestResourceManager) ... ok
> test_configure_secured (test_resourcemanager.TestResourceManager) ... ok
> test_decommission_default (test_resourcemanager.TestResourceManager) ... ok
> test_decommission_secured (test_resourcemanager.TestResourceManager) ... ok
> test_start_default (test_resourcemanager.TestResourceManager) ... ok
> test_start_secured (test_resourcemanager.TestResourceManager) ... ok
> test_stop_default (test_resourcemanager.TestResourceManager) ... ok
> test_stop_secured (test_resourcemanager.TestResourceManager) ... ok
>
> ----------------------------------------------------------------------
> Ran 34 tests in 0.883s
>
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 01:08 h
> [INFO] Finished at: 2015-01-04T03:20:24+00:00
> [INFO] Final Memory: 44M/536M
> [INFO] ------------------------------------------------------------------------
>
>
> Thanks,
>
> Robert Levas
>
>