[jira] [Commented] (AMBARI-15151) Add PHD-3.4 and above stack definitions in pluggable stack config

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15151:
-

ABORTED: Integrated in Ambari-trunk-Commit #4379 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4379/])
AMBARI-15151: Add PHD-3.4 and above stack definitions in pluggable stack 
(jluniya: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4ae5200fd92833e8e6bb42f66432598404223cdb])
* ambari-common/src/main/python/pluggable_stack_definition/configs/PHD.json


> Add PHD-3.4 and above stack definitions in pluggable stack config
> -
>
> Key: AMBARI-15151
> URL: https://issues.apache.org/jira/browse/AMBARI-15151
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.1
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15151-2.2.2.patch, AMBARI-15151-trunk.patch
>
>
> PHD-3.4 and above stacks need to be added to PHD.json



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

[jira] [Commented] (AMBARI-14987) assign_master_component.js does not show recommendations while adding master component for a service which is already installed

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14987:


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

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

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

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

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

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

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

This message is automatically generated.

> assign_master_component.js does not show recommendations while adding master 
> component for a service which is already installed
> ---
>
> Key: AMBARI-14987
> URL: https://issues.apache.org/jira/browse/AMBARI-14987
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-14987-branch-2.2-feedback-orig.patch, 
> AMBARI-14987-branch-2.2-v1.patch, AMBARI-14987-branch-2.2-v2.patch, 
> AMBARI-14987-branch-2.2.patch, AMBARI-14987-trunk-feedback-orig.patch, 
> AMBARI-14987-trunk-v1.patch, AMBARI-14987-trunk-v2.patch, 
> AMBARI-14987-trunk-v3.patch, AMBARI-14987-trunk.patch
>
>
> On the assign masters page for the wizard, recommendations are not shown for 
> a master component that is being added for an installed service.
> This happens while adding HAWQSTANDBY to the cluster using the 'Add 
> HAWQSTANDBY' wizard (situation: HAWQ service is already installed on the 
> cluster). 
> The fix might also solve the issue where there is a installed service and the 
> upgrade of the service includes installing a new master component



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

[jira] [Commented] (AMBARI-15132) in upgrade.xml to support set/replace/transfer

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-15132:


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

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

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

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

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

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

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

This message is automatically generated.

>  in upgrade.xml to support set/replace/transfer
> --
>
> Key: AMBARI-15132
> URL: https://issues.apache.org/jira/browse/AMBARI-15132
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, ambari-web
>Affects Versions: 2.2.0
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-15132.patch
>
>
>  in upgrade.xml  currently only supports single property set. this 
> is to improve it to to support set/replace/transfer. The code change must be 
> backward compatible in order to not break the existing update-***.xml and 
> nonrolling-upgrade-***.xml.



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

[jira] [Commented] (AMBARI-15151) Add PHD-3.4 and above stack definitions in pluggable stack config

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15151:
-

SUCCESS: Integrated in Ambari-branch-2.2 #399 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/399/])
AMBARI-15151: Add PHD-3.4 and above stack definitions in pluggable stack 
(jluniya: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=a01c4ad3f1445b6d016651a0f12c19dc3ac7f0a8])
* ambari-common/src/main/python/pluggable_stack_definition/configs/PHD.json


> Add PHD-3.4 and above stack definitions in pluggable stack config
> -
>
> Key: AMBARI-15151
> URL: https://issues.apache.org/jira/browse/AMBARI-15151
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.1
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15151-2.2.2.patch, AMBARI-15151-trunk.patch
>
>
> PHD-3.4 and above stacks need to be added to PHD.json



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

[jira] [Commented] (AMBARI-15148) Implement AMS collector certificate verification on monitor and service check sides

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-15148:


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

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

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

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

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

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

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

This message is automatically generated.

> Implement AMS collector certificate verification on monitor and service check 
> sides
> ---
>
> Key: AMBARI-15148
> URL: https://issues.apache.org/jira/browse/AMBARI-15148
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, stacks
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15148-trunk.patch
>
>
> Implement AMS collector certificate verification on monitor and service check 
> sides.
> +Grafana
> Implement http(-s) connetion reusing to reduce processing overhead for SSL 
> handshaking



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

Re: Review Request 43743: AMBARI-13424. Allow disabling RU/EU PreChecks

[Jonathan Hurley]

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


Ship it!




Ship It!

- Jonathan Hurley


On Feb. 23, 2016, 7:56 p.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43743/
> ---
> 
> (Updated Feb. 23, 2016, 7:56 p.m.)
> 
> 
> Review request for Ambari, Dmitro Lisnichenko, Jonathan Hurley, Nate Cole, 
> Richard Zang, and Xi Wang.
> 
> 
> Bugs: AMBARI-13424
> https://issues.apache.org/jira/browse/AMBARI-13424
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> In some environments, the customer still wants to proceed with RU & EU even 
> if PreChecks fail. E.g.,
> NameNode HA doesn't actually exist if they have their own distribution of HDFS
> Hosts be down at the time the upgrade is starting, but will come online 
> during the upgrade.
> 
> Today, they are unable to start RU/EU if any of the PreChecks fail.
> Introduce a config in ambari.properties file called 
> "stack.upgrade.bypass.prechecks" whose default value is "false"
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/AbstractCheckDescriptor.java
>  a8af073 
>   
> ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
>  32e2ea9 
>   ambari-server/src/main/java/org/apache/ambari/server/state/CheckHelper.java 
> 5a8d4fd 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/stack/PrereqCheckStatus.java
>  f8009e3 
>   
> ambari-server/src/test/java/org/apache/ambari/server/state/CheckHelperTest.java
>  283a3ca 
>   ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js 
> 29b996f 
>   ambari-web/app/messages.js c9ae08c 
>   ambari-web/app/styles/stack_versions.less b06ec8f 
>   ambari-web/app/templates/common/modal_popups/cluster_check_dialog.hbs 
> 8fd2746 
>   ambari-web/app/templates/main/admin/stack_upgrade/upgrade_options.hbs 
> 268ea1d 
>   ambari-web/app/views/common/modal_popups/cluster_check_popup.js d173d1a 
> 
> Diff: https://reviews.apache.org/r/43743/diff/
> 
> 
> Testing
> ---
> 
> Verified on PreChecks for RU/EU when put hosts in maintenance mode and tested 
> with/without the config "stack.upgrade.bypass.prechecks"
> See screenshots in Apache Jira.
> 
> Waiting for unit test results.
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

[jira] [Commented] (AMBARI-15149) Remove Result.STATUS enum as it is not being used

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-15149:


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

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

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

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

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

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

  org.apache.ambari.server.state.cluster.ClusterDeadlockTest

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

This message is automatically generated.

> Remove Result.STATUS enum as it is not being used
> -
>
> Key: AMBARI-15149
> URL: https://issues.apache.org/jira/browse/AMBARI-15149
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Ajit Kumar
>Assignee: Ajit Kumar
> Fix For: 2.4.0
>
> Attachments: rb43909.patch
>
>
> Remove Result.STATUS enum as it is not being used. ResultStatus.STATUS is 
> being used instead.



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

[jira] [Updated] (AMBARI-15152) Combo Search: Implement "service component" related filters

[Richard Zang (JIRA)]

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

Richard Zang updated AMBARI-15152:
--
Attachment: AMBARI-15152.patch

> Combo Search: Implement "service component" related filters
> ---
>
> Key: AMBARI-15152
> URL: https://issues.apache.org/jira/browse/AMBARI-15152
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Richard Zang
>Assignee: Richard Zang
> Fix For: 2.4.0
>
> Attachments: AMBARI-15152.patch
>
>
> Component:Component (will be a fixed list of choices, should be grouped 
> "category" by Service, since this is a finite list of choices for a given 
> cluster) Example: DataNode, NodeManager, NameNode



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

Review Request 43928: Combo Search: Implement "service component" related filters

[Richard Zang]

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

Review request for Ambari, Jaimin Jetly, Xi Wang, and Yusaku Sako.


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


Repository: ambari


Description
---

Implement "service component" related filters.
Support OR, AND condition for filter tags.


Diffs
-

  ambari-web/app/controllers/global/update_controller.js 04e7427 
  ambari-web/app/controllers/main/host.js 91b4df2 
  ambari-web/app/controllers/main/host/combo_search_box.js 0aeb31b 
  ambari-web/app/mixins/common/table_server_view_mixin.js 674042f 
  ambari-web/app/views/main/host/combo_search_box.js 93c2b9b 

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


Testing
---

Manually tested on live cluster.
All unit tests passed.
  24315 tests complete (22 seconds)
  146 tests pending


Thanks,

Richard Zang

[jira] [Created] (AMBARI-15152) Combo Search: Implement "service component" related filters

[Richard Zang (JIRA)]

Richard Zang created AMBARI-15152:
-

 Summary: Combo Search: Implement "service component" related 
filters
 Key: AMBARI-15152
 URL: https://issues.apache.org/jira/browse/AMBARI-15152
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Richard Zang
Assignee: Richard Zang
 Fix For: 2.4.0


Component:Component (will be a fixed list of choices, should be grouped 
"category" by Service, since this is a finite list of choices for a given 
cluster) Example: DataNode, NodeManager, NameNode



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

[jira] [Commented] (AMBARI-14821) Unit tests doesn't export scripts from common-services folder into PYTHONPATH

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14821:
-

SUCCESS: Integrated in Ambari-trunk-Commit #4378 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4378/])
AMBARI-14821: Unit tests doesn't export scripts from common-services (jaoki: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d032056754246880a48939255784767bc31302e4])
* ambari-server/src/test/python/unitTests.py


> Unit tests doesn't export scripts from common-services folder into PYTHONPATH
> -
>
> Key: AMBARI-14821
> URL: https://issues.apache.org/jira/browse/AMBARI-14821
> Project: Ambari
>  Issue Type: Bug
>Reporter: Newton Alex
>Assignee: Newton Alex
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-14821_trunk.patch
>
>
> When running unit tests with mocks like
> ---
>   @patch ('hawqmaster.common.__set_osparams')
>   @patch ('hawqmaster.master_helper.__is_active_master')
>   @patch ('hawqmaster.master_helper.__is_local_initialized')
>   def test_start_default(self, is_local_initialized_mock, active_master_mock, 
> set_osparams_mock):
> ...
> 
> the unit tests fail with the following msg:
> 
> Failed tests:
> ERROR: test_configure_default (test_hawqmaster.TestHawqMaster)
> --
> Traceback (most recent call last):
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-common/src/test/python/mock/mock.py",
>  line 1191, in patched
> arg = patching.__enter__()
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-common/src/test/python/mock/mock.py",
>  line 1250, in __enter__
> self.target = self.getter()
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-common/src/test/python/mock/mock.py",
>  line 1412, in 
> getter = lambda: _importer(target)
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-common/src/test/python/mock/mock.py",
>  line 1096, in _importer
> thing = __import__(import_path)
> ImportError: No module named hawqmaster
> -
> the source scripts from common-services are not getting exported into 
> PYTHONPATH during unittest execution.



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

[jira] [Commented] (AMBARI-14798) Users cannot login with uppercase username

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14798:
-

FAILURE: Integrated in Ambari-branch-2.2 #398 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/398/])
AMBARI-14798. Users cannot login with uppercase username (Oliver Szabo (rlevas: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3eb1ec9c27bc0558ecab0a6935b4b5b08efb820e])
* 
ambari-server/src/test/java/org/apache/ambari/server/api/services/UserServiceTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/services/UserPrivilegeService.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/services/ActiveWidgetLayoutService.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/services/UserService.java
* 
ambari-server/src/test/java/org/apache/ambari/server/api/services/ActiveWidgetLayoutServiceTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/api/services/UserPrivilegeServiceTest.java


> Users cannot login with uppercase username
> --
>
> Key: AMBARI-14798
> URL: https://issues.apache.org/jira/browse/AMBARI-14798
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.2.2
>
> Attachments: AMBARI-14798.patch, AMBARI-14798_branch-2.2.patch
>
>
> In Ambari DB, every username is stored in lowercase format. If a remote 
> server store users in uppercase format (e.g. an active directory), the user 
> cannot login with using uppercase letters in the username.



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

[jira] [Commented] (AMBARI-15141) Start all services request aborts in the middle and hosts go into heartbeat-lost state

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15141:
-

FAILURE: Integrated in Ambari-branch-2.2 #398 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/398/])
AMBARI-15141. Start all services request aborts in the middle and hosts 
(mpapyrkovskyy: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=19781ff599becf7e89b02acbf8a8e1832b7e68c5])
* 
ambari-server/src/main/java/org/apache/ambari/server/agent/HeartbeatMonitor.java
* 
ambari-server/src/test/java/org/apache/ambari/server/agent/HeartbeatTestHelper.java
* 
ambari-server/src/test/java/org/apache/ambari/server/agent/TestHeartbeatHandler.java
* 
ambari-server/src/main/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostImpl.java
* 
ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java
* 
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
* 
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/HostVersionDAO.java
* 
ambari-server/src/main/java/org/apache/ambari/server/agent/HeartbeatProcessor.java
* 
ambari-server/src/test/java/org/apache/ambari/server/agent/HeartbeatProcessorTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/HostVersionEntity.java


> Start all services request aborts in the middle and hosts go into 
> heartbeat-lost state
> --
>
> Key: AMBARI-15141
> URL: https://issues.apache.org/jira/browse/AMBARI-15141
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15141.patch, AMBARI-15141_branch-2.2.patch
>
>
> On the 1600 node cluster I attempted to do Stop-All and Start-All actions. 
> During both actions, the request would abort itself - sometimes even when 
> there were no failures or timeouts. Also, during this time hosts would go 
> into heartbeat-lost state and the cluster would look like its broken. After 
> like 5-10 minutes, the hosts slowly come back online and correct host-status 
> is got. But due to request abort, some components would be stopped/started 
> when they should not be.



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

[jira] [Commented] (AMBARI-15151) Add PHD-3.4 and above stack definitions in pluggable stack config

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-15151:


Branch-2.2
commit a01c4ad3f1445b6d016651a0f12c19dc3ac7f0a8
Author: Jayush Luniya 
Date:   Tue Feb 23 17:35:52 2016 -0800

AMBARI-15151: Add PHD-3.4 and above stack definitions in pluggable stack 
config (jluniya)

> Add PHD-3.4 and above stack definitions in pluggable stack config
> -
>
> Key: AMBARI-15151
> URL: https://issues.apache.org/jira/browse/AMBARI-15151
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.1
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15151-2.2.2.patch, AMBARI-15151-trunk.patch
>
>
> PHD-3.4 and above stacks need to be added to PHD.json



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

[jira] [Commented] (AMBARI-15151) Add PHD-3.4 and above stack definitions in pluggable stack config

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-15151:


Trunk
commit 4ae5200fd92833e8e6bb42f66432598404223cdb
Author: Jayush Luniya 
Date:   Tue Feb 23 17:35:02 2016 -0800

AMBARI-15151: Add PHD-3.4 and above stack definitions in pluggable stack 
config (jluniya)

> Add PHD-3.4 and above stack definitions in pluggable stack config
> -
>
> Key: AMBARI-15151
> URL: https://issues.apache.org/jira/browse/AMBARI-15151
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.1
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15151-2.2.2.patch, AMBARI-15151-trunk.patch
>
>
> PHD-3.4 and above stacks need to be added to PHD.json



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

[jira] [Commented] (AMBARI-15151) Add PHD-3.4 and above stack definitions in pluggable stack config

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-15151:


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

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

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

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

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

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

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

This message is automatically generated.

> Add PHD-3.4 and above stack definitions in pluggable stack config
> -
>
> Key: AMBARI-15151
> URL: https://issues.apache.org/jira/browse/AMBARI-15151
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.1
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15151-2.2.2.patch, AMBARI-15151-trunk.patch
>
>
> PHD-3.4 and above stacks need to be added to PHD.json



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

Re: Review Request 43743: AMBARI-13424. Allow disabling RU/EU PreChecks

[Nate Cole]

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


Ship it!




Much cleaner!

- Nate Cole


On Feb. 23, 2016, 7:56 p.m., Alejandro Fernandez wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43743/
> ---
> 
> (Updated Feb. 23, 2016, 7:56 p.m.)
> 
> 
> Review request for Ambari, Dmitro Lisnichenko, Jonathan Hurley, Nate Cole, 
> Richard Zang, and Xi Wang.
> 
> 
> Bugs: AMBARI-13424
> https://issues.apache.org/jira/browse/AMBARI-13424
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> In some environments, the customer still wants to proceed with RU & EU even 
> if PreChecks fail. E.g.,
> NameNode HA doesn't actually exist if they have their own distribution of HDFS
> Hosts be down at the time the upgrade is starting, but will come online 
> during the upgrade.
> 
> Today, they are unable to start RU/EU if any of the PreChecks fail.
> Introduce a config in ambari.properties file called 
> "stack.upgrade.bypass.prechecks" whose default value is "false"
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/checks/AbstractCheckDescriptor.java
>  a8af073 
>   
> ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
>  32e2ea9 
>   ambari-server/src/main/java/org/apache/ambari/server/state/CheckHelper.java 
> 5a8d4fd 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/stack/PrereqCheckStatus.java
>  f8009e3 
>   
> ambari-server/src/test/java/org/apache/ambari/server/state/CheckHelperTest.java
>  283a3ca 
>   ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js 
> 29b996f 
>   ambari-web/app/messages.js c9ae08c 
>   ambari-web/app/styles/stack_versions.less b06ec8f 
>   ambari-web/app/templates/common/modal_popups/cluster_check_dialog.hbs 
> 8fd2746 
>   ambari-web/app/templates/main/admin/stack_upgrade/upgrade_options.hbs 
> 268ea1d 
>   ambari-web/app/views/common/modal_popups/cluster_check_popup.js d173d1a 
> 
> Diff: https://reviews.apache.org/r/43743/diff/
> 
> 
> Testing
> ---
> 
> Verified on PreChecks for RU/EU when put hosts in maintenance mode and tested 
> with/without the config "stack.upgrade.bypass.prechecks"
> See screenshots in Apache Jira.
> 
> Waiting for unit test results.
> 
> 
> Thanks,
> 
> Alejandro Fernandez
> 
>

[jira] [Updated] (AMBARI-13424) Allow disabling RU/EU PreChecks

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-13424:
-
Attachment: (was: AMBARI-13424.trunk.v3.patch)

> Allow disabling RU/EU PreChecks
> ---
>
> Key: AMBARI-13424
> URL: https://issues.apache.org/jira/browse/AMBARI-13424
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.2
> Environment: Ambari 2.1.2, upgrading HDP 2.2.8 to 2.3.0.0.
> Single CentOS VM running Ambari Server and Ambari Agent 2.1.2, and HDP.
> Only hdfs, zookeeper and ambari metrics components are installed.
> The cluster has no NameNode HA enabled.
>Reporter: Robert Ketcherside
>Assignee: Alejandro Fernandez
> Attachments: AMBARI-13424.branch-2.2.v3.patch, 
> AMBARI-13424.trunk.v3.patch, Screen Shot 2016-02-18 at 2.53.07 PM.png, Screen 
> Shot 2016-02-18 at 2.53.24 PM.png, Screen Shot 2016-02-18 at 2.53.30 PM.png
>
>
> In some environments, the customer still wants to proceed with RU & EU even 
> if PreChecks fail. E.g.,
> NameNode HA doesn't actually exist if they have their own distribution of HDFS
> Hosts be down at the time the upgrade is starting, but will come online 
> during the upgrade.
> Today, they are unable to start RU/EU if any of the PreChecks fail.
> Introduce a config in ambari.properties file called 
> "stack.upgrade.bypass.prechecks" whose default value is "false"



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

[jira] [Updated] (AMBARI-13424) Allow disabling RU/EU PreChecks

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-13424:
-
Attachment: AMBARI-13424.trunk.v3.patch

> Allow disabling RU/EU PreChecks
> ---
>
> Key: AMBARI-13424
> URL: https://issues.apache.org/jira/browse/AMBARI-13424
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.2
> Environment: Ambari 2.1.2, upgrading HDP 2.2.8 to 2.3.0.0.
> Single CentOS VM running Ambari Server and Ambari Agent 2.1.2, and HDP.
> Only hdfs, zookeeper and ambari metrics components are installed.
> The cluster has no NameNode HA enabled.
>Reporter: Robert Ketcherside
>Assignee: Alejandro Fernandez
> Attachments: AMBARI-13424.branch-2.2.v3.patch, 
> AMBARI-13424.trunk.v3.patch, Screen Shot 2016-02-18 at 2.53.07 PM.png, Screen 
> Shot 2016-02-18 at 2.53.24 PM.png, Screen Shot 2016-02-18 at 2.53.30 PM.png
>
>
> In some environments, the customer still wants to proceed with RU & EU even 
> if PreChecks fail. E.g.,
> NameNode HA doesn't actually exist if they have their own distribution of HDFS
> Hosts be down at the time the upgrade is starting, but will come online 
> during the upgrade.
> Today, they are unable to start RU/EU if any of the PreChecks fail.
> Introduce a config in ambari.properties file called 
> "stack.upgrade.bypass.prechecks" whose default value is "false"



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

Re: Review Request 43743: AMBARI-13424. Allow disabling RU/EU PreChecks

[Alejandro Fernandez]

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

(Updated Feb. 24, 2016, 12:56 a.m.)


Review request for Ambari, Dmitro Lisnichenko, Jonathan Hurley, Nate Cole, 
Richard Zang, and Xi Wang.


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


Repository: ambari


Description
---

In some environments, the customer still wants to proceed with RU & EU even if 
PreChecks fail. E.g.,
NameNode HA doesn't actually exist if they have their own distribution of HDFS
Hosts be down at the time the upgrade is starting, but will come online during 
the upgrade.

Today, they are unable to start RU/EU if any of the PreChecks fail.
Introduce a config in ambari.properties file called 
"stack.upgrade.bypass.prechecks" whose default value is "false"


Diffs (updated)
-

  
ambari-server/src/main/java/org/apache/ambari/server/checks/AbstractCheckDescriptor.java
 a8af073 
  
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
 32e2ea9 
  ambari-server/src/main/java/org/apache/ambari/server/state/CheckHelper.java 
5a8d4fd 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/PrereqCheckStatus.java
 f8009e3 
  
ambari-server/src/test/java/org/apache/ambari/server/state/CheckHelperTest.java 
283a3ca 
  ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js 29b996f 
  ambari-web/app/messages.js c9ae08c 
  ambari-web/app/styles/stack_versions.less b06ec8f 
  ambari-web/app/templates/common/modal_popups/cluster_check_dialog.hbs 8fd2746 
  ambari-web/app/templates/main/admin/stack_upgrade/upgrade_options.hbs 268ea1d 
  ambari-web/app/views/common/modal_popups/cluster_check_popup.js d173d1a 

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


Testing
---

Verified on PreChecks for RU/EU when put hosts in maintenance mode and tested 
with/without the config "stack.upgrade.bypass.prechecks"
See screenshots in Apache Jira.

Waiting for unit test results.


Thanks,

Alejandro Fernandez

[jira] [Commented] (AMBARI-15151) Add PHD-3.4 and above stack definitions in pluggable stack config

[Mahadev konar (JIRA)]

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

Mahadev konar commented on AMBARI-15151:


+1 for hte patch.

> Add PHD-3.4 and above stack definitions in pluggable stack config
> -
>
> Key: AMBARI-15151
> URL: https://issues.apache.org/jira/browse/AMBARI-15151
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.1
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15151-2.2.2.patch, AMBARI-15151-trunk.patch
>
>
> PHD-3.4 and above stacks need to be added to PHD.json



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

[jira] [Updated] (AMBARI-13424) Allow disabling RU/EU PreChecks

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-13424:
-
Attachment: AMBARI-13424.branch-2.2.v3.patch
AMBARI-13424.trunk.v3.patch

> Allow disabling RU/EU PreChecks
> ---
>
> Key: AMBARI-13424
> URL: https://issues.apache.org/jira/browse/AMBARI-13424
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.2
> Environment: Ambari 2.1.2, upgrading HDP 2.2.8 to 2.3.0.0.
> Single CentOS VM running Ambari Server and Ambari Agent 2.1.2, and HDP.
> Only hdfs, zookeeper and ambari metrics components are installed.
> The cluster has no NameNode HA enabled.
>Reporter: Robert Ketcherside
>Assignee: Alejandro Fernandez
> Attachments: AMBARI-13424.branch-2.2.v3.patch, 
> AMBARI-13424.trunk.v3.patch, Screen Shot 2016-02-18 at 2.53.07 PM.png, Screen 
> Shot 2016-02-18 at 2.53.24 PM.png, Screen Shot 2016-02-18 at 2.53.30 PM.png
>
>
> In some environments, the customer still wants to proceed with RU & EU even 
> if PreChecks fail. E.g.,
> NameNode HA doesn't actually exist if they have their own distribution of HDFS
> Hosts be down at the time the upgrade is starting, but will come online 
> during the upgrade.
> Today, they are unable to start RU/EU if any of the PreChecks fail.
> Introduce a config in ambari.properties file called 
> "stack.upgrade.bypass.prechecks" whose default value is "false"



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

[jira] [Updated] (AMBARI-13424) Allow disabling RU/EU PreChecks

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-13424:
-
Attachment: (was: AMBARI-13424.trunk.v3.patch)

> Allow disabling RU/EU PreChecks
> ---
>
> Key: AMBARI-13424
> URL: https://issues.apache.org/jira/browse/AMBARI-13424
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.2
> Environment: Ambari 2.1.2, upgrading HDP 2.2.8 to 2.3.0.0.
> Single CentOS VM running Ambari Server and Ambari Agent 2.1.2, and HDP.
> Only hdfs, zookeeper and ambari metrics components are installed.
> The cluster has no NameNode HA enabled.
>Reporter: Robert Ketcherside
>Assignee: Alejandro Fernandez
> Attachments: Screen Shot 2016-02-18 at 2.53.07 PM.png, Screen Shot 
> 2016-02-18 at 2.53.24 PM.png, Screen Shot 2016-02-18 at 2.53.30 PM.png
>
>
> In some environments, the customer still wants to proceed with RU & EU even 
> if PreChecks fail. E.g.,
> NameNode HA doesn't actually exist if they have their own distribution of HDFS
> Hosts be down at the time the upgrade is starting, but will come online 
> during the upgrade.
> Today, they are unable to start RU/EU if any of the PreChecks fail.
> Introduce a config in ambari.properties file called 
> "stack.upgrade.bypass.prechecks" whose default value is "false"



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

Re: Review Request 43743: AMBARI-13424. Allow disabling RU/EU PreChecks

[Alejandro Fernandez]

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

(Updated Feb. 24, 2016, 12:41 a.m.)


Review request for Ambari, Dmitro Lisnichenko, Jonathan Hurley, Nate Cole, 
Richard Zang, and Xi Wang.


Changes
---

Fixed unit tests.


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


Repository: ambari


Description
---

In some environments, the customer still wants to proceed with RU & EU even if 
PreChecks fail. E.g.,
NameNode HA doesn't actually exist if they have their own distribution of HDFS
Hosts be down at the time the upgrade is starting, but will come online during 
the upgrade.

Today, they are unable to start RU/EU if any of the PreChecks fail.
Introduce a config in ambari.properties file called 
"stack.upgrade.bypass.prechecks" whose default value is "false"


Diffs (updated)
-

  
ambari-server/src/main/java/org/apache/ambari/server/checks/AbstractCheckDescriptor.java
 a8af073 
  
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
 32e2ea9 
  ambari-server/src/main/java/org/apache/ambari/server/state/CheckHelper.java 
5a8d4fd 
  
ambari-server/src/main/java/org/apache/ambari/server/state/stack/PrereqCheckStatus.java
 f8009e3 
  
ambari-server/src/test/java/org/apache/ambari/server/state/CheckHelperTest.java 
283a3ca 
  ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js 29b996f 
  ambari-web/app/messages.js c9ae08c 
  ambari-web/app/styles/stack_versions.less b06ec8f 
  ambari-web/app/templates/common/modal_popups/cluster_check_dialog.hbs 8fd2746 
  ambari-web/app/templates/main/admin/stack_upgrade/upgrade_options.hbs 268ea1d 
  ambari-web/app/views/common/modal_popups/cluster_check_popup.js d173d1a 

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


Testing
---

Verified on PreChecks for RU/EU when put hosts in maintenance mode and tested 
with/without the config "stack.upgrade.bypass.prechecks"
See screenshots in Apache Jira.

Waiting for unit test results.


Thanks,

Alejandro Fernandez

[jira] [Updated] (AMBARI-13424) Allow disabling RU/EU PreChecks

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-13424:
-
Attachment: (was: AMBARI-13424.branch-2.2.v3.patch)

> Allow disabling RU/EU PreChecks
> ---
>
> Key: AMBARI-13424
> URL: https://issues.apache.org/jira/browse/AMBARI-13424
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.2
> Environment: Ambari 2.1.2, upgrading HDP 2.2.8 to 2.3.0.0.
> Single CentOS VM running Ambari Server and Ambari Agent 2.1.2, and HDP.
> Only hdfs, zookeeper and ambari metrics components are installed.
> The cluster has no NameNode HA enabled.
>Reporter: Robert Ketcherside
>Assignee: Alejandro Fernandez
> Attachments: Screen Shot 2016-02-18 at 2.53.07 PM.png, Screen Shot 
> 2016-02-18 at 2.53.24 PM.png, Screen Shot 2016-02-18 at 2.53.30 PM.png
>
>
> In some environments, the customer still wants to proceed with RU & EU even 
> if PreChecks fail. E.g.,
> NameNode HA doesn't actually exist if they have their own distribution of HDFS
> Hosts be down at the time the upgrade is starting, but will come online 
> during the upgrade.
> Today, they are unable to start RU/EU if any of the PreChecks fail.
> Introduce a config in ambari.properties file called 
> "stack.upgrade.bypass.prechecks" whose default value is "false"



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

[jira] [Updated] (AMBARI-13424) Allow disabling RU/EU PreChecks

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-13424:
-
Attachment: (was: AMBARI-13424.branch-2.2.patch)

> Allow disabling RU/EU PreChecks
> ---
>
> Key: AMBARI-13424
> URL: https://issues.apache.org/jira/browse/AMBARI-13424
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.2
> Environment: Ambari 2.1.2, upgrading HDP 2.2.8 to 2.3.0.0.
> Single CentOS VM running Ambari Server and Ambari Agent 2.1.2, and HDP.
> Only hdfs, zookeeper and ambari metrics components are installed.
> The cluster has no NameNode HA enabled.
>Reporter: Robert Ketcherside
>Assignee: Alejandro Fernandez
> Attachments: AMBARI-13424.branch-2.2.v3.patch, 
> AMBARI-13424.trunk.v3.patch, Screen Shot 2016-02-18 at 2.53.07 PM.png, Screen 
> Shot 2016-02-18 at 2.53.24 PM.png, Screen Shot 2016-02-18 at 2.53.30 PM.png
>
>
> In some environments, the customer still wants to proceed with RU & EU even 
> if PreChecks fail. E.g.,
> NameNode HA doesn't actually exist if they have their own distribution of HDFS
> Hosts be down at the time the upgrade is starting, but will come online 
> during the upgrade.
> Today, they are unable to start RU/EU if any of the PreChecks fail.
> Introduce a config in ambari.properties file called 
> "stack.upgrade.bypass.prechecks" whose default value is "false"



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

[jira] [Commented] (AMBARI-15151) Add PHD-3.4 and above stack definitions in pluggable stack config

[Jayush Luniya (JIRA)]

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

Jayush Luniya commented on AMBARI-15151:


[~mahadev] [~sumitmohanty]
Can you review the patches?

> Add PHD-3.4 and above stack definitions in pluggable stack config
> -
>
> Key: AMBARI-15151
> URL: https://issues.apache.org/jira/browse/AMBARI-15151
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.1
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15151-2.2.2.patch, AMBARI-15151-trunk.patch
>
>
> PHD-3.4 and above stacks need to be added to PHD.json



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

[jira] [Commented] (AMBARI-15147) Patch Upgrade: integrate API to POST new repo version when registering new version

[Xi Wang (JIRA)]

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

Xi Wang commented on AMBARI-15147:
--

Committed to branch-dev-patch-upgrade

> Patch Upgrade: integrate API to  POST new repo version when registering new 
> version
> ---
>
> Key: AMBARI-15147
> URL: https://issues.apache.org/jira/browse/AMBARI-15147
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-15147.patch, AMBARI-15147.patch, 
> AMBARI-15147.patch
>
>
> On Register Version page, UI provides two ways to upload version definition 
> file, both should POST new stack version. 
> 1. Browse local files and then Upload file,
> {code}
> POST /api/v1/version_definitions
> 
> {code}
> The equivalent curl call would look like so (the text/xml header is required):
> {code}
> curl -u admin:admin -H "Content-Type: text/xml" -X POST -d 
> @ambari-server/src/test/resources/hbase_version_test.xml 
> http://localhost:8080/api/v1/version_definitions
> {code}
> 2. Enter the Url then click on "Read Version File" button,
> {code}
> POST  /api/v1/version_definitions
> {
>   "RepositoryVersions": {
> "version_url": "http://somewhere/version-definition.xml;
>   }
> }
> {code}



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

[jira] [Updated] (AMBARI-15151) Add PHD-3.4 and above stack definitions in pluggable stack config

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-15151:
---
Attachment: AMBARI-15151-trunk.patch

> Add PHD-3.4 and above stack definitions in pluggable stack config
> -
>
> Key: AMBARI-15151
> URL: https://issues.apache.org/jira/browse/AMBARI-15151
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.1
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15151-2.2.2.patch, AMBARI-15151-trunk.patch
>
>
> PHD-3.4 and above stacks need to be added to PHD.json



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

[jira] [Updated] (AMBARI-13424) Allow disabling RU/EU PreChecks

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-13424:
-
Attachment: (was: AMBARI-13424.trunk.patch)

> Allow disabling RU/EU PreChecks
> ---
>
> Key: AMBARI-13424
> URL: https://issues.apache.org/jira/browse/AMBARI-13424
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.2
> Environment: Ambari 2.1.2, upgrading HDP 2.2.8 to 2.3.0.0.
> Single CentOS VM running Ambari Server and Ambari Agent 2.1.2, and HDP.
> Only hdfs, zookeeper and ambari metrics components are installed.
> The cluster has no NameNode HA enabled.
>Reporter: Robert Ketcherside
>Assignee: Alejandro Fernandez
> Attachments: AMBARI-13424.branch-2.2.v3.patch, 
> AMBARI-13424.trunk.v3.patch, Screen Shot 2016-02-18 at 2.53.07 PM.png, Screen 
> Shot 2016-02-18 at 2.53.24 PM.png, Screen Shot 2016-02-18 at 2.53.30 PM.png
>
>
> In some environments, the customer still wants to proceed with RU & EU even 
> if PreChecks fail. E.g.,
> NameNode HA doesn't actually exist if they have their own distribution of HDFS
> Hosts be down at the time the upgrade is starting, but will come online 
> during the upgrade.
> Today, they are unable to start RU/EU if any of the PreChecks fail.
> Introduce a config in ambari.properties file called 
> "stack.upgrade.bypass.prechecks" whose default value is "false"



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

[jira] [Updated] (AMBARI-13424) Allow disabling RU/EU PreChecks

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-13424:
-
Attachment: AMBARI-13424.branch-2.2.v3.patch
AMBARI-13424.trunk.v3.patch

> Allow disabling RU/EU PreChecks
> ---
>
> Key: AMBARI-13424
> URL: https://issues.apache.org/jira/browse/AMBARI-13424
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.2
> Environment: Ambari 2.1.2, upgrading HDP 2.2.8 to 2.3.0.0.
> Single CentOS VM running Ambari Server and Ambari Agent 2.1.2, and HDP.
> Only hdfs, zookeeper and ambari metrics components are installed.
> The cluster has no NameNode HA enabled.
>Reporter: Robert Ketcherside
>Assignee: Alejandro Fernandez
> Attachments: AMBARI-13424.branch-2.2.v3.patch, 
> AMBARI-13424.trunk.v3.patch, Screen Shot 2016-02-18 at 2.53.07 PM.png, Screen 
> Shot 2016-02-18 at 2.53.24 PM.png, Screen Shot 2016-02-18 at 2.53.30 PM.png
>
>
> In some environments, the customer still wants to proceed with RU & EU even 
> if PreChecks fail. E.g.,
> NameNode HA doesn't actually exist if they have their own distribution of HDFS
> Hosts be down at the time the upgrade is starting, but will come online 
> during the upgrade.
> Today, they are unable to start RU/EU if any of the PreChecks fail.
> Introduce a config in ambari.properties file called 
> "stack.upgrade.bypass.prechecks" whose default value is "false"



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

[jira] [Updated] (AMBARI-15151) Add PHD-3.4 and above stack definitions in pluggable stack config

[Jayush Luniya (JIRA)]

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

Jayush Luniya updated AMBARI-15151:
---
Attachment: AMBARI-15151-2.2.2.patch

> Add PHD-3.4 and above stack definitions in pluggable stack config
> -
>
> Key: AMBARI-15151
> URL: https://issues.apache.org/jira/browse/AMBARI-15151
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.1
>Reporter: Jayush Luniya
>Assignee: Jayush Luniya
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15151-2.2.2.patch
>
>
> PHD-3.4 and above stacks need to be added to PHD.json



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

[jira] [Updated] (AMBARI-13424) Allow disabling RU/EU PreChecks

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-13424:
-
Attachment: (was: AMBARI-13424.branch-2.2.v3.patch)

> Allow disabling RU/EU PreChecks
> ---
>
> Key: AMBARI-13424
> URL: https://issues.apache.org/jira/browse/AMBARI-13424
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.2
> Environment: Ambari 2.1.2, upgrading HDP 2.2.8 to 2.3.0.0.
> Single CentOS VM running Ambari Server and Ambari Agent 2.1.2, and HDP.
> Only hdfs, zookeeper and ambari metrics components are installed.
> The cluster has no NameNode HA enabled.
>Reporter: Robert Ketcherside
>Assignee: Alejandro Fernandez
> Attachments: AMBARI-13424.branch-2.2.patch, AMBARI-13424.trunk.patch, 
> Screen Shot 2016-02-18 at 2.53.07 PM.png, Screen Shot 2016-02-18 at 2.53.24 
> PM.png, Screen Shot 2016-02-18 at 2.53.30 PM.png
>
>
> In some environments, the customer still wants to proceed with RU & EU even 
> if PreChecks fail. E.g.,
> NameNode HA doesn't actually exist if they have their own distribution of HDFS
> Hosts be down at the time the upgrade is starting, but will come online 
> during the upgrade.
> Today, they are unable to start RU/EU if any of the PreChecks fail.
> Introduce a config in ambari.properties file called 
> "stack.upgrade.bypass.prechecks" whose default value is "false"



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

[jira] [Updated] (AMBARI-13424) Allow disabling RU/EU PreChecks

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-13424:
-
Attachment: (was: AMBARI-13424.trunk.v3.patch)

> Allow disabling RU/EU PreChecks
> ---
>
> Key: AMBARI-13424
> URL: https://issues.apache.org/jira/browse/AMBARI-13424
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.2
> Environment: Ambari 2.1.2, upgrading HDP 2.2.8 to 2.3.0.0.
> Single CentOS VM running Ambari Server and Ambari Agent 2.1.2, and HDP.
> Only hdfs, zookeeper and ambari metrics components are installed.
> The cluster has no NameNode HA enabled.
>Reporter: Robert Ketcherside
>Assignee: Alejandro Fernandez
> Attachments: AMBARI-13424.branch-2.2.patch, AMBARI-13424.trunk.patch, 
> Screen Shot 2016-02-18 at 2.53.07 PM.png, Screen Shot 2016-02-18 at 2.53.24 
> PM.png, Screen Shot 2016-02-18 at 2.53.30 PM.png
>
>
> In some environments, the customer still wants to proceed with RU & EU even 
> if PreChecks fail. E.g.,
> NameNode HA doesn't actually exist if they have their own distribution of HDFS
> Hosts be down at the time the upgrade is starting, but will come online 
> during the upgrade.
> Today, they are unable to start RU/EU if any of the PreChecks fail.
> Introduce a config in ambari.properties file called 
> "stack.upgrade.bypass.prechecks" whose default value is "false"



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

[jira] [Created] (AMBARI-15151) Add PHD-3.4 and above stack definitions in pluggable stack config

[Jayush Luniya (JIRA)]

Jayush Luniya created AMBARI-15151:
--

 Summary: Add PHD-3.4 and above stack definitions in pluggable 
stack config
 Key: AMBARI-15151
 URL: https://issues.apache.org/jira/browse/AMBARI-15151
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.2.1
Reporter: Jayush Luniya
Assignee: Jayush Luniya
Priority: Critical
 Fix For: 2.2.2


PHD-3.4 and above stacks need to be added to PHD.json



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

[jira] [Commented] (AMBARI-15147) Patch Upgrade: integrate API to POST new repo version when registering new version

[Xi Wang (JIRA)]

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

Xi Wang commented on AMBARI-15147:
--

Get +1 from review board

> Patch Upgrade: integrate API to  POST new repo version when registering new 
> version
> ---
>
> Key: AMBARI-15147
> URL: https://issues.apache.org/jira/browse/AMBARI-15147
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-15147.patch, AMBARI-15147.patch, 
> AMBARI-15147.patch
>
>
> On Register Version page, UI provides two ways to upload version definition 
> file, both should POST new stack version. 
> 1. Browse local files and then Upload file,
> {code}
> POST /api/v1/version_definitions
> 
> {code}
> The equivalent curl call would look like so (the text/xml header is required):
> {code}
> curl -u admin:admin -H "Content-Type: text/xml" -X POST -d 
> @ambari-server/src/test/resources/hbase_version_test.xml 
> http://localhost:8080/api/v1/version_definitions
> {code}
> 2. Enter the Url then click on "Read Version File" button,
> {code}
> POST  /api/v1/version_definitions
> {
>   "RepositoryVersions": {
> "version_url": "http://somewhere/version-definition.xml;
>   }
> }
> {code}



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

Re: Review Request 43895: Patch Upgrade: integrate API to POST new repo version when registering new version

[Richard Zang]

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


Ship it!




Ship It!

- Richard Zang


On Feb. 24, 2016, 12:08 a.m., Xi Wang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43895/
> ---
> 
> (Updated Feb. 24, 2016, 12:08 a.m.)
> 
> 
> Review request for Ambari, Richard Zang and Yusaku Sako.
> 
> 
> Bugs: AMBARI-15147
> https://issues.apache.org/jira/browse/AMBARI-15147
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> On Register Version page, UI provides two ways to upload version definition 
> file, both should POST new stack version. 
> 
> 1. Browse local files and then Upload file,
> 
> POST /api/v1/version_definitions
> 
> 
> The equivalent curl call would look like so (the text/xml header is required):
> 
> curl -u admin:admin -H "Content-Type: text/xml" -X POST -d 
> @ambari-server/src/test/resources/hbase_version_test.xml 
> http://localhost:8080/api/v1/version_definitions
> 
> 
> 2. Enter the Url then click on "Read Version File" button,
> 
> POST  /api/v1/version_definitions
> {
>   "RepositoryVersions": {
> "version_url": "http://somewhere/version-definition.xml;
>   }
> }
> 
> 
> Diffs
> -
> 
>   
> ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js
>  190670a 
>   ambari-admin/src/main/resources/ui/admin-web/app/scripts/i18n.config.js 
> 0dc10c1 
>   ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Stack.js 
> ae67c7e 
>   
> ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/stackVersionPage.html
>  112ded8 
>   ambari-web/app/mappers/repository_version_mapper.js c937678 
>   ambari-web/app/styles/stack_versions.less 5490592 
>   ambari-web/app/templates/main/admin/stack_upgrade/upgrade_version_box.hbs 
> 84d7835 
>   ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js 
> 1ea0c66 
>   
> ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_column_view.js 
> d7e26e2 
> 
> Diff: https://reviews.apache.org/r/43895/diff/
> 
> 
> Testing
> ---
> 
> UT passed
> 
> 
> Thanks,
> 
> Xi Wang
> 
>

Re: Review Request 43895: Patch Upgrade: integrate API to POST new repo version when registering new version

[Xi Wang]

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

(Updated Feb. 23, 2016, 4:08 p.m.)


Review request for Ambari, Richard Zang and Yusaku Sako.


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


Repository: ambari


Description
---

On Register Version page, UI provides two ways to upload version definition 
file, both should POST new stack version. 

1. Browse local files and then Upload file,

POST /api/v1/version_definitions


The equivalent curl call would look like so (the text/xml header is required):

curl -u admin:admin -H "Content-Type: text/xml" -X POST -d 
@ambari-server/src/test/resources/hbase_version_test.xml 
http://localhost:8080/api/v1/version_definitions


2. Enter the Url then click on "Read Version File" button,

POST  /api/v1/version_definitions
{
  "RepositoryVersions": {
"version_url": "http://somewhere/version-definition.xml;
  }
}


Diffs (updated)
-

  
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js
 190670a 
  ambari-admin/src/main/resources/ui/admin-web/app/scripts/i18n.config.js 
0dc10c1 
  ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Stack.js 
ae67c7e 
  
ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/stackVersionPage.html
 112ded8 
  ambari-web/app/mappers/repository_version_mapper.js c937678 
  ambari-web/app/styles/stack_versions.less 5490592 
  ambari-web/app/templates/main/admin/stack_upgrade/upgrade_version_box.hbs 
84d7835 
  ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js 
1ea0c66 
  ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_column_view.js 
d7e26e2 

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


Testing
---

UT passed


Thanks,

Xi Wang

[jira] [Updated] (AMBARI-15147) Patch Upgrade: integrate API to POST new repo version when registering new version

[Xi Wang (JIRA)]

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

Xi Wang updated AMBARI-15147:
-
Attachment: AMBARI-15147.patch

> Patch Upgrade: integrate API to  POST new repo version when registering new 
> version
> ---
>
> Key: AMBARI-15147
> URL: https://issues.apache.org/jira/browse/AMBARI-15147
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-15147.patch, AMBARI-15147.patch, 
> AMBARI-15147.patch
>
>
> On Register Version page, UI provides two ways to upload version definition 
> file, both should POST new stack version. 
> 1. Browse local files and then Upload file,
> {code}
> POST /api/v1/version_definitions
> 
> {code}
> The equivalent curl call would look like so (the text/xml header is required):
> {code}
> curl -u admin:admin -H "Content-Type: text/xml" -X POST -d 
> @ambari-server/src/test/resources/hbase_version_test.xml 
> http://localhost:8080/api/v1/version_definitions
> {code}
> 2. Enter the Url then click on "Read Version File" button,
> {code}
> POST  /api/v1/version_definitions
> {
>   "RepositoryVersions": {
> "version_url": "http://somewhere/version-definition.xml;
>   }
> }
> {code}



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

[jira] [Commented] (AMBARI-14821) Unit tests doesn't export scripts from common-services folder into PYTHONPATH

[jun aoki (JIRA)]

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

jun aoki commented on AMBARI-14821:
---

Committed to trunk
d032056754246880a48939255784767bc31302e4

> Unit tests doesn't export scripts from common-services folder into PYTHONPATH
> -
>
> Key: AMBARI-14821
> URL: https://issues.apache.org/jira/browse/AMBARI-14821
> Project: Ambari
>  Issue Type: Bug
>Reporter: Newton Alex
>Assignee: Newton Alex
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-14821_trunk.patch
>
>
> When running unit tests with mocks like
> ---
>   @patch ('hawqmaster.common.__set_osparams')
>   @patch ('hawqmaster.master_helper.__is_active_master')
>   @patch ('hawqmaster.master_helper.__is_local_initialized')
>   def test_start_default(self, is_local_initialized_mock, active_master_mock, 
> set_osparams_mock):
> ...
> 
> the unit tests fail with the following msg:
> 
> Failed tests:
> ERROR: test_configure_default (test_hawqmaster.TestHawqMaster)
> --
> Traceback (most recent call last):
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-common/src/test/python/mock/mock.py",
>  line 1191, in patched
> arg = patching.__enter__()
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-common/src/test/python/mock/mock.py",
>  line 1250, in __enter__
> self.target = self.getter()
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-common/src/test/python/mock/mock.py",
>  line 1412, in 
> getter = lambda: _importer(target)
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-common/src/test/python/mock/mock.py",
>  line 1096, in _importer
> thing = __import__(import_path)
> ImportError: No module named hawqmaster
> -
> the source scripts from common-services are not getting exported into 
> PYTHONPATH during unittest execution.



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

[jira] [Updated] (AMBARI-14821) Unit tests doesn't export scripts from common-services folder into PYTHONPATH

[jun aoki (JIRA)]

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

jun aoki updated AMBARI-14821:
--
Fix Version/s: trunk

> Unit tests doesn't export scripts from common-services folder into PYTHONPATH
> -
>
> Key: AMBARI-14821
> URL: https://issues.apache.org/jira/browse/AMBARI-14821
> Project: Ambari
>  Issue Type: Bug
>Reporter: Newton Alex
>Assignee: Newton Alex
>Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-14821_trunk.patch
>
>
> When running unit tests with mocks like
> ---
>   @patch ('hawqmaster.common.__set_osparams')
>   @patch ('hawqmaster.master_helper.__is_active_master')
>   @patch ('hawqmaster.master_helper.__is_local_initialized')
>   def test_start_default(self, is_local_initialized_mock, active_master_mock, 
> set_osparams_mock):
> ...
> 
> the unit tests fail with the following msg:
> 
> Failed tests:
> ERROR: test_configure_default (test_hawqmaster.TestHawqMaster)
> --
> Traceback (most recent call last):
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-common/src/test/python/mock/mock.py",
>  line 1191, in patched
> arg = patching.__enter__()
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-common/src/test/python/mock/mock.py",
>  line 1250, in __enter__
> self.target = self.getter()
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-common/src/test/python/mock/mock.py",
>  line 1412, in 
> getter = lambda: _importer(target)
>   File 
> "/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-common/src/test/python/mock/mock.py",
>  line 1096, in _importer
> thing = __import__(import_path)
> ImportError: No module named hawqmaster
> -
> the source scripts from common-services are not getting exported into 
> PYTHONPATH during unittest execution.



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

[jira] [Updated] (AMBARI-13424) Allow disabling RU/EU PreChecks

[Alejandro Fernandez (JIRA)]

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

Alejandro Fernandez updated AMBARI-13424:
-
Attachment: AMBARI-13424.branch-2.2.v3.patch
AMBARI-13424.trunk.v3.patch

> Allow disabling RU/EU PreChecks
> ---
>
> Key: AMBARI-13424
> URL: https://issues.apache.org/jira/browse/AMBARI-13424
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.1.2
> Environment: Ambari 2.1.2, upgrading HDP 2.2.8 to 2.3.0.0.
> Single CentOS VM running Ambari Server and Ambari Agent 2.1.2, and HDP.
> Only hdfs, zookeeper and ambari metrics components are installed.
> The cluster has no NameNode HA enabled.
>Reporter: Robert Ketcherside
>Assignee: Alejandro Fernandez
> Attachments: AMBARI-13424.branch-2.2.patch, 
> AMBARI-13424.branch-2.2.v3.patch, AMBARI-13424.trunk.patch, 
> AMBARI-13424.trunk.v3.patch, Screen Shot 2016-02-18 at 2.53.07 PM.png, Screen 
> Shot 2016-02-18 at 2.53.24 PM.png, Screen Shot 2016-02-18 at 2.53.30 PM.png
>
>
> In some environments, the customer still wants to proceed with RU & EU even 
> if PreChecks fail. E.g.,
> NameNode HA doesn't actually exist if they have their own distribution of HDFS
> Hosts be down at the time the upgrade is starting, but will come online 
> during the upgrade.
> Today, they are unable to start RU/EU if any of the PreChecks fail.
> Introduce a config in ambari.properties file called 
> "stack.upgrade.bypass.prechecks" whose default value is "false"



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

[jira] [Commented] (AMBARI-15147) Patch Upgrade: integrate API to POST new repo version when registering new version

[Xi Wang (JIRA)]

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

Xi Wang commented on AMBARI-15147:
--

  24312 tests complete (25 seconds)
  146 tests pending


> Patch Upgrade: integrate API to  POST new repo version when registering new 
> version
> ---
>
> Key: AMBARI-15147
> URL: https://issues.apache.org/jira/browse/AMBARI-15147
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-15147.patch, AMBARI-15147.patch
>
>
> On Register Version page, UI provides two ways to upload version definition 
> file, both should POST new stack version. 
> 1. Browse local files and then Upload file,
> {code}
> POST /api/v1/version_definitions
> 
> {code}
> The equivalent curl call would look like so (the text/xml header is required):
> {code}
> curl -u admin:admin -H "Content-Type: text/xml" -X POST -d 
> @ambari-server/src/test/resources/hbase_version_test.xml 
> http://localhost:8080/api/v1/version_definitions
> {code}
> 2. Enter the Url then click on "Read Version File" button,
> {code}
> POST  /api/v1/version_definitions
> {
>   "RepositoryVersions": {
> "version_url": "http://somewhere/version-definition.xml;
>   }
> }
> {code}



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

Re: Review Request 43895: Patch Upgrade: integrate API to POST new repo version when registering new version

[Xi Wang]

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

(Updated Feb. 23, 2016, 3:46 p.m.)


Review request for Ambari, Richard Zang and Yusaku Sako.


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


Repository: ambari


Description
---

On Register Version page, UI provides two ways to upload version definition 
file, both should POST new stack version. 

1. Browse local files and then Upload file,

POST /api/v1/version_definitions


The equivalent curl call would look like so (the text/xml header is required):

curl -u admin:admin -H "Content-Type: text/xml" -X POST -d 
@ambari-server/src/test/resources/hbase_version_test.xml 
http://localhost:8080/api/v1/version_definitions


2. Enter the Url then click on "Read Version File" button,

POST  /api/v1/version_definitions
{
  "RepositoryVersions": {
"version_url": "http://somewhere/version-definition.xml;
  }
}


Diffs (updated)
-

  
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js
 190670a 
  ambari-admin/src/main/resources/ui/admin-web/app/scripts/i18n.config.js 
0dc10c1 
  ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Stack.js 
ae67c7e 
  
ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/stackVersionPage.html
 112ded8 
  ambari-web/app/mappers/repository_version_mapper.js c937678 
  ambari-web/app/styles/stack_versions.less 5490592 
  ambari-web/app/templates/main/admin/stack_upgrade/upgrade_version_box.hbs 
84d7835 
  ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js 
1ea0c66 
  ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_column_view.js 
d7e26e2 
  ambari-web/app/views/main/admin/stack_upgrade/versions_view.js 17010ba 

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


Testing
---

UT passed


Thanks,

Xi Wang

[jira] [Updated] (AMBARI-15147) Patch Upgrade: integrate API to POST new repo version when registering new version

[Xi Wang (JIRA)]

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

Xi Wang updated AMBARI-15147:
-
Attachment: AMBARI-15147.patch

> Patch Upgrade: integrate API to  POST new repo version when registering new 
> version
> ---
>
> Key: AMBARI-15147
> URL: https://issues.apache.org/jira/browse/AMBARI-15147
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-15147.patch, AMBARI-15147.patch
>
>
> On Register Version page, UI provides two ways to upload version definition 
> file, both should POST new stack version. 
> 1. Browse local files and then Upload file,
> {code}
> POST /api/v1/version_definitions
> 
> {code}
> The equivalent curl call would look like so (the text/xml header is required):
> {code}
> curl -u admin:admin -H "Content-Type: text/xml" -X POST -d 
> @ambari-server/src/test/resources/hbase_version_test.xml 
> http://localhost:8080/api/v1/version_definitions
> {code}
> 2. Enter the Url then click on "Read Version File" button,
> {code}
> POST  /api/v1/version_definitions
> {
>   "RepositoryVersions": {
> "version_url": "http://somewhere/version-definition.xml;
>   }
> }
> {code}



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

[jira] [Commented] (AMBARI-15145) Revamped Filebrowser Design - UI

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-15145:


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

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

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

{color:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

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

This message is automatically generated.

> Revamped Filebrowser Design - UI
> 
>
> Key: AMBARI-15145
> URL: https://issues.apache.org/jira/browse/AMBARI-15145
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.2.2
>
> Attachments: AMBARI-15145.branch-2.2.patch
>
>
> REQUEST:  To redo the filebrowser UI
> Requirements: 
> Rework the File Browser mostly on the Front End display to:
> -Make it scalable to handle directories with many files
> -Improve the performance
> -Improve the usability and layout
> -Add some missing capabilities 
> -Increase the quality and robustness
> Here are the high level functionalities achieved in new file browser view.
> - Show HDFS files/folders along with their Name, Size, Last Modified, Owner, 
> Group, and Permission.
> - Capability of sorting by Name, Size, Last Modified, Owner, Group, and 
> Permission in ascending or descending order for files and folders.
> - Capability of creating "New Directory" and "Upload" file in the current 
> directory. 
> - Search file/folder by name in the current directory.
> - User should be able to perform the actions like Open, Rename, Edit 
> Permissions, Delete, Copy, Move and Download for file or folder.
> - User should be able to multi select files/folders for the actions like  
> Delete, Copy, Move and Download
> - User should be able to perform concatenate action for multi selected files.
> - Preview of files before actual download.



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

[jira] [Created] (AMBARI-15150) Support response body for DELETE API

[Ajit Kumar (JIRA)]

Ajit Kumar created AMBARI-15150:
---

 Summary: Support response body for DELETE API 
 Key: AMBARI-15150
 URL: https://issues.apache.org/jira/browse/AMBARI-15150
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.4.0
Reporter: Ajit Kumar
Assignee: Ajit Kumar
 Fix For: 2.4.0


DELETE API in ambari server can send only 200 OK or other response code with 
empty body. Current framework doesn't support sending json response in body.
In case of bulk DELETE API, server should send a json response to communicate 
keys which got deleted successfully and error message for keys which were not 
deleted.

DELETE response json object should be 
{code}
deleteResult : [
deleted : {
key : 
},
   deleted : {
key : 
},
...
error: {
key : 
code: 404
message: "Resource not found"
   },
   error: {
key : 
code: 404
message: "Resource not found"
   }
   ...
]

{code}



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

[jira] [Updated] (AMBARI-15149) Remove Result.STATUS enum as it is not being used

[Ajit Kumar (JIRA)]

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

Ajit Kumar updated AMBARI-15149:

Component/s: ambari-server

> Remove Result.STATUS enum as it is not being used
> -
>
> Key: AMBARI-15149
> URL: https://issues.apache.org/jira/browse/AMBARI-15149
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.4.0
>Reporter: Ajit Kumar
>Assignee: Ajit Kumar
> Fix For: 2.4.0
>
> Attachments: rb43909.patch
>
>
> Remove Result.STATUS enum as it is not being used. ResultStatus.STATUS is 
> being used instead.



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

Re: Review Request 43909: Remove Result.STATUS enum as it is not being used

[Nahappan Somasundaram]

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


Ship it!




Ship It!

- Nahappan Somasundaram


On Feb. 23, 2016, 1:58 p.m., Ajit Kumar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43909/
> ---
> 
> (Updated Feb. 23, 2016, 1:58 p.m.)
> 
> 
> Review request for Ambari and Nahappan Somasundaram.
> 
> 
> Bugs: AMBARI-15149
> https://issues.apache.org/jira/browse/AMBARI-15149
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Remove Result.STATUS enum as it is not being used
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/services/Result.java 
> c827ac49ea204c25065e84ffbe4395a720a8dba9 
> 
> Diff: https://reviews.apache.org/r/43909/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Ajit Kumar
> 
>

Re: Review Request 43909: Remove Result.STATUS enum as it is not being used

[Alejandro Fernandez]

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


Ship it!





ambari-server/src/main/java/org/apache/ambari/server/api/services/Result.java 


I see we use ResultStatus instead.
Good find.


- Alejandro Fernandez


On Feb. 23, 2016, 9:58 p.m., Ajit Kumar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43909/
> ---
> 
> (Updated Feb. 23, 2016, 9:58 p.m.)
> 
> 
> Review request for Ambari and Nahappan Somasundaram.
> 
> 
> Bugs: AMBARI-15149
> https://issues.apache.org/jira/browse/AMBARI-15149
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Remove Result.STATUS enum as it is not being used
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/services/Result.java 
> c827ac49ea204c25065e84ffbe4395a720a8dba9 
> 
> Diff: https://reviews.apache.org/r/43909/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Ajit Kumar
> 
>

Re: Ru/EU not updating alert definitions in Ambari server db?

[Jonathan Hurley]

All good questions. I think that the RU/EU aspect of it can't really be a part 
of the discussion; the orchestration done is really independent of the data 
stored in Ambari.  When using proper inheritance, though, the example below 
will still work since the path still exists to the original script. If the 
stacks have inheritance, it will be picked up. You can also define the alerts 
anywhere within the stack. So if you needed to, you could store them in 
FLUME/alerts/alert_flume_whatever.py in order to apply to any flume alert.

The upgrade catalogs do touch alert definitions on upgrade. In most cases, we 
edit the content; in rare cases, we remove an outdated definition. So I think 
that this would normally be the right place to perform the actions. Aside from 
that, if you're changing locations of the scripts, I think the only course of 
action for alerts to also change their definitions. Ambari 2.4 is going to 
allow editing of script alerts via the UI - so that will certainly help for 
situations like these.

> On Feb 23, 2016, at 4:17 PM, Di Li  wrote:
> 
> Hello folks,
> 
> Yes, I would probably have had seen the error if I had looked at the UI (my 
> bad, I didn't check until post-RU). and yes the issue (since it's about 
> refactored stack structure) will be there the moment I upgrade the Ambari 
> server.
> 
> I wanted to know if there is someway to have the alert definitions updated 
> during ambari server upgrade or RU/EU. I am keeping RU/EU in the loop because 
> I may have different versions of the same service in the common service 
> mapped to service in stack. By that, I mean
>   common-services/FLUME/1.2.3.4.5 mapped to MyStack/1.0/FLUME
>   common-services/FLUME/1.3.4.5.1 mapped to MyStack/2.0/FLUMEwhere two 
> versions of FLUME have different alert_definition Python script.
> 
> In this case,I 'd rather have RU/EU take care of updating the alert 
> definition when the stack version is switched (from 1.0 to 2.0).
> 
> Understandably this may not be something currently in place in Ambari upgrade 
> nor RU/EU, so I figured I'd better check about this behavior on the mail list.
> Di
> 
>  From: Jonathan Hurley 
> To: Ambari ; Di Li  
> Sent: Tuesday, February 23, 2016 3:43 PM
> Subject: Re: Ru/EU not updating alert definitions in Ambari server db?
> 
> Based on this description, you should have seen the error before RU since you 
> refactored your stacks and moved the script. RU and, for that matter, Ambari 
> upgrade, has no built-in knowledge of your scripts. You can pretty much put 
> them anywhere. So, if you change your directory structure around, you're 
> going to also have to update your definitions to have the right path.
> 
> This is why you should probably always put them in common services, and use 
> inheritance between stacks.
> 
>> On Feb 23, 2016, at 2:24 PM, Di Li  wrote:
>> 
>> Hello folks,
>> 
>> Thanks for the reply. I have my own stack called MyStack 1.0 and MyStack 
>> 2.0. I found the issue after I heavily refactored the MyStack directory 
>> structure.
>> 
>> 1. In Ambari 2.1/MyStack 1.0, I have Flume's alert_flume_agent_status.py 
>> defined as 
>> MyStack/1.0/services/FLUME/package/alerts/alert_flume_agent_status.py
>> 2. In Ambari 2.2, I changed the structure of MyStack to make use of common 
>> services, so 
>> a) The Flume directories are moved into common-services
>> b) MyStack 1.0 now contains a Flume dir with just a metainfo.xml file.
>> c) I also added MyStack 2.0 so I can run RU/EU. MyStack 2.0 also only 
>> contains a Flume dir with just a metainfo.xml file.
>> d) common-services has Flume agent alert Python script as 
>> FLUME/1.2.3.4.5/package/alerts/alert_flume_agent_status.py (note the custom 
>> version I used here...). As you can see, I changed the path to the 
>> alert_flume_agent_status.py...
>> 3. Perform RU
>> 
>> -- Post RU, I saw Flume agent produced an "UNKNOWN" alert with an error 
>> message
>> Flume Agent Status
>> Unable to find 
>> 'MyStack/1.0/services/FLUME/package/alerts/alert_flume_agent_status.py' as 
>> an absolute path or part of /var/lib/ambari-agent/cache/stacks or 
>> /var/lib/ambari-agent/cache/host_scripts
>> 
>> -- I noticed tht in the Ambari server database, the Flume agent alert 
>> definition had the wrong patch to the Python script as shown below. It still 
>> has the old MyStack based path.
>> 9 |  2 | flume_agent_status| FLUME   
>>| FLUME_HANDLER  |
>> ANY| Flume Agent Status  | This host-level 
>> alert is triggered if any of the expect
>> ed flume agent processes are not available.
>> |  1 |1 | SCRIPT  | 
>> {"path":"MyStack/1.0/services/FLUME/package/alerts/alert_flu
>> me_agent_status.py","parameters":[{"name":"run.directory","display_name":"Run
>>  

Re: Review Request 43900: Implement AMS collector certificate verification on monitor and service check sides

[Sid Wagle]

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


Ship it!




Ship It!

- Sid Wagle


On Feb. 23, 2016, 9:27 p.m., Dmytro Sen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43900/
> ---
> 
> (Updated Feb. 23, 2016, 9:27 p.m.)
> 
> 
> Review request for Ambari, Aravindan Vijayan and Sid Wagle.
> 
> 
> Bugs: AMBARI-15148
> https://issues.apache.org/jira/browse/AMBARI-15148
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Implement AMS collector certificate verification on monitor and service check 
> sides.
> +Grafana
> Implement http(-s) connetion reusing to reduce processing overhead for SSL 
> handshaking
> 
> 
> Diffs
> -
> 
>   ambari-metrics/ambari-metrics-host-monitoring/conf/unix/metric_monitor.ini 
> 5952982 
>   
> ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/config_reader.py
>  d533537 
>   
> ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/controller.py
>  1713501 
>   
> ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/emitter.py 
> 4e39ab5 
>   
> ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/security.py
>  PRE-CREATION 
>   
> ambari-metrics/ambari-metrics-host-monitoring/src/test/python/core/TestEmitter.py
>  8f5236a 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
>  417574b 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/functions.py
>  140c24c 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py
>  02caa11 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/network.py
>  PRE-CREATION 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
>  f1ff998 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/service_check.py
>  4346f0f 
>   
> ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/templates/metric_monitor.ini.j2
>  4e2d0f5 
>   
> ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_collector.py
>  64b16c6 
>   
> ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_grafana.py
>  755bb4f 
>   ambari-server/src/test/python/stacks/2.0.6/configs/default.json adf12ad 
> 
> Diff: https://reviews.apache.org/r/43900/diff/
> 
> 
> Testing
> ---
> 
> Unit tests passed
> 
> 
> Thanks,
> 
> Dmytro Sen
> 
>

Re: Review Request 43909: Remove Result.STATUS enum as it is not being used

[Sumit Mohanty]

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


Ship it!




Interesting.

- Sumit Mohanty


On Feb. 23, 2016, 9:58 p.m., Ajit Kumar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43909/
> ---
> 
> (Updated Feb. 23, 2016, 9:58 p.m.)
> 
> 
> Review request for Ambari and Nahappan Somasundaram.
> 
> 
> Bugs: AMBARI-15149
> https://issues.apache.org/jira/browse/AMBARI-15149
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Remove Result.STATUS enum as it is not being used
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/java/org/apache/ambari/server/api/services/Result.java 
> c827ac49ea204c25065e84ffbe4395a720a8dba9 
> 
> Diff: https://reviews.apache.org/r/43909/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Ajit Kumar
> 
>

[jira] [Updated] (AMBARI-15149) Remove Result.STATUS enum as it is not being used

[Ajit Kumar (JIRA)]

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

Ajit Kumar updated AMBARI-15149:

Attachment: rb43909.patch

> Remove Result.STATUS enum as it is not being used
> -
>
> Key: AMBARI-15149
> URL: https://issues.apache.org/jira/browse/AMBARI-15149
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Ajit Kumar
>Assignee: Ajit Kumar
> Fix For: 2.4.0
>
> Attachments: rb43909.patch
>
>
> Remove Result.STATUS enum as it is not being used. ResultStatus.STATUS is 
> being used instead.



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

Review Request 43909: Remove Result.STATUS enum as it is not being used

[Ajit Kumar]

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

Review request for Ambari and Nahappan Somasundaram.


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


Repository: ambari


Description
---

Remove Result.STATUS enum as it is not being used


Diffs
-

  ambari-server/src/main/java/org/apache/ambari/server/api/services/Result.java 
c827ac49ea204c25065e84ffbe4395a720a8dba9 

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


Testing
---


Thanks,

Ajit Kumar

[jira] [Created] (AMBARI-15149) Remove Result.STATUS enum as it is not being used

[Ajit Kumar (JIRA)]

Ajit Kumar created AMBARI-15149:
---

 Summary: Remove Result.STATUS enum as it is not being used
 Key: AMBARI-15149
 URL: https://issues.apache.org/jira/browse/AMBARI-15149
 Project: Ambari
  Issue Type: Bug
Affects Versions: 2.4.0
Reporter: Ajit Kumar
Assignee: Ajit Kumar
 Fix For: 2.4.0


Remove Result.STATUS enum as it is not being used. ResultStatus.STATUS is being 
used instead.



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

[jira] [Commented] (AMBARI-15141) Start all services request aborts in the middle and hosts go into heartbeat-lost state

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15141:
-

SUCCESS: Integrated in Ambari-trunk-Commit #4377 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4377/])
AMBARI-15141. Start all services request aborts in the middle and hosts 
(mpapyrkovskyy: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=083ac6dab5cf59c01da054eb656507c089a54620])
* 
ambari-server/src/main/java/org/apache/ambari/server/state/svccomphost/ServiceComponentHostImpl.java
* 
ambari-server/src/main/java/org/apache/ambari/server/agent/HeartBeatHandler.java
* 
ambari-server/src/main/java/org/apache/ambari/server/orm/dao/HostVersionDAO.java
* 
ambari-server/src/test/java/org/apache/ambari/server/agent/TestHeartbeatHandler.java
* 
ambari-server/src/test/java/org/apache/ambari/server/agent/HeartbeatProcessorTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/agent/HeartbeatProcessor.java
* 
ambari-server/src/main/java/org/apache/ambari/server/agent/HeartbeatMonitor.java
* 
ambari-server/src/test/java/org/apache/ambari/server/agent/HeartbeatTestHelper.java
* 
ambari-server/src/main/java/org/apache/ambari/server/state/cluster/ClusterImpl.java
* 
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/HostVersionEntity.java


> Start all services request aborts in the middle and hosts go into 
> heartbeat-lost state
> --
>
> Key: AMBARI-15141
> URL: https://issues.apache.org/jira/browse/AMBARI-15141
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Myroslav Papirkovskyy
>Assignee: Myroslav Papirkovskyy
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15141.patch, AMBARI-15141_branch-2.2.patch
>
>
> On the 1600 node cluster I attempted to do Stop-All and Start-All actions. 
> During both actions, the request would abort itself - sometimes even when 
> there were no failures or timeouts. Also, during this time hosts would go 
> into heartbeat-lost state and the cluster would look like its broken. After 
> like 5-10 minutes, the hosts slowly come back online and correct host-status 
> is got. But due to request abort, some components would be stopped/started 
> when they should not be.



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

Review Request 43900: Implement AMS collector certificate verification on monitor and service check sides

[Dmytro Sen]

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

Review request for Ambari, Aravindan Vijayan and Sid Wagle.


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


Repository: ambari


Description
---

Implement AMS collector certificate verification on monitor and service check 
sides.
+Grafana
Implement http(-s) connetion reusing to reduce processing overhead for SSL 
handshaking


Diffs
-

  ambari-metrics/ambari-metrics-host-monitoring/conf/unix/metric_monitor.ini 
5952982 
  
ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/config_reader.py
 d533537 
  
ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/controller.py
 1713501 
  ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/emitter.py 
4e39ab5 
  
ambari-metrics/ambari-metrics-host-monitoring/src/main/python/core/security.py 
PRE-CREATION 
  
ambari-metrics/ambari-metrics-host-monitoring/src/test/python/core/TestEmitter.py
 8f5236a 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams.py
 417574b 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/functions.py
 140c24c 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py
 02caa11 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/network.py
 PRE-CREATION 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/params.py
 f1ff998 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/service_check.py
 4346f0f 
  
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/templates/metric_monitor.ini.j2
 4e2d0f5 
  
ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_collector.py
 64b16c6 
  
ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_grafana.py
 755bb4f 
  ambari-server/src/test/python/stacks/2.0.6/configs/default.json adf12ad 

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


Testing
---

Unit tests passed


Thanks,

Dmytro Sen

[jira] [Updated] (AMBARI-15148) Implement AMS collector certificate verification on monitor and service check sides

[Dmytro Sen (JIRA)]

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

Dmytro Sen updated AMBARI-15148:

Attachment: AMBARI-15148-trunk.patch

> Implement AMS collector certificate verification on monitor and service check 
> sides
> ---
>
> Key: AMBARI-15148
> URL: https://issues.apache.org/jira/browse/AMBARI-15148
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-metrics, stacks
>Affects Versions: 2.2.2
>Reporter: Dmytro Sen
>Assignee: Dmytro Sen
>Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15148-trunk.patch
>
>
> Implement AMS collector certificate verification on monitor and service check 
> sides.
> +Grafana
> Implement http(-s) connetion reusing to reduce processing overhead for SSL 
> handshaking



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

Re: Ru/EU not updating alert definitions in Ambari server db?

[Di Li]

Hello folks,

Yes, I would probably have had seen the error if I had looked at the UI (my 
bad, I didn't check until post-RU). and yes the issue (since it's about 
refactored stack structure) will be there the moment I upgrade the Ambari 
server.

I wanted to know if there is someway to have the alert definitions updated 
during ambari server upgrade or RU/EU. I am keeping RU/EU in the loop because I 
may have different versions of the same service in the common service mapped to 
service in stack. By that, I mean
  common-services/FLUME/1.2.3.4.5 mapped to MyStack/1.0/FLUME
  common-services/FLUME/1.3.4.5.1 mapped to MyStack/2.0/FLUMEwhere two versions 
of FLUME have different alert_definition Python script.

In this case,I 'd rather have RU/EU take care of updating the alert definition 
when the stack version is switched (from 1.0 to 2.0).

Understandably this may not be something currently in place in Ambari upgrade 
nor RU/EU, so I figured I'd better check about this behavior on the mail list.
Di

  From: Jonathan Hurley 
 To: Ambari ; Di Li  
 Sent: Tuesday, February 23, 2016 3:43 PM
 Subject: Re: Ru/EU not updating alert definitions in Ambari server db?
   
Based on this description, you should have seen the error before RU since you 
refactored your stacks and moved the script. RU and, for that matter, Ambari 
upgrade, has no built-in knowledge of your scripts. You can pretty much put 
them anywhere. So, if you change your directory structure around, you're going 
to also have to update your definitions to have the right path.

This is why you should probably always put them in common services, and use 
inheritance between stacks.

> On Feb 23, 2016, at 2:24 PM, Di Li  wrote:
> 
> Hello folks,
> 
> Thanks for the reply. I have my own stack called MyStack 1.0 and MyStack 2.0. 
> I found the issue after I heavily refactored the MyStack directory structure.
> 
> 1. In Ambari 2.1/MyStack 1.0, I have Flume's alert_flume_agent_status.py 
> defined as 
> MyStack/1.0/services/FLUME/package/alerts/alert_flume_agent_status.py
> 2. In Ambari 2.2, I changed the structure of MyStack to make use of common 
> services, so 
>    a) The Flume directories are moved into common-services
>    b) MyStack 1.0 now contains a Flume dir with just a metainfo.xml file.
>    c) I also added MyStack 2.0 so I can run RU/EU. MyStack 2.0 also only 
>contains a Flume dir with just a metainfo.xml file.
>    d) common-services has Flume agent alert Python script as 
>FLUME/1.2.3.4.5/package/alerts/alert_flume_agent_status.py (note the custom 
>version I used here...). As you can see, I changed the path to the 
>alert_flume_agent_status.py...
> 3. Perform RU
> 
> -- Post RU, I saw Flume agent produced an "UNKNOWN" alert with an error 
> message
> Flume Agent Status
> Unable to find 
> 'MyStack/1.0/services/FLUME/package/alerts/alert_flume_agent_status.py' as an 
> absolute path or part of /var/lib/ambari-agent/cache/stacks or 
> /var/lib/ambari-agent/cache/host_scripts
> 
> -- I noticed tht in the Ambari server database, the Flume agent alert 
> definition had the wrong patch to the Python script as shown below. It still 
> has the old MyStack based path.
> 9 |          2 | flume_agent_status                            | FLUME        
>   | FLUME_HANDLER      |
> ANY    | Flume Agent Status                              | This host-level 
> alert is triggered if any of the expect
> ed flume agent processes are not available.
>        |      1 |                1 | SCRIPT      | 
>{"path":"MyStack/1.0/services/FLUME/package/alerts/alert_flu
> me_agent_status.py","parameters":[{"name":"run.directory","display_name":"Run 
> Directory","value":"/var/run/flume","de
> scription":"The directory where flume agent processes will place their PID 
> files.","type":"STRING"}],"type":"SCRIPT"}
> 
> -- This prompted me to ask the question about whether the alert definition 
> should have been updated by RU/EU (or ambari server upgrade maybe).
> 
> -- I was able to update Flume agent's alert definition with the correct path 
> via following REST API.
> curl -u admin:admin -H 'X-Requested-By:ambari' -X PUT -d '{"AlertDefinition" 
> : {"source" : {"path" : 
> "FLUME/1.2.3.4.5/package/alerts/alert_flume_agent_status.py",      "type" : 
> "SCRIPT" }}}' 
> http://myhost.mydomain.com:8080/api/v1/clusters/test/alert_definitions/9
> 
> 
>      From: Jonathan Hurley 
> To: "dev@ambari.apache.org" ; Di Li 
>  
> Sent: Tuesday, February 23, 2016 1:23 PM
> Subject: Re: Ru/EU not updating alert definitions in Ambari server db?
> 
> No, they are not updated; however, stack inheritance should allow you to 
> reference the files from the new stack. We've performed many different 
> upgrades both both inter-stack and intra-stack and have never seen any issues 
> with alert definitions. 
> 
>> 

[jira] [Updated] (AMBARI-15132) in upgrade.xml to support set/replace/transfer

[Di Li (JIRA)]

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

Di Li updated AMBARI-15132:
---
Attachment: AMBARI-15132.patch

>  in upgrade.xml to support set/replace/transfer
> --
>
> Key: AMBARI-15132
> URL: https://issues.apache.org/jira/browse/AMBARI-15132
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, ambari-web
>Affects Versions: 2.2.0
>Reporter: Di Li
>Assignee: Di Li
> Fix For: trunk
>
> Attachments: AMBARI-15132.patch
>
>
>  in upgrade.xml  currently only supports single property set. this 
> is to improve it to to support set/replace/transfer. The code change must be 
> backward compatible in order to not break the existing update-***.xml and 
> nonrolling-upgrade-***.xml.



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

[jira] [Updated] (AMBARI-15146) 500 status code received on POST method for API: /api/v1/clusters//requests

[Sam Mingolelli (JIRA)]

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

Sam Mingolelli updated AMBARI-15146:

Description: 
While attempting to enable kerberos on a clean install of HDP 2.3 (Ambari 
2.1.2) I encounter the following error dialog:

!Ambari_-_dev09_ost.png|width=50%,height=50%!

{quote}
Error
500 status code received on POST method for API: 
/api/v1/clusters/dev09_ost_hivetest_h/requests 

Error message: Server Error

The log file also contains an exception:
{quote}

{code}
23 Feb 2016 14:14:45,633  WARN [qtp-client-33592] 
KdcServerConnectionVerification:167 - Failed to connect to the KDC server at 
kdc01.td.teradata.com:88 over TCP
23 Feb 2016 14:14:45,664  INFO [qtp-client-33592] 
KdcServerConnectionVerification:164 - Successfully connected to the KDC server 
at kdc01.td.teradata.com:88 over UDP
23 Feb 2016 14:15:02,723  INFO [qtp-client-3016] ClusterImpl:1901 - Deleting 
service for cluster, clusterName=dev09_ost_hivetest_h, serviceName=KERBEROS
23 Feb 2016 14:15:02,724  INFO [qtp-client-3016] ServiceImpl:583 - Deleting all 
components for service, clusterName=dev09_ost_hivetest_h, serviceName=KERBEROS
23 Feb 2016 14:15:02,724  INFO [qtp-client-3016] ServiceComponentImpl:589 - 
Deleting all servicecomponenthosts for component, 
clusterName=dev09_ost_hivetest_h, serviceName=KERBEROS, 
componentName=KERBEROS_CLIENT
23 Feb 2016 14:15:02,727  INFO [qtp-client-3016] ServiceImpl:550 - Deleting all 
serviceconfigs for service, clusterName=dev09_ost_hivetest_h, 
serviceName=KERBEROS
23 Feb 2016 14:15:04,294  INFO [qtp-client-48401] 
AmbariManagementControllerImpl:1324 - Received a updateCluster request, 
clusterId=2, clusterName=dev09_ost_hivetest_h, securityType=null, request={ 
clusterName=dev09_ost_hivetest_h, clusterId=2, provisioningState=null, 
securityType=null, stackVersion=HDP-2.3, desired_scv=null, hosts=[] }
23 Feb 2016 14:15:04,294  INFO [qtp-client-48401] 
AmbariManagementControllerImpl:1415 - Applying configuration with tag 
'version1456254905543' to cluster 'dev09_ost_hivetest_h'  for configuration 
type kerberos-env
23 Feb 2016 14:15:04,303  INFO [qtp-client-48401] 
AmbariManagementControllerImpl:1415 - Applying configuration with tag 
'version1456254905543' to cluster 'dev09_ost_hivetest_h'  for configuration 
type krb5-conf
23 Feb 2016 14:15:04,421  INFO [qtp-client-48101] 
AmbariManagementControllerImpl:1324 - Received a updateCluster request, 
clusterId=2, clusterName=dev09_ost_hivetest_h, securityType=null, request={ 
clusterName=dev09_ost_hivetest_h, clusterId=2, provisioningState=null, 
securityType=null, stackVersion=HDP-2.3, desired_scv=null, hosts=[] }
23 Feb 2016 14:15:04,996  INFO [qtp-client-48129] AbstractResourceProvider:590 
- Received a updateService request, clusterName=dev09_ost_hivetest_h, 
serviceName=KERBEROS, request=clusterName=dev09_ost_hivetest_h, 
serviceName=KERBEROS, desiredState=INSTALLED
23 Feb 2016 14:15:04,999  INFO [qtp-client-48129] 
AmbariManagementControllerImpl:2025 - 
AmbariManagementControllerImpl.createHostAction: created ExecutionCommand for 
host dev09-ost-hivetest-h-hb02.td.local, role KERBEROS_CLIENT, roleCommand 
INSTALL, and command ID 85--1, with cluster-env tags version1
23 Feb 2016 14:15:05,016  INFO [ambari-action-scheduler] 
ServiceComponentHostImpl:949 - Host role transitioned to a new state, 
serviceComponentName=KERBEROS_CLIENT, 
hostName=dev09-ost-hivetest-h-hb02.td.local, oldState=INIT, 
currentState=INSTALLING
23 Feb 2016 14:15:09,045  INFO [qtp-ambari-agent-48404] 
ServiceComponentHostImpl:949 - Host role transitioned to a new state, 
serviceComponentName=KERBEROS_CLIENT, 
hostName=dev09-ost-hivetest-h-hb02.td.local, oldState=INSTALLING, 
currentState=INSTALLED
23 Feb 2016 14:15:09,580  INFO [qtp-client-3016] 
AmbariManagementControllerImpl:3312 - Received action execution request, 
clusterName=dev09_ost_hivetest_h, request=isCommand :true, action :null, 
command :KERBEROS_SERVICE_CHECK, inputs :{}, resourceFilters: 
[RequestResourceFilter{serviceName='KERBEROS', componentName='null', 
hostNames=[]}], exclusive: false, clusterName :dev09_ost_hivetest_h
23 Feb 2016 14:15:09,668 ERROR [qtp-client-3016] BaseManagementHandler:66 - 
Caught a runtime exception while attempting to create a resource
java.lang.NullPointerException
at 
org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.persistActions(ActionDBAccessorImpl.java:300)
at 
org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:68)
at 
org.apache.ambari.server.actionmanager.ActionManager.sendActions(ActionManager.java:99)
at 
org.apache.ambari.server.controller.internal.RequestStageContainer.persist(RequestStageContainer.java:216)
at 
org.apache.ambari.server.controller.AmbariManagementControllerImpl.createAction(AmbariManagementControllerImpl.java:3400)
at 

[jira] [Updated] (AMBARI-15146) 500 status code received on POST method for API: /api/v1/clusters//requests

[Sam Mingolelli (JIRA)]

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

Sam Mingolelli updated AMBARI-15146:

Description: 
While attempting to enable kerberos on a clean install of HDP 2.3 (Ambari 
2.1.2) I encounter the following error dialog:

!Ambari_-_dev09_ost.png|width=50%,height=50%!

{quote}
Error
500 status code received on POST method for API: 
/api/v1/clusters/dev09_ost_hivetest_h/requests 

Error message: Server Error

The log file also contains an exception:
{quote}

{code}
23 Feb 2016 14:14:45,633  WARN [qtp-client-33592] 
KdcServerConnectionVerification:167 - Failed to connect to the KDC server at 
kdc01.td.teradata.com:88 over TCP
23 Feb 2016 14:14:45,664  INFO [qtp-client-33592] 
KdcServerConnectionVerification:164 - Successfully connected to the KDC server 
at kdc01.td.teradata.com:88 over UDP
23 Feb 2016 14:15:02,723  INFO [qtp-client-3016] ClusterImpl:1901 - Deleting 
service for cluster, clusterName=dev09_ost_hivetest_h, serviceName=KERBEROS
23 Feb 2016 14:15:02,724  INFO [qtp-client-3016] ServiceImpl:583 - Deleting all 
components for service, clusterName=dev09_ost_hivetest_h, serviceName=KERBEROS
23 Feb 2016 14:15:02,724  INFO [qtp-client-3016] ServiceComponentImpl:589 - 
Deleting all servicecomponenthosts for component, 
clusterName=dev09_ost_hivetest_h, serviceName=KERBEROS, 
componentName=KERBEROS_CLIENT
23 Feb 2016 14:15:02,727  INFO [qtp-client-3016] ServiceImpl:550 - Deleting all 
serviceconfigs for service, clusterName=dev09_ost_hivetest_h, 
serviceName=KERBEROS
23 Feb 2016 14:15:04,294  INFO [qtp-client-48401] 
AmbariManagementControllerImpl:1324 - Received a updateCluster request, 
clusterId=2, clusterName=dev09_ost_hivetest_h, securityType=null, request={ 
clusterName=dev09_ost_hivetest_h, clusterId=2, provisioningState=null, 
securityType=null, stackVersion=HDP-2.3, desired_scv=null, hosts=[] }
23 Feb 2016 14:15:04,294  INFO [qtp-client-48401] 
AmbariManagementControllerImpl:1415 - Applying configuration with tag 
'version1456254905543' to cluster 'dev09_ost_hivetest_h'  for configuration 
type kerberos-env
23 Feb 2016 14:15:04,303  INFO [qtp-client-48401] 
AmbariManagementControllerImpl:1415 - Applying configuration with tag 
'version1456254905543' to cluster 'dev09_ost_hivetest_h'  for configuration 
type krb5-conf
23 Feb 2016 14:15:04,421  INFO [qtp-client-48101] 
AmbariManagementControllerImpl:1324 - Received a updateCluster request, 
clusterId=2, clusterName=dev09_ost_hivetest_h, securityType=null, request={ 
clusterName=dev09_ost_hivetest_h, clusterId=2, provisioningState=null, 
securityType=null, stackVersion=HDP-2.3, desired_scv=null, hosts=[] }
23 Feb 2016 14:15:04,996  INFO [qtp-client-48129] AbstractResourceProvider:590 
- Received a updateService request, clusterName=dev09_ost_hivetest_h, 
serviceName=KERBEROS, request=clusterName=dev09_ost_hivetest_h, 
serviceName=KERBEROS, desiredState=INSTALLED
23 Feb 2016 14:15:04,999  INFO [qtp-client-48129] 
AmbariManagementControllerImpl:2025 - 
AmbariManagementControllerImpl.createHostAction: created ExecutionCommand for 
host dev09-ost-hivetest-h-hb02.td.local, role KERBEROS_CLIENT, roleCommand 
INSTALL, and command ID 85--1, with cluster-env tags version1
23 Feb 2016 14:15:05,016  INFO [ambari-action-scheduler] 
ServiceComponentHostImpl:949 - Host role transitioned to a new state, 
serviceComponentName=KERBEROS_CLIENT, 
hostName=dev09-ost-hivetest-h-hb02.td.local, oldState=INIT, 
currentState=INSTALLING
23 Feb 2016 14:15:09,045  INFO [qtp-ambari-agent-48404] 
ServiceComponentHostImpl:949 - Host role transitioned to a new state, 
serviceComponentName=KERBEROS_CLIENT, 
hostName=dev09-ost-hivetest-h-hb02.td.local, oldState=INSTALLING, 
currentState=INSTALLED
23 Feb 2016 14:15:09,580  INFO [qtp-client-3016] 
AmbariManagementControllerImpl:3312 - Received action execution request, 
clusterName=dev09_ost_hivetest_h, request=isCommand :true, action :null, 
command :KERBEROS_SERVICE_CHECK, inputs :{}, resourceFilters: 
[RequestResourceFilter{serviceName='KERBEROS', componentName='null', 
hostNames=[]}], exclusive: false, clusterName :dev09_ost_hivetest_h
23 Feb 2016 14:15:09,668 ERROR [qtp-client-3016] BaseManagementHandler:66 - 
Caught a runtime exception while attempting to create a resource
java.lang.NullPointerException
at 
org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.persistActions(ActionDBAccessorImpl.java:300)
at 
org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:68)
at 
org.apache.ambari.server.actionmanager.ActionManager.sendActions(ActionManager.java:99)
at 
org.apache.ambari.server.controller.internal.RequestStageContainer.persist(RequestStageContainer.java:216)
at 
org.apache.ambari.server.controller.AmbariManagementControllerImpl.createAction(AmbariManagementControllerImpl.java:3400)
at 

[jira] [Commented] (AMBARI-14932) "download zip" does not work

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14932:


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

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

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

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

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

{color:green}+1 core tests{color}.  The patch passed unit tests in 
contrib/views/files.

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

This message is automatically generated.

> "download zip"  does not work
> -
>
> Key: AMBARI-14932
> URL: https://issues.apache.org/jira/browse/AMBARI-14932
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views, contrib
>Affects Versions: trunk
>Reporter: Keta Patel
>Assignee: Keta Patel
> Attachments: AMBARI-14932_Feb10_fix1.patch, AMBARI-14932_Feb11.patch, 
> AMBARI_14932_Feb23.patch, DownloadService.tiff, adapter.tiff, 
> error_after_file_open.tiff, file_1.tiff, file_2.tiff, screenshot.tiff
>
>
> Steps to Reproduce:
> 1. go to "View" - "FILES" - " Create Instance"
> 2. go to hdfs file view
> 3. click "download zip" icon
> The click doesn't download any file. The REST call returns 200 OK status.
> Detailed steps on configuring Views can be found in the link below:
> http://docs.hortonworks.com/HDPDocuments/Ambari-2.1.0.0/bk_ambari_views_guide/bk_ambari_views_guide-20150721.pdf



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

[jira] [Updated] (AMBARI-15146) 500 status code received on POST method for API: /api/v1/clusters//requests

[Sam Mingolelli (JIRA)]

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

Sam Mingolelli updated AMBARI-15146:

Description: 
While attempting to enable kerberos on a clean install of HDP 2.3 (Ambari 
2.1.2) I encounter the following error dialog:

!Amb
Error
500 status code received on POST method for API: 
/api/v1/clusters/dev09_ost_hivetest_h/requests 

Error message: Server Error

The log file also contains an exception:

{code}
23 Feb 2016 14:14:45,633  WARN [qtp-client-33592] 
KdcServerConnectionVerification:167 - Failed to connect to the KDC server at 
kdc01.td.teradata.com:88 over TCP
23 Feb 2016 14:14:45,664  INFO [qtp-client-33592] 
KdcServerConnectionVerification:164 - Successfully connected to the KDC server 
at kdc01.td.teradata.com:88 over UDP
23 Feb 2016 14:15:02,723  INFO [qtp-client-3016] ClusterImpl:1901 - Deleting 
service for cluster, clusterName=dev09_ost_hivetest_h, serviceName=KERBEROS
23 Feb 2016 14:15:02,724  INFO [qtp-client-3016] ServiceImpl:583 - Deleting all 
components for service, clusterName=dev09_ost_hivetest_h, serviceName=KERBEROS
23 Feb 2016 14:15:02,724  INFO [qtp-client-3016] ServiceComponentImpl:589 - 
Deleting all servicecomponenthosts for component, 
clusterName=dev09_ost_hivetest_h, serviceName=KERBEROS, 
componentName=KERBEROS_CLIENT
23 Feb 2016 14:15:02,727  INFO [qtp-client-3016] ServiceImpl:550 - Deleting all 
serviceconfigs for service, clusterName=dev09_ost_hivetest_h, 
serviceName=KERBEROS
23 Feb 2016 14:15:04,294  INFO [qtp-client-48401] 
AmbariManagementControllerImpl:1324 - Received a updateCluster request, 
clusterId=2, clusterName=dev09_ost_hivetest_h, securityType=null, request={ 
clusterName=dev09_ost_hivetest_h, clusterId=2, provisioningState=null, 
securityType=null, stackVersion=HDP-2.3, desired_scv=null, hosts=[] }
23 Feb 2016 14:15:04,294  INFO [qtp-client-48401] 
AmbariManagementControllerImpl:1415 - Applying configuration with tag 
'version1456254905543' to cluster 'dev09_ost_hivetest_h'  for configuration 
type kerberos-env
23 Feb 2016 14:15:04,303  INFO [qtp-client-48401] 
AmbariManagementControllerImpl:1415 - Applying configuration with tag 
'version1456254905543' to cluster 'dev09_ost_hivetest_h'  for configuration 
type krb5-conf
23 Feb 2016 14:15:04,421  INFO [qtp-client-48101] 
AmbariManagementControllerImpl:1324 - Received a updateCluster request, 
clusterId=2, clusterName=dev09_ost_hivetest_h, securityType=null, request={ 
clusterName=dev09_ost_hivetest_h, clusterId=2, provisioningState=null, 
securityType=null, stackVersion=HDP-2.3, desired_scv=null, hosts=[] }
23 Feb 2016 14:15:04,996  INFO [qtp-client-48129] AbstractResourceProvider:590 
- Received a updateService request, clusterName=dev09_ost_hivetest_h, 
serviceName=KERBEROS, request=clusterName=dev09_ost_hivetest_h, 
serviceName=KERBEROS, desiredState=INSTALLED
23 Feb 2016 14:15:04,999  INFO [qtp-client-48129] 
AmbariManagementControllerImpl:2025 - 
AmbariManagementControllerImpl.createHostAction: created ExecutionCommand for 
host dev09-ost-hivetest-h-hb02.td.local, role KERBEROS_CLIENT, roleCommand 
INSTALL, and command ID 85--1, with cluster-env tags version1
23 Feb 2016 14:15:05,016  INFO [ambari-action-scheduler] 
ServiceComponentHostImpl:949 - Host role transitioned to a new state, 
serviceComponentName=KERBEROS_CLIENT, 
hostName=dev09-ost-hivetest-h-hb02.td.local, oldState=INIT, 
currentState=INSTALLING
23 Feb 2016 14:15:09,045  INFO [qtp-ambari-agent-48404] 
ServiceComponentHostImpl:949 - Host role transitioned to a new state, 
serviceComponentName=KERBEROS_CLIENT, 
hostName=dev09-ost-hivetest-h-hb02.td.local, oldState=INSTALLING, 
currentState=INSTALLED
23 Feb 2016 14:15:09,580  INFO [qtp-client-3016] 
AmbariManagementControllerImpl:3312 - Received action execution request, 
clusterName=dev09_ost_hivetest_h, request=isCommand :true, action :null, 
command :KERBEROS_SERVICE_CHECK, inputs :{}, resourceFilters: 
[RequestResourceFilter{serviceName='KERBEROS', componentName='null', 
hostNames=[]}], exclusive: false, clusterName :dev09_ost_hivetest_h
23 Feb 2016 14:15:09,668 ERROR [qtp-client-3016] BaseManagementHandler:66 - 
Caught a runtime exception while attempting to create a resource
java.lang.NullPointerException
at 
org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.persistActions(ActionDBAccessorImpl.java:300)
at 
org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:68)
at 
org.apache.ambari.server.actionmanager.ActionManager.sendActions(ActionManager.java:99)
at 
org.apache.ambari.server.controller.internal.RequestStageContainer.persist(RequestStageContainer.java:216)
at 
org.apache.ambari.server.controller.AmbariManagementControllerImpl.createAction(AmbariManagementControllerImpl.java:3400)
at 

[jira] [Updated] (AMBARI-15146) 500 status code received on POST method for API: /api/v1/clusters//requests

[Sam Mingolelli (JIRA)]

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

Sam Mingolelli updated AMBARI-15146:

Attachment: Ambari_-_dev09_ost.png

> 500 status code received on POST method for API: 
> /api/v1/clusters//requests
> 
>
> Key: AMBARI-15146
> URL: https://issues.apache.org/jira/browse/AMBARI-15146
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.2
> Environment: {code}
> $ cat /etc/redhat-release
> CentOS Linux release 7.2.1511 (Core)
> $ uname -a
> Linux dev09-ost-hivetest-h-hb02.td.local 3.10.0-327.10.1.el7.x86_64 #1 SMP 
> Tue Feb 16 17:03:50 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> {code}
>Reporter: Sam Mingolelli
>Priority: Critical
> Attachments: Ambari_-_dev09_ost.png
>
>
> While attempting to enable kerberos on a clean install of HDP 2.3 (Ambari 
> 2.1.2) I encounter the following error dialog:
> Error
> 500 status code received on POST method for API: 
> /api/v1/clusters/dev09_ost_hivetest_h/requests 
> Error message: Server Error
> The log file also contains an exception:
> {code}
> 23 Feb 2016 14:14:45,633  WARN [qtp-client-33592] 
> KdcServerConnectionVerification:167 - Failed to connect to the KDC server at 
> kdc01.td.teradata.com:88 over TCP
> 23 Feb 2016 14:14:45,664  INFO [qtp-client-33592] 
> KdcServerConnectionVerification:164 - Successfully connected to the KDC 
> server at kdc01.td.teradata.com:88 over UDP
> 23 Feb 2016 14:15:02,723  INFO [qtp-client-3016] ClusterImpl:1901 - Deleting 
> service for cluster, clusterName=dev09_ost_hivetest_h, serviceName=KERBEROS
> 23 Feb 2016 14:15:02,724  INFO [qtp-client-3016] ServiceImpl:583 - Deleting 
> all components for service, clusterName=dev09_ost_hivetest_h, 
> serviceName=KERBEROS
> 23 Feb 2016 14:15:02,724  INFO [qtp-client-3016] ServiceComponentImpl:589 - 
> Deleting all servicecomponenthosts for component, 
> clusterName=dev09_ost_hivetest_h, serviceName=KERBEROS, 
> componentName=KERBEROS_CLIENT
> 23 Feb 2016 14:15:02,727  INFO [qtp-client-3016] ServiceImpl:550 - Deleting 
> all serviceconfigs for service, clusterName=dev09_ost_hivetest_h, 
> serviceName=KERBEROS
> 23 Feb 2016 14:15:04,294  INFO [qtp-client-48401] 
> AmbariManagementControllerImpl:1324 - Received a updateCluster request, 
> clusterId=2, clusterName=dev09_ost_hivetest_h, securityType=null, request={ 
> clusterName=dev09_ost_hivetest_h, clusterId=2, provisioningState=null, 
> securityType=null, stackVersion=HDP-2.3, desired_scv=null, hosts=[] }
> 23 Feb 2016 14:15:04,294  INFO [qtp-client-48401] 
> AmbariManagementControllerImpl:1415 - Applying configuration with tag 
> 'version1456254905543' to cluster 'dev09_ost_hivetest_h'  for configuration 
> type kerberos-env
> 23 Feb 2016 14:15:04,303  INFO [qtp-client-48401] 
> AmbariManagementControllerImpl:1415 - Applying configuration with tag 
> 'version1456254905543' to cluster 'dev09_ost_hivetest_h'  for configuration 
> type krb5-conf
> 23 Feb 2016 14:15:04,421  INFO [qtp-client-48101] 
> AmbariManagementControllerImpl:1324 - Received a updateCluster request, 
> clusterId=2, clusterName=dev09_ost_hivetest_h, securityType=null, request={ 
> clusterName=dev09_ost_hivetest_h, clusterId=2, provisioningState=null, 
> securityType=null, stackVersion=HDP-2.3, desired_scv=null, hosts=[] }
> 23 Feb 2016 14:15:04,996  INFO [qtp-client-48129] 
> AbstractResourceProvider:590 - Received a updateService request, 
> clusterName=dev09_ost_hivetest_h, serviceName=KERBEROS, 
> request=clusterName=dev09_ost_hivetest_h, serviceName=KERBEROS, 
> desiredState=INSTALLED
> 23 Feb 2016 14:15:04,999  INFO [qtp-client-48129] 
> AmbariManagementControllerImpl:2025 - 
> AmbariManagementControllerImpl.createHostAction: created ExecutionCommand for 
> host dev09-ost-hivetest-h-hb02.td.local, role KERBEROS_CLIENT, roleCommand 
> INSTALL, and command ID 85--1, with cluster-env tags version1
> 23 Feb 2016 14:15:05,016  INFO [ambari-action-scheduler] 
> ServiceComponentHostImpl:949 - Host role transitioned to a new state, 
> serviceComponentName=KERBEROS_CLIENT, 
> hostName=dev09-ost-hivetest-h-hb02.td.local, oldState=INIT, 
> currentState=INSTALLING
> 23 Feb 2016 14:15:09,045  INFO [qtp-ambari-agent-48404] 
> ServiceComponentHostImpl:949 - Host role transitioned to a new state, 
> serviceComponentName=KERBEROS_CLIENT, 
> hostName=dev09-ost-hivetest-h-hb02.td.local, oldState=INSTALLING, 
> currentState=INSTALLED
> 23 Feb 2016 14:15:09,580  INFO [qtp-client-3016] 
> AmbariManagementControllerImpl:3312 - Received action execution request, 
> clusterName=dev09_ost_hivetest_h, request=isCommand :true, action :null, 
> command :KERBEROS_SERVICE_CHECK, inputs :{}, resourceFilters: 
> 

Re: Ru/EU not updating alert definitions in Ambari server db?

[Jonathan Hurley]

Based on this description, you should have seen the error before RU since you 
refactored your stacks and moved the script. RU and, for that matter, Ambari 
upgrade, has no built-in knowledge of your scripts. You can pretty much put 
them anywhere. So, if you change your directory structure around, you're going 
to also have to update your definitions to have the right path.

This is why you should probably always put them in common services, and use 
inheritance between stacks.

> On Feb 23, 2016, at 2:24 PM, Di Li  wrote:
> 
> Hello folks,
> 
> Thanks for the reply. I have my own stack called MyStack 1.0 and MyStack 2.0. 
> I found the issue after I heavily refactored the MyStack directory structure.
> 
> 1. In Ambari 2.1/MyStack 1.0, I have Flume's alert_flume_agent_status.py 
> defined as 
> MyStack/1.0/services/FLUME/package/alerts/alert_flume_agent_status.py
> 2. In Ambari 2.2, I changed the structure of MyStack to make use of common 
> services, so 
>a) The Flume directories are moved into common-services
>b) MyStack 1.0 now contains a Flume dir with just a metainfo.xml file.
>c) I also added MyStack 2.0 so I can run RU/EU. MyStack 2.0 also only 
> contains a Flume dir with just a metainfo.xml file.
>d) common-services has Flume agent alert Python script as 
> FLUME/1.2.3.4.5/package/alerts/alert_flume_agent_status.py (note the custom 
> version I used here...). As you can see, I changed the path to the 
> alert_flume_agent_status.py...
> 3. Perform RU
> 
> -- Post RU, I saw Flume agent produced an "UNKNOWN" alert with an error 
> message
> Flume Agent Status
> Unable to find 
> 'MyStack/1.0/services/FLUME/package/alerts/alert_flume_agent_status.py' as an 
> absolute path or part of /var/lib/ambari-agent/cache/stacks or 
> /var/lib/ambari-agent/cache/host_scripts
> 
> -- I noticed tht in the Ambari server database, the Flume agent alert 
> definition had the wrong patch to the Python script as shown below. It still 
> has the old MyStack based path.
> 9 |  2 | flume_agent_status | FLUME   
>| FLUME_HANDLER   |
> ANY | Flume Agent Status   | This host-level 
> alert is triggered if any of the expect
> ed flume agent processes are not available.
>|   1 | 1 | SCRIPT  | 
> {"path":"MyStack/1.0/services/FLUME/package/alerts/alert_flu
> me_agent_status.py","parameters":[{"name":"run.directory","display_name":"Run 
> Directory","value":"/var/run/flume","de
> scription":"The directory where flume agent processes will place their PID 
> files.","type":"STRING"}],"type":"SCRIPT"}
> 
> -- This prompted me to ask the question about whether the alert definition 
> should have been updated by RU/EU (or ambari server upgrade maybe).
> 
> -- I was able to update Flume agent's alert definition with the correct path 
> via following REST API.
> curl -u admin:admin -H 'X-Requested-By:ambari' -X PUT -d '{"AlertDefinition" 
> : {"source" : {"path" : 
> "FLUME/1.2.3.4.5/package/alerts/alert_flume_agent_status.py",  "type" : 
> "SCRIPT" }}}' 
> http://myhost.mydomain.com:8080/api/v1/clusters/test/alert_definitions/9
> 
> 
>  From: Jonathan Hurley 
> To: "dev@ambari.apache.org" ; Di Li 
>  
> Sent: Tuesday, February 23, 2016 1:23 PM
> Subject: Re: Ru/EU not updating alert definitions in Ambari server db?
> 
> No, they are not updated; however, stack inheritance should allow you to 
> reference the files from the new stack. We've performed many different 
> upgrades both both inter-stack and intra-stack and have never seen any issues 
> with alert definitions. 
> 
>> On Feb 23, 2016, at 1:13 PM, Di Li  wrote:
>> 
>> Hello folks,
>> 
>> Do RU and EU handle updating alert definitions stored in the Ambari server 
>> database? 
>> 
>> Based on what I tested, alert definitions, especially the paths to 
>> alert_***.py Python scripts are not updated by neither RU and EU. meaning if 
>> I changed the path to the alert_***.py scripts in a new release, the alert 
>> definitions are broken and certain components would show with a UNKNOWN 
>> alert state after I run RU/EU.
>> 
>> 
>> P.S
>> I know that, post upgrade, I can manually update the alert definitions 
>> via REST APIs.
>> 
>> Thanks.
>> 
>> 
> 
> 

[jira] [Created] (AMBARI-15148) Implement AMS collector certificate verification on monitor and service check sides

[Dmytro Sen (JIRA)]

Dmytro Sen created AMBARI-15148:
---

 Summary: Implement AMS collector certificate verification on 
monitor and service check sides
 Key: AMBARI-15148
 URL: https://issues.apache.org/jira/browse/AMBARI-15148
 Project: Ambari
  Issue Type: Bug
  Components: ambari-metrics, stacks
Affects Versions: 2.2.2
Reporter: Dmytro Sen
Assignee: Dmytro Sen
Priority: Critical
 Fix For: 2.2.2


Implement AMS collector certificate verification on monitor and service check 
sides.
+Grafana
Implement http(-s) connetion reusing to reduce processing overhead for SSL 
handshaking




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

[jira] [Commented] (AMBARI-14830) Clients names different on host details page and filter

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14830:


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

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

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

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

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

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

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

This message is automatically generated.

> Clients names different on host details page and filter
> ---
>
> Key: AMBARI-14830
> URL: https://issues.apache.org/jira/browse/AMBARI-14830
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server, ambari-web
>Reporter: Daniel Gergely
>Assignee: Daniel Gergely
> Fix For: 2.4.0, 2.2.2
>
> Attachments: AMBARI-14830.patch, AMBARI-14830_branch-2.2.2.patch
>
>
> Clients names different on host details page and filter for components Pig, 
> Sqoop, Slider, Mahout.
> Displayed names should be come from metainfo.xml



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

[jira] [Updated] (AMBARI-14987) assign_master_component.js does not show recommendations while adding master component for a service which is already installed

[Matt (JIRA)]

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

Matt updated AMBARI-14987:
--
Attachment: AMBARI-14987-trunk-feedback-orig.patch

> assign_master_component.js does not show recommendations while adding master 
> component for a service which is already installed
> ---
>
> Key: AMBARI-14987
> URL: https://issues.apache.org/jira/browse/AMBARI-14987
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-14987-branch-2.2-feedback-orig.patch, 
> AMBARI-14987-branch-2.2-v1.patch, AMBARI-14987-branch-2.2-v2.patch, 
> AMBARI-14987-branch-2.2.patch, AMBARI-14987-trunk-feedback-orig.patch, 
> AMBARI-14987-trunk-v1.patch, AMBARI-14987-trunk-v2.patch, 
> AMBARI-14987-trunk-v3.patch, AMBARI-14987-trunk.patch
>
>
> On the assign masters page for the wizard, recommendations are not shown for 
> a master component that is being added for an installed service.
> This happens while adding HAWQSTANDBY to the cluster using the 'Add 
> HAWQSTANDBY' wizard (situation: HAWQ service is already installed on the 
> cluster). 
> The fix might also solve the issue where there is a installed service and the 
> upgrade of the service includes installing a new master component



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

[jira] [Updated] (AMBARI-14987) assign_master_component.js does not show recommendations while adding master component for a service which is already installed

[Matt (JIRA)]

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

Matt updated AMBARI-14987:
--
Attachment: AMBARI-14987-branch-2.2-feedback-orig.patch

> assign_master_component.js does not show recommendations while adding master 
> component for a service which is already installed
> ---
>
> Key: AMBARI-14987
> URL: https://issues.apache.org/jira/browse/AMBARI-14987
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Reporter: Matt
>Assignee: Matt
>Priority: Minor
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-14987-branch-2.2-feedback-orig.patch, 
> AMBARI-14987-branch-2.2-v1.patch, AMBARI-14987-branch-2.2-v2.patch, 
> AMBARI-14987-branch-2.2.patch, AMBARI-14987-trunk-v1.patch, 
> AMBARI-14987-trunk-v2.patch, AMBARI-14987-trunk-v3.patch, 
> AMBARI-14987-trunk.patch
>
>
> On the assign masters page for the wizard, recommendations are not shown for 
> a master component that is being added for an installed service.
> This happens while adding HAWQSTANDBY to the cluster using the 'Add 
> HAWQSTANDBY' wizard (situation: HAWQ service is already installed on the 
> cluster). 
> The fix might also solve the issue where there is a installed service and the 
> upgrade of the service includes installing a new master component



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

Re: Review Request 43430: assign_master_component.js does not show recommendations while adding master component for a service which is already installed

[Matt]

> On Feb. 19, 2016, 10:57 a.m., Alexandr Antonenko wrote:
> > ambari-web/app/mixins/wizard/assign_master_components.js, line 776
> > 
> >
> > No need in such construction, there is native ember function 
> > pushObjects.
> 
> Matt wrote:
> Thanks for reviewing Alexander
> 
> 
> I've been having an issue with the unit test when I use 
> `hostList.pushObjects(hostNames)`.
> The existing unit test for `loadRecommendationsSuccessCallback` works 
> when I use `Array.prototype.push.apply(hostList, hostNames);`
> However, when I use `hostList.pushObjects(hostNames)`, the deep 
> comparison 
> `expect(c.get('content.recommendedHostsForComponents')).to.deep.equal(expected)`
>  does not work, and the unit test keeps failing.
> 
> I tried changing the expect to use `to.deep.equal`, `to.eql`, 
> `to.deep.eq` - neither of them worked.
> 
> Do you have any suggestions on how to get past this issue? 
> 
> As a last resort, I was planning to convert the result into JSON and 
> compare it with an `expectedJSON`.
> 
> 
> ```
>   describe('#loadRecommendationsSuccessCallback', function () {
> 
> it('should set recommendations', function() {
>   c.loadRecommendationsSuccessCallback(data);
>   
> expect(c.get('content.recommendations')).to.eq(data.resources[0].recommendations);
> });
> 
> it('should set recommendedHostsForComponents', function() {
>   c.loadRecommendationsSuccessCallback(data);
>   var expected = {
> "c1": ["h1", "h2", "h4", "h3"],
> "c3": ["h1"],
> "c2": ["h1", "h2", "h4"]
>   };
> 
>   
> expect(c.get('content.recommendedHostsForComponents')).to.deep.equal(expected);
> });
>   });
> ```
> 
> Alexandr Antonenko wrote:
> This is something that you will also see in future, and while using other 
> functions, including native js function. If you do some modification with 
> object or array, sometimes deep/equal return incorrect result. In that case 
> please use JSON.stringify() and compare as plain text.
> p.s. For deep equal please use eql()

I've opened a new review after accomodating your feedback: 
https://reviews.apache.org/r/43812/

Thanks
Matt


- Matt


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


On Feb. 16, 2016, 2:13 p.m., Matt wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43430/
> ---
> 
> (Updated Feb. 16, 2016, 2:13 p.m.)
> 
> 
> Review request for Ambari, Alexander Denissov, Alejandro Fernandez, Aleksandr 
> Kovalenko, Alexandr Antonenko, bhuvnesh chaudhary, Goutam Tadi, Jaimin Jetly, 
> jun aoki, Lav Jain, Newton Alex, Oleksandr Diachenko, and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-14987
> https://issues.apache.org/jira/browse/AMBARI-14987
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> On the assign masters page for the wizard, recommendations are not shown for 
> a master component that is being added for an installed service.
> 
> This happens while adding HAWQSTANDBY to the cluster using the 'Add 
> HAWQSTANDBY' wizard (situation: HAWQ service is already installed on the 
> cluster).
> 
> The function getHostForMaster used to return the next available host for the 
> master.
> For example:
> Case 1: component C1 is NOT installed on any hosts.
> getHostForMaster would return the first host from the allHosts list.
> Case 2: component C2 is installed on host H1
> getHostForMaster would return next available host from the allHosts list.
> If allHosts = ['H1', 'H2', 'H3']. It would return H2
> 
> To avoid just placing the component on the next available host, the 
> recommendation is considered.
> Current implementation:
> If a host is recommended for the master, place it on that host (if it is not 
> already installed on that host).
> If no recommendation is given, place it on the next available host.
> 
> 
> Diffs
> -
> 
>   ambari-web/app/assets/test/tests.js 9d5cbc1 
>   ambari-web/app/mixins/wizard/assign_master_components.js f6d1b1a 
>   ambari-web/test/mixins/wizard/assign_master_components_test.js PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/43430/diff/
> 
> 
> Testing
> ---
> 
> Manually Tested.
> 
> Tested assign_master page on cluster installation, add service wizard, enable 
> namenode wizard and add hawq standby wizard.
> 
> Unit test added:
>   10412 tests complete (9 seconds)
>   121 tests pending
> 
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> 

Review Request 43812: Use ember functions mapProperty and pushObjects in AMBARI-14987

[Matt]

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

Review request for Ambari and Alexandr Antonenko.


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


Repository: ambari


Description
---

Use mapProperty and pushObjects as suggested by AlexAntonenko in 
https://reviews.apache.org/r/43430/


Diffs
-

  ambari-web/app/mixins/wizard/assign_master_components.js 62efdac 
  ambari-web/test/mixins/wizard/assign_master_components_test.js a3ffb22 

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


Testing
---

Manually Tested.

Updated unit test to use JSON.stringify(). All unit tests passed.

  10422 tests complete (9 seconds)
  121 tests pending


[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 40.956 s
[INFO] Finished at: 2016-02-23T12:18:56-08:00
[INFO] Final Memory: 12M/310M
[INFO] 


Thanks,

Matt

Review Request 43895: Patch Upgrade: integrate API to POST new repo version when registering new version

[Xi Wang]

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

Review request for Ambari, Richard Zang and Yusaku Sako.


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


Repository: ambari


Description
---

On Register Version page, UI provides two ways to upload version definition 
file, both should POST new stack version. 

1. Browse local files and then Upload file,

POST /api/v1/version_definitions


The equivalent curl call would look like so (the text/xml header is required):

curl -u admin:admin -H "Content-Type: text/xml" -X POST -d 
@ambari-server/src/test/resources/hbase_version_test.xml 
http://localhost:8080/api/v1/version_definitions


2. Enter the Url then click on "Read Version File" button,

POST  /api/v1/version_definitions
{
  "RepositoryVersions": {
"version_url": "http://somewhere/version-definition.xml;
  }
}


Diffs
-

  
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/stackVersions/StackVersionsCreateCtrl.js
 190670a 
  ambari-admin/src/main/resources/ui/admin-web/app/scripts/i18n.config.js 
4caf85f 
  ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Stack.js 
ae67c7e 
  
ambari-admin/src/main/resources/ui/admin-web/app/views/stackVersions/stackVersionPage.html
 112ded8 
  ambari-web/app/mappers/repository_version_mapper.js c937678 
  ambari-web/app/styles/stack_versions.less 5490592 
  ambari-web/app/templates/main/admin/stack_upgrade/upgrade_version_box.hbs 
84d7835 
  ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_box_view.js 
1ea0c66 
  ambari-web/app/views/main/admin/stack_upgrade/upgrade_version_column_view.js 
d7e26e2 
  ambari-web/app/views/main/admin/stack_upgrade/versions_view.js 17010ba 

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


Testing
---

UT passed


Thanks,

Xi Wang

[jira] [Commented] (AMBARI-15135) [Ambari tarballs] ambari-server java-side should support running from custom root

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15135:
-

SUCCESS: Integrated in Ambari-trunk-Commit #4376 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4376/])
AMBARI-15135. [Ambari tarballs] ambari-server java-side should support 
(aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9d7ff5f14f44a58ba280a964a51a85e9f654b27f])
* Committed


> [Ambari tarballs] ambari-server java-side should support running from custom 
> root
> -
>
> Key: AMBARI-15135
> URL: https://issues.apache.org/jira/browse/AMBARI-15135
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15135.patch
>
>




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

[jira] [Updated] (AMBARI-15147) Patch Upgrade: integrate API to POST new repo version when registering new version

[Xi Wang (JIRA)]

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

Xi Wang updated AMBARI-15147:
-
Attachment: AMBARI-15147.patch

> Patch Upgrade: integrate API to  POST new repo version when registering new 
> version
> ---
>
> Key: AMBARI-15147
> URL: https://issues.apache.org/jira/browse/AMBARI-15147
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-15147.patch
>
>
> On Register Version page, UI provides two ways to upload version definition 
> file, both should POST new stack version. 
> 1. Browse local files and then Upload file,
> {code}
> POST /api/v1/version_definitions
> 
> {code}
> The equivalent curl call would look like so (the text/xml header is required):
> {code}
> curl -u admin:admin -H "Content-Type: text/xml" -X POST -d 
> @ambari-server/src/test/resources/hbase_version_test.xml 
> http://localhost:8080/api/v1/version_definitions
> {code}
> 2. Enter the Url then click on "Read Version File" button,
> {code}
> POST  /api/v1/version_definitions
> {
>   "RepositoryVersions": {
> "version_url": "http://somewhere/version-definition.xml;
>   }
> }
> {code}



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

[jira] [Commented] (AMBARI-15147) Patch Upgrade: integrate API to POST new repo version when registering new version

[Xi Wang (JIRA)]

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

Xi Wang commented on AMBARI-15147:
--

Executed 61 of 61 SUCCESS (0.097 secs / 0.314 secs)

> Patch Upgrade: integrate API to  POST new repo version when registering new 
> version
> ---
>
> Key: AMBARI-15147
> URL: https://issues.apache.org/jira/browse/AMBARI-15147
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Xi Wang
>Assignee: Xi Wang
> Fix For: 2.4.0
>
>
> On Register Version page, UI provides two ways to upload version definition 
> file, both should POST new stack version. 
> 1. Browse local files and then Upload file,
> {code}
> POST /api/v1/version_definitions
> 
> {code}
> The equivalent curl call would look like so (the text/xml header is required):
> {code}
> curl -u admin:admin -H "Content-Type: text/xml" -X POST -d 
> @ambari-server/src/test/resources/hbase_version_test.xml 
> http://localhost:8080/api/v1/version_definitions
> {code}
> 2. Enter the Url then click on "Read Version File" button,
> {code}
> POST  /api/v1/version_definitions
> {
>   "RepositoryVersions": {
> "version_url": "http://somewhere/version-definition.xml;
>   }
> }
> {code}



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

[jira] [Created] (AMBARI-15147) Patch Upgrade: integrate API to POST new repo version when registering new version

[Xi Wang (JIRA)]

Xi Wang created AMBARI-15147:


 Summary: Patch Upgrade: integrate API to  POST new repo version 
when registering new version
 Key: AMBARI-15147
 URL: https://issues.apache.org/jira/browse/AMBARI-15147
 Project: Ambari
  Issue Type: Task
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Xi Wang
Assignee: Xi Wang
 Fix For: 2.4.0


On Register Version page, UI provides two ways to upload version definition 
file, both should POST new stack version. 

1. Browse local files and then Upload file,
{code}
POST /api/v1/version_definitions

{code}
The equivalent curl call would look like so (the text/xml header is required):
{code}
curl -u admin:admin -H "Content-Type: text/xml" -X POST -d 
@ambari-server/src/test/resources/hbase_version_test.xml 
http://localhost:8080/api/v1/version_definitions
{code}



2. Enter the Url then click on "Read Version File" button,
{code}
POST  /api/v1/version_definitions
{
  "RepositoryVersions": {
"version_url": "http://somewhere/version-definition.xml;
  }
}
{code}



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

[jira] [Created] (AMBARI-15146) 500 status code received on POST method for API: /api/v1/clusters//requests

[Sam Mingolelli (JIRA)]

Sam Mingolelli created AMBARI-15146:
---

 Summary: 500 status code received on POST method for API: 
/api/v1/clusters//requests
 Key: AMBARI-15146
 URL: https://issues.apache.org/jira/browse/AMBARI-15146
 Project: Ambari
  Issue Type: Bug
  Components: ambari-server
Affects Versions: 2.1.2
 Environment: {code}
$ cat /etc/redhat-release
CentOS Linux release 7.2.1511 (Core)

$ uname -a
Linux dev09-ost-hivetest-h-hb02.td.local 3.10.0-327.10.1.el7.x86_64 #1 SMP Tue 
Feb 16 17:03:50 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
{code}
Reporter: Sam Mingolelli
Priority: Critical


While attempting to enable kerberos on a clean install of HDP 2.3 (Ambari 
2.1.2) I encounter the following error dialog:

Error
500 status code received on POST method for API: 
/api/v1/clusters/dev09_ost_hivetest_h/requests 

Error message: Server Error

The log file also contains an exception:

{code}
23 Feb 2016 14:14:45,633  WARN [qtp-client-33592] 
KdcServerConnectionVerification:167 - Failed to connect to the KDC server at 
kdc01.td.teradata.com:88 over TCP
23 Feb 2016 14:14:45,664  INFO [qtp-client-33592] 
KdcServerConnectionVerification:164 - Successfully connected to the KDC server 
at kdc01.td.teradata.com:88 over UDP
23 Feb 2016 14:15:02,723  INFO [qtp-client-3016] ClusterImpl:1901 - Deleting 
service for cluster, clusterName=dev09_ost_hivetest_h, serviceName=KERBEROS
23 Feb 2016 14:15:02,724  INFO [qtp-client-3016] ServiceImpl:583 - Deleting all 
components for service, clusterName=dev09_ost_hivetest_h, serviceName=KERBEROS
23 Feb 2016 14:15:02,724  INFO [qtp-client-3016] ServiceComponentImpl:589 - 
Deleting all servicecomponenthosts for component, 
clusterName=dev09_ost_hivetest_h, serviceName=KERBEROS, 
componentName=KERBEROS_CLIENT
23 Feb 2016 14:15:02,727  INFO [qtp-client-3016] ServiceImpl:550 - Deleting all 
serviceconfigs for service, clusterName=dev09_ost_hivetest_h, 
serviceName=KERBEROS
23 Feb 2016 14:15:04,294  INFO [qtp-client-48401] 
AmbariManagementControllerImpl:1324 - Received a updateCluster request, 
clusterId=2, clusterName=dev09_ost_hivetest_h, securityType=null, request={ 
clusterName=dev09_ost_hivetest_h, clusterId=2, provisioningState=null, 
securityType=null, stackVersion=HDP-2.3, desired_scv=null, hosts=[] }
23 Feb 2016 14:15:04,294  INFO [qtp-client-48401] 
AmbariManagementControllerImpl:1415 - Applying configuration with tag 
'version1456254905543' to cluster 'dev09_ost_hivetest_h'  for configuration 
type kerberos-env
23 Feb 2016 14:15:04,303  INFO [qtp-client-48401] 
AmbariManagementControllerImpl:1415 - Applying configuration with tag 
'version1456254905543' to cluster 'dev09_ost_hivetest_h'  for configuration 
type krb5-conf
23 Feb 2016 14:15:04,421  INFO [qtp-client-48101] 
AmbariManagementControllerImpl:1324 - Received a updateCluster request, 
clusterId=2, clusterName=dev09_ost_hivetest_h, securityType=null, request={ 
clusterName=dev09_ost_hivetest_h, clusterId=2, provisioningState=null, 
securityType=null, stackVersion=HDP-2.3, desired_scv=null, hosts=[] }
23 Feb 2016 14:15:04,996  INFO [qtp-client-48129] AbstractResourceProvider:590 
- Received a updateService request, clusterName=dev09_ost_hivetest_h, 
serviceName=KERBEROS, request=clusterName=dev09_ost_hivetest_h, 
serviceName=KERBEROS, desiredState=INSTALLED
23 Feb 2016 14:15:04,999  INFO [qtp-client-48129] 
AmbariManagementControllerImpl:2025 - 
AmbariManagementControllerImpl.createHostAction: created ExecutionCommand for 
host dev09-ost-hivetest-h-hb02.td.local, role KERBEROS_CLIENT, roleCommand 
INSTALL, and command ID 85--1, with cluster-env tags version1
23 Feb 2016 14:15:05,016  INFO [ambari-action-scheduler] 
ServiceComponentHostImpl:949 - Host role transitioned to a new state, 
serviceComponentName=KERBEROS_CLIENT, 
hostName=dev09-ost-hivetest-h-hb02.td.local, oldState=INIT, 
currentState=INSTALLING
23 Feb 2016 14:15:09,045  INFO [qtp-ambari-agent-48404] 
ServiceComponentHostImpl:949 - Host role transitioned to a new state, 
serviceComponentName=KERBEROS_CLIENT, 
hostName=dev09-ost-hivetest-h-hb02.td.local, oldState=INSTALLING, 
currentState=INSTALLED
23 Feb 2016 14:15:09,580  INFO [qtp-client-3016] 
AmbariManagementControllerImpl:3312 - Received action execution request, 
clusterName=dev09_ost_hivetest_h, request=isCommand :true, action :null, 
command :KERBEROS_SERVICE_CHECK, inputs :{}, resourceFilters: 
[RequestResourceFilter{serviceName='KERBEROS', componentName='null', 
hostNames=[]}], exclusive: false, clusterName :dev09_ost_hivetest_h
23 Feb 2016 14:15:09,668 ERROR [qtp-client-3016] BaseManagementHandler:66 - 
Caught a runtime exception while attempting to create a resource
java.lang.NullPointerException
at 
org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.persistActions(ActionDBAccessorImpl.java:300)
at 

Re: Ru/EU not updating alert definitions in Ambari server db?

[Di Li]

Hello folks,

Thanks for the reply. I have my own stack called MyStack 1.0 and MyStack 2.0. I 
found the issue after I heavily refactored the MyStack directory structure.

1. In Ambari 2.1/MyStack 1.0, I have Flume's alert_flume_agent_status.py 
defined as MyStack/1.0/services/FLUME/package/alerts/alert_flume_agent_status.py
2. In Ambari 2.2, I changed the structure of MyStack to make use of common 
services, so 
   a) The Flume directories are moved into common-services
   b) MyStack 1.0 now contains a Flume dir with just a metainfo.xml file.
   c) I also added MyStack 2.0 so I can run RU/EU. MyStack 2.0 also only 
contains a Flume dir with just a metainfo.xml file.
   d) common-services has Flume agent alert Python script as 
FLUME/1.2.3.4.5/package/alerts/alert_flume_agent_status.py (note the custom 
version I used here...). As you can see, I changed the path to the 
alert_flume_agent_status.py...
3. Perform RU

-- Post RU, I saw Flume agent produced an "UNKNOWN" alert with an error message
Flume Agent Status
Unable to find 
'MyStack/1.0/services/FLUME/package/alerts/alert_flume_agent_status.py' as an 
absolute path or part of /var/lib/ambari-agent/cache/stacks or 
/var/lib/ambari-agent/cache/host_scripts

-- I noticed tht in the Ambari server database, the Flume agent alert 
definition had the wrong patch to the Python script as shown below. It still 
has the old MyStack based path.
9 |  2 | flume_agent_status | FLUME 
 | FLUME_HANDLER   |
 ANY | Flume Agent Status   | This host-level 
alert is triggered if any of the expect
ed flume agent processes are not available.
   |   1 | 1 | SCRIPT  | 
{"path":"MyStack/1.0/services/FLUME/package/alerts/alert_flu
me_agent_status.py","parameters":[{"name":"run.directory","display_name":"Run 
Directory","value":"/var/run/flume","de
scription":"The directory where flume agent processes will place their PID 
files.","type":"STRING"}],"type":"SCRIPT"}

-- This prompted me to ask the question about whether the alert definition 
should have been updated by RU/EU (or ambari server upgrade maybe).

-- I was able to update Flume agent's alert definition with the correct path 
via following REST API.
curl -u admin:admin -H 'X-Requested-By:ambari' -X PUT -d '{"AlertDefinition" : 
{"source" : {"path" : 
"FLUME/1.2.3.4.5/package/alerts/alert_flume_agent_status.py",  "type" : 
"SCRIPT" }}}' 
http://myhost.mydomain.com:8080/api/v1/clusters/test/alert_definitions/9


  From: Jonathan Hurley 
 To: "dev@ambari.apache.org" ; Di Li 
 
 Sent: Tuesday, February 23, 2016 1:23 PM
 Subject: Re: Ru/EU not updating alert definitions in Ambari server db?
   
No, they are not updated; however, stack inheritance should allow you to 
reference the files from the new stack. We've performed many different upgrades 
both both inter-stack and intra-stack and have never seen any issues with alert 
definitions. 

> On Feb 23, 2016, at 1:13 PM, Di Li  wrote:
> 
> Hello folks,
> 
> Do RU and EU handle updating alert definitions stored in the Ambari server 
> database? 
> 
> Based on what I tested, alert definitions, especially the paths to 
> alert_***.py Python scripts are not updated by neither RU and EU. meaning if 
> I changed the path to the alert_***.py scripts in a new release, the alert 
> definitions are broken and certain components would show with a UNKNOWN alert 
> state after I run RU/EU.
> 
> 
> P.S
>    I know that, post upgrade, I can manually update the alert definitions via 
>REST APIs.
> 
> Thanks.
> 
> 


  

[jira] [Commented] (AMBARI-15144) Login Message: clicking on submit button of login message has not action

[Oleg Nechiporenko (JIRA)]

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

Oleg Nechiporenko commented on AMBARI-15144:


+1 for patch

> Login Message: clicking on submit button of login message has not action
> 
>
> Key: AMBARI-15144
> URL: https://issues.apache.org/jira/browse/AMBARI-15144
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-15144.patch
>
>
> While reviewing login message if you click on submit button nothing will 
> happen



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

[jira] [Commented] (AMBARI-14798) Users cannot login with uppercase username

[Hadoop QA (JIRA)]

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

Hadoop QA commented on AMBARI-14798:


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

This message is automatically generated.

> Users cannot login with uppercase username
> --
>
> Key: AMBARI-14798
> URL: https://issues.apache.org/jira/browse/AMBARI-14798
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.2.2
>
> Attachments: AMBARI-14798.patch, AMBARI-14798_branch-2.2.patch
>
>
> In Ambari DB, every username is stored in lowercase format. If a remote 
> server store users in uppercase format (e.g. an active directory), the user 
> cannot login with using uppercase letters in the username.



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

Re: Review Request 43830: AMBARI-15127 : Add retry logic for DB Setup during Ranger upgrade step (to handle upgrade with Ranger HA)

[Alejandro Fernandez]

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



Actually, is this because Ranger DB script is called from multiple hosts during 
RU/EU and instead it should only be called once?
In which case, the fix is to change the orchestration and not the retries.

- Alejandro Fernandez


On Feb. 23, 2016, 12:10 p.m., Gautam Borad wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/43830/
> ---
> 
> (Updated Feb. 23, 2016, 12:10 p.m.)
> 
> 
> Review request for Ambari, Alejandro Fernandez, Jaimin Jetly, Jonathan 
> Hurley, Mahadev Konar, Sumit Mohanty, Selvamohan Neethiraj, and Velmurugan 
> Periasamy.
> 
> 
> Bugs: AMBARI-15127
> https://issues.apache.org/jira/browse/AMBARI-15127
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> Need to apply multiple retries for Ranger DB setup calls to handle concurrent 
> calls to one DB from 2 different hosts where Ranger Admin is installed.
> This scenario is needed to handle upgrades of HDP in a case when Ranger HA is 
> enabled.
> 
> 
> Diffs
> -
> 
>   
> ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py
>  4660cf8 
> 
> Diff: https://reviews.apache.org/r/43830/diff/
> 
> 
> Testing
> ---
> 
> Installed Ranger on Debian 7 + Ranger HA and then performed EU to 2.4.0.0-XXX.
> 
> 
> Thanks,
> 
> Gautam Borad
> 
>

[jira] [Commented] (AMBARI-15096) Edit WEB Alert should show Critical for Connection Timeout

[Zhe (Joe) Wang (JIRA)]

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

Zhe (Joe) Wang commented on AMBARI-15096:
-

Correction: Patch committed to trunk and branch-2.2

> Edit WEB Alert should show Critical for Connection Timeout
> --
>
> Key: AMBARI-15096
> URL: https://issues.apache.org/jira/browse/AMBARI-15096
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.2.2
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.2.2
>
> Attachments: AMBARI-15096_branch_2_2.0.patch, 
> AMBARI-15096_branch_2_2.1.patch, AMBARI-15096_trunk.0.patch, 
> AMBARI-15096_trunk.1.patch, AMBARI-15096_trunk.2.patch
>
>
> For WEB alerts, the Connection Timeout fields should show CRITICAL badge 
> since if the connection times out, it is a critical situation.



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

Re: Ru/EU not updating alert definitions in Ambari server db?

[Jonathan Hurley]

No, they are not updated; however, stack inheritance should allow you to 
reference the files from the new stack. We've performed many different upgrades 
both both inter-stack and intra-stack and have never seen any issues with alert 
definitions. 

> On Feb 23, 2016, at 1:13 PM, Di Li  wrote:
> 
> Hello folks,
> 
> Do RU and EU handle updating alert definitions stored in the Ambari server 
> database? 
> 
> Based on what I tested, alert definitions, especially the paths to 
> alert_***.py Python scripts are not updated by neither RU and EU. meaning if 
> I changed the path to the alert_***.py scripts in a new release, the alert 
> definitions are broken and certain components would show with a UNKNOWN alert 
> state after I run RU/EU.
> 
> 
> P.S
> I know that, post upgrade, I can manually update the alert definitions 
> via REST APIs.
> 
> Thanks.
> 
> 

[jira] [Commented] (AMBARI-15120) Alerts UI Usability Changes

[Zhe (Joe) Wang (JIRA)]

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

Zhe (Joe) Wang commented on AMBARI-15120:
-

Correction: Patch committed to trunk

> Alerts UI Usability Changes
> ---
>
> Key: AMBARI-15120
> URL: https://issues.apache.org/jira/browse/AMBARI-15120
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Zhe (Joe) Wang
>Assignee: Zhe (Joe) Wang
> Fix For: 2.4.0
>
> Attachments: AMBARI-15120.0.patch, AMBARI-15120.1.patch
>
>
> 1) Remove host badge from Hosts tab
> 2) On summary page, next to component "Started" text, need to show if a 
> component has alerts



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

Re: Ru/EU not updating alert definitions in Ambari server db?

[Alejandro Fernandez]

Typically, alert definitions are modified during Ambari Upgrade as opposed
to RU/EU since alert definitions are for the most part agnostic to the
individual versions inside the stack.
Can you provide an example of an alert that needs to change during a stack
upgrade?

Thanks,
Alejandro

On 2/23/16, 10:13 AM, "Di Li"  wrote:

>Hello folks,
>
>Do RU and EU handle updating alert definitions stored in the Ambari
>server database? 
>
>Based on what I tested, alert definitions, especially the paths to
>alert_***.py Python scripts are not updated by neither RU and EU. meaning
>if I changed the path to the alert_***.py scripts in a new release, the
>alert definitions are broken and certain components would show with a
>UNKNOWN alert state after I run RU/EU.
>
>
>P.S
>I know that, post upgrade, I can manually update the alert
>definitions via REST APIs.
>
>Thanks.
>
>

Ru/EU not updating alert definitions in Ambari server db?

[Di Li]

Hello folks,

Do RU and EU handle updating alert definitions stored in the Ambari server 
database? 

Based on what I tested, alert definitions, especially the paths to alert_***.py 
Python scripts are not updated by neither RU and EU. meaning if I changed the 
path to the alert_***.py scripts in a new release, the alert definitions are 
broken and certain components would show with a UNKNOWN alert state after I run 
RU/EU.


P.S
I know that, post upgrade, I can manually update the alert definitions via 
REST APIs.

Thanks.

[jira] [Commented] (AMBARI-15135) [Ambari tarballs] ambari-server java-side should support running from custom root

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk commented on AMBARI-15135:
--

Nevermind last comment, pushed the new change.

> [Ambari tarballs] ambari-server java-side should support running from custom 
> root
> -
>
> Key: AMBARI-15135
> URL: https://issues.apache.org/jira/browse/AMBARI-15135
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15135.patch
>
>




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

[jira] [Commented] (AMBARI-15135) [Ambari tarballs] ambari-server java-side should support running from custom root

[Andrew Onischuk (JIRA)]

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

Andrew Onischuk commented on AMBARI-15135:
--

Doesn't look related to Hudson rat failure. I just rechecked it:
{noformat}
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Ambari Web  SUCCESS [13.028s]
[INFO] Ambari Views .. SUCCESS [3.961s]
[INFO] Ambari Metrics Common . SUCCESS [3.505s]
[INFO] Ambari Server . SUCCESS [1:02.206s]
[INFO] Ambari Agent .. SUCCESS [33.439s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 1:07.121s (Wall Clock)
[INFO] Finished at: Tue Feb 23 19:56:43 EET 2016
[INFO] Final Memory: 74M/1601M
[INFO] 
{noformat}

The patch committed adds one new file, and includes license to it. Also Hadoop 
QA's rat check didn't fail for it.

> [Ambari tarballs] ambari-server java-side should support running from custom 
> root
> -
>
> Key: AMBARI-15135
> URL: https://issues.apache.org/jira/browse/AMBARI-15135
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15135.patch
>
>




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

[jira] [Updated] (AMBARI-15145) Revamped Filebrowser Design - UI

[DIPAYAN BHOWMICK (JIRA)]

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

DIPAYAN BHOWMICK updated AMBARI-15145:
--
Attachment: AMBARI-15145.branch-2.2.patch

> Revamped Filebrowser Design - UI
> 
>
> Key: AMBARI-15145
> URL: https://issues.apache.org/jira/browse/AMBARI-15145
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-views
>Affects Versions: 2.2.0
>Reporter: DIPAYAN BHOWMICK
>Assignee: DIPAYAN BHOWMICK
> Fix For: 2.2.2
>
> Attachments: AMBARI-15145.branch-2.2.patch
>
>
> REQUEST:  To redo the filebrowser UI
> Requirements: 
> Rework the File Browser mostly on the Front End display to:
> -Make it scalable to handle directories with many files
> -Improve the performance
> -Improve the usability and layout
> -Add some missing capabilities 
> -Increase the quality and robustness
> Here are the high level functionalities achieved in new file browser view.
> - Show HDFS files/folders along with their Name, Size, Last Modified, Owner, 
> Group, and Permission.
> - Capability of sorting by Name, Size, Last Modified, Owner, Group, and 
> Permission in ascending or descending order for files and folders.
> - Capability of creating "New Directory" and "Upload" file in the current 
> directory. 
> - Search file/folder by name in the current directory.
> - User should be able to perform the actions like Open, Rename, Edit 
> Permissions, Delete, Copy, Move and Download for file or folder.
> - User should be able to multi select files/folders for the actions like  
> Delete, Copy, Move and Download
> - User should be able to perform concatenate action for multi selected files.
> - Preview of files before actual download.



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

[jira] [Updated] (AMBARI-15137) Parameterize distro-specific stack information for TEZ

[Juanjo Marron (JIRA)]

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

Juanjo Marron updated AMBARI-15137:
---
Attachment: (was: AMBARI-15137.patch)

> Parameterize distro-specific stack information for TEZ
> --
>
> Key: AMBARI-15137
> URL: https://issues.apache.org/jira/browse/AMBARI-15137
> Project: Ambari
>  Issue Type: Technical task
>  Components: ambari-server
>Affects Versions: 2.1.0, 2.2.0
>Reporter: Juanjo Marron
>Assignee: Juanjo Marron
>
> Apply the prototype detailed on AMBARI-13364 to TEZ .
> Tokens such as: current version, upgrade version, stack name, install 
> path..., will be parameterized and distro-agnostic at common-service 
> definition level.



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

[jira] [Commented] (AMBARI-14798) Users cannot login with uppercase username

[Hudson (JIRA)]

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

Hudson commented on AMBARI-14798:
-

FAILURE: Integrated in Ambari-trunk-Commit #4375 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4375/])
AMBARI-14798. Users cannot login with uppercase username (Oliver Szabo (rlevas: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=e1ca24160027d73cf27b90b35bc0757442a0cbdd])
* 
ambari-server/src/main/java/org/apache/ambari/server/api/services/ActiveWidgetLayoutService.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/services/UserAuthorizationService.java
* 
ambari-server/src/test/java/org/apache/ambari/server/api/services/UserAuthorizationServiceTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/api/services/UserPrivilegeServiceTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/services/UserService.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/services/UserPrivilegeService.java
Revert "AMBARI-14798. Users cannot login with uppercase username (Oliver 
(rlevas: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=f7ebe912b7647caa97b8c28f243d0f8a92f5dfb6])
* 
ambari-server/src/main/java/org/apache/ambari/server/api/services/UserPrivilegeService.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/services/UserService.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/services/UserAuthorizationService.java
* 
ambari-server/src/test/java/org/apache/ambari/server/api/services/UserPrivilegeServiceTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/api/services/UserAuthorizationServiceTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/services/ActiveWidgetLayoutService.java
AMBARI-14798. Users cannot login with uppercase username (Oliver Szabo (rlevas: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=2b42559f516d0f45072174dac5f9d230b8e7c31c])
* 
ambari-server/src/main/java/org/apache/ambari/server/api/services/UserService.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/services/ActiveWidgetLayoutService.java
* 
ambari-server/src/test/java/org/apache/ambari/server/api/services/ActiveWidgetLayoutServiceTest.java
* 
ambari-server/src/test/java/org/apache/ambari/server/api/services/UserServiceTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/services/UserPrivilegeService.java
* 
ambari-server/src/test/java/org/apache/ambari/server/api/services/UserPrivilegeServiceTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/api/services/UserAuthorizationService.java
* 
ambari-server/src/test/java/org/apache/ambari/server/api/services/UserAuthorizationServiceTest.java


> Users cannot login with uppercase username
> --
>
> Key: AMBARI-14798
> URL: https://issues.apache.org/jira/browse/AMBARI-14798
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.2.0
>Reporter: Olivér Szabó
>Assignee: Olivér Szabó
> Fix For: 2.2.2
>
> Attachments: AMBARI-14798.patch, AMBARI-14798_branch-2.2.patch
>
>
> In Ambari DB, every username is stored in lowercase format. If a remote 
> server store users in uppercase format (e.g. an active directory), the user 
> cannot login with using uppercase letters in the username.



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

[jira] [Commented] (AMBARI-15135) [Ambari tarballs] ambari-server java-side should support running from custom root

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15135:
-

FAILURE: Integrated in Ambari-trunk-Commit #4375 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4375/])
AMBARI-15135. [Ambari tarballs] ambari-server java-side should support 
(aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=18d5a6964212237c0cd9a5c8c8211cd059cae716])
* ambari-server/pom.xml
* Committed
* ambari-server/src/main/package/rpm/postinstall.sh
* ambari-server/conf/unix/ca.config
* 
ambari-server/src/main/java/org/apache/ambari/server/security/encryption/MasterKeyServiceImpl.java
* ambari-server/conf/unix/log4j.properties
* ambari-server/src/main/package/deb/control/preinst
* ambari-server/src/main/package/deb/control/prerm
* 
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java
* ambari-server/src/main/package/rpm/preremove.sh
* ambari-common/src/main/repo/install_ambari_tarball.py
* ambari-server/src/main/java/org/apache/ambari/server/utils/AmbariPath.java
* ambari-server/src/main/package/deb/control/postinst
* ambari-server/src/main/package/rpm/posttrans_server.sh
* ambari-server/src/main/package/rpm/preinstall.sh
* ambari-server/conf/unix/install-helper.sh


> [Ambari tarballs] ambari-server java-side should support running from custom 
> root
> -
>
> Key: AMBARI-15135
> URL: https://issues.apache.org/jira/browse/AMBARI-15135
> Project: Ambari
>  Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15135.patch
>
>




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

[jira] [Commented] (AMBARI-15142) Small refactor for configs

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15142:
-

SUCCESS: Integrated in Ambari-trunk-Commit #4374 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4374/])
AMBARI-15142 Small refactor for configs. (ababiichuk) (ababiichuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=ea6a7a614190917abaa22dbec5895cb9b66b13b4])
* ambari-web/app/utils/config.js
* ambari-web/test/utils/config_test.js
* ambari-web/app/utils.js
* ambari-web/test/controllers/main/admin/kerberos/step4_controller_test.js
* ambari-web/app/views/common/configs/widgets/config_widget_view.js
* ambari-web/app/controllers/main/service/info/configs.js
* ambari-web/app/utils/configs/theme/theme.js
* ambari-web/app/mappers/configs/stack_config_properties_mapper.js
* ambari-web/app/controllers/wizard.js
* ambari-web/app/mixins/common/kdc_credentials_controller_mixin.js
* ambari-web/app/models/stack_service.js
* ambari-web/app/controllers/main/admin/serviceAccounts_controller.js
* 
ambari-web/app/controllers/main/admin/highAvailability/resourceManager/step3_controller.js
* ambari-web/test/controllers/wizard/step7_test.js
* ambari-web/app/controllers/main/admin/kerberos/step4_controller.js
* ambari-web/app/controllers/wizard/step7_controller.js


> Small refactor for configs
> --
>
> Key: AMBARI-15142
> URL: https://issues.apache.org/jira/browse/AMBARI-15142
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15142.patch
>
>
> Refactor some methods to make them usable on installer and service info 
> configs.



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

[jira] [Commented] (AMBARI-15134) Issues with Login Message dialog Round #2

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15134:
-

FAILURE: Integrated in Ambari-trunk-Commit #4375 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4375/])
AMBARI-15134. Issues with Login Message dialog Round #2 (alexantonenko) 
(hiveww: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=df0b18ca5da59d9ed6bc4340ac09eb51db9963a4])
* 
ambari-admin/src/main/resources/ui/admin-web/app/views/loginActivities/loginMessage.html
* ambari-admin/src/main/resources/ui/admin-web/app/scripts/i18n.config.js
* 
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/loginActivities/LoginMessageMainCtrl.js
* ambari-web/app/router.js


> Issues with Login Message dialog Round #2
> -
>
> Key: AMBARI-15134
> URL: https://issues.apache.org/jira/browse/AMBARI-15134
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15134.patch
>
>
> minor changes for login message 



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

[jira] [Updated] (AMBARI-15144) Login Message: clicking on submit button of login message has not action

[Antonenko Alexander (JIRA)]

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

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

> Login Message: clicking on submit button of login message has not action
> 
>
> Key: AMBARI-15144
> URL: https://issues.apache.org/jira/browse/AMBARI-15144
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-web
>Affects Versions: 2.4.0
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
> Fix For: 2.4.0
>
> Attachments: AMBARI-15144.patch
>
>
> While reviewing login message if you click on submit button nothing will 
> happen



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

[jira] [Commented] (AMBARI-15130) Upgrade alert definition for App Timeline Web UI alert

[Hudson (JIRA)]

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

Hudson commented on AMBARI-15130:
-

FAILURE: Integrated in Ambari-branch-2.2 #378 (See 
[https://builds.apache.org/job/Ambari-branch-2.2/378/])
AMBARI-15130. Upgrade alert definition for App Timeline Web UI (vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=d4a980f26ca2d40777cf3d92e1dfbcc1c38b6186])
* 
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog222.java
* 
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog222Test.java


> Upgrade alert definition for App Timeline Web UI alert
> --
>
> Key: AMBARI-15130
> URL: https://issues.apache.org/jira/browse/AMBARI-15130
> Project: Ambari
>  Issue Type: Bug
>  Components: stacks
>Affects Versions: 2.2.2
>Reporter: Sumit Mohanty
>Assignee: Vitaly Brodetskyi
> Fix For: 2.2.2
>
> Attachments: AMBARI-15130.patch
>
>
> Update the alert definition of the App Timeline Web UI alert. See 
> AMBARI-15123 for the change.



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

[jira] [Created] (AMBARI-15145) Revamped Filebrowser Design - UI

[DIPAYAN BHOWMICK (JIRA)]

DIPAYAN BHOWMICK created AMBARI-15145:
-

 Summary: Revamped Filebrowser Design - UI
 Key: AMBARI-15145
 URL: https://issues.apache.org/jira/browse/AMBARI-15145
 Project: Ambari
  Issue Type: Bug
  Components: ambari-views
Affects Versions: 2.2.0
Reporter: DIPAYAN BHOWMICK
Assignee: DIPAYAN BHOWMICK
 Fix For: 2.2.2


REQUEST:  To redo the filebrowser UI
Requirements: 
Rework the File Browser mostly on the Front End display to:
-Make it scalable to handle directories with many files
-Improve the performance
-Improve the usability and layout
-Add some missing capabilities 
-Increase the quality and robustness

Here are the high level functionalities achieved in new file browser view.
- Show HDFS files/folders along with their Name, Size, Last Modified, Owner, 
Group, and Permission.
- Capability of sorting by Name, Size, Last Modified, Owner, Group, and 
Permission in ascending or descending order for files and folders.
- Capability of creating "New Directory" and "Upload" file in the current 
directory. 
- Search file/folder by name in the current directory.
- User should be able to perform the actions like Open, Rename, Edit 
Permissions, Delete, Copy, Move and Download for file or folder.
- User should be able to multi select files/folders for the actions like  
Delete, Copy, Move and Download
- User should be able to perform concatenate action for multi selected files.
- Preview of files before actual download.



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

[jira] [Created] (AMBARI-15144) Login Message: clicking on submit button of login message has not action

[Antonenko Alexander (JIRA)]

Antonenko Alexander created AMBARI-15144:


 Summary: Login Message: clicking on submit button of login message 
has not action
 Key: AMBARI-15144
 URL: https://issues.apache.org/jira/browse/AMBARI-15144
 Project: Ambari
  Issue Type: Bug
  Components: ambari-web
Affects Versions: 2.4.0
Reporter: Antonenko Alexander
Assignee: Antonenko Alexander
 Fix For: 2.4.0


While reviewing login message if you click on submit button nothing will happen




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