[jira] [Updated] (AMBARI-14159) UI Revisit "dfs.namenode.rpc-address" property usage in NN HA environment

[Aleksandr Kovalenko (JIRA)]

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

Aleksandr Kovalenko updated AMBARI-14159:
-
Attachment: AMBARI-14159.patch

> UI Revisit "dfs.namenode.rpc-address" property usage in NN HA environment
> -
>
> Key: AMBARI-14159
> URL: https://issues.apache.org/jira/browse/AMBARI-14159
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.1.3
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-14159.patch
>
>
> To make HDFS working correctly in NN HA mode, property 
> "dfs.namenode.rpc-address" from hdfs-site need to be removed. This was 
> implemented in NN HA Wizard, but "Move Namenode" wizard keeps adding it back. 
> We need to check all possible occurrences of "dfs.namenode.rpc-address" in UI 
> and make sure that UI don't add this property if NN HA is enabled.



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

Re: Review Request 40852: AMBARI-14147. RU: Kafka broker restart failed on downgrade from HDP 2.3 to 2.2

[Jonathan Hurley]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40852/#review108644
---

Ship it!


Ship It!

- Jonathan Hurley


On Dec. 1, 2015, 10:11 p.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40852/
> ---
> 
> (Updated Dec. 1, 2015, 10:11 p.m.)
> 
> 
> Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jonathan 
> Hurley, Nate Cole, and Swapan Shridhar.
> 
> 
> Bugs: AMBARI-14147
> https://issues.apache.org/jira/browse/AMBARI-14147
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> HDP Version: 2.2.8.0-3150
> Kafka service
> Rolling Upgrade to 2.3.4.0-3335, then downgrade
> 
> Kafka broker restart failed on downgrade. (Upgrade had no issues)
> 
> ```
> Traceback (most recent call last):
>   File 
> \"/var/lib/ambari-agent/cache/common-services/KAFKA/0.8.1.2.2/package/scripts/kafka_broker.py\",
>  line 101, in 
> KafkaBroker().execute()
>   File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 217, in execute
> method(env)
>   File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 506, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
>   File 
> \"/var/lib/ambari-agent/cache/common-services/KAFKA/0.8.1.2.2/package/scripts/kafka_broker.py\",
>  line 67, in pre_upgrade_restart
> self.configure(env)
>   File 
> \"/var/lib/ambari-agent/cache/common-services/KAFKA/0.8.1.2.2/package/scripts/kafka_broker.py\",
>  line 44, in configure
> kafka()
>   File 
> \"/var/lib/ambari-agent/cache/common-services/KAFKA/0.8.1.2.2/package/scripts/kafka.py\",
>  line 53, in kafka
> listeners = kafka_server_config['listeners'].replace(\"localhost\", 
> params.hostname)
> KeyError: 'listeners'",
> ```
> 
> 
> This happened because the code in kafka.py is comparing against 
> params.hdp_stack_version (which stays as HDP 2.3 during a downgrade) instead 
> of params.version (which is the version either upgrading or downgrading to).
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/KAFKA/0.8.1.2.2/package/scripts/kafka.py
>  2bd93d2 
>   
> ambari-server/src/main/resources/common-services/KAFKA/0.8.1.2.2/package/scripts/kafka_broker.py
>  3caeb6d 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml
>  f4c7f61 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.2.xml
>  b48184e 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.3.xml
>  766f443 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml
>  0c18f32 
> 
> Diff: https://reviews.apache.org/r/40852/diff/
> 
> 
> Testing
> ---
> 
> EU and RU from HDP 2.2 to 2.3 followed by downgrade.
> Python unit tests passed,
> 
> --
> Total run:839
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

Re: Review Request 40805: Enforce granular role-based access control for stack version functions

[Robert Levas]

> On Dec. 2, 2015, 9:41 a.m., Jonathan Hurley wrote:
> > ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProvider.java,
> >  lines 284-286
> > 
> >
> > Why is this check inside of an if-statement? By virtue of the fact that 
> > you're in the `updateResourcesAuthorized` method, wouldn't that mean that 
> > you need to run this check regardless of what data is in the map?

This is basically the crux of the issues forcing us to get deep into the logic 
of the resource providers in order to perform authorization checks.  

The `updateResourcesAuthorized` method is _protected_ such that the 
authenticated user must have the privileges to _manage stack versions_ *or* 
_edit stack repositories_ in order to perform the operation. See line 150:

```

setRequiredUpdateAuthorizations(EnumSet.of(RoleAuthorization.AMBARI_MANAGE_STACK_VERSIONS,
 RoleAuthorization.AMBARI_EDIT_STACK_REPOS));
```

Once allowed _update resources_, we need to figure out what the user is tring 
to do.  If the user is trying to set the stack repositories, then we need to 
make sure that he is authorized to do so. Hence the if check before the 
authorization check.


- Robert


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40805/#review108647
---


On Dec. 1, 2015, 9:24 p.m., Robert Levas wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40805/
> ---
> 
> (Updated Dec. 1, 2015, 9:24 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, Myroslav 
> Papirkovskyy, Nate Cole, and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-14114
> https://issues.apache.org/jira/browse/AMBARI-14114
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Enforce granular role-based access control for stack version functions:
> 
>| Cluster User | Service Operator | Service 
> Administrator | Cluster Operator | Cluster Administrator | Administrator 
> ---|--|--|---|--|---|---
>
> View stack version details | (+)  | (+)  | (+)
>| (+)  | (+)   | (+)
> Manage stack versions  |  |  |
>|  |   | (+)
> Edit stack repository URLs |  |  |
>|  |   | (+)
> 
> Entry points affected:
> - GET /api/v1/stacks/:stack_name/versions/:version_id
> - GET /api/v1/stacks/:stack_name/versions/:version_id
> - PUT /api/v1/stacks/:stack_name/versions/:version_id
> - POST /api/v1/stacks/:stack_name/versions/:version_id
> - DELETE /api/v1/stacks/:stack_name/versions/:version_id
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProvider.java
>  062b0cb 
>   
> ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationFilter.java
>  7f88286 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/CompatibleRepositoryVersionResourceProviderTest.java
>  4e4386e 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProviderTest.java
>  dfaef98 
>   
> ambari-server/src/test/java/org/apache/ambari/server/security/TestAuthenticationFactory.java
>  634d840 
> 
> Diff: https://reviews.apache.org/r/40805/diff/
> 
> 
> Testing
> ---
> 
> manually tested
> 
> # Local test resuts:
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 59:46.219s
> [INFO] Finished at: Mon Nov 30 18:47:07 EST 2015
> [INFO] Final Memory: 66M/923M
> [INFO] 
> 
> 
> # Jenkins test resuts:
> 
> 
> Thanks,
> 
> Robert Levas
> 
>

[jira] [Updated] (AMBARI-14155) Blueprints: Kerberos deployments cause Kerberos UI to hang

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-14155:
-
Attachment: AMBARI-14155.patch

> Blueprints: Kerberos deployments cause Kerberos UI to hang
> --
>
> Key: AMBARI-14155
> URL: https://issues.apache.org/jira/browse/AMBARI-14155
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-14155.patch
>
>
> This issue was discovered while debugging a problem with Microsoft.
> When a Kerberos cluster is created via a Blueprint request, the Kerberos UI 
> appears to be in a hanging state.  
> Steps to reproduce: 
> 1. POST the Blueprint to http://host:port/api/v1/blueprints/blueprint_name
> 2. POST the Cluster Creation Template to 
> http://host:port/api/v1/clusters/cluster_name
> 3. In the upper right-hand corner of the Ambari UI, click on 
> "Admin->Kerberos". 
> 4. The Kerberos UI will indicate a hanging problem, with the cursor shown 



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

[jira] [Commented] (AMBARI-14155) Blueprints: Kerberos deployments cause Kerberos UI to hang

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk commented on AMBARI-14155:
---

+1 for the patch

> Blueprints: Kerberos deployments cause Kerberos UI to hang
> --
>
> Key: AMBARI-14155
> URL: https://issues.apache.org/jira/browse/AMBARI-14155
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-14155.patch
>
>
> This issue was discovered while debugging a problem with Microsoft.
> When a Kerberos cluster is created via a Blueprint request, the Kerberos UI 
> appears to be in a hanging state.  
> Steps to reproduce: 
> 1. POST the Blueprint to http://host:port/api/v1/blueprints/blueprint_name
> 2. POST the Cluster Creation Template to 
> http://host:port/api/v1/clusters/cluster_name
> 3. In the upper right-hand corner of the Ambari UI, click on 
> "Admin->Kerberos". 
> 4. The Kerberos UI will indicate a hanging problem, with the cursor shown 



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

[jira] [Updated] (AMBARI-14148) Exported blueprint does not contain "policymgr_external_url" property

[Sebastian Toader (JIRA)]

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

Sebastian Toader updated AMBARI-14148:
--
Attachment: AMBARI-14148.v2.patch

> Exported blueprint does not contain "policymgr_external_url" property
> -
>
> Key: AMBARI-14148
> URL: https://issues.apache.org/jira/browse/AMBARI-14148
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Critical
> Fix For: ambari-2.2.0
>
> Attachments: AMBARI-14148.v2.patch
>
>
> 1. Deployed cluster via blueprint with Ranger HA and all plugins enabled.
> 2. Export blueprint
> 3. The exported Blueprint does not contain property "policymgr_external_url"



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

Re: Review Request 40831: Allow client component information for a specific host to be queried from hooks scripts

[Dmytro Sen]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40831/
---

(Updated Дек. 2, 2015, 4:36 п.п.)


Review request for Ambari and Sumit Gupta.


Bugs: AMBARI-13917
https://issues.apache.org/jira/browse/AMBARI-13917


Repository: ambari


Description
---

command-*.json should have the host mapping info for the client components.
The specific situation is that stack deployment needs to decide on some 
operation if client component of certain type is deployed. E.g. if PIG/ECS/etc 
are deployed.


Diffs (updated)
-

  
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionScheduler.java
 5415264 
  
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ExecutionCommandWrapper.java
 99d61af 
  
ambari-server/src/main/java/org/apache/ambari/server/agent/ExecutionCommand.java
 ac16626 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariActionExecutionHelper.java
 215aca8 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java
 9ba5a22 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
 c0dc342 
  
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClientConfigResourceProvider.java
 43aba04 
  
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java
 3bf6cad 

Diff: https://reviews.apache.org/r/40831/diff/


Testing
---

Unit tests passed


Thanks,

Dmytro Sen

[jira] [Commented] (AMBARI-14088) Add GC tuning params to Collector daemon similar to HBase

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14088:
-

SUCCESS: Integrated in Ambari-trunk-Commit #3952 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3952/])
AMBARI-14088 Add GC tuning params to Collector daemon similar to HBase (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=08227a64e3d26aeb9035c5f97e4abf7576917169])
* 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog213Test.java
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog213.java
* 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-env.xml


> Add GC tuning params to Collector daemon similar to HBase
> -
>
> Key: AMBARI-14088
> URL: https://issues.apache.org/jira/browse/AMBARI-14088
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, ambari-upgrade, stacks
>Affects Versions: 2.1.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-14088_2.patch
>
>
> Presently we resort to all defaults. We can optimize this much better by 
> doing some memory profiling on the collector.
> Error trace:
> {code}
> javax.ws.rs.WebApplicationException: 
> org.apache.phoenix.exception.PhoenixIOException: 
> org.apache.phoenix.exception.PhoenixIOException: 
> org.apache.hadoop.hbase.DoNotRetryIOException: 
> METRIC_RECORD,,1447979747302.84e03f0ea4ac1ba9d0dde2ce14d0c878.: Requested 
> memory of 31743360 bytes could not be allocated from remaining memory of 
> 69028112 bytes from global pool of 96642662 bytes after waiting for 1ms.
> at 
> org.apache.phoenix.util.ServerUtil.createIOException(ServerUtil.java:84)
> {code}



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

Re: Review Request 40853: FK_permission_roleauthorization_permission_id is too long for a constraint identifier

[Jonathan Hurley]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40853/#review108643
---

Ship it!


Ship It!

- Jonathan Hurley


On Dec. 1, 2015, 9:13 p.m., Robert Levas wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40853/
> ---
> 
> (Updated Dec. 1, 2015, 9:13 p.m.)
> 
> 
> Review request for Ambari, Jonathan Hurley, Nate Cole, and Robert Nettleton.
> 
> 
> Bugs: AMBARI-14144
> https://issues.apache.org/jira/browse/AMBARI-14144
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> ```
> ALTER TABLE permission_roleauthorization ADD CONSTRAINT 
> FK_permission_roleauthorization_permission_id FOREIGN KEY (permission_id) 
> REFERENCES adminpermission(permission_id)
> Error report -
> SQL Error: ORA-00972: identifier is too long
> 00972. 0 -  "identifier is too long"
> *Cause:An identifier with more than 30 characters was specified.
> *Action:   Specify at most 30 characters.
> ```
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog220.java
>  5f7e850 
>   ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql 3941ccf 
>   ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql bcf6d01 
>   ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql 547c40f 
>   ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql 
> e78aa17 
>   ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql e3ae8fd 
>   ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql 16354f6 
>   
> ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog220Test.java
>  0861878 
> 
> Diff: https://reviews.apache.org/r/40853/diff/
> 
> 
> Testing
> ---
> 
> Manually testing clean install and upgrade
> 
> # Local test results: PASSED
> 
> # Jenkins test results: PENDING
> 
> 
> Thanks,
> 
> Robert Levas
> 
>

[jira] [Commented] (AMBARI-14088) Add GC tuning params to Collector daemon similar to HBase

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14088:
-

FAILURE: Integrated in Ambari-branch-2.1 #986 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/986/])
AMBARI-14088 Add GC tuning params to Collector daemon similar to HBase (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=57317adaabf0afe894e25aac4ded28bb65b1bd49])
* 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-env.xml
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog213.java
* 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog213Test.java


> Add GC tuning params to Collector daemon similar to HBase
> -
>
> Key: AMBARI-14088
> URL: https://issues.apache.org/jira/browse/AMBARI-14088
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, ambari-upgrade, stacks
>Affects Versions: 2.1.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-14088_2.patch
>
>
> Presently we resort to all defaults. We can optimize this much better by 
> doing some memory profiling on the collector.
> Error trace:
> {code}
> javax.ws.rs.WebApplicationException: 
> org.apache.phoenix.exception.PhoenixIOException: 
> org.apache.phoenix.exception.PhoenixIOException: 
> org.apache.hadoop.hbase.DoNotRetryIOException: 
> METRIC_RECORD,,1447979747302.84e03f0ea4ac1ba9d0dde2ce14d0c878.: Requested 
> memory of 31743360 bytes could not be allocated from remaining memory of 
> 69028112 bytes from global pool of 96642662 bytes after waiting for 1ms.
> at 
> org.apache.phoenix.util.ServerUtil.createIOException(ServerUtil.java:84)
> {code}



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

Re: Review Request 40870: NN HA HDFS service check failed because NameNode was in the SafeMode

[Dmytro Sen]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40870/
---

(Updated Дек. 2, 2015, 2:48 п.п.)


Review request for Ambari, Myroslav Papirkovskyy and Vitalyi Brodetskyi.


Bugs: AMBARI-14157
https://issues.apache.org/jira/browse/AMBARI-14157


Repository: ambari


Description
---

On Start Services during Kerberization HDFS Check failed because NN was in the 
SafeMode
NN was active, but when we were waiting to leave safe mode:We waited for 
another NN to exit safe mode, which is not active.
It's because "dfsadmin -fs hdfs://nameservice -safemode get" returns safemode 
state for both NN, not only for the current


Diffs
-

  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
 0902637 
  ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py 6477d00 

Diff: https://reviews.apache.org/r/40870/diff/


Testing (updated)
---

Unit tests passed

--
Ran 250 tests in 8.384s

OK
--
Total run:842
Total errors:0
Total failures:0
OK


Thanks,

Dmytro Sen

[jira] [Updated] (AMBARI-14148) Exported blueprint does not contain "policymgr_external_url" property

[Sebastian Toader (JIRA)]

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

Sebastian Toader updated AMBARI-14148:
--
Attachment: (was: AMBARI-14148.v1.patch)

> Exported blueprint does not contain "policymgr_external_url" property
> -
>
> Key: AMBARI-14148
> URL: https://issues.apache.org/jira/browse/AMBARI-14148
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Critical
> Fix For: ambari-2.2.0
>
>
> 1. Deployed cluster via blueprint with Ranger HA and all plugins enabled.
> 2. Export blueprint
> 3. The exported Blueprint does not contain property "policymgr_external_url"



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

[jira] [Created] (AMBARI-14159) UI Revisit "dfs.namenode.rpc-address" property usage in NN HA environment

[Aleksandr Kovalenko (JIRA)]

Aleksandr Kovalenko created AMBARI-14159:


 Summary: UI Revisit "dfs.namenode.rpc-address" property usage in 
NN HA environment
 Key: AMBARI-14159
 URL: https://issues.apache.org/jira/browse/AMBARI-14159
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.1.3
Reporter: Aleksandr Kovalenko
Assignee: Aleksandr Kovalenko
Priority: Critical
 Fix For: 2.1.3


To make HDFS working correctly in NN HA mode, property 
"dfs.namenode.rpc-address" from hdfs-site need to be removed. This was 
implemented in NN HA Wizard, but "Move Namenode" wizard keeps adding it back. 
We need to check all possible occurrences of "dfs.namenode.rpc-address" in UI 
and make sure that UI don't add this property if NN HA is enabled.



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

[jira] [Created] (AMBARI-14156) Analyze configs changes done to 500 node cluster for AMS config updates

[Dmytro Sen (JIRA)]

Dmytro Sen created AMBARI-14156:
---

 Summary: Analyze configs changes done to 500 node cluster for AMS 
config updates
 Key: AMBARI-14156
 URL: https://issues.apache.org/jira/browse/AMBARI-14156
 Project: Ambari
  Issue Type: Bug
  Components: ambari-metrics, stacks
Affects Versions: 2.1.3
Reporter: Dmytro Sen
Assignee: Dmytro Sen
 Fix For: 2.1.3


- set default hstore max file size to 4 GB
- change UpgradeCatalog213 to replace default 2 with 12 for 
zookeeper.session.timeout.localHBaseCluster



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

Re: Review Request 40855: Exported blueprint does not contain "policymgr_external_url" property

[Sebastian Toader]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40855/
---

(Updated Dec. 2, 2015, 4:35 p.m.)


Review request for Ambari, Dmitro Lisnichenko and Robert Nettleton.


Changes
---

Modifed the comment for configPropertiesWithHASupport field.


Bugs: AMBARI-14148
https://issues.apache.org/jira/browse/AMBARI-14148


Repository: ambari


Description
---

In case of HA deployment the "policy_external_url" is not automatically 
constructed from the host and port of Ranger Admin but rather is the load 
balancer URL that is on front of the Ranger Admin instances which is provided 
by user. 

This property has been added to the list of properties that can support HA 
using a nameservice name otherwise this property is ignored by Blueprint export 
when it's format differs from cluster_host:port


Diffs (updated)
-

  
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
 7f11bb9 
  ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py 
d4d0e83 
  
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
 17c0157 

Diff: https://reviews.apache.org/r/40855/diff/


Testing
---

Manual testing:
1. Verified export with both cases when Ranger is deployed with UI and using 
Blueprint

Unit tests:
--
Total run:804
Total errors:0
Total failures:0
OK


Thanks,

Sebastian Toader

[jira] [Updated] (AMBARI-13917) Allow client component information for a specific host to be queried from hooks scripts

[Dmytro Sen (JIRA)]

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

Dmytro Sen updated AMBARI-13917:

Attachment: AMBARI-13917_4.patch

> Allow client component information for a specific host to be queried from 
> hooks scripts
> ---
>
> Key: AMBARI-13917
> URL: https://issues.apache.org/jira/browse/AMBARI-13917
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Vijay Srinivasaraghavan
>Assignee: Dmytro Sen
> Attachments: AMBARI-13917_4.patch
>
>
> For HCFS stack, the before-START hook has a function to create /tmp and /user 
> directory. 
> {code}
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/shared_initialization.py#L104
> {code}
> The function needs to be invoked only when file system client component 
> (HDFS_CLIENT, ECS_CLIENT etc.,) is being part of the host. The command json 
> file currently does not populate the client component information in 
> "clusterHostInfo" section.



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

[jira] [Updated] (AMBARI-14156) Analyze configs changes done to 500 node cluster for AMS config updates

[Dmytro Sen (JIRA)]

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

Dmytro Sen updated AMBARI-14156:

Attachment: AMBARI-14156.patch

> Analyze configs changes done to 500 node cluster for AMS config updates
> ---
>
> Key: AMBARI-14156
> URL: https://issues.apache.org/jira/browse/AMBARI-14156
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, stacks
>Affects Versions: 2.1.3
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.1.3
>
> Attachments: AMBARI-14156.patch
>
>
> - set default hstore max file size to 4 GB
> - change UpgradeCatalog213 to replace default 2 with 12 for 
> zookeeper.session.timeout.localHBaseCluster



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

Review Request 40869: Analyze configs changes done to 500 node cluster for AMS config updates

[Dmytro Sen]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40869/
---

Review request for Ambari, Aravindan Vijayan, Sumit Gupta, and Sid Wagle.


Bugs: AMBARI-14156
https://issues.apache.org/jira/browse/AMBARI-14156


Repository: ambari


Description
---

- set default hstore max file size to 4 GB
- change UpgradeCatalog213 to replace default 2 with 12 for 
zookeeper.session.timeout.localHBaseCluster


Diffs
-

  
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog213.java
 07c56de 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-hbase-site.xml
 33ac1b7 
  
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog213Test.java
 068ffe6 

Diff: https://reviews.apache.org/r/40869/diff/


Testing
---

Unit tests passed


Thanks,

Dmytro Sen

Review Request 40870: NN HA HDFS service check failed because NameNode was in the SafeMode

[Dmytro Sen]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40870/
---

Review request for Ambari, Myroslav Papirkovskyy and Vitalyi Brodetskyi.


Bugs: AMBARI-14157
https://issues.apache.org/jira/browse/AMBARI-14157


Repository: ambari


Description
---

On Start Services during Kerberization HDFS Check failed because NN was in the 
SafeMode
NN was active, but when we were waiting to leave safe mode:We waited for 
another NN to exit safe mode, which is not active.
It's because "dfsadmin -fs hdfs://nameservice -safemode get" returns safemode 
state for both NN, not only for the current


Diffs
-

  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
 0902637 
  ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py 6477d00 

Diff: https://reviews.apache.org/r/40870/diff/


Testing
---

Unit tests passed


Thanks,

Dmytro Sen

[jira] [Commented] (AMBARI-13364) Parameterize stack information used by common services

[Eric Yang (JIRA)]

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

Eric Yang commented on AMBARI-13364:


I created AMBARI-13364 branch for this work.

>  Parameterize stack information used by common services
> ---
>
> Key: AMBARI-13364
> URL: https://issues.apache.org/jira/browse/AMBARI-13364
> Project: Ambari
>  Issue Type: New Feature
>  Components: ambari-server
>Reporter: Tuong Truong
>Assignee: Juanjo Marron
> Attachments: AMBARI-13364 Parameterize stack information used by 
> common services.pdf, AMBARI-13364.patch
>
>
> This feature will add a basic framework to remove hardcoded stack information 
> out of the common services and use parameter to get access to stack 
> information.  Currently, the common services hardcoded much information 
> specific to Hortonworks' HDP stack including name (HDP), specific versions 
> (2.0, 2.1, 2.2), and install location.   This feature will propose a way of 
> configuration these information and parameterize them into the services for 
> reference as require. 



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

[jira] [Commented] (AMBARI-14094) Remove raise condition in Ranger KMS start if repo creation fails

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14094:
-

SUCCESS: Integrated in Ambari-trunk-Commit #3952 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3952/])
AMBARI-14094 Remove raise condition in Ranger KMS start if repo creation 
(gautam: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d28134dab9cbb8758a0fc820d208231eec327aa4])
* 
ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/kms.py
* ambari-server/src/main/resources/stacks/HDP/2.3/role_command_order.json
* ambari-server/src/main/resources/stacks/HDP/2.2/role_command_order.json


> Remove raise condition in Ranger KMS start if repo creation fails
> -
>
> Key: AMBARI-14094
> URL: https://issues.apache.org/jira/browse/AMBARI-14094
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Gautam Borad
>Assignee: Gautam Borad
> Fix For: 2.2.0, 2.1.3
>
> Attachments: AMBARI-14094.1.patch, AMBARI-14094.2.patch, 
> AMBARI-14094.patch
>
>
> Ranger KMS service start fails if Repository creation fails in Ranger. Log 
> the error for the same however, do not stop  the Ranger KMS service to be 
> started. 
> Also add delay in repository creation from KMS, so that when all services are 
> started together it gets the buffer for Ranger service to start and 
> stabilize. 



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

Re: Review Request 40855: Exported blueprint does not contain "policymgr_external_url" property

[Robert Nettleton]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40855/#review108641
---

Ship it!


Patch looks fine, just a minor javadoc issue below.


ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
 (line 132)


Minor issue:

Adding the Ranger property here is fine, but the Ranger property is a 
little different than the properties in this set, which all refer to the HDFS 
Nameservice logical name. 

Maybe add a comment here to indicate that this set contains other HA 
properties that will be exported even if the expected hostname information 
isn't found.  

I think adding the property here is correct, it might just be a good idea 
to add some comments to make this clearer.  

Thanks


- Robert Nettleton


On Dec. 2, 2015, 7:37 a.m., Sebastian Toader wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40855/
> ---
> 
> (Updated Dec. 2, 2015, 7:37 a.m.)
> 
> 
> Review request for Ambari, Dmitro Lisnichenko and Robert Nettleton.
> 
> 
> Bugs: AMBARI-14148
> https://issues.apache.org/jira/browse/AMBARI-14148
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> In case of HA deployment the "policy_external_url" is not automatically 
> constructed from the host and port of Ranger Admin but rather is the load 
> balancer URL that is on front of the Ranger Admin instances which is provided 
> by user. 
> 
> This property has been added to the list of properties that can support HA 
> using a nameservice name otherwise this property is ignored by Blueprint 
> export when it's format differs from cluster_host:port
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
>  7f11bb9 
>   ambari-server/src/main/resources/stacks/HDP/2.0.6/services/stack_advisor.py 
> d4d0e83 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
>  17c0157 
> 
> Diff: https://reviews.apache.org/r/40855/diff/
> 
> 
> Testing
> ---
> 
> Manual testing:
> 1. Verified export with both cases when Ranger is deployed with UI and using 
> Blueprint
> 
> Unit tests:
> --
> Total run:804
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Sebastian Toader
> 
>

Re: Review Request 40843: Enforce granular role-based access control for group functions

[Jonathan Hurley]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40843/#review108648
---

Ship it!


Ship It!

- Jonathan Hurley


On Dec. 1, 2015, 5:34 p.m., Robert Levas wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40843/
> ---
> 
> (Updated Dec. 1, 2015, 5:34 p.m.)
> 
> 
> Review request for Ambari, Jonathan Hurley, Myroslav Papirkovskyy, Nate Cole, 
> Sumit Mohanty, and Sid Wagle.
> 
> 
> Bugs: AMBARI-14142
> https://issues.apache.org/jira/browse/AMBARI-14142
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Enforce granular role-based access control for alert functions:
> 
>   | Cluster User | Service Operator | Service Administrator | 
> Cluster Operator | ClusterAdministrator | Administrator 
> --|--|--|---|--|--|---
>   
> Manage groups |  |  |   | 
>  |  | (+)
> 
> Entry points affected: 
> - GET /api/v1/groups
> - GET /api/v1/groups/:group_name
> - PUT /api/v1/groups/:group_name
> - POST /api/v1/groups/:group_name
> - DELETE /api/v1/groups/:group_name
> - GET /api/v1/groups/:group_name/members
> - PUT /api/v1/groups/:group_name/members
> - POST /api/v1/groups/:group_name/members
> - DELETE /api/v1/groups/:group_name/members
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/GroupResourceProvider.java
>  36e1007 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/MemberResourceProvider.java
>  0f6b66d 
>   
> ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationFilter.java
>  7f88286 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/GroupResourceProviderTest.java
>  0cd1be1 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/MemberResourceProviderTest.java
>  da8d781 
>   
> ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationFilterTest.java
>  d4b7d5a 
> 
> Diff: https://reviews.apache.org/r/40843/diff/
> 
> 
> Testing
> ---
> 
> Manually tested
> 
> # Local test results: PASSED
> 
> # Jenkins test results: PENDING
> 
> 
> Thanks,
> 
> Robert Levas
> 
>

Re: Review Request 40870: NN HA HDFS service check failed because NameNode was in the SafeMode

[Vitalyi Brodetskyi]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40870/#review108652
---

Ship it!


Ship It!

- Vitalyi Brodetskyi


On Гру. 2, 2015, 2:48 після полудня, Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40870/
> ---
> 
> (Updated Гру. 2, 2015, 2:48 після полудня)
> 
> 
> Review request for Ambari, Myroslav Papirkovskyy and Vitalyi Brodetskyi.
> 
> 
> Bugs: AMBARI-14157
> https://issues.apache.org/jira/browse/AMBARI-14157
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> On Start Services during Kerberization HDFS Check failed because NN was in 
> the SafeMode
> NN was active, but when we were waiting to leave safe mode:We waited for 
> another NN to exit safe mode, which is not active.
> It's because "dfsadmin -fs hdfs://nameservice -safemode get" returns safemode 
> state for both NN, not only for the current
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
>  0902637 
>   ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py 6477d00 
> 
> Diff: https://reviews.apache.org/r/40870/diff/
> 
> 
> Testing
> ---
> 
> Unit tests passed
> 
> --
> Ran 250 tests in 8.384s
> 
> OK
> --
> Total run:842
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

[jira] [Updated] (AMBARI-14158) BG operation window: Running task shows duration with negative value

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-14158:
-
Attachment: AMBARI-14158.patch

> BG operation window: Running task shows duration with negative value
> 
>
> Key: AMBARI-14158
> URL: https://issues.apache.org/jira/browse/AMBARI-14158
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.1.3
>
> Attachments: AMBARI-14158.patch
>
>
> This might happen because end time from API for the request is -1 until the 
> request is over.



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

[jira] [Updated] (AMBARI-13917) Allow client component information for a specific host to be queried from hooks scripts

[Dmytro Sen (JIRA)]

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

Dmytro Sen updated AMBARI-13917:

Attachment: (was: AMBARI-13917-trunk-8_client_components.patch)

> Allow client component information for a specific host to be queried from 
> hooks scripts
> ---
>
> Key: AMBARI-13917
> URL: https://issues.apache.org/jira/browse/AMBARI-13917
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Vijay Srinivasaraghavan
>Assignee: Dmytro Sen
>
> For HCFS stack, the before-START hook has a function to create /tmp and /user 
> directory. 
> {code}
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/shared_initialization.py#L104
> {code}
> The function needs to be invoked only when file system client component 
> (HDFS_CLIENT, ECS_CLIENT etc.,) is being part of the host. The command json 
> file currently does not populate the client component information in 
> "clusterHostInfo" section.



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

Re: Review Request 40793: Enforce granular role-based access control for cluster functions

[Robert Levas]

> On Dec. 1, 2015, 9:57 a.m., Jonathan Hurley wrote:
> > I have a concern about the way that we're coupling the security logic here. 
> > The AMC class is a mess - it really is just a massive steaming pot of 
> > "anything goes" - there's no real separation of concerns and no real 
> > contract. It feels like we're just catching a few places where front-end 
> > logic eventually gets funneled. What about trying to catch this stuff at a 
> > lower level? Maybe in the DAOs?
> > 
> > What about catching it at a higher level? Could there be a branch new 
> > request processor that inspects the incoming request, picks it apart to see 
> > the different things it's trying to do and throws auth exceptions there? 
> > This way we wouldn't be trying to find all of the spots sprinkeled 
> > throughout the code that we need to intercept.
> 
> Nate Cole wrote:
> I like the service-level (endpoint) approach.
> 
> DAOs feel like it would get complicated fast, especially when performing 
> joins across tables - trying to decide if the user is authenticated to update 
> rows of one table, but not another (if that's a valid use case).
> 
> Robert Levas wrote:
> I agree and think this logic should be at a high(er) level.  However 
> doing so may hinder performance since we need to essentially parse the 
> request multiple times - at least once to determine authorzation and at least 
> once to perform the operation. It will also duplicate logic needed to 
> detemine what the user is trying to do.  
> 
> Essentually protecting this type of API is very difficult.  We really 
> need a higher-level API for Ambari rather than exposing a web-based SQL 
> front-end. 
> 
> Regarding the AMC code, I suppose we can move the relevant resource 
> provider code back to the resource provider, but I was trying to limit the 
> amount of code changes. If you look at the methods being altered, they are 
> the ones directly related to request handling.  The lower-level methods are 
> untouched.
> 
> Robert Levas wrote:
> @jurley, would it be better if the request-specific methods were moved 
> from the AMC and into the proper resource provider?  For example, moving 
> `org.apache.ambari.server.controller.AmbariManagementControllerImpl#createCluster`
>  to 
> `org.apache.ambari.server.controller.internal.ClusterResourceProvider#createCluster`
> 
> Jonathan Hurley wrote:
> I think it would be better if we did that, yes. It would at least try to 
> keep with the consistency of the implementation approach here.

Moving the relevant methods from the AMC is too large of a task for this 
effort.  It would require many test cases to be updated along with a few other 
non-test-related classes.  I think a new JIRA should be created for this.


- Robert


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40793/#review108503
---


On Dec. 1, 2015, 9:34 p.m., Robert Levas wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40793/
> ---
> 
> (Updated Dec. 1, 2015, 9:34 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, Myroslav 
> Papirkovskyy, Nate Cole, and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-14072
> https://issues.apache.org/jira/browse/AMBARI-14072
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Enforce granular role-based access control for cluster functions:
> 
>| Cluster User | Service Operator | Service 
> Administrator | Cluster Operator | Cluster Administrator | Administrator
> ---|--|--|---|--|---|---
> View status information|(+)   |(+)   |(+) 
>|(+)   |(+)|(+)
> View configuration |(+)   |(+)   |(+) 
>|(+)   |(+)|(+)
> View stack version details |(+)   |(+)   |(+) 
>|(+)   |(+)|(+)
> Enable/disable Kerberos|  |  |
>|  |(+)|(+)
> Upgrade/downgrade stack|  |  |
>|  |(+)|(+)
> Create new clusters|  |  |
>|  |   |(+)
> Rename clusters|  |  |
>|  | 

[jira] [Commented] (AMBARI-12193) Step2 installer. Popup with hosts contains duplicates

[Hudson (JIRA)]

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

Hudson commented on AMBARI-12193:
-

FAILURE: Integrated in Ambari-branch-2.1 #986 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/986/])
AMBARI-12193. Step2 installer. Popup with hosts contains duplicates 
(onechiporenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1c5fc7ccc44e8bd15c00413985ef902dff41755b])
* ambari-web/app/controllers/wizard/step2_controller.js
* ambari-web/test/controllers/wizard/step2_test.js


> Step2 installer. Popup with hosts contains duplicates
> -
>
> Key: AMBARI-12193
> URL: https://issues.apache.org/jira/browse/AMBARI-12193
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.0
>Reporter: Oleg Nechiporenko
>Assignee: Oleg Nechiporenko
> Fix For: 2.2.0
>
> Attachments: AMBARI-12193.patch, AMBARI-12193_branch-2.1.patch
>
>
> On the step2 installer put to the hosts textarea text like:
> {code}
> host[1-3]
> host2
> {code}
> Click Next
> Popup with list of hosts contains text:
> {code}
> host1
> host2
> host3
> host2
> {code}
> {{host2}} is added twice.
> On the next step table contains 3 hosts (it's correct behavior)



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

[jira] [Commented] (AMBARI-14158) BG operation window: Running task shows duration with negative value

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko commented on AMBARI-14158:


+1 for patch

> BG operation window: Running task shows duration with negative value
> 
>
> Key: AMBARI-14158
> URL: https://issues.apache.org/jira/browse/AMBARI-14158
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.1.3
>
> Attachments: AMBARI-14158.patch
>
>
> This might happen because end time from API for the request is -1 until the 
> request is over.



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

Re: Review Request 40853: FK_permission_roleauthorization_permission_id is too long for a constraint identifier

[Robert Nettleton]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40853/#review108640
---

Ship it!


Ship It!

- Robert Nettleton


On Dec. 2, 2015, 2:13 a.m., Robert Levas wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40853/
> ---
> 
> (Updated Dec. 2, 2015, 2:13 a.m.)
> 
> 
> Review request for Ambari, Jonathan Hurley, Nate Cole, and Robert Nettleton.
> 
> 
> Bugs: AMBARI-14144
> https://issues.apache.org/jira/browse/AMBARI-14144
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> ```
> ALTER TABLE permission_roleauthorization ADD CONSTRAINT 
> FK_permission_roleauthorization_permission_id FOREIGN KEY (permission_id) 
> REFERENCES adminpermission(permission_id)
> Error report -
> SQL Error: ORA-00972: identifier is too long
> 00972. 0 -  "identifier is too long"
> *Cause:An identifier with more than 30 characters was specified.
> *Action:   Specify at most 30 characters.
> ```
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog220.java
>  5f7e850 
>   ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql 3941ccf 
>   ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql bcf6d01 
>   ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql 547c40f 
>   ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql 
> e78aa17 
>   ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql e3ae8fd 
>   ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql 16354f6 
>   
> ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog220Test.java
>  0861878 
> 
> Diff: https://reviews.apache.org/r/40853/diff/
> 
> 
> Testing
> ---
> 
> Manually testing clean install and upgrade
> 
> # Local test results: PASSED
> 
> # Jenkins test results: PENDING
> 
> 
> Thanks,
> 
> Robert Levas
> 
>

Re: Review Request 40793: Enforce granular role-based access control for cluster functions

[Robert Levas]

> On Dec. 1, 2015, 9:57 a.m., Jonathan Hurley wrote:
> > I have a concern about the way that we're coupling the security logic here. 
> > The AMC class is a mess - it really is just a massive steaming pot of 
> > "anything goes" - there's no real separation of concerns and no real 
> > contract. It feels like we're just catching a few places where front-end 
> > logic eventually gets funneled. What about trying to catch this stuff at a 
> > lower level? Maybe in the DAOs?
> > 
> > What about catching it at a higher level? Could there be a branch new 
> > request processor that inspects the incoming request, picks it apart to see 
> > the different things it's trying to do and throws auth exceptions there? 
> > This way we wouldn't be trying to find all of the spots sprinkeled 
> > throughout the code that we need to intercept.
> 
> Nate Cole wrote:
> I like the service-level (endpoint) approach.
> 
> DAOs feel like it would get complicated fast, especially when performing 
> joins across tables - trying to decide if the user is authenticated to update 
> rows of one table, but not another (if that's a valid use case).
> 
> Robert Levas wrote:
> I agree and think this logic should be at a high(er) level.  However 
> doing so may hinder performance since we need to essentially parse the 
> request multiple times - at least once to determine authorzation and at least 
> once to perform the operation. It will also duplicate logic needed to 
> detemine what the user is trying to do.  
> 
> Essentually protecting this type of API is very difficult.  We really 
> need a higher-level API for Ambari rather than exposing a web-based SQL 
> front-end. 
> 
> Regarding the AMC code, I suppose we can move the relevant resource 
> provider code back to the resource provider, but I was trying to limit the 
> amount of code changes. If you look at the methods being altered, they are 
> the ones directly related to request handling.  The lower-level methods are 
> untouched.

@jurley, would it be better if the request-specific methods were moved from the 
AMC and into the proper resource provider?  For example, moving 
`org.apache.ambari.server.controller.AmbariManagementControllerImpl#createCluster`
 to 
`org.apache.ambari.server.controller.internal.ClusterResourceProvider#createCluster`


- Robert


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40793/#review108503
---


On Dec. 1, 2015, 9:34 p.m., Robert Levas wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40793/
> ---
> 
> (Updated Dec. 1, 2015, 9:34 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, Myroslav 
> Papirkovskyy, Nate Cole, and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-14072
> https://issues.apache.org/jira/browse/AMBARI-14072
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Enforce granular role-based access control for cluster functions:
> 
>| Cluster User | Service Operator | Service 
> Administrator | Cluster Operator | Cluster Administrator | Administrator
> ---|--|--|---|--|---|---
> View status information|(+)   |(+)   |(+) 
>|(+)   |(+)|(+)
> View configuration |(+)   |(+)   |(+) 
>|(+)   |(+)|(+)
> View stack version details |(+)   |(+)   |(+) 
>|(+)   |(+)|(+)
> Enable/disable Kerberos|  |  |
>|  |(+)|(+)
> Upgrade/downgrade stack|  |  |
>|  |(+)|(+)
> Create new clusters|  |  |
>|  |   |(+)
> Rename clusters|  |  |
>|  |   |(+)
> 
> Entry points affected:
> - PUT /api/v1/clusters/:cluster_name 
> - POST /api/v1/clusters/:cluster_name 
> 
> # Note: Read-only requests (GET) are not protected so that the front end is 
> not broken.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/services/ClusterService.java
>  4954a96 
>   
> 

Re: Review Request 40805: Enforce granular role-based access control for stack version functions

[Jonathan Hurley]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40805/#review108647
---



ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProvider.java
 (lines 284 - 286)


Why is this check inside of an if-statement? By virtue of the fact that 
you're in the `updateResourcesAuthorized` method, wouldn't that mean that you 
need to run this check regardless of what data is in the map?


- Jonathan Hurley


On Dec. 1, 2015, 9:24 p.m., Robert Levas wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40805/
> ---
> 
> (Updated Dec. 1, 2015, 9:24 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, Myroslav 
> Papirkovskyy, Nate Cole, and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-14114
> https://issues.apache.org/jira/browse/AMBARI-14114
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Enforce granular role-based access control for stack version functions:
> 
>| Cluster User | Service Operator | Service 
> Administrator | Cluster Operator | Cluster Administrator | Administrator 
> ---|--|--|---|--|---|---
>
> View stack version details | (+)  | (+)  | (+)
>| (+)  | (+)   | (+)
> Manage stack versions  |  |  |
>|  |   | (+)
> Edit stack repository URLs |  |  |
>|  |   | (+)
> 
> Entry points affected:
> - GET /api/v1/stacks/:stack_name/versions/:version_id
> - GET /api/v1/stacks/:stack_name/versions/:version_id
> - PUT /api/v1/stacks/:stack_name/versions/:version_id
> - POST /api/v1/stacks/:stack_name/versions/:version_id
> - DELETE /api/v1/stacks/:stack_name/versions/:version_id
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProvider.java
>  062b0cb 
>   
> ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationFilter.java
>  7f88286 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/CompatibleRepositoryVersionResourceProviderTest.java
>  4e4386e 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProviderTest.java
>  dfaef98 
>   
> ambari-server/src/test/java/org/apache/ambari/server/security/TestAuthenticationFactory.java
>  634d840 
> 
> Diff: https://reviews.apache.org/r/40805/diff/
> 
> 
> Testing
> ---
> 
> manually tested
> 
> # Local test resuts:
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 59:46.219s
> [INFO] Finished at: Mon Nov 30 18:47:07 EST 2015
> [INFO] Final Memory: 66M/923M
> [INFO] 
> 
> 
> # Jenkins test resuts:
> 
> 
> Thanks,
> 
> Robert Levas
> 
>

[jira] [Created] (AMBARI-14157) NN HA HDFS service check failed because NameNode was in the SafeMode

[Dmytro Sen (JIRA)]

Dmytro Sen created AMBARI-14157:
---

 Summary: NN HA HDFS service check failed because NameNode was in 
the SafeMode
 Key: AMBARI-14157
 URL: https://issues.apache.org/jira/browse/AMBARI-14157
 Project: Ambari
  Issue Type: Bug
  Components: stacks
Affects Versions: 2.1.3
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
 Fix For: 2.1.3


On Start Services during Kerberization HDFS Check failed because NN was in the 
SafeMode
NN was active, but when we were waiting to leave safe mode:We waited for 
another NN to exit safe mode, which is not active.
It's because "dfsadmin -fs hdfs://nameservice -safemode get" returns safemode 
state for both NN, not only for the current



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

Re: Review Request 40793: Enforce granular role-based access control for cluster functions

[Jonathan Hurley]

> On Dec. 1, 2015, 9:57 a.m., Jonathan Hurley wrote:
> > I have a concern about the way that we're coupling the security logic here. 
> > The AMC class is a mess - it really is just a massive steaming pot of 
> > "anything goes" - there's no real separation of concerns and no real 
> > contract. It feels like we're just catching a few places where front-end 
> > logic eventually gets funneled. What about trying to catch this stuff at a 
> > lower level? Maybe in the DAOs?
> > 
> > What about catching it at a higher level? Could there be a branch new 
> > request processor that inspects the incoming request, picks it apart to see 
> > the different things it's trying to do and throws auth exceptions there? 
> > This way we wouldn't be trying to find all of the spots sprinkeled 
> > throughout the code that we need to intercept.
> 
> Nate Cole wrote:
> I like the service-level (endpoint) approach.
> 
> DAOs feel like it would get complicated fast, especially when performing 
> joins across tables - trying to decide if the user is authenticated to update 
> rows of one table, but not another (if that's a valid use case).
> 
> Robert Levas wrote:
> I agree and think this logic should be at a high(er) level.  However 
> doing so may hinder performance since we need to essentially parse the 
> request multiple times - at least once to determine authorzation and at least 
> once to perform the operation. It will also duplicate logic needed to 
> detemine what the user is trying to do.  
> 
> Essentually protecting this type of API is very difficult.  We really 
> need a higher-level API for Ambari rather than exposing a web-based SQL 
> front-end. 
> 
> Regarding the AMC code, I suppose we can move the relevant resource 
> provider code back to the resource provider, but I was trying to limit the 
> amount of code changes. If you look at the methods being altered, they are 
> the ones directly related to request handling.  The lower-level methods are 
> untouched.
> 
> Robert Levas wrote:
> @jurley, would it be better if the request-specific methods were moved 
> from the AMC and into the proper resource provider?  For example, moving 
> `org.apache.ambari.server.controller.AmbariManagementControllerImpl#createCluster`
>  to 
> `org.apache.ambari.server.controller.internal.ClusterResourceProvider#createCluster`

I think it would be better if we did that, yes. It would at least try to keep 
with the consistency of the implementation approach here.


- Jonathan


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40793/#review108503
---


On Dec. 1, 2015, 9:34 p.m., Robert Levas wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40793/
> ---
> 
> (Updated Dec. 1, 2015, 9:34 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, Myroslav 
> Papirkovskyy, Nate Cole, and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-14072
> https://issues.apache.org/jira/browse/AMBARI-14072
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Enforce granular role-based access control for cluster functions:
> 
>| Cluster User | Service Operator | Service 
> Administrator | Cluster Operator | Cluster Administrator | Administrator
> ---|--|--|---|--|---|---
> View status information|(+)   |(+)   |(+) 
>|(+)   |(+)|(+)
> View configuration |(+)   |(+)   |(+) 
>|(+)   |(+)|(+)
> View stack version details |(+)   |(+)   |(+) 
>|(+)   |(+)|(+)
> Enable/disable Kerberos|  |  |
>|  |(+)|(+)
> Upgrade/downgrade stack|  |  |
>|  |(+)|(+)
> Create new clusters|  |  |
>|  |   |(+)
> Rename clusters|  |  |
>|  |   |(+)
> 
> Entry points affected:
> - PUT /api/v1/clusters/:cluster_name 
> - POST /api/v1/clusters/:cluster_name 
> 
> # Note: Read-only requests (GET) are not protected so that the front end is 
> not broken.
> 
> 
> Diffs
> -

[jira] [Updated] (AMBARI-14157) NN HA HDFS service check failed because NameNode was in the SafeMode

[Dmytro Sen (JIRA)]

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

Dmytro Sen updated AMBARI-14157:

Attachment: AMBARI-14157.patch

> NN HA HDFS service check failed because NameNode was in the SafeMode
> 
>
> Key: AMBARI-14157
> URL: https://issues.apache.org/jira/browse/AMBARI-14157
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.1.3
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-14157.patch
>
>
> On Start Services during Kerberization HDFS Check failed because NN was in 
> the SafeMode
> NN was active, but when we were waiting to leave safe mode:We waited for 
> another NN to exit safe mode, which is not active.
> It's because "dfsadmin -fs hdfs://nameservice -safemode get" returns safemode 
> state for both NN, not only for the current



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

[jira] [Created] (AMBARI-14161) Enforce granular role-based access control for credential functions

[Robert Levas (JIRA)]

Robert Levas created AMBARI-14161:
-

 Summary: Enforce granular role-based access control for credential 
functions
 Key: AMBARI-14161
 URL: https://issues.apache.org/jira/browse/AMBARI-14161
 Project: Ambari
  Issue Type: Task
  Components: ambari-server
Affects Versions: 2.3.0
Reporter: Robert Levas
Assignee: Robert Levas
Priority: Critical
 Fix For: 2.3.0


Enforce granular role-based access control for credential functions

Entry points affected:
* GET /clusters/:cluster_name/credentials
* GET /clusters/:cluster_name/credentials/:alias
* POST /clusters/:cluster_name/credentials/:alias
* PUT /clusters/:cluster_name/credentials/:alias
* DELETE /clusters/:cluster_name/credentials/:alias




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

[jira] [Commented] (AMBARI-14159) UI Revisit "dfs.namenode.rpc-address" property usage in NN HA environment

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14159:


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

This message is automatically generated.

> UI Revisit "dfs.namenode.rpc-address" property usage in NN HA environment
> -
>
> Key: AMBARI-14159
> URL: https://issues.apache.org/jira/browse/AMBARI-14159
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.1.3
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-14159.patch
>
>
> To make HDFS working correctly in NN HA mode, property 
> "dfs.namenode.rpc-address" from hdfs-site need to be removed. This was 
> implemented in NN HA Wizard, but "Move Namenode" wizard keeps adding it back. 
> We need to check all possible occurrences of "dfs.namenode.rpc-address" in UI 
> and make sure that UI don't add this property if NN HA is enabled.



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

[jira] [Commented] (AMBARI-13917) Allow client component information for a specific host to be queried from hooks scripts

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-13917:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

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

This message is automatically generated.

> Allow client component information for a specific host to be queried from 
> hooks scripts
> ---
>
> Key: AMBARI-13917
> URL: https://issues.apache.org/jira/browse/AMBARI-13917
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Vijay Srinivasaraghavan
>Assignee: Dmytro Sen
> Attachments: AMBARI-13917_4.patch
>
>
> For HCFS stack, the before-START hook has a function to create /tmp and /user 
> directory. 
> {code}
> https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/shared_initialization.py#L104
> {code}
> The function needs to be invoked only when file system client component 
> (HDFS_CLIENT, ECS_CLIENT etc.,) is being part of the host. The command json 
> file currently does not populate the client component information in 
> "clusterHostInfo" section.



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

[jira] [Commented] (AMBARI-14156) Analyze configs changes done to 500 node cluster for AMS config updates

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14156:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

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

This message is automatically generated.

> Analyze configs changes done to 500 node cluster for AMS config updates
> ---
>
> Key: AMBARI-14156
> URL: https://issues.apache.org/jira/browse/AMBARI-14156
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, stacks
>Affects Versions: 2.1.3
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.1.3
>
> Attachments: AMBARI-14156.patch
>
>
> - set default hstore max file size to 4 GB
> - change UpgradeCatalog213 to replace default 2 with 12 for 
> zookeeper.session.timeout.localHBaseCluster



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

[jira] [Commented] (AMBARI-14155) Blueprints: Kerberos deployments cause Kerberos UI to hang

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14155:
-

FAILURE: Integrated in Ambari-branch-2.1 #987 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/987/])
AMBARI-14155. Blueprints: Kerberos deployments cause Kerberos UI to hang 
(hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=dd015ce3e189e42883179a236e086ae8908fd8ac])
* ambari-web/app/controllers/main/admin/kerberos.js
* ambari-web/app/mixins/wizard/addSecurityConfigs.js


> Blueprints: Kerberos deployments cause Kerberos UI to hang
> --
>
> Key: AMBARI-14155
> URL: https://issues.apache.org/jira/browse/AMBARI-14155
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-14155.patch
>
>
> This issue was discovered while debugging a problem with Microsoft.
> When a Kerberos cluster is created via a Blueprint request, the Kerberos UI 
> appears to be in a hanging state.  
> Steps to reproduce: 
> 1. POST the Blueprint to http://host:port/api/v1/blueprints/blueprint_name
> 2. POST the Cluster Creation Template to 
> http://host:port/api/v1/clusters/cluster_name
> 3. In the upper right-hand corner of the Ambari UI, click on 
> "Admin->Kerberos". 
> 4. The Kerberos UI will indicate a hanging problem, with the cursor shown 



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

Re: Review Request 40853: FK_permission_roleauthorization_permission_id is too long for a constraint identifier

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40853/#review108689
---



ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog220.java
 (line 340)


I know this doesn't follow the current convention, but I propose that we 
start making all named keys (FK, PK, UQ) in lowercase.
This will help us out in the upgrade catalogs especially for DBs that are 
configured to be case sensitive.


- Alejandro Fernandez


On Dec. 2, 2015, 2:13 a.m., Robert Levas wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40853/
> ---
> 
> (Updated Dec. 2, 2015, 2:13 a.m.)
> 
> 
> Review request for Ambari, Jonathan Hurley, Nate Cole, and Robert Nettleton.
> 
> 
> Bugs: AMBARI-14144
> https://issues.apache.org/jira/browse/AMBARI-14144
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> ```
> ALTER TABLE permission_roleauthorization ADD CONSTRAINT 
> FK_permission_roleauthorization_permission_id FOREIGN KEY (permission_id) 
> REFERENCES adminpermission(permission_id)
> Error report -
> SQL Error: ORA-00972: identifier is too long
> 00972. 0 -  "identifier is too long"
> *Cause:An identifier with more than 30 characters was specified.
> *Action:   Specify at most 30 characters.
> ```
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog220.java
>  5f7e850 
>   ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql 3941ccf 
>   ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql bcf6d01 
>   ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql 547c40f 
>   ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql 
> e78aa17 
>   ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql e3ae8fd 
>   ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql 16354f6 
>   
> ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog220Test.java
>  0861878 
> 
> Diff: https://reviews.apache.org/r/40853/diff/
> 
> 
> Testing
> ---
> 
> Manually testing clean install and upgrade
> 
> # Local test results: PASSED
> 
> # Jenkins test results: PENDING
> 
> 
> Thanks,
> 
> Robert Levas
> 
>

Re: Review Request 40826: Rebalance HDFS after enabling NN HA failed

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40826/#review108694
---



ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py
 (line 319)


This would also confuse customers that would see the value present through 
the API, but not in the file.


- Alejandro Fernandez


On Dec. 1, 2015, 5:01 p.m., Dmitro Lisnichenko wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40826/
> ---
> 
> (Updated Dec. 1, 2015, 5:01 p.m.)
> 
> 
> Review request for Ambari, Andrew Onischuk and Vitalyi Brodetskyi.
> 
> 
> Bugs: AMBARI-14137
> https://issues.apache.org/jira/browse/AMBARI-14137
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> STR:
> 1) Install and deploy cluster
> 2) Enable NameNode HA
> 3) Enable security
> 3) Start rebalance HDFS
> 
> Actually result:
> 
> {code}
> "stderr" : "Traceback (most recent call last):\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py\",
>  line 425, in \nNameNode().execute()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 218, in execute\nmethod(env)\n  File 
> \"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py\",
>  line 363, in rebalancehdfs\nlogoutput = False,\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 156, in run\nself.run_action(resource, action)\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/environment.py\", 
> line 119, in run_action\nprovider_action()\n  File 
> \"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py\",
>  line 238, in action_run\ntri
 es=self.resource.tries, try_sleep=self.resource.try_sleep)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
70, in inner\nresult = function(command, **kwargs)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
92, in checked_call\ntries=tries, try_sleep=try_sleep)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
140, in _call_wrapper\nresult = _call(command, **kwargs_copy)\n  File 
\"/usr/lib/python2.6/site-packages/resource_management/core/shell.py\", line 
291, in _call\nraise 
Fail(err_msg)\nresource_management.core.exceptions.Fail: Execution of 
'ambari-sudo.sh su cstm-hdfs -l -s /bin/bash -c 'export  
PATH='\"'\"'/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/sbin:/sbin:/usr/lib/ambari-server/*:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/var/lib/ambari-agent:/var/lib/ambari-agent:/usr/hdp/current/hadoop-client/bin'\"'\"'
 KRB5CCNAME=/tmp/hdfs_reba
 lance_cc_6ec913166750834c9d9302d65b9c6cb8 ; hdfs --config 
/usr/hdp/current/hadoop-client/conf balancer -threshold 10'' returned 252. 
 Hortonworks #\nThis is MOTD message, added for testing in 
qe infra\n15/11/17 07:29:08 INFO balancer.Balancer: Using a threshold of 
10.0\n15/11/17 07:29:08 INFO balancer.Balancer: namenodes  = 
[hdfs://os-d7-mwznvu-ambari-hv-ser-ha-5-2.novalocal:8020, 
hdfs://nameservice]\n15/11/17 07:29:08 INFO balancer.Balancer: parameters = 
Balancer.BalancerParameters [BalancingPolicy.Node, threshold = 10.0, max idle 
iteration = 5, #excluded nodes = 0, #included nodes = 0, #source nodes = 0, 
#blockpools = 0, run during upgrade = false]\n15/11/17 07:29:08 INFO 
balancer.Balancer: included nodes = []\n15/11/17 07:29:08 INFO 
balancer.Balancer: excluded nodes = []\n15/11/17 07:29:08 INFO 
balancer.Balancer: source nodes = []\nTime Stamp   Iteration#  
Bytes Already Moved  Bytes Left To Move  Bytes Being 
Moved\norg.apache.hadoop.ipc.RemoteExcep
 tion(org.apache.hadoop.ipc.StandbyException): Operation category READ is not 
supported in state standby\n\tat 
org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)\n\tat
 
org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1927)\n\tat
 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:1313)\n\tat
 
org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getServerDefaults(FSNamesystem.java:1625)\n\tat
 
org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.getServerDefaults(NameNodeRpcServer.java:659)\n\tat
 

[jira] [Created] (AMBARI-14160) Ambari Slider View should pick up multiple versions of the same app package

[Ted Yu (JIRA)]

Ted Yu created AMBARI-14160:
---

 Summary: Ambari Slider View should pick up multiple versions of 
the same app package
 Key: AMBARI-14160
 URL: https://issues.apache.org/jira/browse/AMBARI-14160
 Project: Ambari
  Issue Type: Improvement
Reporter: Ted Yu


I was validating some fix for Slider hbase with Gour.
A new Slider hbase app package was built and moved to under:
/var/lib/ambari-server/resources/apps

We tried naming the new app package ending with -ted.zip -999.zip
After 'ambari-server restart', the new app package was not picked up by Ambari.

Ambari Slider View should be able to accommodate more than one version of app 
package.



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

[jira] [Created] (AMBARI-14162) Files view fails at runtime to instantiate ProtobufRpcEngine class

[DIPAYAN BHOWMICK (JIRA)]

DIPAYAN BHOWMICK created AMBARI-14162:
-

 Summary: Files view fails at runtime to instantiate 
ProtobufRpcEngine class
 Key: AMBARI-14162
 URL: https://issues.apache.org/jira/browse/AMBARI-14162
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Affects Versions: 2.1.2
Reporter: DIPAYAN BHOWMICK
Assignee: DIPAYAN BHOWMICK
Priority: Blocker
 Fix For: 2.1.3


After ambari-server start, when user navigates to Files view, 500 Server error 
is returned with the following stacktrace in logs:


{code:java}
02 Dec 2015 14:29:02,731  WARN [qtp-ambari-client-28] ServletHandler:563 - 
/api/v1/views/FILES/versions/1.0.0/instances/files_instance/resources/files/fileops/listdir
java.lang.NoClassDefFoundError: org/apache/commons/io/Charsets
at org.apache.hadoop.ipc.Server.(Server.java:182)
at 
org.apache.hadoop.ipc.ProtobufRpcEngine.(ProtobufRpcEngine.java:72)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:348)
at 
org.apache.hadoop.conf.Configuration.getClassByNameOrNull(Configuration.java:2134)
at 
org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2099)
at 
org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
at org.apache.hadoop.ipc.RPC.getProtocolEngine(RPC.java:204)
at org.apache.hadoop.ipc.RPC.getProtocolProxy(RPC.java:577)
at 
org.apache.hadoop.hdfs.NameNodeProxies.createNNProxyWithClientProtocol(NameNodeProxies.java:418)
at 
org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:314)
at 
org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176)
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:678)
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:619)
at 
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:149)
at 
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2653)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:92)
at 
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2687)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2669)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:371)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:170)
at org.apache.ambari.view.utils.hdfs.HdfsApi$1.run(HdfsApi.java:70)
at org.apache.ambari.view.utils.hdfs.HdfsApi$1.run(HdfsApi.java:68)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
at org.apache.ambari.view.utils.hdfs.HdfsApi.execute(HdfsApi.java:397)
at org.apache.ambari.view.utils.hdfs.HdfsApi.(HdfsApi.java:68)
at 
org.apache.ambari.view.utils.hdfs.HdfsUtil.connectToHDFSApi(HdfsUtil.java:126)
at 
org.apache.ambari.view.filebrowser.HdfsService.getApi(HdfsService.java:79)
at 
org.apache.ambari.view.filebrowser.FileOperationService.listdir(FileOperationService.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
at 

[jira] [Resolved] (AMBARI-14120) AMS Collector and HBase heap memory config properties are incompatible between 2.1.2 and 2.1.3 when deployed through the same blueprint.

[Aravindan Vijayan (JIRA)]

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

Aravindan Vijayan resolved AMBARI-14120.

Resolution: Fixed

> AMS Collector and HBase heap memory config properties are incompatible 
> between 2.1.2 and 2.1.3 when deployed through the same blueprint.
> 
>
> Key: AMBARI-14120
> URL: https://issues.apache.org/jira/browse/AMBARI-14120
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.1.3
>Reporter: Aravindan Vijayan
>Assignee: Aravindan Vijayan
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-14120.patch
>
>
> PROBLEM
> On Version 2.1.2, AMS had no "m" in the heap properties in the *-env.sh 
> templates and the user was expected to specify the "m" suffix through the UI 
> config.
> On Version 2.1.3, AMS had the "m" suffix in the heapsize properties in the 
> *-env.sh templates, and the user was not allowed to give the "m" suffix in 
> the UI.
> When a 2.1.2 blueprint is used to deploy Ambari 2.1.3, AMS does not start due 
> to invalid heap properties.
> FIX
> The input heapsize parameter can either be 512 (UI) or 512m (blueprint). The 
> "m" is added to the former case programmatically to achieve uniformity. The 
> ams-hbase-content will not have "m" appended to any property.



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

Re: Review Request 40870: NN HA HDFS service check failed because NameNode was in the SafeMode

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40870/#review108687
---



ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
 (line 119)


There are other places where we check for safemode during EU and RU, please 
grep for "safemode" in all of HDFS.


- Alejandro Fernandez


On Dec. 2, 2015, 2:48 p.m., Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40870/
> ---
> 
> (Updated Dec. 2, 2015, 2:48 p.m.)
> 
> 
> Review request for Ambari, Myroslav Papirkovskyy and Vitalyi Brodetskyi.
> 
> 
> Bugs: AMBARI-14157
> https://issues.apache.org/jira/browse/AMBARI-14157
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> On Start Services during Kerberization HDFS Check failed because NN was in 
> the SafeMode
> NN was active, but when we were waiting to leave safe mode:We waited for 
> another NN to exit safe mode, which is not active.
> It's because "dfsadmin -fs hdfs://nameservice -safemode get" returns safemode 
> state for both NN, not only for the current
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
>  0902637 
>   ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py 6477d00 
> 
> Diff: https://reviews.apache.org/r/40870/diff/
> 
> 
> Testing
> ---
> 
> Unit tests passed
> 
> --
> Ran 250 tests in 8.384s
> 
> OK
> --
> Total run:842
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

Re: Review Request 40866: AMBARI-14153 : [Ranger's smart configs] Group User Map Sync should not drive user attributes in usersync config

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40866/#review108690
---



ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml (line 
95)


Doesn't this need to be present in the other upgrade packs?
2.2->2.2*
2.3->2.3*



ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/configuration/ranger-ugsync-site.xml
 (line 343)


Does this value need to be changed in config-upgrade.xml used by RU and EU 
from 2.2->2.3?


- Alejandro Fernandez


On Dec. 2, 2015, 11:46 a.m., Gautam Borad wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40866/
> ---
> 
> (Updated Dec. 2, 2015, 11:46 a.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, Mahadev Konar, 
> Sumit Mohanty, Selvamohan Neethiraj, and Velmurugan Periasamy.
> 
> 
> Bugs: AMBARI-14153
> https://issues.apache.org/jira/browse/AMBARI-14153
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Patch contains : 
> 1. Setting ranger.usersync.group.usermapsyncenabled value to true by default. 
> 2. Removed dependency of user parameters (in user configs tab) on group user 
> map sync property.
> 
> 
> Diffs
> -
> 
>   ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml 
> 6a85479 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/configuration/ranger-ugsync-site.xml
>  6b9b0a0 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/themes/theme_version_2.json
>  db65e54 
> 
> Diff: https://reviews.apache.org/r/40866/diff/
> 
> 
> Testing
> ---
> 
> Verified updated properties in Ambari UI for Ranger Configs. 
> 
> ---
> Ran 271 tests in 8.151s
> 
> OK
> --
> Total run:879
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Gautam Borad
> 
>

Re: Review Request 40852: AMBARI-14147. RU: Kafka broker restart failed on downgrade from HDP 2.3 to 2.2

[Nate Cole]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40852/#review108664
---

Ship it!


- Nate Cole


On Dec. 1, 2015, 10:11 p.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40852/
> ---
> 
> (Updated Dec. 1, 2015, 10:11 p.m.)
> 
> 
> Review request for Ambari, Dmytro Grinenko, Dmitro Lisnichenko, Jonathan 
> Hurley, Nate Cole, and Swapan Shridhar.
> 
> 
> Bugs: AMBARI-14147
> https://issues.apache.org/jira/browse/AMBARI-14147
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> HDP Version: 2.2.8.0-3150
> Kafka service
> Rolling Upgrade to 2.3.4.0-3335, then downgrade
> 
> Kafka broker restart failed on downgrade. (Upgrade had no issues)
> 
> ```
> Traceback (most recent call last):
>   File 
> \"/var/lib/ambari-agent/cache/common-services/KAFKA/0.8.1.2.2/package/scripts/kafka_broker.py\",
>  line 101, in 
> KafkaBroker().execute()
>   File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 217, in execute
> method(env)
>   File 
> \"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py\",
>  line 506, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
>   File 
> \"/var/lib/ambari-agent/cache/common-services/KAFKA/0.8.1.2.2/package/scripts/kafka_broker.py\",
>  line 67, in pre_upgrade_restart
> self.configure(env)
>   File 
> \"/var/lib/ambari-agent/cache/common-services/KAFKA/0.8.1.2.2/package/scripts/kafka_broker.py\",
>  line 44, in configure
> kafka()
>   File 
> \"/var/lib/ambari-agent/cache/common-services/KAFKA/0.8.1.2.2/package/scripts/kafka.py\",
>  line 53, in kafka
> listeners = kafka_server_config['listeners'].replace(\"localhost\", 
> params.hostname)
> KeyError: 'listeners'",
> ```
> 
> 
> This happened because the code in kafka.py is comparing against 
> params.hdp_stack_version (which stays as HDP 2.3 during a downgrade) instead 
> of params.version (which is the version either upgrading or downgrading to).
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/KAFKA/0.8.1.2.2/package/scripts/kafka.py
>  2bd93d2 
>   
> ambari-server/src/main/resources/common-services/KAFKA/0.8.1.2.2/package/scripts/kafka_broker.py
>  3caeb6d 
>   
> ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml
>  f4c7f61 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.2.xml
>  b48184e 
>   
> ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.3.xml
>  766f443 
>   
> ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml
>  0c18f32 
> 
> Diff: https://reviews.apache.org/r/40852/diff/
> 
> 
> Testing
> ---
> 
> EU and RU from HDP 2.2 to 2.3 followed by downgrade.
> Python unit tests passed,
> 
> --
> Total run:839
> Total errors:0
> Total failures:0
> OK
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

Re: Review Request 40831: Allow client component information for a specific host to be queried from hooks scripts

[Dmitro Lisnichenko]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40831/#review108666
---

Ship it!


Ship It!

- Dmitro Lisnichenko


On Dec. 2, 2015, 6:36 p.m., Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40831/
> ---
> 
> (Updated Dec. 2, 2015, 6:36 p.m.)
> 
> 
> Review request for Ambari and Sumit Gupta.
> 
> 
> Bugs: AMBARI-13917
> https://issues.apache.org/jira/browse/AMBARI-13917
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> command-*.json should have the host mapping info for the client components.
> The specific situation is that stack deployment needs to decide on some 
> operation if client component of certain type is deployed. E.g. if 
> PIG/ECS/etc are deployed.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionScheduler.java
>  5415264 
>   
> ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ExecutionCommandWrapper.java
>  99d61af 
>   
> ambari-server/src/main/java/org/apache/ambari/server/agent/ExecutionCommand.java
>  ac16626 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariActionExecutionHelper.java
>  215aca8 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java
>  9ba5a22 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariManagementControllerImpl.java
>  c0dc342 
>   
> ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ClientConfigResourceProvider.java
>  43aba04 
>   
> ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java
>  3bf6cad 
> 
> Diff: https://reviews.apache.org/r/40831/diff/
> 
> 
> Testing
> ---
> 
> Unit tests passed
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

[jira] [Commented] (AMBARI-14153) [Ranger's smart configs] Group User Map Sync should not drive user attributes in usersync config

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14153:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

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

This message is automatically generated.

> [Ranger's smart configs] Group User Map Sync should not drive user attributes 
> in usersync config
> 
>
> Key: AMBARI-14153
> URL: https://issues.apache.org/jira/browse/AMBARI-14153
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Gautam Borad
>Assignee: Gautam Borad
> Fix For: 2.1.3
>
> Attachments: AMBARI-14153.patch
>
>
> Steps to reproduce:
> 1. Login to Ambari
> 2. Go to Ranger --> Config --> Ranger User Info tab.
> 3. Enable Ranger UserSync and go to User Configs
> 4. Only after enabling Group User Map Sync, the user properties are shown and 
> expected to be filled in. This needs to be changed. Move "Group User Map 
> Sync" property as the last property on the user Configs tab and don't make 
> the user properties depend on this flag.



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

[jira] [Updated] (AMBARI-14158) BG operation window: Running task shows duration with negative value

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-14158:
-
Attachment: AMBARI-14158.patch

> BG operation window: Running task shows duration with negative value
> 
>
> Key: AMBARI-14158
> URL: https://issues.apache.org/jira/browse/AMBARI-14158
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.1.3
>
> Attachments: AMBARI-14158.patch
>
>
> This might happen because end time from API for the request is -1 until the 
> request is over.



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

[jira] [Commented] (AMBARI-14162) Files view fails at runtime to instantiate ProtobufRpcEngine class

[DIPAYAN BHOWMICK (JIRA)]

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

DIPAYAN BHOWMICK commented on AMBARI-14162:
---

After the changes to Hadoop 2.7.1 jar there is a dependency of Charsets class 
and that is not present in the commons-io:2.1 that gets pulled in as the 
dependency. 

Below is the dependency tree:

{code:java}
➜  files git:(branch-2.1) ✗ mvn dependency:tree -Dverbose -Dincludes=commons-io
Picked up _JAVA_OPTIONS: -Xmx2048m -XX:MaxPermSize=512m -Djava.awt.headless=true
[INFO] Scanning for projects...
[INFO]
[INFO] 
[INFO] Building Files 1.0.0.0-SNAPSHOT
[INFO] 
[INFO]
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ files ---
[INFO] org.apache.ambari.contrib.views:files:jar:1.0.0.0-SNAPSHOT
[INFO] +- org.apache.hadoop:hadoop-hdfs:jar:2.7.1:compile
[INFO] |  \- commons-io:commons-io:jar:2.1:compile (version managed from 2.4)
[INFO] +- org.apache.hadoop:hadoop-common:jar:2.7.1:compile
[INFO] |  \- (commons-io:commons-io:jar:2.1:compile - version managed from 2.4; 
omitted for duplicate)
[INFO] +- org.apache.hadoop:hadoop-minicluster:jar:2.7.1:test
[INFO] |  +- org.apache.hadoop:hadoop-common:test-jar:tests:2.7.1:test
[INFO] |  |  \- (commons-io:commons-io:jar:2.1:test - version managed from 2.4; 
omitted for duplicate)
[INFO] |  +- org.apache.hadoop:hadoop-hdfs:test-jar:tests:2.7.1:test
[INFO] |  |  \- (commons-io:commons-io:jar:2.1:test - version managed from 2.4; 
omitted for duplicate)
[INFO] |  \- 
org.apache.hadoop:hadoop-yarn-server-tests:test-jar:tests:2.7.1:test
[INFO] | \- 
org.apache.hadoop:hadoop-yarn-server-resourcemanager:jar:2.7.1:test
[INFO] |\- (commons-io:commons-io:jar:2.1:test - version managed from 
2.4; omitted for duplicate)
[INFO] \- 
org.apache.ambari.contrib.views:ambari-views-utils:jar:0.0.1.0-SNAPSHOT:compile
[INFO]+- (commons-io:commons-io:jar:2.1:compile - version managed from 2.4; 
omitted for duplicate)
[INFO]\- org.apache.hadoop:hadoop-yarn-common:jar:2.7.1:compile
[INFO]   \- (commons-io:commons-io:jar:2.1:compile - version managed from 
2.4; omitted for duplicate)
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 3.804s
[INFO] Finished at: Wed Dec 02 19:48:19 IST 2015
[INFO] Final Memory: 20M/443M
[INFO] 
{code}

So, dependency for commons-io:2.4 has to be added to the Files project.

Similar issue: https://issues.apache.org/jira/browse/AMBARI-10644

> Files view fails at runtime to instantiate ProtobufRpcEngine class
> --
>
> Key: AMBARI-14162
> URL: https://issues.apache.org/jira/browse/AMBARI-14162
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.1.2
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
>Priority: Blocker
> Fix For: 2.1.3
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> After ambari-server start, when user navigates to Files view, 500 Server 
> error is returned with the following stacktrace in logs:
> {code:java}
> 02 Dec 2015 14:29:02,731  WARN [qtp-ambari-client-28] ServletHandler:563 - 
> /api/v1/views/FILES/versions/1.0.0/instances/files_instance/resources/files/fileops/listdir
> java.lang.NoClassDefFoundError: org/apache/commons/io/Charsets
>   at org.apache.hadoop.ipc.Server.(Server.java:182)
>   at 
> org.apache.hadoop.ipc.ProtobufRpcEngine.(ProtobufRpcEngine.java:72)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:348)
>   at 
> org.apache.hadoop.conf.Configuration.getClassByNameOrNull(Configuration.java:2134)
>   at 
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2099)
>   at 
> org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
>   at org.apache.hadoop.ipc.RPC.getProtocolEngine(RPC.java:204)
>   at org.apache.hadoop.ipc.RPC.getProtocolProxy(RPC.java:577)
>   at 
> org.apache.hadoop.hdfs.NameNodeProxies.createNNProxyWithClientProtocol(NameNodeProxies.java:418)
>   at 
> org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:314)
>   at 
> org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176)
>   at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:678)
>   at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:619)
>   at 
> 

[jira] [Updated] (AMBARI-14162) Files view fails at runtime to instantiate ProtobufRpcEngine class

[DIPAYAN BHOWMICK (JIRA)]

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

DIPAYAN BHOWMICK updated AMBARI-14162:
--
Attachment: AMBARI-14162_branch-2.1.patch

> Files view fails at runtime to instantiate ProtobufRpcEngine class
> --
>
> Key: AMBARI-14162
> URL: https://issues.apache.org/jira/browse/AMBARI-14162
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.1.2
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
>Priority: Blocker
> Fix For: 2.1.3
>
> Attachments: AMBARI-14162_branch-2.1.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> After ambari-server start, when user navigates to Files view, 500 Server 
> error is returned with the following stacktrace in logs:
> {code:java}
> 02 Dec 2015 14:29:02,731  WARN [qtp-ambari-client-28] ServletHandler:563 - 
> /api/v1/views/FILES/versions/1.0.0/instances/files_instance/resources/files/fileops/listdir
> java.lang.NoClassDefFoundError: org/apache/commons/io/Charsets
>   at org.apache.hadoop.ipc.Server.(Server.java:182)
>   at 
> org.apache.hadoop.ipc.ProtobufRpcEngine.(ProtobufRpcEngine.java:72)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:348)
>   at 
> org.apache.hadoop.conf.Configuration.getClassByNameOrNull(Configuration.java:2134)
>   at 
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2099)
>   at 
> org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
>   at org.apache.hadoop.ipc.RPC.getProtocolEngine(RPC.java:204)
>   at org.apache.hadoop.ipc.RPC.getProtocolProxy(RPC.java:577)
>   at 
> org.apache.hadoop.hdfs.NameNodeProxies.createNNProxyWithClientProtocol(NameNodeProxies.java:418)
>   at 
> org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:314)
>   at 
> org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176)
>   at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:678)
>   at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:619)
>   at 
> org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:149)
>   at 
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2653)
>   at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:92)
>   at 
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2687)
>   at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2669)
>   at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:371)
>   at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:170)
>   at org.apache.ambari.view.utils.hdfs.HdfsApi$1.run(HdfsApi.java:70)
>   at org.apache.ambari.view.utils.hdfs.HdfsApi$1.run(HdfsApi.java:68)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
>   at org.apache.ambari.view.utils.hdfs.HdfsApi.execute(HdfsApi.java:397)
>   at org.apache.ambari.view.utils.hdfs.HdfsApi.(HdfsApi.java:68)
>   at 
> org.apache.ambari.view.utils.hdfs.HdfsUtil.connectToHDFSApi(HdfsUtil.java:126)
>   at 
> org.apache.ambari.view.filebrowser.HdfsService.getApi(HdfsService.java:79)
>   at 
> org.apache.ambari.view.filebrowser.FileOperationService.listdir(FileOperationService.java:64)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>   at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>   at 
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   at 
> com.sun.jersey.server.impl.uri.rules.SubLocatorRule.accept(SubLocatorRule.java:137)
>   at 
> 

[jira] [Updated] (AMBARI-14158) BG operation window: Running task shows duration with negative value

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-14158:
-
Attachment: (was: AMBARI-14158.patch)

> BG operation window: Running task shows duration with negative value
> 
>
> Key: AMBARI-14158
> URL: https://issues.apache.org/jira/browse/AMBARI-14158
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.1.3
>
> Attachments: AMBARI-14158.patch
>
>
> This might happen because end time from API for the request is -1 until the 
> request is over.



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

[jira] [Commented] (AMBARI-14158) BG operation window: Running task shows duration with negative value

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander commented on AMBARI-14158:
--

Committed to trunk and 2.1

> BG operation window: Running task shows duration with negative value
> 
>
> Key: AMBARI-14158
> URL: https://issues.apache.org/jira/browse/AMBARI-14158
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.1.3
>
> Attachments: AMBARI-14158.patch, Duration_is_negative.png
>
>
> This might happen because end time from API for the request is -1 until the 
> request is over.



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

[jira] [Assigned] (AMBARI-14150) Remove Obsolete Upgrade Pre-requisite Check Logic

[Dmytro Sen (JIRA)]

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

Dmytro Sen reassigned AMBARI-14150:
---

Assignee: Dmytro Sen

> Remove Obsolete Upgrade Pre-requisite Check Logic
> -
>
> Key: AMBARI-14150
> URL: https://issues.apache.org/jira/browse/AMBARI-14150
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: trunk
>
>
> In earlier incarnations of rolling upgrades, the pre-req checks were not 
> specified in the upgrade packs as they are today. However, they are now 
> explicitly defined in each and every upgrade pack, so we can remove a lot of 
> confusing and obsolete code.
> - AbstractCheckDescriptor.getSourceStack
> - AbstractCheckDescriptor.getTargetStack
> - Configuration.getRollingUpgradeMinStack
> - Configuration.getRollingUpgradeMaxStack
> - ambari.properties
> {code}
> rolling.upgrade.min.stack=HDP-2.2
> rolling.upgrade.max.stack=
> {code}
> Let's clean up this old code that has no more use.



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

[jira] [Commented] (AMBARI-14155) Blueprints: Kerberos deployments cause Kerberos UI to hang

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14155:
-

FAILURE: Integrated in Ambari-trunk-Commit #3953 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3953/])
AMBARI-14155. Blueprints: Kerberos deployments cause Kerberos UI to hang 
(hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=1de9934216c653843b7e4cec9065a5c76f9b84a4])
* ambari-web/app/controllers/main/admin/kerberos.js
* ambari-web/app/mixins/wizard/addSecurityConfigs.js


> Blueprints: Kerberos deployments cause Kerberos UI to hang
> --
>
> Key: AMBARI-14155
> URL: https://issues.apache.org/jira/browse/AMBARI-14155
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-14155.patch
>
>
> This issue was discovered while debugging a problem with Microsoft.
> When a Kerberos cluster is created via a Blueprint request, the Kerberos UI 
> appears to be in a hanging state.  
> Steps to reproduce: 
> 1. POST the Blueprint to http://host:port/api/v1/blueprints/blueprint_name
> 2. POST the Cluster Creation Template to 
> http://host:port/api/v1/clusters/cluster_name
> 3. In the upper right-hand corner of the Ambari UI, click on 
> "Admin->Kerberos". 
> 4. The Kerberos UI will indicate a hanging problem, with the cursor shown 



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

[jira] [Commented] (AMBARI-14159) UI Revisit "dfs.namenode.rpc-address" property usage in NN HA environment

[Andrii Babiichuk (JIRA)]

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

Andrii Babiichuk commented on AMBARI-14159:
---

+1 for the patch

> UI Revisit "dfs.namenode.rpc-address" property usage in NN HA environment
> -
>
> Key: AMBARI-14159
> URL: https://issues.apache.org/jira/browse/AMBARI-14159
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.1.3
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-14159.patch
>
>
> To make HDFS working correctly in NN HA mode, property 
> "dfs.namenode.rpc-address" from hdfs-site need to be removed. This was 
> implemented in NN HA Wizard, but "Move Namenode" wizard keeps adding it back. 
> We need to check all possible occurrences of "dfs.namenode.rpc-address" in UI 
> and make sure that UI don't add this property if NN HA is enabled.



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

[jira] [Commented] (AMBARI-14158) BG operation window: Running task shows duration with negative value

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14158:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

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

This message is automatically generated.

> BG operation window: Running task shows duration with negative value
> 
>
> Key: AMBARI-14158
> URL: https://issues.apache.org/jira/browse/AMBARI-14158
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.1.3
>
> Attachments: AMBARI-14158.patch
>
>
> This might happen because end time from API for the request is -1 until the 
> request is over.



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

[jira] [Commented] (AMBARI-14162) Files view fails at runtime to instantiate ProtobufRpcEngine class

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14162:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

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

This message is automatically generated.

> Files view fails at runtime to instantiate ProtobufRpcEngine class
> --
>
> Key: AMBARI-14162
> URL: https://issues.apache.org/jira/browse/AMBARI-14162
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.1.2
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
>Priority: Blocker
> Fix For: 2.1.3
>
> Attachments: AMBARI-14162_branch-2.1.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> After ambari-server start, when user navigates to Files view, 500 Server 
> error is returned with the following stacktrace in logs:
> {code:java}
> 02 Dec 2015 14:29:02,731  WARN [qtp-ambari-client-28] ServletHandler:563 - 
> /api/v1/views/FILES/versions/1.0.0/instances/files_instance/resources/files/fileops/listdir
> java.lang.NoClassDefFoundError: org/apache/commons/io/Charsets
>   at org.apache.hadoop.ipc.Server.(Server.java:182)
>   at 
> org.apache.hadoop.ipc.ProtobufRpcEngine.(ProtobufRpcEngine.java:72)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:348)
>   at 
> org.apache.hadoop.conf.Configuration.getClassByNameOrNull(Configuration.java:2134)
>   at 
> org.apache.hadoop.conf.Configuration.getClassByName(Configuration.java:2099)
>   at 
> org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2193)
>   at org.apache.hadoop.ipc.RPC.getProtocolEngine(RPC.java:204)
>   at org.apache.hadoop.ipc.RPC.getProtocolProxy(RPC.java:577)
>   at 
> org.apache.hadoop.hdfs.NameNodeProxies.createNNProxyWithClientProtocol(NameNodeProxies.java:418)
>   at 
> org.apache.hadoop.hdfs.NameNodeProxies.createNonHAProxy(NameNodeProxies.java:314)
>   at 
> org.apache.hadoop.hdfs.NameNodeProxies.createProxy(NameNodeProxies.java:176)
>   at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:678)
>   at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:619)
>   at 
> org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:149)
>   at 
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2653)
>   at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:92)
>   at 
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2687)
>   at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2669)
>   at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:371)
>   at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:170)
>   at org.apache.ambari.view.utils.hdfs.HdfsApi$1.run(HdfsApi.java:70)
>   at org.apache.ambari.view.utils.hdfs.HdfsApi$1.run(HdfsApi.java:68)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1657)
>   at org.apache.ambari.view.utils.hdfs.HdfsApi.execute(HdfsApi.java:397)
>   at org.apache.ambari.view.utils.hdfs.HdfsApi.(HdfsApi.java:68)
>   at 
> org.apache.ambari.view.utils.hdfs.HdfsUtil.connectToHDFSApi(HdfsUtil.java:126)
>   at 
> org.apache.ambari.view.filebrowser.HdfsService.getApi(HdfsService.java:79)
>   at 
> org.apache.ambari.view.filebrowser.FileOperationService.listdir(FileOperationService.java:64)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at 
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
>   at 
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>   at 
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
>   at 
> 

Re: Review Request 40869: Analyze configs changes done to 500 node cluster for AMS config updates

[Sid Wagle]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40869/#review108667
---

Ship it!


Ship It!

- Sid Wagle


On Dec. 2, 2015, 2:39 p.m., Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40869/
> ---
> 
> (Updated Dec. 2, 2015, 2:39 p.m.)
> 
> 
> Review request for Ambari, Aravindan Vijayan, Sumit Gupta, and Sid Wagle.
> 
> 
> Bugs: AMBARI-14156
> https://issues.apache.org/jira/browse/AMBARI-14156
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> - set default hstore max file size to 4 GB
> - change UpgradeCatalog213 to replace default 2 with 12 for 
> zookeeper.session.timeout.localHBaseCluster
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog213.java
>  07c56de 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-hbase-site.xml
>  33ac1b7 
>   
> ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog213Test.java
>  068ffe6 
> 
> Diff: https://reviews.apache.org/r/40869/diff/
> 
> 
> Testing
> ---
> 
> Unit tests passed
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

[jira] [Commented] (AMBARI-14148) Exported blueprint does not contain "policymgr_external_url" property

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14148:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

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

This message is automatically generated.

> Exported blueprint does not contain "policymgr_external_url" property
> -
>
> Key: AMBARI-14148
> URL: https://issues.apache.org/jira/browse/AMBARI-14148
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Critical
> Fix For: ambari-2.2.0
>
> Attachments: AMBARI-14148.v2.patch
>
>
> 1. Deployed cluster via blueprint with Ranger HA and all plugins enabled.
> 2. Export blueprint
> 3. The exported Blueprint does not contain property "policymgr_external_url"



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

[jira] [Updated] (AMBARI-14158) BG operation window: Running task shows duration with negative value

[Antonenko Alexander (JIRA)]

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

Antonenko Alexander updated AMBARI-14158:
-
Attachment: Duration_is_negative.png

> BG operation window: Running task shows duration with negative value
> 
>
> Key: AMBARI-14158
> URL: https://issues.apache.org/jira/browse/AMBARI-14158
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.1.3
>
> Attachments: AMBARI-14158.patch, Duration_is_negative.png
>
>
> This might happen because end time from API for the request is -1 until the 
> request is over.



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

[jira] [Updated] (AMBARI-14161) Enforce granular role-based access control for credential functions

[Robert Levas (JIRA)]

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

Robert Levas updated AMBARI-14161:
--
Attachment: AMBARI-14161_trunk_02.patch

> Enforce granular role-based access control for credential functions
> ---
>
> Key: AMBARI-14161
> URL: https://issues.apache.org/jira/browse/AMBARI-14161
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.3.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
>  Labels: rbac
> Fix For: 2.3.0
>
> Attachments: AMBARI-14161_trunk_01.patch, AMBARI-14161_trunk_02.patch
>
>
> Enforce granular role-based access control for credential functions
> Entry points affected:
> * GET /clusters/:cluster_name/credentials
> * GET /clusters/:cluster_name/credentials/:alias
> * POST /clusters/:cluster_name/credentials/:alias
> * PUT /clusters/:cluster_name/credentials/:alias
> * DELETE /clusters/:cluster_name/credentials/:alias



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

Re: Review Request 40790: Invalid session handle error in hive view when hive server is restarted in http mode

[Yusaku Sako]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40790/#review108711
---

Ship it!


Ship It!

- Yusaku Sako


On Dec. 1, 2015, 9:22 a.m., Gaurav Nagar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40790/
> ---
> 
> (Updated Dec. 1, 2015, 9:22 a.m.)
> 
> 
> Review request for Ambari, Srimanth Gunturi, Sid Wagle, and Yusaku Sako.
> 
> 
> Bugs: AMBARI-14109
> https://issues.apache.org/jira/browse/AMBARI-14109
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Removing session when we get Invalid session in query response.
> 
> 
> Diffs
> -
> 
>   
> contrib/views/hive/src/main/java/org/apache/ambari/view/hive/client/Connection.java
>  451f2aa 
>   
> contrib/views/hive/src/main/java/org/apache/ambari/view/hive/client/DDLDelegator.java
>  eda12ed 
>   
> contrib/views/hive/src/main/java/org/apache/ambari/view/hive/client/HiveCall.java
>  1b565eb 
> 
> Diff: https://reviews.apache.org/r/40790/diff/
> 
> 
> Testing
> ---
> 
> Manual testing.
> 
> 
> Thanks,
> 
> Gaurav Nagar
> 
>

[jira] [Commented] (AMBARI-14159) UI Revisit "dfs.namenode.rpc-address" property usage in NN HA environment

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14159:
-

FAILURE: Integrated in Ambari-branch-2.1 #988 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/988/])
AMBARI-14159 UI Revisit "dfs.namenode.rpc-address" property usage in NN 
(akovalenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=b5cff6fee4f6e3c75e315e555aa0581b5f09575c])
* ambari-web/app/controllers/main/service/reassign/step4_controller.js
* ambari-web/test/controllers/main/service/reassign/step4_controller_test.js


> UI Revisit "dfs.namenode.rpc-address" property usage in NN HA environment
> -
>
> Key: AMBARI-14159
> URL: https://issues.apache.org/jira/browse/AMBARI-14159
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.1.3
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-14159.patch
>
>
> To make HDFS working correctly in NN HA mode, property 
> "dfs.namenode.rpc-address" from hdfs-site need to be removed. This was 
> implemented in NN HA Wizard, but "Move Namenode" wizard keeps adding it back. 
> We need to check all possible occurrences of "dfs.namenode.rpc-address" in UI 
> and make sure that UI don't add this property if NN HA is enabled.



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

[jira] [Commented] (AMBARI-14158) BG operation window: Running task shows duration with negative value

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14158:
-

FAILURE: Integrated in Ambari-branch-2.1 #988 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/988/])
AMBARI-14158. BG operation window: Running task shows duration with (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=7061caeae34e3a617066baed1248aece7b2310c5])
* contrib/views/slider/src/main/resources/ui/app/models/config_property.js
* ambari-web/app/utils/date/date.js


> BG operation window: Running task shows duration with negative value
> 
>
> Key: AMBARI-14158
> URL: https://issues.apache.org/jira/browse/AMBARI-14158
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.1.3
>
> Attachments: AMBARI-14158.patch, Duration_is_negative.png
>
>
> This might happen because end time from API for the request is -1 until the 
> request is over.



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

[jira] [Resolved] (AMBARI-14057) ambari-web build is failing on trunk

[Yusaku Sako (JIRA)]

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

Yusaku Sako resolved AMBARI-14057.
--
Resolution: Fixed
  Assignee: Yusaku Sako  (was: Jaimin D Jetly)

I've reconfigured the Jenkins jobs to use brunch@1.7.20.

> ambari-web build is failing on trunk
> 
>
> Key: AMBARI-14057
> URL: https://issues.apache.org/jira/browse/AMBARI-14057
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.2.0
>Reporter: Jaimin D Jetly
>Assignee: Yusaku Sako
>Priority: Critical
> Fix For: 2.2.0
>
>
> Last several runs have failed with build failure in ambari-web.
> E.g. https://builds.apache.org/job/Ambari-trunk-Commit/3905/consoleFull
> {code}
> [INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---
> Error: Brunch 2+ requires node v4.0+. Upgrade node or use older brunch for 
> old node.js: npm i -g brunch@1
> {code}



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

[jira] [Updated] (AMBARI-14161) Enforce granular role-based access control for credential functions

[Robert Levas (JIRA)]

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

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

> Enforce granular role-based access control for credential functions
> ---
>
> Key: AMBARI-14161
> URL: https://issues.apache.org/jira/browse/AMBARI-14161
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.3.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
>  Labels: rbac
> Fix For: 2.3.0
>
> Attachments: AMBARI-14161_trunk_01.patch
>
>
> Enforce granular role-based access control for credential functions
> Entry points affected:
> * GET /clusters/:cluster_name/credentials
> * GET /clusters/:cluster_name/credentials/:alias
> * POST /clusters/:cluster_name/credentials/:alias
> * PUT /clusters/:cluster_name/credentials/:alias
> * DELETE /clusters/:cluster_name/credentials/:alias



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

Review Request 40879: Enforce granular role-based access control for credential functions

[Robert Levas]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40879/
---

Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, Nate Cole, 
Robert Nettleton, and Sumit Mohanty.


Bugs: AMBARI-14161
https://issues.apache.org/jira/browse/AMBARI-14161


Repository: ambari


Description
---

Enforce granular role-based access control for credential functions

Entry points affected:
- GET /clusters/:cluster_name/credentials
- GET /clusters/:cluster_name/credentials/:alias
- POST /clusters/:cluster_name/credentials/:alias
- PUT /clusters/:cluster_name/credentials/:alias
- DELETE /clusters/:cluster_name/credentials/:alias


Diffs
-

  
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/CredentialResourceProvider.java
 52783c9 
  
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/RoleAuthorization.java
 00ad412 
  
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog220.java
 9eaced1 
  ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql 0731cf7 
  ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql 2a4c776 
  ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql 2492978 
  ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql 
970231b 
  ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql 4091b70 
  ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql da756f7 
  
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/CredentialResourceProviderTest.java
 5f32d39 
  
ambari-server/src/test/java/org/apache/ambari/server/security/TestAuthenticationFactory.java
 634d840 

Diff: https://reviews.apache.org/r/40879/diff/


Testing
---

Manually tested - clean install, ugrade, enable Kerberos (uses credential entry 
points)

# Local test results:
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 1:00:55.637s
[INFO] Finished at: Wed Dec 02 14:39:27 EST 2015
[INFO] Final Memory: 67M/921M
[INFO] 

# Jenkins test results: PENDING


Thanks,

Robert Levas

[jira] [Commented] (AMBARI-14157) NN HA HDFS service check failed because NameNode was in the SafeMode

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14157:
-

FAILURE: Integrated in Ambari-branch-2.1 #988 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/988/])
AMBARI-14157 NN HA HDFS service check failed because NameNode was in the (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=67e4f25497501bfa481f753e4bd878b778662f2e])
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py


> NN HA HDFS service check failed because NameNode was in the SafeMode
> 
>
> Key: AMBARI-14157
> URL: https://issues.apache.org/jira/browse/AMBARI-14157
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.1.3
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-14157.patch
>
>
> On Start Services during Kerberization HDFS Check failed because NN was in 
> the SafeMode
> NN was active, but when we were waiting to leave safe mode:We waited for 
> another NN to exit safe mode, which is not active.
> It's because "dfsadmin -fs hdfs://nameservice -safemode get" returns safemode 
> state for both NN, not only for the current



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

Re: Review Request 40879: Enforce granular role-based access control for credential functions

[Robert Levas]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40879/
---

(Updated Dec. 2, 2015, 3:09 p.m.)


Review request for Ambari, Alejandro Fernandez, Jonathan Hurley, Nate Cole, 
Robert Nettleton, and Sumit Mohanty.


Changes
---

Added AmbariAuthorizationFileter changes.


Bugs: AMBARI-14161
https://issues.apache.org/jira/browse/AMBARI-14161


Repository: ambari


Description
---

Enforce granular role-based access control for credential functions

Entry points affected:
- GET /clusters/:cluster_name/credentials
- GET /clusters/:cluster_name/credentials/:alias
- POST /clusters/:cluster_name/credentials/:alias
- PUT /clusters/:cluster_name/credentials/:alias
- DELETE /clusters/:cluster_name/credentials/:alias


Diffs (updated)
-

  
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/CredentialResourceProvider.java
 52783c9 
  
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationFilter.java
 43c9aa2 
  
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/RoleAuthorization.java
 00ad412 
  
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog220.java
 9eaced1 
  ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql 0731cf7 
  ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql 2a4c776 
  ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql 2492978 
  ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql 
970231b 
  ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql 4091b70 
  ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql da756f7 
  
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/CredentialResourceProviderTest.java
 5f32d39 
  
ambari-server/src/test/java/org/apache/ambari/server/security/TestAuthenticationFactory.java
 634d840 
  
ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationFilterTest.java
 09972a7 

Diff: https://reviews.apache.org/r/40879/diff/


Testing
---

Manually tested - clean install, ugrade, enable Kerberos (uses credential entry 
points)

# Local test results:
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 1:00:55.637s
[INFO] Finished at: Wed Dec 02 14:39:27 EST 2015
[INFO] Final Memory: 67M/921M
[INFO] 

# Jenkins test results: PENDING


Thanks,

Robert Levas

[jira] [Commented] (AMBARI-14148) Exported blueprint does not contain "policymgr_external_url" property

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14148:


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

{color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

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

This message is automatically generated.

> Exported blueprint does not contain "policymgr_external_url" property
> -
>
> Key: AMBARI-14148
> URL: https://issues.apache.org/jira/browse/AMBARI-14148
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Sebastian Toader
>Assignee: Sebastian Toader
>Priority: Critical
> Fix For: ambari-2.2.0
>
> Attachments: AMBARI-14148.v1.patch
>
>
> 1. Deployed cluster via blueprint with Ranger HA and all plugins enabled.
> 2. Export blueprint
> 3. The exported Blueprint does not contain property "policymgr_external_url"



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

Re: Review Request 40686: HAWQ gives ownership of hawq parent directory to hawq_user

[bhuvnesh chaudhary]

> On Dec. 2, 2015, 5:48 a.m., jun aoki wrote:
> > ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/hawqsegment.py,
> >  line 87
> > 
> >
> > I'm probably missing something here and educate me.
> > If the chown execution at the parent directory  is deleted completely, 
> > how chmod actually occurs at the actual directory (segment_dir in this 
> > particular case) which has the right permission?

chmod is executed by root to make the segment or master dir non readable to 
users other than gpadmin. 
these directories when created are given gpadmin as the ownership. so now they 
hve gpadmin as the owner and 700 as the permission.
parent directories of segment / master dir were earlier given gpadmin ownership 
as init db logs were created under the parent directory which is now fixed at 
hawq and thus step is removed.


- bhuvnesh


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40686/#review108608
---


On Nov. 25, 2015, 1:08 a.m., Matt wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40686/
> ---
> 
> (Updated Nov. 25, 2015, 1:08 a.m.)
> 
> 
> Review request for Ambari.
> 
> 
> Bugs: AMBARI-14054
> https://issues.apache.org/jira/browse/AMBARI-14054
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> HAWQ service gives the ownership of parent directories of hawq_master_dir and 
> hawq_segment_dir to hawq_user.
> 
> This is not ideal because the parent directory might be / (root directory), 
> and root directory ownership should not be given to hawq_user
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/hawqsegment.py
>  0e349d2 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/master_helper.py
>  fdfd7c9 
> 
> Diff: https://reviews.apache.org/r/40686/diff/
> 
> 
> Testing
> ---
> 
> Manually tested 
> 
> After changes were made, HAWQ was deployed on a cluster, and the directory 
> ownership and permissions were verified for hawq_master_dir and 
> hawq_segment_dir
> 
> 
> Thanks,
> 
> Matt
> 
>

[jira] [Created] (AMBARI-14151) config comparison should not happen for UI only configs

[Andrii Babiichuk (JIRA)]

Andrii Babiichuk created AMBARI-14151:
-

 Summary: config comparison should not happen for UI only configs
 Key: AMBARI-14151
 URL: https://issues.apache.org/jira/browse/AMBARI-14151
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.1.3
Reporter: Andrii Babiichuk
Assignee: Andrii Babiichuk
Priority: Critical
 Fix For: 2.1.3


if "isRequiredByAgent" is marked as false for a config in site properties, then 
it should not show up on config comparison page. 



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

Re: Review Request 40686: HAWQ gives ownership of hawq parent directory to hawq_user

[jun aoki]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40686/#review108721
---

Ship it!


Ship It!

- jun aoki


On Nov. 25, 2015, 1:08 a.m., Matt wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40686/
> ---
> 
> (Updated Nov. 25, 2015, 1:08 a.m.)
> 
> 
> Review request for Ambari.
> 
> 
> Bugs: AMBARI-14054
> https://issues.apache.org/jira/browse/AMBARI-14054
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> HAWQ service gives the ownership of parent directories of hawq_master_dir and 
> hawq_segment_dir to hawq_user.
> 
> This is not ideal because the parent directory might be / (root directory), 
> and root directory ownership should not be given to hawq_user
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/hawqsegment.py
>  0e349d2 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/master_helper.py
>  fdfd7c9 
> 
> Diff: https://reviews.apache.org/r/40686/diff/
> 
> 
> Testing
> ---
> 
> Manually tested 
> 
> After changes were made, HAWQ was deployed on a cluster, and the directory 
> ownership and permissions were verified for hawq_master_dir and 
> hawq_segment_dir
> 
> 
> Thanks,
> 
> Matt
> 
>

[jira] [Created] (AMBARI-14163) zookeeper session timeout for hbase should take zookeeper tickTime into account

[Ted Yu (JIRA)]

Ted Yu created AMBARI-14163:
---

 Summary: zookeeper session timeout for hbase should take zookeeper 
tickTime into account
 Key: AMBARI-14163
 URL: https://issues.apache.org/jira/browse/AMBARI-14163
 Project: Ambari
  Issue Type: Bug
Reporter: Ted Yu


With tickTime=2000 in zoo.cfg, I tried to set zookeeper.session.timeout value 
of 1 min 40 seconds.
The change was accepted.

However, such timeout is not reachable (it is > 20 times tickTime)

Ambari should detect such scenario and warn user.



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

[jira] [Commented] (AMBARI-14142) Enforce granular role-based access control for group functions

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14142:
-

ABORTED: Integrated in Ambari-trunk-Commit #3954 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3954/])
AMBARI-14142. Enforce granular role-based access control for group (rlevas: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=35f0d3c4234361dc74bf64bbe91720d79b8ecaa7])
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/GroupResourceProvider.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/MemberResourceProviderTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationFilterTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationFilter.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/GroupResourceProviderTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/MemberResourceProvider.java


> Enforce granular role-based access control for group functions
> --
>
> Key: AMBARI-14142
> URL: https://issues.apache.org/jira/browse/AMBARI-14142
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server
>Affects Versions: 2.3.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>  Labels: rbac
> Fix For: 2.3.0
>
> Attachments: AMBARI-14142_trunk_01.patch
>
>
> Enforce granular role-based access control for alert functions:
> || || Cluster\\User || Service\\Operator || Service\\Administrator || 
> Cluster\\Operator || Cluster\\Administrator || Administrator ||
> |Manage groups |   |   |   |   |   |(+)|
> Entry points affected: 
> * GET /api/v1/groups
> * GET /api/v1/groups/:group_name
> * PUT /api/v1/groups/:group_name
> * POST /api/v1/groups/:group_name
> * DELETE /api/v1/groups/:group_name
> * GET /api/v1/groups/:group_name/members
> * PUT /api/v1/groups/:group_name/members
> * POST /api/v1/groups/:group_name/members
> * DELETE /api/v1/groups/:group_name/members



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

[jira] [Commented] (AMBARI-14159) UI Revisit "dfs.namenode.rpc-address" property usage in NN HA environment

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14159:
-

ABORTED: Integrated in Ambari-trunk-Commit #3954 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3954/])
AMBARI-14159 UI Revisit "dfs.namenode.rpc-address" property usage in NN 
(akovalenko: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c2f1cef29f5390ff28d450199e75bff144ddc665])
* ambari-web/app/controllers/main/service/reassign/step4_controller.js
* ambari-web/test/controllers/main/service/reassign/step4_controller_test.js


> UI Revisit "dfs.namenode.rpc-address" property usage in NN HA environment
> -
>
> Key: AMBARI-14159
> URL: https://issues.apache.org/jira/browse/AMBARI-14159
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.1.3
>Reporter: Aleksandr Kovalenko
>Assignee: Aleksandr Kovalenko
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-14159.patch
>
>
> To make HDFS working correctly in NN HA mode, property 
> "dfs.namenode.rpc-address" from hdfs-site need to be removed. This was 
> implemented in NN HA Wizard, but "Move Namenode" wizard keeps adding it back. 
> We need to check all possible occurrences of "dfs.namenode.rpc-address" in UI 
> and make sure that UI don't add this property if NN HA is enabled.



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

[jira] [Commented] (AMBARI-14144) FK_permission_roleauthorization_permission_id is too long for a constraint identifier

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14144:
-

ABORTED: Integrated in Ambari-trunk-Commit #3954 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3954/])
AMBARI-14144. FK_permission_roleauthorization_permission_id is too long 
(rlevas: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ed80206e891093e3c9708c4c164ea2349cf8f1ba])
* ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog220.java
* ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
* 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog220Test.java


> FK_permission_roleauthorization_permission_id is too long for a constraint 
> identifier
> -
>
> Key: AMBARI-14144
> URL: https://issues.apache.org/jira/browse/AMBARI-14144
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.3.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Blocker
>  Labels: rbac
> Fix For: 2.3.0
>
> Attachments: AMBARI-14144_trunk_01.patch
>
>
> {noformat}
> ALTER TABLE permission_roleauthorization ADD CONSTRAINT 
> FK_permission_roleauthorization_permission_id FOREIGN KEY (permission_id) 
> REFERENCES adminpermission(permission_id)
> Error report -
> SQL Error: ORA-00972: identifier is too long
> 00972. 0 -  "identifier is too long"
> *Cause:An identifier with more than 30 characters was specified.
> *Action:   Specify at most 30 characters.
> {noformat}



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

[jira] [Commented] (AMBARI-14157) NN HA HDFS service check failed because NameNode was in the SafeMode

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14157:
-

ABORTED: Integrated in Ambari-trunk-Commit #3954 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3954/])
AMBARI-14157 NN HA HDFS service check failed because NameNode was in the (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=233afcd2d621f40b029e5bdb33a4b496bf9e23c3])
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py
* 
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py


> NN HA HDFS service check failed because NameNode was in the SafeMode
> 
>
> Key: AMBARI-14157
> URL: https://issues.apache.org/jira/browse/AMBARI-14157
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.1.3
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.1.3
>
> Attachments: AMBARI-14157.patch
>
>
> On Start Services during Kerberization HDFS Check failed because NN was in 
> the SafeMode
> NN was active, but when we were waiting to leave safe mode:We waited for 
> another NN to exit safe mode, which is not active.
> It's because "dfsadmin -fs hdfs://nameservice -safemode get" returns safemode 
> state for both NN, not only for the current



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

[jira] [Commented] (AMBARI-14156) Analyze configs changes done to 500 node cluster for AMS config updates

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14156:
-

ABORTED: Integrated in Ambari-trunk-Commit #3954 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3954/])
AMBARI-14156 Analyze configs changes done to 500 node cluster for AMS (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4fe479b0f4ad7bdf97e8609b3a1182ad3c0f57fd])
* 
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-hbase-site.xml
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog213.java
* 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog213Test.java


> Analyze configs changes done to 500 node cluster for AMS config updates
> ---
>
> Key: AMBARI-14156
> URL: https://issues.apache.org/jira/browse/AMBARI-14156
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, stacks
>Affects Versions: 2.1.3
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
> Fix For: 2.1.3
>
> Attachments: AMBARI-14156.patch
>
>
> - set default hstore max file size to 4 GB
> - change UpgradeCatalog213 to replace default 2 with 12 for 
> zookeeper.session.timeout.localHBaseCluster



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

[jira] [Commented] (AMBARI-14150) Remove Obsolete Upgrade Pre-requisite Check Logic

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14150:
-

ABORTED: Integrated in Ambari-trunk-Commit #3954 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3954/])
AMBARI-14150 Remove Obsolete Upgrade Pre-requisite Check Logic (dsen) (dsen: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2a970f8de48656012d7aba364f1066cec31de99b])
* 
ambari-server/src/test/java/org/apache/ambari/server/checks/ServicesMaintenanceModeCheckTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/checks/ConfigurationMergeCheckTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/checks/AbstractCheckDescriptor.java
* 
ambari-server/src/test/java/org/apache/ambari/server/checks/ComponentsInstallationCheckTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/checks/InstallPackagesCheckTest.java
* ambari-server/conf/unix/ambari.properties
* 
ambari-server/src/test/java/org/apache/ambari/server/checks/MapReduce2JobHistoryStatePreservingCheckTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/checks/ServicesYarnWorkPreservingCheckTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/checks/ServicesNamenodeHighAvailabilityCheckTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/checks/ServicesMapReduceDistributedCacheCheckTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/checks/HostsRepositoryVersionCheckTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* 
ambari-server/src/test/java/org/apache/ambari/server/checks/HiveDynamicServiceDiscoveryCheckTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/checks/YarnTimelineServerStatePreservingCheckTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/checks/SecondaryNamenodeDeletedCheckTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/checks/HostsMasterMaintenanceCheckTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/checks/ServicesTezDistributedCacheCheckTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/checks/HostsHeartbeatCheckTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/checks/ServicesUpCheckTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/checks/ServicesNamenodeTruncateCheckTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/checks/ClientRetryPropertyCheckTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/checks/HiveMultipleMetastoreCheckTest.java


> Remove Obsolete Upgrade Pre-requisite Check Logic
> -
>
> Key: AMBARI-14150
> URL: https://issues.apache.org/jira/browse/AMBARI-14150
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: trunk
>Reporter: Dmytro Grinenko
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: trunk
>
>
> In earlier incarnations of rolling upgrades, the pre-req checks were not 
> specified in the upgrade packs as they are today. However, they are now 
> explicitly defined in each and every upgrade pack, so we can remove a lot of 
> confusing and obsolete code.
> - AbstractCheckDescriptor.getSourceStack
> - AbstractCheckDescriptor.getTargetStack
> - Configuration.getRollingUpgradeMinStack
> - Configuration.getRollingUpgradeMaxStack
> - ambari.properties
> {code}
> rolling.upgrade.min.stack=HDP-2.2
> rolling.upgrade.max.stack=
> {code}
> Let's clean up this old code that has no more use.



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

[jira] [Commented] (AMBARI-14158) BG operation window: Running task shows duration with negative value

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14158:
-

ABORTED: Integrated in Ambari-trunk-Commit #3954 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3954/])
AMBARI-14158. BG operation window: Running task shows duration with (hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9f0538e023f0dd5f1e357f2f2623377c1aee865d])
* ambari-web/app/utils/date/date.js
* contrib/views/slider/src/main/resources/ui/app/models/config_property.js


> BG operation window: Running task shows duration with negative value
> 
>
> Key: AMBARI-14158
> URL: https://issues.apache.org/jira/browse/AMBARI-14158
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.1.3
>
> Attachments: AMBARI-14158.patch, Duration_is_negative.png
>
>
> This might happen because end time from API for the request is -1 until the 
> request is over.



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

[jira] [Updated] (AMBARI-14165) Populate hawq's yarn-client xml under /usr/local/hawq/etc

[bhuvnesh chaudhary (JIRA)]

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

bhuvnesh chaudhary updated AMBARI-14165:

Attachment: AMBARI-14165.patch

patch attached

> Populate hawq's yarn-client xml under /usr/local/hawq/etc
> -
>
> Key: AMBARI-14165
> URL: https://issues.apache.org/jira/browse/AMBARI-14165
> Project: Ambari
>  Issue Type: New Feature
>Affects Versions: trunk
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
> Fix For: trunk
>
> Attachments: AMBARI-14165.patch
>
>
> Populate hawq's yarn-client xml under /usr/local/hawq/etc.
> If Yarn ha is enabled, ensure that /usr/local/hawq/etc/yarn-client.xml is 
> updated with required ha parameters.



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

Review Request 40885: Populate hawq's yarn-client xml under /usr/local/hawq/etc

[bhuvnesh chaudhary]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40885/
---

Review request for Ambari, jun aoki and Oleksandr Diachenko.


Bugs: AMBARI-14165
https://issues.apache.org/jira/browse/AMBARI-14165


Repository: ambari


Description
---

Populate hawq's yarn-client xml under /usr/local/hawq/etc.
If Yarn ha is enabled, ensure that /usr/local/hawq/etc/yarn-client.xml is 
updated with required ha parameters.


Diffs
-

  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/configuration/yarn-client.xml
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/common.py
 31ef2fa 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/constants.py
 b56fd59 
  
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/params.py
 fb449b9 

Diff: https://reviews.apache.org/r/40885/diff/


Testing
---

yes


Thanks,

bhuvnesh chaudhary

[jira] [Updated] (AMBARI-14164) Downgrade could not save cluster state to remove configs

[Nate Cole (JIRA)]

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

Nate Cole updated AMBARI-14164:
---
Attachment: AMBARI-14164.patch

> Downgrade could not save cluster state to remove configs
> 
>
> Key: AMBARI-14164
> URL: https://issues.apache.org/jira/browse/AMBARI-14164
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
> Fix For: 2.1.3
>
> Attachments: AMBARI-14164.patch
>
>
> During EU, an error was encountered preventing the removal of configurations. 
>  The {{equals()}} method was forcing a lazy-load of data for an entity that 
> didn't exist.



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

Re: Review Request 40883: Downgrade could not save cluster state to remove configs

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40883/#review108728
---

Ship it!


Ship It!

- Alejandro Fernandez


On Dec. 2, 2015, 10:04 p.m., Nate Cole wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40883/
> ---
> 
> (Updated Dec. 2, 2015, 10:04 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez and Jonathan Hurley.
> 
> 
> Bugs: AMBARI-14164
> https://issues.apache.org/jira/browse/AMBARI-14164
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> During EU, an error was encountered preventing the removal of configurations. 
> The equals() method was forcing a lazy-load of data for an entity that didn't 
> exist.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterConfigEntity.java
>  f28cc02 
> 
> Diff: https://reviews.apache.org/r/40883/diff/
> 
> 
> Testing
> ---
> 
> No new tests required.  Manual upgrade worked.  Automated to confirm no 
> breakage pending.
> 
> 
> Thanks,
> 
> Nate Cole
> 
>

Re: Review Request 40883: Downgrade could not save cluster state to remove configs

[Jonathan Hurley]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40883/#review108742
---

Ship it!


Ship It!

- Jonathan Hurley


On Dec. 2, 2015, 5:48 p.m., Nate Cole wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40883/
> ---
> 
> (Updated Dec. 2, 2015, 5:48 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez and Jonathan Hurley.
> 
> 
> Bugs: AMBARI-14164
> https://issues.apache.org/jira/browse/AMBARI-14164
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> During EU, an error was encountered preventing the removal of configurations. 
> The equals() method was forcing a lazy-load of data for an entity that didn't 
> exist.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterConfigEntity.java
>  f28cc02 
> 
> Diff: https://reviews.apache.org/r/40883/diff/
> 
> 
> Testing
> ---
> 
> No new tests required.  Manual upgrade worked.  Automated to confirm no 
> breakage pending.
> 
> 
> Thanks,
> 
> Nate Cole
> 
>

Re: Review Request 40686: HAWQ gives ownership of hawq parent directory to hawq_user

[Matt]

> On Dec. 1, 2015, 9:48 p.m., jun aoki wrote:
> >

More information regarding this change:
- Location of initdb has been moved to logs directory as a result of 
https://issues.apache.org/jira/browse/HAWQ-33
- Please refer 
https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/utils.py#L34-#L38
 which creates the hawq_segment_dir as hawq_user. The call to this function is 
made here 
https://github.com/Pivotal-Hadoop/ambari/blob/trunk/ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/hawqsegment.py#L84


- Matt


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40686/#review108608
---


On Nov. 24, 2015, 5:08 p.m., Matt wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40686/
> ---
> 
> (Updated Nov. 24, 2015, 5:08 p.m.)
> 
> 
> Review request for Ambari.
> 
> 
> Bugs: AMBARI-14054
> https://issues.apache.org/jira/browse/AMBARI-14054
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> HAWQ service gives the ownership of parent directories of hawq_master_dir and 
> hawq_segment_dir to hawq_user.
> 
> This is not ideal because the parent directory might be / (root directory), 
> and root directory ownership should not be given to hawq_user
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/hawqsegment.py
>  0e349d2 
>   
> ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/master_helper.py
>  fdfd7c9 
> 
> Diff: https://reviews.apache.org/r/40686/diff/
> 
> 
> Testing
> ---
> 
> Manually tested 
> 
> After changes were made, HAWQ was deployed on a cluster, and the directory 
> ownership and permissions were verified for hawq_master_dir and 
> hawq_segment_dir
> 
> 
> Thanks,
> 
> Matt
> 
>

Review Request 40883: Downgrade could not save cluster state to remove configs

[Nate Cole]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40883/
---

Review request for Ambari, Alejandro Fernandez and Jonathan Hurley.


Bugs: AMBARI-14164
https://issues.apache.org/jira/browse/AMBARI-14164


Repository: ambari


Description
---

During EU, an error was encountered preventing the removal of configurations. 
The equals() method was forcing a lazy-load of data for an entity that didn't 
exist.


Diffs
-

  
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterConfigEntity.java
 f28cc02 

Diff: https://reviews.apache.org/r/40883/diff/


Testing
---

Manual.  Automated pending.


Thanks,

Nate Cole

[jira] [Commented] (AMBARI-14054) HAWQ gives ownership of hawq parent directory to hawq_user

[jun aoki (JIRA)]

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

jun aoki commented on AMBARI-14054:
---

+1. Will commit it shortly 

> HAWQ gives ownership of hawq parent directory to hawq_user
> --
>
> Key: AMBARI-14054
> URL: https://issues.apache.org/jira/browse/AMBARI-14054
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Mithun Mathew
>Assignee: Mithun Mathew
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-14054.patch
>
>
> HAWQ service gives the ownership of parent directories of hawq_master_dir and 
> hawq_segment_dir to hawq_user.
> This is not ideal because the parent directory might be / (root directory), 
> and root directory ownership should not be given to hawq_user



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

[jira] [Created] (AMBARI-14164) Downgrade could not save cluster state to remove configs

[Nate Cole (JIRA)]

Nate Cole created AMBARI-14164:
--

 Summary: Downgrade could not save cluster state to remove configs
 Key: AMBARI-14164
 URL: https://issues.apache.org/jira/browse/AMBARI-14164
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Reporter: Nate Cole
Assignee: Nate Cole
 Fix For: 2.1.3


During EU, an error was encountered preventing the removal of configurations.  
The {{equals()}} method was forcing a lazy-load of data for an entity that 
didn't exist.



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

[jira] [Created] (AMBARI-14165) Populate hawq's yarn-client xml under /usr/local/hawq/etc

[bhuvnesh chaudhary (JIRA)]

bhuvnesh chaudhary created AMBARI-14165:
---

 Summary: Populate hawq's yarn-client xml under /usr/local/hawq/etc
 Key: AMBARI-14165
 URL: https://issues.apache.org/jira/browse/AMBARI-14165
 Project: Ambari
  Issue Type: Bug
Reporter: bhuvnesh chaudhary


Populate hawq's yarn-client xml under /usr/local/hawq/etc.

If Yarn ha is enabled, ensure that /usr/local/hawq/etc/yarn-client.xml is 
updated with required ha parameters.



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

[jira] [Updated] (AMBARI-14165) Populate hawq's yarn-client xml under /usr/local/hawq/etc

[bhuvnesh chaudhary (JIRA)]

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

bhuvnesh chaudhary updated AMBARI-14165:

Issue Type: New Feature  (was: Bug)

> Populate hawq's yarn-client xml under /usr/local/hawq/etc
> -
>
> Key: AMBARI-14165
> URL: https://issues.apache.org/jira/browse/AMBARI-14165
> Project: Ambari
>  Issue Type: New Feature
>Reporter: bhuvnesh chaudhary
>
> Populate hawq's yarn-client xml under /usr/local/hawq/etc.
> If Yarn ha is enabled, ensure that /usr/local/hawq/etc/yarn-client.xml is 
> updated with required ha parameters.



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

[jira] [Commented] (AMBARI-14164) Downgrade could not save cluster state to remove configs

[Nate Cole (JIRA)]

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

Nate Cole commented on AMBARI-14164:


No new tests required.  Confirming that existing tests are unbroken.

> Downgrade could not save cluster state to remove configs
> 
>
> Key: AMBARI-14164
> URL: https://issues.apache.org/jira/browse/AMBARI-14164
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Reporter: Nate Cole
>Assignee: Nate Cole
> Fix For: 2.1.3
>
> Attachments: AMBARI-14164.patch
>
>
> During EU, an error was encountered preventing the removal of configurations. 
>  The {{equals()}} method was forcing a lazy-load of data for an entity that 
> didn't exist.



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

[jira] [Assigned] (AMBARI-14165) Populate hawq's yarn-client xml under /usr/local/hawq/etc

[bhuvnesh chaudhary (JIRA)]

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

bhuvnesh chaudhary reassigned AMBARI-14165:
---

Assignee: bhuvnesh chaudhary

> Populate hawq's yarn-client xml under /usr/local/hawq/etc
> -
>
> Key: AMBARI-14165
> URL: https://issues.apache.org/jira/browse/AMBARI-14165
> Project: Ambari
>  Issue Type: New Feature
>Reporter: bhuvnesh chaudhary
>Assignee: bhuvnesh chaudhary
>
> Populate hawq's yarn-client xml under /usr/local/hawq/etc.
> If Yarn ha is enabled, ensure that /usr/local/hawq/etc/yarn-client.xml is 
> updated with required ha parameters.



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

Re: Review Request 40883: Downgrade could not save cluster state to remove configs

[Jonathan Hurley]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40883/#review108734
---



ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterConfigEntity.java
 (line 203)


This is actually bad practice I think. Two non-equal objects can return the 
same hashcode. Safer to do the explicit variable comparisons.


- Jonathan Hurley


On Dec. 2, 2015, 5:04 p.m., Nate Cole wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40883/
> ---
> 
> (Updated Dec. 2, 2015, 5:04 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez and Jonathan Hurley.
> 
> 
> Bugs: AMBARI-14164
> https://issues.apache.org/jira/browse/AMBARI-14164
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> During EU, an error was encountered preventing the removal of configurations. 
> The equals() method was forcing a lazy-load of data for an entity that didn't 
> exist.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterConfigEntity.java
>  f28cc02 
> 
> Diff: https://reviews.apache.org/r/40883/diff/
> 
> 
> Testing
> ---
> 
> No new tests required.  Manual upgrade worked.  Automated to confirm no 
> breakage pending.
> 
> 
> Thanks,
> 
> Nate Cole
> 
>

Re: Review Request 40883: Downgrade could not save cluster state to remove configs

[Nate Cole]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40883/
---

(Updated Dec. 2, 2015, 5:48 p.m.)


Review request for Ambari, Alejandro Fernandez and Jonathan Hurley.


Changes
---

Fix for wrong diff


Bugs: AMBARI-14164
https://issues.apache.org/jira/browse/AMBARI-14164


Repository: ambari


Description
---

During EU, an error was encountered preventing the removal of configurations. 
The equals() method was forcing a lazy-load of data for an entity that didn't 
exist.


Diffs (updated)
-

  
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterConfigEntity.java
 f28cc02 

Diff: https://reviews.apache.org/r/40883/diff/


Testing
---

No new tests required.  Manual upgrade worked.  Automated to confirm no 
breakage pending.


Thanks,

Nate Cole

Re: Review Request 40883: Downgrade could not save cluster state to remove configs

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/40883/#review108743
---

Ship it!


Ship It!

- Alejandro Fernandez


On Dec. 2, 2015, 10:48 p.m., Nate Cole wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40883/
> ---
> 
> (Updated Dec. 2, 2015, 10:48 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez and Jonathan Hurley.
> 
> 
> Bugs: AMBARI-14164
> https://issues.apache.org/jira/browse/AMBARI-14164
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> During EU, an error was encountered preventing the removal of configurations. 
> The equals() method was forcing a lazy-load of data for an entity that didn't 
> exist.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ClusterConfigEntity.java
>  f28cc02 
> 
> Diff: https://reviews.apache.org/r/40883/diff/
> 
> 
> Testing
> ---
> 
> No new tests required.  Manual upgrade worked.  Automated to confirm no 
> breakage pending.
> 
> 
> Thanks,
> 
> Nate Cole
> 
>