[jira] [Updated] (AMBARI-13535) Hive service check failed with ssl enabled

2015-10-25 Thread Chen Xin Yu (JIRA) 

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

Chen Xin Yu updated AMBARI-13535:
-
Attachment: AMBARI-13535.patch

> Hive service check failed with ssl enabled
> --
>
> Key: AMBARI-13535
> URL: https://issues.apache.org/jira/browse/AMBARI-13535
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Chen Xin Yu
> Attachments: AMBARI-13535.patch
>
>
> If user enable SSL for Hive on ambari UI, hive service check script is not 
> correct, jdbc connection to detect HS2 status is missing ssl params as below:
>  ! beeline -u 'jdbc:hive2://com.apache.host:1/;transportMode=binary;'  -e 
> ''
> Service check for hive on ambari UI works well as there is less error detect, 
> although service check passed, but user will be confused. It's deceiving.



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

[jira] [Updated] (AMBARI-13535) Hive service check failed with ssl enabled

2015-10-25 Thread Chen Xin Yu (JIRA) 

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

Chen Xin Yu updated AMBARI-13535:
-
Attachment: (was: AMBARI-13535.patch)

> Hive service check failed with ssl enabled
> --
>
> Key: AMBARI-13535
> URL: https://issues.apache.org/jira/browse/AMBARI-13535
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Chen Xin Yu
> Attachments: AMBARI-13535.patch
>
>
> If user enable SSL for Hive on ambari UI, hive service check script is not 
> correct, jdbc connection to detect HS2 status is missing ssl params as below:
>  ! beeline -u 'jdbc:hive2://com.apache.host:1/;transportMode=binary;'  -e 
> ''
> Service check for hive on ambari UI works well as there is less error detect, 
> although service check passed, but user will be confused. It's deceiving.



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

[jira] [Updated] (AMBARI-13495) JAVA_HOME setting is improper for Hive

2015-10-25 Thread Chen Xin Yu (JIRA) 

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

Chen Xin Yu updated AMBARI-13495:
-
Attachment: (was: AMBARI-13495.patch)

> JAVA_HOME setting is improper for Hive
> --
>
> Key: AMBARI-13495
> URL: https://issues.apache.org/jira/browse/AMBARI-13495
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Chen Xin Yu
> Attachments: AMBARI-13495.patch
>
>
> Ambari would setup jdk with directory /usr/jdk64/* during ambari-server 
> setup, and several components will export java_home which ambari used in 
> **-env.xml(such as oozie-env.xml), but it's less in hive.
> So hive maybe using another existing jdk, or less JAVA_HOME setting.



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

[jira] [Updated] (AMBARI-13495) JAVA_HOME setting is improper for Hive

2015-10-25 Thread Chen Xin Yu (JIRA) 

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

Chen Xin Yu updated AMBARI-13495:
-
Attachment: AMBARI-13495.patch

> JAVA_HOME setting is improper for Hive
> --
>
> Key: AMBARI-13495
> URL: https://issues.apache.org/jira/browse/AMBARI-13495
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Chen Xin Yu
> Attachments: AMBARI-13495.patch
>
>
> Ambari would setup jdk with directory /usr/jdk64/* during ambari-server 
> setup, and several components will export java_home which ambari used in 
> **-env.xml(such as oozie-env.xml), but it's less in hive.
> So hive maybe using another existing jdk, or less JAVA_HOME setting.



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

[jira] [Commented] (AMBARI-13442) stack advisor layout and validations for HAWQ service master components

2015-10-25 Thread jun aoki (JIRA) 

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

jun aoki commented on AMBARI-13442:
---

Got 2 +1s on reviewboard.
[~adenisso], could you please rebase the patch? I can not apply it.

> stack advisor layout and validations for HAWQ service master components
> ---
>
> Key: AMBARI-13442
> URL: https://issues.apache.org/jira/browse/AMBARI-13442
> Project: Ambari
>  Issue Type: Story
>Affects Versions: 2.1.2
>Reporter: Alexander Denissov
>Assignee: Alexander Denissov
> Fix For: 2.2.0
>
> Attachments: AMBARI-13442.patch, AMBARI-13442.patch.1
>
>
> Apache HAWQ will be a common service. When installing the service via UI 
> wizard, HAWQ Master and HAWQ Standby Master need to be placed on master 
> nodes. They should not be collocated with each other (causing an ERROR 
> message) and with Ambari Server (causing a WARN message).



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

[jira] [Updated] (AMBARI-13535) Hive service check failed with ssl enabled

2015-10-25 Thread Chen Xin Yu (JIRA) 

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

Chen Xin Yu updated AMBARI-13535:
-
Attachment: AMBARI-13535.patch

> Hive service check failed with ssl enabled
> --
>
> Key: AMBARI-13535
> URL: https://issues.apache.org/jira/browse/AMBARI-13535
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Chen Xin Yu
> Attachments: AMBARI-13535.patch
>
>
> If user enable SSL for Hive on ambari UI, hive service check script is not 
> correct, jdbc connection to detect HS2 status is missing ssl params as below:
>  ! beeline -u 'jdbc:hive2://com.apache.host:1/;transportMode=binary;'  -e 
> ''
> Service check for hive on ambari UI works well as there is less error detect, 
> although service check passed, but user will be confused. It's deceiving.



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

[jira] [Updated] (AMBARI-13495) JAVA_HOME setting is improper for Hive

2015-10-25 Thread Chen Xin Yu (JIRA) 

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

Chen Xin Yu updated AMBARI-13495:
-
Attachment: AMBARI-13495.patch

> JAVA_HOME setting is improper for Hive
> --
>
> Key: AMBARI-13495
> URL: https://issues.apache.org/jira/browse/AMBARI-13495
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Chen Xin Yu
> Attachments: AMBARI-13495.patch
>
>
> Ambari would setup jdk with directory /usr/jdk64/* during ambari-server 
> setup, and several components will export java_home which ambari used in 
> **-env.xml(such as oozie-env.xml), but it's less in hive.
> So hive maybe using another existing jdk, or less JAVA_HOME setting.



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

[jira] [Updated] (AMBARI-13535) Hive service check failed with ssl enabled

2015-10-25 Thread Chen Xin Yu (JIRA) 

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

Chen Xin Yu updated AMBARI-13535:
-
Attachment: (was: AMBARI-13535.patch.txt)

> Hive service check failed with ssl enabled
> --
>
> Key: AMBARI-13535
> URL: https://issues.apache.org/jira/browse/AMBARI-13535
> Project: Ambari
>  Issue Type: Bug
>Affects Versions: 2.1.0
>Reporter: Chen Xin Yu
>
> If user enable SSL for Hive on ambari UI, hive service check script is not 
> correct, jdbc connection to detect HS2 status is missing ssl params as below:
>  ! beeline -u 'jdbc:hive2://com.apache.host:1/;transportMode=binary;'  -e 
> ''
> Service check for hive on ambari UI works well as there is less error detect, 
> although service check passed, but user will be confused. It's deceiving.



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

[jira] [Updated] (AMBARI-13495) JAVA_HOME setting is improper for Hive

2015-10-25 Thread Chen Xin Yu (JIRA) 

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

Chen Xin Yu updated AMBARI-13495:
-
Attachment: (was: AMBARI-13495.patch.txt)

> JAVA_HOME setting is improper for Hive
> --
>
> Key: AMBARI-13495
> URL: https://issues.apache.org/jira/browse/AMBARI-13495
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.0
>Reporter: Chen Xin Yu
> Attachments: AMBARI-13495.patch
>
>
> Ambari would setup jdk with directory /usr/jdk64/* during ambari-server 
> setup, and several components will export java_home which ambari used in 
> **-env.xml(such as oozie-env.xml), but it's less in hive.
> So hive maybe using another existing jdk, or less JAVA_HOME setting.



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

Review Request 39637: ActionScheduler#filterParallelPerHostStages should not filter out stages with server-side actions

2015-10-25 Thread Robert Levas 

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

Review request for Ambari, Jonathan Hurley, Nate Cole, Robert Nettleton, and 
Sandor Magyari.


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


Repository: ambari


Description
---

org.apache.ambari.server.actionmanager.ActionScheduler#filterParallelPerHostStages
 should not filter out stages that contain server-side actions (to be executed 
on the Ambari server host). This is because tasks in these stages are typically 
required to complete before other stages on other hosts are executed. 

For example while enabling Kerberos for an added service, principals and keytab 
files need to be created before the stage to distribute the key tab files. The 
principal and keytab file creation happens on the Ambari server (as server-side 
actions) and the distribution tasks happen on the relevant hosts. If the 
server-side stages are filtered out (in the event multiple stages are pending 
for the Ambari server host), then one or more might be skipped and the 
distribution task is queued.  In this scenario, the distribution stage will 
fail since the required keytab files will not have been created.


Diffs
-

  
ambari-server/src/main/java/org/apache/ambari/server/actionmanager/ActionScheduler.java
 3f289b2 
  ambari-server/src/main/java/org/apache/ambari/server/actionmanager/Stage.java 
8b2703c 
  
ambari-server/src/test/java/org/apache/ambari/server/actionmanager/TestActionScheduler.java
 f8f9ce9 

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


Testing
---

Manually tested in cluster... testing kerberizing and rolling upgrades.

#Jenkins test results: PENDING


Thanks,

Robert Levas

[jira] [Updated] (AMBARI-13550) ActionScheduler#filterParallelPerHostStages should not filter out stages with server-side actions

2015-10-25 Thread Robert Levas (JIRA) 

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

Robert Levas updated AMBARI-13550:
--
Attachment: AMBARI-13550_trunk_01.patch
AMBARI-13550_branch-2.1_01.patch

> ActionScheduler#filterParallelPerHostStages should not filter out stages with 
> server-side actions
> -
>
> Key: AMBARI-13550
> URL: https://issues.apache.org/jira/browse/AMBARI-13550
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.3
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Critical
>  Labels: actions, kerberos
> Fix For: 2.1.3
>
> Attachments: AMBARI-13550_branch-2.1_01.patch, 
> AMBARI-13550_trunk_01.patch
>
>
> org.apache.ambari.server.actionmanager.ActionScheduler#filterParallelPerHostStages
>  should not filter out stages that contain server-side actions (to be 
> executed on the Ambari server host). This is because tasks in these stages 
> are typically required to complete before other stages on other hosts are 
> executed. 
> For example while enabling Kerberos for an added service, principals and 
> keytab files need to be created before the stage to distribute the key tab 
> files. The principal and keytab file creation happens on the Ambari server 
> (as server-side actions) and the distribution tasks happen on the relevant 
> hosts. If the server-side stages are filtered out (in the event multiple 
> stages are pending for the Ambari server host), then one or more might be 
> skipped and the distribution task is queued.  In this scenario, the 
> distribution stage will fail since the required keytab files will not have 
> been created. 



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

[jira] [Commented] (AMBARI-11990) Deployment fails on snappy with HDP 2.3 on CentOS7

2015-10-25 Thread Rudy (JIRA) 

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

Rudy commented on AMBARI-11990:
---

The problem is still present when installing `snappy-devel`. It uses the 
version from the EL6 HDP-UTILS repo.

{code}
stderr: 
Traceback (most recent call last):
  File 
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py",
 line 153, in 
DataNode().execute()
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 219, in execute
method(env)
  File 
"/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/datanode.py",
 line 34, in install
self.install_packages(env, params.exclude_packages)
  File 
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
 line 395, in install_packages
Package(name)
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", 
line 154, in __init__
self.env.run()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 152, in run
self.run_action(resource, action)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py", 
line 118, in run_action
provider_action()
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/providers/package/__init__.py",
 line 45, in action_install
self.install_package(package_name, self.resource.use_repos, 
self.resource.skip_repos)
  File 
"/usr/lib/python2.6/site-packages/resource_management/core/providers/package/yumrpm.py",
 line 49, in install_package
shell.checked_call(cmd, sudo=True, logoutput=self.get_logoutput())
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 70, in inner
result = function(command, **kwargs)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 92, in checked_call
tries=tries, try_sleep=try_sleep)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 140, in _call_wrapper
result = _call(command, **kwargs_copy)
  File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py", 
line 291, in _call
raise Fail(err_msg)
resource_management.core.exceptions.Fail: Execution of '/usr/bin/yum -d 0 -e 0 
-y install snappy-devel' returned 1. Error: Package: 
snappy-devel-1.0.5-1.el6.x86_64 (HDP-UTILS-1.1.0.20)
   Requires: snappy(x86-64) = 1.0.5-1.el6
   Installed: snappy-1.1.0-3.el7.x86_64 (@anaconda/7.1)
   snappy(x86-64) = 1.1.0-3.el7
   Available: snappy-1.0.5-1.el6.x86_64 (HDP-UTILS-1.1.0.20)
   snappy(x86-64) = 1.0.5-1.el6
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
 stdout:
2015-10-25 16:57:11,828 - Group['spark'] {}
2015-10-25 16:57:11,829 - Group['hadoop'] {}
2015-10-25 16:57:11,829 - Group['users'] {}
2015-10-25 16:57:11,829 - User['hive'] {'gid': 'hadoop', 'groups': [u'hadoop']}
2015-10-25 16:57:11,830 - User['storm'] {'gid': 'hadoop', 'groups': [u'hadoop']}
2015-10-25 16:57:11,830 - User['zookeeper'] {'gid': 'hadoop', 'groups': 
[u'hadoop']}
2015-10-25 16:57:11,831 - User['atlas'] {'gid': 'hadoop', 'groups': [u'hadoop']}
2015-10-25 16:57:11,831 - User['ams'] {'gid': 'hadoop', 'groups': [u'hadoop']}
2015-10-25 16:57:11,831 - User['tez'] {'gid': 'hadoop', 'groups': [u'users']}
2015-10-25 16:57:11,832 - User['mahout'] {'gid': 'hadoop', 'groups': 
[u'hadoop']}
2015-10-25 16:57:11,832 - User['spark'] {'gid': 'hadoop', 'groups': [u'hadoop']}
2015-10-25 16:57:11,833 - User['ambari-qa'] {'gid': 'hadoop', 'groups': 
[u'users']}
2015-10-25 16:57:11,833 - User['hdfs'] {'gid': 'hadoop', 'groups': [u'hadoop']}
2015-10-25 16:57:11,834 - User['yarn'] {'gid': 'hadoop', 'groups': [u'hadoop']}
2015-10-25 16:57:11,834 - User['mapred'] {'gid': 'hadoop', 'groups': 
[u'hadoop']}
2015-10-25 16:57:11,835 - User['hbase'] {'gid': 'hadoop', 'groups': [u'hadoop']}
2015-10-25 16:57:11,835 - User['hcat'] {'gid': 'hadoop', 'groups': [u'hadoop']}
2015-10-25 16:57:11,836 - File['/var/lib/ambari-agent/tmp/changeUid.sh'] 
{'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
2015-10-25 16:57:11,837 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh 
ambari-qa 
/tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
 {'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}
2015-10-25 16:57:11,842 - Skipping 
Execute['/var/lib/ambari-agent/tmp/changeUid.sh ambari-qa 
/tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa']
 due to not_if
2015-10-25 16:57:11,842 - Directory['/tmp/hbase-hbase'] {'owner': 'hbase', 
'recursive': True, 'mode': 0775, 'cd_access': 'a'}
2015-10-25 16:57:11,843 - File['/var/lib/ambari-agent/tmp/changeUid.sh'] 
{'content'

Re: Review Request 39519: Create a script to change host names for a stopped cluster

2015-10-25 Thread Sumit Mohanty 

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



ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog210Test.java
 (line 257)


Why are these being ignored? There are a few Ignore tests.


- Sumit Mohanty


On Oct. 24, 2015, 9:16 p.m., Vitalyi Brodetskyi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39519/
> ---
> 
> (Updated Oct. 24, 2015, 9:16 p.m.)
> 
> 
> Review request for Ambari, Dmitro Lisnichenko, Jonathan Hurley, Myroslav 
> Papirkovskyy, and Sumit Mohanty.
> 
> 
> Bugs: AMBARI-13507
> https://issues.apache.org/jira/browse/AMBARI-13507
> 
> 
> Repository: ambari
> 
> 
> Description
> ---
> 
> At a high-level we may follow this approach:
> Ensure cluster is not kerberized
> Assume all services to be stopped (add a check to ensure that services are 
> stopped)
> We may also need to check and confirm that there are no commands pending 
> execution - or just mark them as aborted
> Update all host names in the database based on the mapping provided (e.g. 
> host1 --> master01.dev.com)
> As SQLClient cannot be assumed consider using jdbc - similar to the Upgrade 
> code
> Modify all configs to replace the hostnames as needed (not sure if plain 
> search and replace will suffice)
> Agents need to be re-configured if ambari-server hostname changes
> 
> 
> Diffs
> -
> 
>   ambari-server/sbin/ambari-server 1843cd6 
>   
> ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
>  04ab1ef 
>   
> ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java 
> 62c3b61 
>   
> ambari-server/src/main/java/org/apache/ambari/server/update/HostUpdateHelper.java
>  PRE-CREATION 
>   
> ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java
>  92cc9e6 
>   ambari-server/src/main/python/ambari-server.py 88df81a 
>   ambari-server/src/main/python/ambari_server/hostUpdate.py PRE-CREATION 
>   ambari-server/src/main/python/ambari_server/setupActions.py 6c6e7ea 
>   
> ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog210Test.java
>  482ac38 
>   
> ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog211Test.java
>  b692368 
>   
> ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog212Test.java
>  d427e1a 
>   
> ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog213Test.java
>  1a9088c 
> 
> Diff: https://reviews.apache.org/r/39519/diff/
> 
> 
> Testing
> ---
> 
> mvn clean test
> 
> 
> Thanks,
> 
> Vitalyi Brodetskyi
> 
>

[jira] [Commented] (AMBARI-12701) Stop-and-Start Upgrade: Handle Core Services

2015-10-25 Thread Hudson (JIRA) 

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

Hudson commented on AMBARI-12701:
-

FAILURE: Integrated in Ambari-branch-2.1 #744 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/744/])
AMBARI-12701. Addendum for patch. Stop-and-Start Upgrade: Handle Core 
(afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1a5cd771c59242cb635f9a6e9a52b219ef5b02d5])
* ambari-common/src/main/python/resource_management/libraries/script/script.py


> Stop-and-Start Upgrade: Handle Core Services
> 
>
> Key: AMBARI-12701
> URL: https://issues.apache.org/jira/browse/AMBARI-12701
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-server
>Affects Versions: 2.2.0, 2.1.3
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>  Labels: branch:branch-dev-stop-all-upgrade
> Fix For: 2.2.0, 2.1.3
>
> Attachments: AMBARI-12701.additional.fix.patch, 
> AMBARI-12701.branch-2.1.patch, AMBARI-12701.trunk.patch
>
>
> Stop-and-Start Upgrade of the Stack to handle core services: HDFS, YARN, MR, 
> ZK



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

[jira] [Commented] (AMBARI-12701) Stop-and-Start Upgrade: Handle Core Services

2015-10-25 Thread Hudson (JIRA) 

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

Hudson commented on AMBARI-12701:
-

FAILURE: Integrated in Ambari-trunk-Commit #3713 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/3713/])
AMBARI-12701. Addendum for patch. Stop-and-Start Upgrade: Handle Core 
(afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=16a457543208fd54329de9f4f42f445965f787a0])
* ambari-common/src/main/python/resource_management/libraries/script/script.py


> Stop-and-Start Upgrade: Handle Core Services
> 
>
> Key: AMBARI-12701
> URL: https://issues.apache.org/jira/browse/AMBARI-12701
> Project: Ambari
>  Issue Type: Story
>  Components: ambari-server
>Affects Versions: 2.2.0, 2.1.3
>Reporter: Alejandro Fernandez
>Assignee: Alejandro Fernandez
>  Labels: branch:branch-dev-stop-all-upgrade
> Fix For: 2.2.0, 2.1.3
>
> Attachments: AMBARI-12701.additional.fix.patch, 
> AMBARI-12701.branch-2.1.patch, AMBARI-12701.trunk.patch
>
>
> Stop-and-Start Upgrade of the Stack to handle core services: HDFS, YARN, MR, 
> ZK



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

[jira] [Commented] (AMBARI-13557) Add Admin, usersync and Audit tab in Ranger theme for Ranger 0.4.0 (HDP-2.2 stack)

2015-10-25 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on AMBARI-13557:


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

This message is automatically generated.

> Add Admin, usersync and Audit tab in Ranger theme for Ranger 0.4.0 (HDP-2.2 
> stack)
> --
>
> Key: AMBARI-13557
> URL: https://issues.apache.org/jira/browse/AMBARI-13557
> Project: Ambari
>  Issue Type: Task
>  Components: ambari-server, ambari-web
>Affects Versions: 2.1.3
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
> Fix For: 2.1.3
>
> Attachments: AMBARI-13557.patch
>
>
> Add Admin, usersync and Audit tab in Ranger theme for Ranger 0.4.0 (HDP-2.2 
> stack)
> Make stack advsior changes to set service related ranger properties in 
> HDP-2.2 stacks automatically
> Patch also resolves a bug where JDBC URL value for Oracle database had 
> missing '/'



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

[jira] [Commented] (AMBARI-11679) Ambari view - Create a wrapper view that wraps around any url accessible from the browser.

2015-10-25 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on AMBARI-11679:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12768578/AMBARI-11679.2.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 test build failed in 
contrib/views/wrapper 

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

This message is automatically generated.

> Ambari view - Create a wrapper view that wraps around any url accessible from 
> the browser.
> --
>
> Key: AMBARI-11679
> URL: https://issues.apache.org/jira/browse/AMBARI-11679
> Project: Ambari
>  Issue Type: Task
>Reporter: Sreenath Somarajapuram
>Assignee: Sreenath Somarajapuram
>Priority: Minor
> Attachments: AMBARI-11679.1.patch, AMBARI-11679.2.patch
>
>
> We already have something similar https://github.com/abajwa-hw/iframe-view.
> But the intention here is to create a view who's target can be configured 
> from the UI.



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