[jira] [Comment Edited] (AMBARI-22580) Streaming Analytics Manager (SAM) not working with PostgreSQL
[
https://issues.apache.org/jira/browse/AMBARI-22580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16365172#comment-16365172
]
Sindhu Subhas edited comment on AMBARI-22580 at 2/15/18 6:27 AM:
-
Fix for this is to add below snippet under
/var/lib/ambari-server/resources/common-services/STREAMLINE/0.5.0/package/scripts/params.py:
{code:java}
Line 209: Logger.info("sudo ambari-server setup --jdbc-db=oracle
--jdbc-driver=/usr/share/java/ojdbc.jar")
Line 211:
if 'postgres' == streamline_storage_type:
jdbc_driver_jar = default("/hostLevelParams/custom_postgres_jdbc_name", None)
if jdbc_driver_jar == None:
Logger.error("Failed to find postgres jar. Make sure you followed the steps to
register mysql driver")
Logger.info("Users should register the mysql java driver jar.")
Logger.info("Create a symlink e.g. ln -s /usr/share/java/postgres94-jdbc.jar
/usr/share/java/postgres-jdbc.jar")
Logger.info("sudo ambari-server setup --jdbc-db=postgres
--jdbc-driver=/usr/share/java/postgresql-jdbc.jar")
{code}
Also, attached sample params.py.
was (Author: ssubhas):
Fix for this is to add below snippet under
/var/lib/ambari-server/resources/common-services/STREAMLINE/0.5.0/package/scripts/params.py:
{code:java}
Line 209: Logger.info("sudo ambari-server setup --jdbc-db=oracle
--jdbc-driver=/usr/share/java/ojdbc.jar")
Line 210:
if 'postgres' == streamline_storage_type:
jdbc_driver_jar = default("/hostLevelParams/custom_postgres_jdbc_name", None)
if jdbc_driver_jar == None:
Logger.error("Failed to find postgres jar. Make sure you followed the steps to
register mysql driver")
Logger.info("Users should register the mysql java driver jar.")
Logger.info("Create a symlink e.g. ln -s /usr/share/java/postgres94-jdbc.jar
/usr/share/java/postgres-jdbc.jar")
Logger.info("sudo ambari-server setup --jdbc-db=postgres
--jdbc-driver=/usr/share/java/postgresql-jdbc.jar")
{code}
Also, attached sample params.py.
> Streaming Analytics Manager (SAM) not working with PostgreSQL
> -
>
> Key: AMBARI-22580
> URL: https://issues.apache.org/jira/browse/AMBARI-22580
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Unai P. Mendizabal
>Priority: Major
>
> Hi!
> I was trying to install SAM on my Ambari cluster and trying to use the same
> PostgreSQL database I use for Ambari server. The installation fails though,
> with error "KeyError: 'jdbc_driver_jar" coming from the params.py file of the
> Streamline service. I dived into it and realized that variable
> 'jdbc_driver_jar' is never initialized for PostgreSQL databases, while it
> does when it comes to Oracle or MySQL.
> The file is
> /var/lib/ambari-server/resources/common-services/STREAMLINE/0.5.0/package/scripts/params.py,
> you can see the problem from line 192 on. As a workaround, I think it should
> be possible to manually set 'jdbc_driver_jar' to the path to the jdbc driver
> on that same file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (AMBARI-22580) Streaming Analytics Manager (SAM) not working with PostgreSQL
[
https://issues.apache.org/jira/browse/AMBARI-22580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16365172#comment-16365172
]
Sindhu Subhas edited comment on AMBARI-22580 at 2/15/18 6:27 AM:
-
Fix for this is to add below snippet under
/var/lib/ambari-server/resources/common-services/STREAMLINE/0.5.0/package/scripts/params.py:
{code:java}
Line 209: Logger.info("sudo ambari-server setup --jdbc-db=oracle
--jdbc-driver=/usr/share/java/ojdbc.jar")
Line 211:
if 'postgres' == streamline_storage_type:
jdbc_driver_jar = default("/hostLevelParams/custom_postgres_jdbc_name", None)
if jdbc_driver_jar == None:
Logger.error("Failed to find postgres jar. Make sure you followed the steps to
register mysql driver")
Logger.info("Users should register the mysql java driver jar.")
Logger.info("Create a symlink e.g. ln -s /usr/share/java/postgres94-jdbc.jar
/usr/share/java/postgres-jdbc.jar")
Logger.info("sudo ambari-server setup --jdbc-db=postgres
--jdbc-driver=/usr/share/java/postgresql-jdbc.jar")
{code}
was (Author: ssubhas):
Fix for this is to add below snippet under
/var/lib/ambari-server/resources/common-services/STREAMLINE/0.5.0/package/scripts/params.py:
{code:java}
Line 209: Logger.info("sudo ambari-server setup --jdbc-db=oracle
--jdbc-driver=/usr/share/java/ojdbc.jar")
Line 211:
if 'postgres' == streamline_storage_type:
jdbc_driver_jar = default("/hostLevelParams/custom_postgres_jdbc_name", None)
if jdbc_driver_jar == None:
Logger.error("Failed to find postgres jar. Make sure you followed the steps to
register mysql driver")
Logger.info("Users should register the mysql java driver jar.")
Logger.info("Create a symlink e.g. ln -s /usr/share/java/postgres94-jdbc.jar
/usr/share/java/postgres-jdbc.jar")
Logger.info("sudo ambari-server setup --jdbc-db=postgres
--jdbc-driver=/usr/share/java/postgresql-jdbc.jar")
{code}
Also, attached sample params.py.
> Streaming Analytics Manager (SAM) not working with PostgreSQL
> -
>
> Key: AMBARI-22580
> URL: https://issues.apache.org/jira/browse/AMBARI-22580
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Unai P. Mendizabal
>Priority: Major
>
> Hi!
> I was trying to install SAM on my Ambari cluster and trying to use the same
> PostgreSQL database I use for Ambari server. The installation fails though,
> with error "KeyError: 'jdbc_driver_jar" coming from the params.py file of the
> Streamline service. I dived into it and realized that variable
> 'jdbc_driver_jar' is never initialized for PostgreSQL databases, while it
> does when it comes to Oracle or MySQL.
> The file is
> /var/lib/ambari-server/resources/common-services/STREAMLINE/0.5.0/package/scripts/params.py,
> you can see the problem from line 192 on. As a workaround, I think it should
> be possible to manually set 'jdbc_driver_jar' to the path to the jdbc driver
> on that same file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (AMBARI-22580) Streaming Analytics Manager (SAM) not working with PostgreSQL
[
https://issues.apache.org/jira/browse/AMBARI-22580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16365172#comment-16365172
]
Sindhu Subhas edited comment on AMBARI-22580 at 2/15/18 6:27 AM:
-
Fix for this is to add below snippet under
/var/lib/ambari-server/resources/common-services/STREAMLINE/0.5.0/package/scripts/params.py:
{code:java}
Line 209: Logger.info("sudo ambari-server setup --jdbc-db=oracle
--jdbc-driver=/usr/share/java/ojdbc.jar")
Line 210:
if 'postgres' == streamline_storage_type:
jdbc_driver_jar = default("/hostLevelParams/custom_postgres_jdbc_name", None)
if jdbc_driver_jar == None:
Logger.error("Failed to find postgres jar. Make sure you followed the steps to
register mysql driver")
Logger.info("Users should register the mysql java driver jar.")
Logger.info("Create a symlink e.g. ln -s /usr/share/java/postgres94-jdbc.jar
/usr/share/java/postgres-jdbc.jar")
Logger.info("sudo ambari-server setup --jdbc-db=postgres
--jdbc-driver=/usr/share/java/postgresql-jdbc.jar")
{code}
Also, attached sample params.py.
was (Author: ssubhas):
Fix for this is to add below snippet under
/var/lib/ambari-server/resources/common-services/STREAMLINE/0.5.0/package/scripts/params.py:
{code:java}
if 'postgres' == streamline_storage_type:
jdbc_driver_jar = default("/hostLevelParams/custom_postgres_jdbc_name", None)
if jdbc_driver_jar == None:
Logger.error("Failed to find postgres jar. Make sure you followed the steps to
register mysql driver")
Logger.info("Users should register the mysql java driver jar.")
Logger.info("Create a symlink e.g. ln -s /usr/share/java/postgres94-jdbc.jar
/usr/share/java/postgres-jdbc.jar")
Logger.info("sudo ambari-server setup --jdbc-db=postgres
--jdbc-driver=/usr/share/java/postgresql-jdbc.jar")
{code}
Also, attached sample params.py.
> Streaming Analytics Manager (SAM) not working with PostgreSQL
> -
>
> Key: AMBARI-22580
> URL: https://issues.apache.org/jira/browse/AMBARI-22580
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Unai P. Mendizabal
>Priority: Major
>
> Hi!
> I was trying to install SAM on my Ambari cluster and trying to use the same
> PostgreSQL database I use for Ambari server. The installation fails though,
> with error "KeyError: 'jdbc_driver_jar" coming from the params.py file of the
> Streamline service. I dived into it and realized that variable
> 'jdbc_driver_jar' is never initialized for PostgreSQL databases, while it
> does when it comes to Oracle or MySQL.
> The file is
> /var/lib/ambari-server/resources/common-services/STREAMLINE/0.5.0/package/scripts/params.py,
> you can see the problem from line 192 on. As a workaround, I think it should
> be possible to manually set 'jdbc_driver_jar' to the path to the jdbc driver
> on that same file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22580) Streaming Analytics Manager (SAM) not working with PostgreSQL
[
https://issues.apache.org/jira/browse/AMBARI-22580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16365172#comment-16365172
]
Sindhu Subhas commented on AMBARI-22580:
Fix for this is to add below snippet under
/var/lib/ambari-server/resources/common-services/STREAMLINE/0.5.0/package/scripts/params.py:
{code:java}
if 'postgres' == streamline_storage_type:
jdbc_driver_jar = default("/hostLevelParams/custom_postgres_jdbc_name", None)
if jdbc_driver_jar == None:
Logger.error("Failed to find postgres jar. Make sure you followed the steps to
register mysql driver")
Logger.info("Users should register the mysql java driver jar.")
Logger.info("Create a symlink e.g. ln -s /usr/share/java/postgres94-jdbc.jar
/usr/share/java/postgres-jdbc.jar")
Logger.info("sudo ambari-server setup --jdbc-db=postgres
--jdbc-driver=/usr/share/java/postgresql-jdbc.jar")
{code}
Also, attached sample params.py.
> Streaming Analytics Manager (SAM) not working with PostgreSQL
> -
>
> Key: AMBARI-22580
> URL: https://issues.apache.org/jira/browse/AMBARI-22580
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Unai P. Mendizabal
>Priority: Major
>
> Hi!
> I was trying to install SAM on my Ambari cluster and trying to use the same
> PostgreSQL database I use for Ambari server. The installation fails though,
> with error "KeyError: 'jdbc_driver_jar" coming from the params.py file of the
> Streamline service. I dived into it and realized that variable
> 'jdbc_driver_jar' is never initialized for PostgreSQL databases, while it
> does when it comes to Oracle or MySQL.
> The file is
> /var/lib/ambari-server/resources/common-services/STREAMLINE/0.5.0/package/scripts/params.py,
> you can see the problem from line 192 on. As a workaround, I think it should
> be possible to manually set 'jdbc_driver_jar' to the path to the jdbc driver
> on that same file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22987) Fix Ambari doc site to fix errors from https://whimsy.apache.org/site/project/ambari
[ https://issues.apache.org/jira/browse/AMBARI-22987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16365169#comment-16365169 ] Hudson commented on AMBARI-22987: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8734 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8734/]) AMBARI-22987: fix errors found in sitecheck - (jonathanhurley: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=d07395a246d56153df44876dcc2cc2110e43297e]) * (edit) docs/src/site/site.xml > Fix Ambari doc site to fix errors from > https://whimsy.apache.org/site/project/ambari > > > Key: AMBARI-22987 > URL: https://issues.apache.org/jira/browse/AMBARI-22987 > Project: Ambari > Issue Type: Bug > Components: site >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > Labels: pull-request-available > Attachments: > 0001-AMBARI-22987-fixes-to-errors-shown-from-whimsy.apach.patch > > Time Spent: 20m > Remaining Estimate: 0h > > Fix errors shown in https://whimsy.apache.org/site/project/ambari -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AMBARI-22407) MaxFileSize does not work with DailyRollingFileAppender
[
https://issues.apache.org/jira/browse/AMBARI-22407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Masahiro Tanaka reassigned AMBARI-22407:
Assignee: Masahiro Tanaka
> MaxFileSize does not work with DailyRollingFileAppender
> ---
>
> Key: AMBARI-22407
> URL: https://issues.apache.org/jira/browse/AMBARI-22407
> Project: Ambari
> Issue Type: Bug
> Environment: Ambari 2.6.0
>Reporter: Masahiro Tanaka
>Assignee: Masahiro Tanaka
>Priority: Minor
>
> Apache Ranger uses DailyRollingFileAppender which doesn't use maxfilesize
> property.
> AMBARI-21889 fixed a part of this issue, but if we contain maxFileSize
> property, it shows a warning message like below
> {code}
> log4j:WARN No such property [maxFileSize] in
> org.apache.log4j.DailyRollingFileAppender.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22998) Wrong user used to execute the Spark/Livy Server service check
[
https://issues.apache.org/jira/browse/AMBARI-22998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22998:
--
Status: Patch Available (was: In Progress)
> Wrong user used to execute the Spark/Livy Server service check
> --
>
> Key: AMBARI-22998
> URL: https://issues.apache.org/jira/browse/AMBARI-22998
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.6.2, 2.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {code:title=common-services/SPARK/1.2.1/package/scripts/service_check.py:36}
> livy_kinit_cmd = format("{kinit_path_local} -kt {smoke_user_keytab}
> {smokeuser_principal}; ")
> Execute(livy_kinit_cmd, user=params.livy_user)
> {code}
> Notice the Kerberos identity is for the smoke user, but the exec is for the
> livy user. This will replace the livy user's interactive Kerberos ticket
> cache.
> This should be
> {code}
> smoke_user_kinit_cmd = format("{kinit_path_local} -kt {smoke_user_keytab}
> {smokeuser_principal}; ")
> Execute(smoke_user_kinit_cmd, user=params.smoke_user)
> {code}
> Where {{smoke_user}} is
> {code}
> smoke_user = config['configurations']['cluster-env']['smokeuser']
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22998) Wrong user used to execute the Spark/Livy Server service check
[
https://issues.apache.org/jira/browse/AMBARI-22998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-22998:
Labels: pull-request-available (was: )
> Wrong user used to execute the Spark/Livy Server service check
> --
>
> Key: AMBARI-22998
> URL: https://issues.apache.org/jira/browse/AMBARI-22998
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.6.2, 2.7.0
>
>
> {code:title=common-services/SPARK/1.2.1/package/scripts/service_check.py:36}
> livy_kinit_cmd = format("{kinit_path_local} -kt {smoke_user_keytab}
> {smokeuser_principal}; ")
> Execute(livy_kinit_cmd, user=params.livy_user)
> {code}
> Notice the Kerberos identity is for the smoke user, but the exec is for the
> livy user. This will replace the livy user's interactive Kerberos ticket
> cache.
> This should be
> {code}
> smoke_user_kinit_cmd = format("{kinit_path_local} -kt {smoke_user_keytab}
> {smokeuser_principal}; ")
> Execute(smoke_user_kinit_cmd, user=params.smoke_user)
> {code}
> Where {{smoke_user}} is
> {code}
> smoke_user = config['configurations']['cluster-env']['smokeuser']
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22998) Wrong user used to execute the Spark/Livy Server service check
[
https://issues.apache.org/jira/browse/AMBARI-22998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22998:
--
Summary: Wrong user used to execute the Spark/Livy Server service check
(was: Wrong user us used to execute the Spark/Livy Server service check)
> Wrong user used to execute the Spark/Livy Server service check
> --
>
> Key: AMBARI-22998
> URL: https://issues.apache.org/jira/browse/AMBARI-22998
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Fix For: 2.6.2, 2.7.0
>
>
> {code:title=common-services/SPARK/1.2.1/package/scripts/service_check.py:36}
> livy_kinit_cmd = format("{kinit_path_local} -kt {smoke_user_keytab}
> {smokeuser_principal}; ")
> Execute(livy_kinit_cmd, user=params.livy_user)
> {code}
> Notice the Kerberos identity is for the smoke user, but the exec is for the
> livy user. This will replace the livy user's interactive Kerberos ticket
> cache.
> This should be
> {code}
> smoke_user_kinit_cmd = format("{kinit_path_local} -kt {smoke_user_keytab}
> {smokeuser_principal}; ")
> Execute(smoke_user_kinit_cmd, user=params.smoke_user)
> {code}
> Where {{smoke_user}} is
> {code}
> smoke_user = config['configurations']['cluster-env']['smokeuser']
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22918) Decommission RegionServer fails when kerberos is enabled
[
https://issues.apache.org/jira/browse/AMBARI-22918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16365089#comment-16365089
]
Toshihiro Suzuki commented on AMBARI-22918:
---
[~rlevas] I just sent PRs for trunk and branch-2.6 to fix the unit test failure.
> Decommission RegionServer fails when kerberos is enabled
>
>
> Key: AMBARI-22918
> URL: https://issues.apache.org/jira/browse/AMBARI-22918
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Toshihiro Suzuki
>Priority: Major
> Labels: pull-request-available
> Time Spent: 3h
> Remaining Estimate: 0h
>
> When kerberos is enabled, Decommission RegionServer fails with the following
> errors:
> stderr:
> {code:java}
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_master.py",
> line 114, in
> HbaseMaster().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 329, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_master.py",
> line 55, in decommission
> hbase_decommission(env)
> File "/usr/lib/python2.6/site-packages/ambari_commons/os_family_impl.py",
> line 89, in thunk
> return fn(*args, **kwargs)
> File
> "/var/lib/ambari-agent/cache/common-services/HBASE/0.96.0.2.0/package/scripts/hbase_decommission.py",
> line 84, in hbase_decommission
> logoutput=True
> File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
> line 166, in __init__
> self.env.run()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 160, in run
> self.run_action(resource, action)
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
> line 124, in run_action
> provider_action()
> File
> "/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
> line 262, in action_run
> tries=self.resource.tries, try_sleep=self.resource.try_sleep)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 72, in inner
> result = function(command, **kwargs)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 102, in checked_call
> tries=tries, try_sleep=try_sleep,
> timeout_kill_strategy=timeout_kill_strategy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 150, in _call_wrapper
> result = _call(command, **kwargs_copy)
> File "/usr/lib/python2.6/site-packages/resource_management/core/shell.py",
> line 303, in _call
> raise ExecutionFailed(err_msg, code, out, err)
> resource_management.core.exceptions.ExecutionFailed: Execution of
> '/usr/bin/kinit -kt /etc/security/keytabs/hbase.service.keytab
> hbase/mast...@example.com; /usr/hdp/current/hbase-master/bin/hbase --config
> /usr/hdp/current/hbase-master/conf
> -Djava.security.auth.login.config=/usr/hdp/current/hbase-master/conf/hbase_master_jaas.conf
> org.jruby.Main /usr/hdp/current/hbase-master/bin/draining_servers.rb add
> worker1' returned 1. Error: Could not find or load main class
> org.jruby.Main{code}
> stdout:
> {code:java}
> 2018-02-06 07:25:03,453 - Stack Feature Version Info: Cluster Stack=2.6,
> Cluster Current Version=2.6.2.0-205, Command Stack=None, Command
> Version=2.6.2.0-205 -> 2.6.2.0-205
> 2018-02-06 07:25:03,476 - Using hadoop conf dir:
> /usr/hdp/current/hadoop-client/conf
> 2018-02-06 07:25:03,484 - checked_call['hostid'] {}
> 2018-02-06 07:25:03,490 - checked_call returned (0, '1aacc56c')
> 2018-02-06 07:25:03,502 -
> File['/usr/hdp/current/hbase-master/bin/draining_servers.rb'] {'content':
> StaticFile('draining_servers.rb'), 'mode': 0755}
> 2018-02-06 07:25:03,504 - Execute['/usr/bin/kinit -kt
> /etc/security/keytabs/hbase.service.keytab hbase/mast...@example.com;
> /usr/hdp/current/hbase-master/bin/hbase --config
> /usr/hdp/current/hbase-master/conf
> -Djava.security.auth.login.config=/usr/hdp/current/hbase-master/conf/hbase_master_jaas.conf
> org.jruby.Main /usr/hdp/current/hbase-master/bin/draining_servers.rb add
> worker1'] {'logoutput': True, 'user': 'hbase'}
> Error: Could not find or load main class org.jruby.Main
> Command failed after 1 tries{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22999) Ambari Hive View 2.0 'Upload Table' does not support UTF8 files with BOM
[ https://issues.apache.org/jira/browse/AMBARI-22999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hajime Osako updated AMBARI-22999: -- Description: Creating this Jira to request same fix as AMBARI-18583 for Ambari Hive 2.0 View. was: Creating this Jira to request same fix as AMBARI-18583 is required for Ambari Hive 2.0 View. > Ambari Hive View 2.0 'Upload Table' does not support UTF8 files with BOM > > > Key: AMBARI-22999 > URL: https://issues.apache.org/jira/browse/AMBARI-22999 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.0 >Reporter: Hajime Osako >Priority: Major > > Creating this Jira to request same fix as AMBARI-18583 for Ambari Hive 2.0 > View. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22999) Ambari Hive View 2.0 'Upload Table' does not support UTF8 files with BOM
Hajime Osako created AMBARI-22999: - Summary: Ambari Hive View 2.0 'Upload Table' does not support UTF8 files with BOM Key: AMBARI-22999 URL: https://issues.apache.org/jira/browse/AMBARI-22999 Project: Ambari Issue Type: Bug Components: ambari-views Affects Versions: 2.5.0 Reporter: Hajime Osako Creating this Jira to request same fix as AMBARI-18583 is required for Ambari Hive 2.0 View. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22918) Decommission RegionServer fails when kerberos is enabled
[
https://issues.apache.org/jira/browse/AMBARI-22918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16365022#comment-16365022
]
Robert Levas commented on AMBARI-22918:
---
[~brfrn169], This is likely causing python unit test failures in trunk and
branch-2.6. If so, please fix...
{noformat}
--
Failed tests:
FAIL: test_decom_default (test_hbase_master.TestHBaseMaster)
--
Traceback (most recent call last):
File
"/Users/rlevas/github/ambari/ambari-common/src/test/python/mock/mock.py", line
1199, in patched
return func(*args, **keywargs)
File
"/Users/rlevas/github/ambari/ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_master.py",
line 190, in test_decom_default
user = 'hbase',
File
"/Users/rlevas/github/ambari/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
line 344, in assertResourceCalled
self.assertEquals(name, resource.name)
AssertionError: ' /usr/lib/hbase/bin/hbase --config /etc/hbase/conf
org.jruby.Main /usr/lib/hbase/bin/draining_servers.rb add host1' != u'
HBASE_OPTS="$HBASE_OPTS " /usr/lib/hbase/bin/hbase --config /etc/hbase/conf
org.jruby.Main /usr/lib/hbase/bin/draining_servers.rb add host1'
FAIL: test_decom_default_draining_only (test_hbase_master.TestHBaseMaster)
--
Traceback (most recent call last):
File
"/Users/rlevas/github/ambari/ambari-common/src/test/python/mock/mock.py", line
1199, in patched
return func(*args, **keywargs)
File
"/Users/rlevas/github/ambari/ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_master.py",
line 221, in test_decom_default_draining_only
user = 'hbase',
File
"/Users/rlevas/github/ambari/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
line 344, in assertResourceCalled
self.assertEquals(name, resource.name)
AssertionError: ' /usr/lib/hbase/bin/hbase --config /etc/hbase/conf
org.jruby.Main /usr/lib/hbase/bin/draining_servers.rb remove host1' != u'
HBASE_OPTS="$HBASE_OPTS " /usr/lib/hbase/bin/hbase --config /etc/hbase/conf
org.jruby.Main /usr/lib/hbase/bin/draining_servers.rb remove host1'
FAIL: test_decom_secure (test_hbase_master.TestHBaseMaster)
--
Traceback (most recent call last):
File
"/Users/rlevas/github/ambari/ambari-common/src/test/python/mock/mock.py", line
1199, in patched
return func(*args, **keywargs)
File
"/Users/rlevas/github/ambari/ambari-server/src/test/python/stacks/2.0.6/HBASE/test_hbase_master.py",
line 289, in test_decom_secure
user = 'hbase',
File
"/Users/rlevas/github/ambari/ambari-server/src/test/python/stacks/utils/RMFTestCase.py",
line 344, in assertResourceCalled
self.assertEquals(name, resource.name)
AssertionError: '/usr/bin/kinit -kt /etc/security/keytabs/hbase.service.keytab
hbase/c6401.ambari.apache@example.com; /usr/lib/hbase/bin/hbase --config
/etc/hbase/conf
-Djava.security.auth.login.config=/etc/hbase/conf/hbase_master_jaas.conf
org.jruby.Main /usr/lib/hbase/bin/draining_servers.rb add host1' !=
u'/usr/bin/kinit -kt /etc/security/keytabs/hbase.service.keytab
hbase/c6401.ambari.apache@example.com; HBASE_OPTS="$HBASE_OPTS
-Djava.security.auth.login.config=/etc/hbase/conf/hbase_master_jaas.conf"
/usr/lib/hbase/bin/hbase --config /etc/hbase/conf org.jruby.Main
/usr/lib/hbase/bin/draining_servers.rb add host1'
FAIL: test_performance (test_stack_advisor_perf.TestStackAdvisorPerformance)
--
Traceback (most recent call last):
File
"/Users/rlevas/github/ambari/ambari-common/src/test/python/mock/mock.py", line
1199, in patched
return func(*args, **keywargs)
File
"/Users/rlevas/github/ambari/ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor_perf.py",
line 77, in test_performance
self.assertTrue(time_taken < TestStackAdvisorPerformance.TIME_ALLOWED) #
Python 2.7: assertLess
AssertionError: False is not true
--
Total run:1046
Total errors:0
Total failures:4
{noformat}
> Decommission RegionServer fails when kerberos is enabled
>
>
> Key: AMBARI-22918
> URL: https://issues.apache.org/jira/browse/AMBARI-22918
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Reporter: Toshihiro Suzuki
>Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> When kerberos is enabled, Decommission RegionServer fails with the following
> errors:
> stderr:
> {code:java}
> Traceback (most recent call
[jira] [Created] (AMBARI-22998) Wrong user us used to execute the Spark/Livy Server service check
Robert Levas created AMBARI-22998:
-
Summary: Wrong user us used to execute the Spark/Livy Server
service check
Key: AMBARI-22998
URL: https://issues.apache.org/jira/browse/AMBARI-22998
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.6.0
Reporter: Robert Levas
Assignee: Robert Levas
Fix For: 2.6.2, 2.7.0
{code:title=common-services/SPARK/1.2.1/package/scripts/service_check.py:36}
livy_kinit_cmd = format("{kinit_path_local} -kt {smoke_user_keytab}
{smokeuser_principal}; ")
Execute(livy_kinit_cmd, user=params.livy_user)
{code}
Notice the Kerberos identity is for the smoke user, but the exec is for the
livy user. This will replace the livy user's interactive Kerberos ticket cache.
This should be
{code}
smoke_user_kinit_cmd = format("{kinit_path_local} -kt {smoke_user_keytab}
{smokeuser_principal}; ")
Execute(smoke_user_kinit_cmd, user=params.smoke_user)
{code}
Where {{smoke_user}} is
{code}
smoke_user = config['configurations']['cluster-env']['smokeuser']
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22998) Wrong user us used to execute the Spark/Livy Server service check
[
https://issues.apache.org/jira/browse/AMBARI-22998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22998:
--
Description:
{code:title=common-services/SPARK/1.2.1/package/scripts/service_check.py:36}
livy_kinit_cmd = format("{kinit_path_local} -kt {smoke_user_keytab}
{smokeuser_principal}; ")
Execute(livy_kinit_cmd, user=params.livy_user)
{code}
Notice the Kerberos identity is for the smoke user, but the exec is for the
livy user. This will replace the livy user's interactive Kerberos ticket cache.
This should be
{code}
smoke_user_kinit_cmd = format("{kinit_path_local} -kt {smoke_user_keytab}
{smokeuser_principal}; ")
Execute(smoke_user_kinit_cmd, user=params.smoke_user)
{code}
Where {{smoke_user}} is
{code}
smoke_user = config['configurations']['cluster-env']['smokeuser']
{code}
was:
{code:title=common-services/SPARK/1.2.1/package/scripts/service_check.py:36}
livy_kinit_cmd = format("{kinit_path_local} -kt {smoke_user_keytab}
{smokeuser_principal}; ")
Execute(livy_kinit_cmd, user=params.livy_user)
{code}
Notice the Kerberos identity is for the smoke user, but the exec is for the
livy user. This will replace the livy user's interactive Kerberos ticket cache.
This should be
{code}
smoke_user_kinit_cmd = format("{kinit_path_local} -kt {smoke_user_keytab}
{smokeuser_principal}; ")
Execute(smoke_user_kinit_cmd, user=params.smoke_user)
{code}
Where {{smoke_user}} is
{code}
smoke_user = config['configurations']['cluster-env']['smokeuser']
{code}
> Wrong user us used to execute the Spark/Livy Server service check
> -
>
> Key: AMBARI-22998
> URL: https://issues.apache.org/jira/browse/AMBARI-22998
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.0
>Reporter: Robert Levas
>Assignee: Robert Levas
>Priority: Major
> Fix For: 2.6.2, 2.7.0
>
>
> {code:title=common-services/SPARK/1.2.1/package/scripts/service_check.py:36}
> livy_kinit_cmd = format("{kinit_path_local} -kt {smoke_user_keytab}
> {smokeuser_principal}; ")
> Execute(livy_kinit_cmd, user=params.livy_user)
> {code}
> Notice the Kerberos identity is for the smoke user, but the exec is for the
> livy user. This will replace the livy user's interactive Kerberos ticket
> cache.
> This should be
> {code}
> smoke_user_kinit_cmd = format("{kinit_path_local} -kt {smoke_user_keytab}
> {smokeuser_principal}; ")
> Execute(smoke_user_kinit_cmd, user=params.smoke_user)
> {code}
> Where {{smoke_user}} is
> {code}
> smoke_user = config['configurations']['cluster-env']['smokeuser']
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22837) AmbariAuthorizationFilterTest.testDoFilter_userNoPermissionsAccess fails unexpectedly
[ https://issues.apache.org/jira/browse/AMBARI-22837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16364991#comment-16364991 ] Hudson commented on AMBARI-22837: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8733 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8733/]) AMBARI-22837. Remove mocked SecurityContext in (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=91462df2291e0cb5a1b66d006b9101307e9c]) * (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationFilterTest.java > AmbariAuthorizationFilterTest.testDoFilter_userNoPermissionsAccess fails > unexpectedly > - > > Key: AMBARI-22837 > URL: https://issues.apache.org/jira/browse/AMBARI-22837 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk > Environment: Ubuntu, 16.04 LTS >Reporter: Wing Lam >Priority: Minor > Labels: pull-request-available > Fix For: trunk > > Time Spent: 1h > Remaining Estimate: 0h > > This test requires that the security context not be set up when it runs to > pass. If a test that sets up the security context improperly is run before > this test, it will fail despite there being no changes in the code. > > This can be fixed by clearing the security context, as shown in the pull > request. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22997) cluster-settings.xml is not present in /var/lib/ambari-server/resources post ambari installation
Madhuvanthi Radhakrishnan created AMBARI-22997: -- Summary: cluster-settings.xml is not present in /var/lib/ambari-server/resources post ambari installation Key: AMBARI-22997 URL: https://issues.apache.org/jira/browse/AMBARI-22997 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Madhuvanthi Radhakrishnan Assignee: Madhuvanthi Radhakrishnan Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22996) ViewInstanceResourceProviderTest, ViewPermissionResourceProviderTest, and ViewURLResourceProviderTest fail unexpectedly
[ https://issues.apache.org/jira/browse/AMBARI-22996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22996: Labels: pull-request-available (was: ) > ViewInstanceResourceProviderTest, ViewPermissionResourceProviderTest, and > ViewURLResourceProviderTest fail unexpectedly > > > Key: AMBARI-22996 > URL: https://issues.apache.org/jira/browse/AMBARI-22996 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk > Environment: Ubuntu, 16.04 LTS >Reporter: Wing Lam >Priority: Minor > Labels: pull-request-available > Fix For: trunk > > > The tests in ViewInstanceResourceProviderTest, > ViewPermissionResourceProviderTest, and ViewURLResourceProviderTest rely on a > ViewRegistry that is set up in a static initializer block. However, if the > another test sets the ViewRegistry after the class is initialized, then the > test class will use the wrong ViewRegistry and fail, despite there being no > changes in code. This can be fixed by setting the ViewRegistry in the @Before > method in each of the three test classes as shown in the pull request. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22996) ViewInstanceResourceProviderTest, ViewPermissionResourceProviderTest, and ViewURLResourceProviderTest fail unexpectedly
Wing Lam created AMBARI-22996: - Summary: ViewInstanceResourceProviderTest, ViewPermissionResourceProviderTest, and ViewURLResourceProviderTest fail unexpectedly Key: AMBARI-22996 URL: https://issues.apache.org/jira/browse/AMBARI-22996 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: trunk Environment: Ubuntu, 16.04 LTS Reporter: Wing Lam Fix For: trunk The tests in ViewInstanceResourceProviderTest, ViewPermissionResourceProviderTest, and ViewURLResourceProviderTest rely on a ViewRegistry that is set up in a static initializer block. However, if the another test sets the ViewRegistry after the class is initialized, then the test class will use the wrong ViewRegistry and fail, despite there being no changes in code. This can be fixed by setting the ViewRegistry in the @Before method in each of the three test classes as shown in the pull request. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22988) master-key option is missing from ambari-server setup action
[
https://issues.apache.org/jira/browse/AMBARI-22988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16364882#comment-16364882
]
Hudson commented on AMBARI-22988:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8731 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8731/])
AMBARI-22988. master-key option is missing from ambari-server setup (rlevas:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=619ecf6a6ab197eafcc985b3ec7d808623594442])
* (edit) ambari-server/src/main/python/ambari-server.py
> master-key option is missing from ambari-server setup action
>
>
> Key: AMBARI-22988
> URL: https://issues.apache.org/jira/browse/AMBARI-22988
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Kishor Ramakrishnan
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{ambari-server setup --enable-lzo-under-gpl-license}} failing with
> {{Unexpected AttibuteError}}
> {noformat}
> # ambari-server setup --enable-lzo-under-gpl-license -s
> Using python /usr/bin/python
> Setup ambari-server
> Checking SELinux...
> SELinux status is 'disabled'
> Customize user account for ambari-server daemon [y/n] (n)?
> Adjusting ambari-server permissions and ownership...
> Checking firewall status...
> Checking JDK...
> Do you want to change Oracle JDK [y/n] (n)?
> Check JDK version for Ambari Server...
> JDK version found: 8
> Minimum JDK version is 8 for Ambari. Skipping to setup different JDK for
> Ambari Server.
> Checking GPL software agreement...
> Completing setup...
> Configuring database...
> Enter advanced database configuration [y/n] (n)?
> Configuring database...
> ERROR: Unexpected AttributeError: Values instance has no attribute
> 'master_key'
> For more info run ambari-server with -v or --verbose option
> {noformat}
> *Note*: This occurs after encrypting passwords in the
> {{ambari_server.properties}} file:
> {noformat}
> # ambari-server setup-security
> Using python /usr/bin/python
> Security setup options...
> ===
> Choose one of the following options:
> [1] Enable HTTPS for Ambari server.
> [2] Encrypt passwords stored in ambari.properties file.
> [3] Setup Ambari kerberos JAAS configuration.
> [4] Setup truststore.
> [5] Import certificate to truststore.
> ===
> Enter choice, (1-5): 2
> Please provide master key for locking the credential store:
> Re-enter master key:
> Do you want to persist master key. If you choose not to persist, you need to
> provide the Master Key while starting the ambari server as an env variable
> named AMBARI_SECURITY_MASTER_KEY or the start will prompt for the master key.
> Persist [y/n] (y)? y
> Adjusting ambari-server permissions and ownership...
> Ambari Server 'setup-security' completed successfully.
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22988) master-key option is missing from ambari-server setup action
[
https://issues.apache.org/jira/browse/AMBARI-22988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22988:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> master-key option is missing from ambari-server setup action
>
>
> Key: AMBARI-22988
> URL: https://issues.apache.org/jira/browse/AMBARI-22988
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Kishor Ramakrishnan
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {{ambari-server setup --enable-lzo-under-gpl-license}} failing with
> {{Unexpected AttibuteError}}
> {noformat}
> # ambari-server setup --enable-lzo-under-gpl-license -s
> Using python /usr/bin/python
> Setup ambari-server
> Checking SELinux...
> SELinux status is 'disabled'
> Customize user account for ambari-server daemon [y/n] (n)?
> Adjusting ambari-server permissions and ownership...
> Checking firewall status...
> Checking JDK...
> Do you want to change Oracle JDK [y/n] (n)?
> Check JDK version for Ambari Server...
> JDK version found: 8
> Minimum JDK version is 8 for Ambari. Skipping to setup different JDK for
> Ambari Server.
> Checking GPL software agreement...
> Completing setup...
> Configuring database...
> Enter advanced database configuration [y/n] (n)?
> Configuring database...
> ERROR: Unexpected AttributeError: Values instance has no attribute
> 'master_key'
> For more info run ambari-server with -v or --verbose option
> {noformat}
> *Note*: This occurs after encrypting passwords in the
> {{ambari_server.properties}} file:
> {noformat}
> # ambari-server setup-security
> Using python /usr/bin/python
> Security setup options...
> ===
> Choose one of the following options:
> [1] Enable HTTPS for Ambari server.
> [2] Encrypt passwords stored in ambari.properties file.
> [3] Setup Ambari kerberos JAAS configuration.
> [4] Setup truststore.
> [5] Import certificate to truststore.
> ===
> Enter choice, (1-5): 2
> Please provide master key for locking the credential store:
> Re-enter master key:
> Do you want to persist master key. If you choose not to persist, you need to
> provide the Master Key while starting the ambari server as an env variable
> named AMBARI_SECURITY_MASTER_KEY or the start will prompt for the master key.
> Persist [y/n] (y)? y
> Adjusting ambari-server permissions and ownership...
> Ambari Server 'setup-security' completed successfully.
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22987) Fix Ambari doc site to fix errors from https://whimsy.apache.org/site/project/ambari
[ https://issues.apache.org/jira/browse/AMBARI-22987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22987: Labels: pull-request-available (was: ) > Fix Ambari doc site to fix errors from > https://whimsy.apache.org/site/project/ambari > > > Key: AMBARI-22987 > URL: https://issues.apache.org/jira/browse/AMBARI-22987 > Project: Ambari > Issue Type: Bug > Components: site >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > Labels: pull-request-available > Attachments: > 0001-AMBARI-22987-fixes-to-errors-shown-from-whimsy.apach.patch > > > Fix errors shown in https://whimsy.apache.org/site/project/ambari -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22995) Remove deprecated Upgrade Packs
[ https://issues.apache.org/jira/browse/AMBARI-22995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22995: Labels: pull-request-available (was: ) > Remove deprecated Upgrade Packs > --- > > Key: AMBARI-22995 > URL: https://issues.apache.org/jira/browse/AMBARI-22995 > Project: Ambari > Issue Type: Task > Components: ambari-server >Reporter: Nate Cole >Assignee: Nate Cole >Priority: Critical > Labels: pull-request-available > Fix For: 3.0.0 > > > The old upgrade packs and test should be removed to make way for the new > format that supports lifecycles. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22991) Grafana shows incorrect info for HBase Average Regions per RegionServer
[ https://issues.apache.org/jira/browse/AMBARI-22991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16364801#comment-16364801 ] Hudson commented on AMBARI-22991: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8730 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8730/]) AMBARI-22991 Grafana shows incorrect info for HBase Average Regions per (avijayan: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=869e4cdeeb318ca86991a95fa8ad90b42686b998]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-hbase-home.json * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/default/grafana-ams-hbase-home.json > Grafana shows incorrect info for HBase Average Regions per RegionServer > --- > > Key: AMBARI-22991 > URL: https://issues.apache.org/jira/browse/AMBARI-22991 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > Problem > These are number widgets on Grafana and is expected to show point in time > information for "Average Regions per RegionServer" > ambari-web that shows expected correct information gets the data from > "Hadoop:service=HBase,name=Master,sub=Server.averageLoad" jmx metric via > ambari-server metrics API resource. > It seems having aggregator as "avg" looks to be causing this issue. when > there are more than one HBase master than the metric value is averaged across > all masters -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22991) Grafana shows incorrect info for HBase Average Regions per RegionServer
[ https://issues.apache.org/jira/browse/AMBARI-22991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16364785#comment-16364785 ] Hudson commented on AMBARI-22991: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #610 (See [https://builds.apache.org/job/Ambari-branch-2.6/610/]) AMBARI-22991 : Grafana shows incorrect info for HBase Average Regions (avijayan: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=2ba8e9d9b2301a7e11d6873a5e38cfe368dbac61]) * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/default/grafana-ams-hbase-home.json * (edit) ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/files/grafana-dashboards/HDP/grafana-hbase-home.json > Grafana shows incorrect info for HBase Average Regions per RegionServer > --- > > Key: AMBARI-22991 > URL: https://issues.apache.org/jira/browse/AMBARI-22991 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > Problem > These are number widgets on Grafana and is expected to show point in time > information for "Average Regions per RegionServer" > ambari-web that shows expected correct information gets the data from > "Hadoop:service=HBase,name=Master,sub=Server.averageLoad" jmx metric via > ambari-server metrics API resource. > It seems having aggregator as "avg" looks to be causing this issue. when > there are more than one HBase master than the metric value is averaged across > all masters -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22993) Get rid of overriding solr start script during infra solr build
[ https://issues.apache.org/jira/browse/AMBARI-22993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22993: Labels: pull-request-available (was: ) > Get rid of overriding solr start script during infra solr build > --- > > Key: AMBARI-22993 > URL: https://issues.apache.org/jira/browse/AMBARI-22993 > Project: Ambari > Issue Type: Bug > Components: ambari-infra >Affects Versions: 2.7.0 >Reporter: Olivér Szabó >Assignee: Olivér Szabó >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22992) Update error handling during mpack installation
[ https://issues.apache.org/jira/browse/AMBARI-22992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22992: Labels: pull-request-available (was: ) > Update error handling during mpack installation > --- > > Key: AMBARI-22992 > URL: https://issues.apache.org/jira/browse/AMBARI-22992 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > > Remove stale code and update error handling in MpackManager. At present the > code supports refreshing a stack definition when an mpack is installed. Given > we are will map stack to mpack 1:1, we need to remove this stale code and > replace with error handling. Also the old mpack json schema used to contain > stack-id that we no longer need. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22995) Remove deprecated Upgrade Packs
Nate Cole created AMBARI-22995: -- Summary: Remove deprecated Upgrade Packs Key: AMBARI-22995 URL: https://issues.apache.org/jira/browse/AMBARI-22995 Project: Ambari Issue Type: Task Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 3.0.0 The old upgrade packs and test should be removed to make way for the new format that supports lifecycles. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22994) Management Packs: Upgrade Pack Changes
Nate Cole created AMBARI-22994: -- Summary: Management Packs: Upgrade Pack Changes Key: AMBARI-22994 URL: https://issues.apache.org/jira/browse/AMBARI-22994 Project: Ambari Issue Type: Epic Components: ambari-server Reporter: Nate Cole Assignee: Nate Cole Fix For: 3.0.0 This epic is used to track all the work necessary to change Upgrade Packs to work with the architecture changes for Management Packs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-22991) Grafana shows incorrect info for HBase Average Regions per RegionServer
[ https://issues.apache.org/jira/browse/AMBARI-22991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved AMBARI-22991. Resolution: Fixed Pushed to branch-2.6 and trunk. > Grafana shows incorrect info for HBase Average Regions per RegionServer > --- > > Key: AMBARI-22991 > URL: https://issues.apache.org/jira/browse/AMBARI-22991 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > Problem > These are number widgets on Grafana and is expected to show point in time > information for "Average Regions per RegionServer" > ambari-web that shows expected correct information gets the data from > "Hadoop:service=HBase,name=Master,sub=Server.averageLoad" jmx metric via > ambari-server metrics API resource. > It seems having aggregator as "avg" looks to be causing this issue. when > there are more than one HBase master than the metric value is averaged across > all masters -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22993) Get rid of overriding solr start script during infra solr build
Olivér Szabó created AMBARI-22993: - Summary: Get rid of overriding solr start script during infra solr build Key: AMBARI-22993 URL: https://issues.apache.org/jira/browse/AMBARI-22993 Project: Ambari Issue Type: Bug Components: ambari-infra Affects Versions: 2.7.0 Reporter: Olivér Szabó Assignee: Olivér Szabó Fix For: 2.7.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22992) Update error handling during mpack installation
Madhuvanthi Radhakrishnan created AMBARI-22992: -- Summary: Update error handling during mpack installation Key: AMBARI-22992 URL: https://issues.apache.org/jira/browse/AMBARI-22992 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Madhuvanthi Radhakrishnan Assignee: Madhuvanthi Radhakrishnan Fix For: 3.0.0 Remove stale code and update error handling in MpackManager. At present the code supports refreshing a stack definition when an mpack is installed. Given we are will map stack to mpack 1:1, we need to remove this stale code and replace with error handling. Also the old mpack json schema used to contain stack-id that we no longer need. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22991) Grafana shows incorrect info for HBase Average Regions per RegionServer
[ https://issues.apache.org/jira/browse/AMBARI-22991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22991: Labels: pull-request-available (was: ) > Grafana shows incorrect info for HBase Average Regions per RegionServer > --- > > Key: AMBARI-22991 > URL: https://issues.apache.org/jira/browse/AMBARI-22991 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > Labels: pull-request-available > > Problem > These are number widgets on Grafana and is expected to show point in time > information for "Average Regions per RegionServer" > ambari-web that shows expected correct information gets the data from > "Hadoop:service=HBase,name=Master,sub=Server.averageLoad" jmx metric via > ambari-server metrics API resource. > It seems having aggregator as "avg" looks to be causing this issue. when > there are more than one HBase master than the metric value is averaged across > all masters -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22891) Logging improvement during the Upgrade when there is invalid Alert definition
[
https://issues.apache.org/jira/browse/AMBARI-22891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
amarnath reddy pappu updated AMBARI-22891:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Logging improvement during the Upgrade when there is invalid Alert definition
> -
>
> Key: AMBARI-22891
> URL: https://issues.apache.org/jira/browse/AMBARI-22891
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.1
>Reporter: amarnath reddy pappu
>Assignee: amarnath reddy pappu
>Priority: Major
> Labels: pull-request-available
> Fix For: 2.6.2
>
> Attachments: AMBARI-22891.txt
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> If there is invalid definition/json in alert definition then Upgrade would
> fail with below exception. there is no way to determine which alert is
> causing the issue here.
> its not clear how this alert definition gets corrupted but we have seen this
> with 3 to 4 customers already - printing the alert definition name would he
> helpful in support point of view to determine the root cause.. other wise it
> is very difficult to find it out - had a give a dev patch to customers to
> find it out.
> {noformat}
> 29 Jan 2018 19:58:50,173 ERROR [main] AlertDefinitionFactory:199 - Unable to
> deserialize the alert definition source during coercion
> com.google.gson.JsonSyntaxException: java.lang.IllegalStateException:
> Expected STRING but was BEGIN_OBJECT
> at
> com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:176)
> at com.google.gson.Gson.fromJson(Gson.java:795)
> at com.google.gson.Gson.fromJson(Gson.java:859)
> at com.google.gson.Gson$2.deserialize(Gson.java:131)
> at
> org.apache.ambari.server.state.alert.AlertDefinitionFactory$AlertDefinitionSourceAdapter.deserialize(AlertDefinitionFactory.java:373)
> at
> org.apache.ambari.server.state.alert.AlertDefinitionFactory$AlertDefinitionSourceAdapter.deserialize(AlertDefinitionFactory.java:313)
> at com.google.gson.TreeTypeAdapter.read(TreeTypeAdapter.java:58)
> at com.google.gson.Gson.fromJson(Gson.java:795)
> at com.google.gson.Gson.fromJson(Gson.java:761)
> at com.google.gson.Gson.fromJson(Gson.java:710)
> at com.google.gson.Gson.fromJson(Gson.java:682)
> at
> org.apache.ambari.server.state.alert.AlertDefinitionFactory.coerce(AlertDefinitionFactory.java:196)
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1150)
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:946)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:450)
> Caused by: java.lang.IllegalStateException: Expected STRING but was
> BEGIN_OBJECT
> at
> com.google.gson.internal.bind.JsonTreeReader.nextString(JsonTreeReader.java:154)
> at
> com.google.gson.internal.bind.TypeAdapters$13.read(TypeAdapters.java:349)
> at
> com.google.gson.internal.bind.TypeAdapters$13.read(TypeAdapters.java:337)
> at
> com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$1.read(ReflectiveTypeAdapterFactory.java:93)
> at
> com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(ReflectiveTypeAdapterFactory.java:172)
> ... 16 more
> 29 Jan 2018 19:58:50,176 ERROR [main] SchemaUpgradeHelper:239 - Upgrade
> failed.
> java.lang.NullPointerException
> at
> org.apache.ambari.server.api.services.AmbariMetaInfo.reconcileAlertDefinitions(AmbariMetaInfo.java:1163)
> at
> org.apache.ambari.server.upgrade.UpdateAlertScriptPaths.executeDMLUpdates(UpdateAlertScriptPaths.java:46)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:946)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:450)
> 29 Jan 2018 19:58:50,177 ERROR [main] SchemaUpgradeHelper:464 - Exception
> occurred during upgrade, failed
> org.apache.ambari.server.AmbariException
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
> at
>
[jira] [Assigned] (AMBARI-22991) Grafana shows incorrect info for HBase Average Regions per RegionServer
[ https://issues.apache.org/jira/browse/AMBARI-22991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan reassigned AMBARI-22991: -- Assignee: Aravindan Vijayan > Grafana shows incorrect info for HBase Average Regions per RegionServer > --- > > Key: AMBARI-22991 > URL: https://issues.apache.org/jira/browse/AMBARI-22991 > Project: Ambari > Issue Type: Bug > Components: ambari-metrics >Reporter: Aravindan Vijayan >Assignee: Aravindan Vijayan >Priority: Major > > Problem > These are number widgets on Grafana and is expected to show point in time > information for "Average Regions per RegionServer" > ambari-web that shows expected correct information gets the data from > "Hadoop:service=HBase,name=Master,sub=Server.averageLoad" jmx metric via > ambari-server metrics API resource. > It seems having aggregator as "avg" looks to be causing this issue. when > there are more than one HBase master than the metric value is averaged across > all masters -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-22934) [API] Updating current stack repo without GPL repos in the body does not throw any error
[
https://issues.apache.org/jira/browse/AMBARI-22934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle resolved AMBARI-22934.
--
Resolution: Fixed
Thanks, [~aonishuk] for merging the changes.
> [API] Updating current stack repo without GPL repos in the body does not
> throw any error
>
>
> Key: AMBARI-22934
> URL: https://issues.apache.org/jira/browse/AMBARI-22934
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.6.2
>Reporter: Myroslav Papirkovskyi
>Assignee: Myroslav Papirkovskyi
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.6.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> # Install HDP 2.6.4.0 stack with Ambari 2.6.1
> # Update the current repository versions with the following body on
> ambari-2.6.1
> {code:java}
> PUT
> http://:8080/api/v1/stacks/HDP/versions/2.6/repository_versions/1
> {
> "operating_systems": [
> {
> "OperatingSystems": {
> "os_type": "debian7",
> "ambari_managed_repositories": true
> },
> "repositories": [
> {
> "Repositories": {
> "base_url":
> "http://public-repo-1.hortonworks.com/HDP/debian7/2.x/updates/2.6.0.3;,
> "repo_id": "HDP-2.6",
> "repo_name": "HDP"
> }
> },
> {
> "Repositories": {
> "base_url":
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/debian6;,
> "repo_id": "HDP-UTILS-1.1.0.21",
> "repo_name": "HDP-UTILS"
> }
> }
> ]
> },
> {
> "OperatingSystems": {
> "os_type": "redhat6",
> "ambari_managed_repositories": true
> },
> "repositories": [
> {
> "Repositories": {
> "base_url":
> "http://public-repo-1.hortonworks.com/HDP/centos6/2.x/updates/2.4.2.0/;,
> "repo_id": "HDP-2.6",
> "repo_name": "HDP"
> }
> },
> {
> "Repositories": {
> "base_url":
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/centos6;,
> "repo_id": "HDP-UTILS-1.1.0.21",
> "repo_name": "HDP-UTILS"
> }
> }
> ]
> },
> {
> "OperatingSystems": {
> "os_type": "redhat7",
> "ambari_managed_repositories": true
> },
> "repositories": [
> {
> "Repositories": {
> "base_url":
> "http://public-repo-1.hortonworks.com/HDP/centos7/2.x/updates/2.6.0.3;,
> "repo_id": "HDP-2.6",
> "repo_name": "HDP"
> }
> },
> {
> "Repositories": {
> "base_url":
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/centos7;,
> "repo_id": "HDP-UTILS-1.1.0.21",
> "repo_name": "HDP-UTILS"
> }
> }
> ]
> },
> {
> "OperatingSystems": {
> "os_type": "suse11",
> "ambari_managed_repositories": true
> },
> "repositories": [
> {
> "Repositories": {
> "base_url":
> "http://public-repo-1.hortonworks.com/HDP/suse11sp3/2.x/updates/2.6.0.3;,
> "repo_id": "HDP-2.6",
> "repo_name": "HDP"
> }
> },
> {
> "Repositories": {
> "base_url":
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/suse11sp3;,
> "repo_id": "HDP-UTILS-1.1.0.21",
> "repo_name": "HDP-UTILS"
> }
> }
> ]
> },
> {
> "OperatingSystems": {
> "os_type": "suse12",
> "ambari_managed_repositories": true
> },
> "repositories": [
> {
> "Repositories": {
> "base_url":
> "http://public-repo-1.hortonworks.com/HDP/suse11sp3/2.x/updates/2.6.0.3;,
> "repo_id": "HDP-2.6",
> "repo_name": "HDP"
> }
> },
> {
> "Repositories": {
> "base_url":
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/suse11sp3;,
> "repo_id": "HDP-UTILS-1.1.0.21",
> "repo_name": "HDP-UTILS"
> }
> }
> ]
> },
> {
> "OperatingSystems": {
> "os_type": "ubuntu12",
> "ambari_managed_repositories": true
> },
> "repositories": [
> {
> "Repositories": {
> "base_url":
> "http://public-repo-1.hortonworks.com/HDP/ubuntu12/2.x/updates/2.6.0.3;,
> "repo_id": "HDP-2.6",
> "repo_name": "HDP"
> }
> },
> {
> "Repositories": {
> "base_url":
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/ubuntu12;,
> "repo_id": "HDP-UTILS-1.1.0.21",
> "repo_name": "HDP-UTILS"
> }
> }
> ]
> },
> {
> "OperatingSystems": {
> "os_type": "ubuntu14",
> "ambari_managed_repositories": true
> },
> "repositories": [
> {
> "Repositories": {
> "base_url":
> "http://public-repo-1.hortonworks.com/HDP/ubuntu14/2.x/updates/2.6.0.3;,
> "repo_id": "HDP-2.6",
> "repo_name": "HDP"
> }
> },
> {
> "Repositories": {
> "base_url":
> "http://public-repo-1.hortonworks.com/HDP-UTILS-1.1.0.21/repos/ubuntu14;,
> "repo_id": "HDP-UTILS-1.1.0.21",
> "repo_name": "HDP-UTILS"
> }
> }
> ]
> },
> {
> "OperatingSystems": {
> "os_type": "ubuntu16",
> "ambari_managed_repositories": true
> },
> "repositories": [
> {
> "Repositories": {
> "base_url":
> "http://public-repo-1.hortonworks.com/HDP/ubuntu16/2.x/updates/2.6.0.3;,
> "repo_id": "HDP-2.6",
> "repo_name": "HDP"
> }
> },
> {
[jira] [Created] (AMBARI-22990) Provide Bootstrap test connection feature
Scott Duan created AMBARI-22990: --- Summary: Provide Bootstrap test connection feature Key: AMBARI-22990 URL: https://issues.apache.org/jira/browse/AMBARI-22990 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: ambari-server Reporter: Scott Duan Assignee: Scott Duan Fix For: ambari-server Currently the bootstrap API uses the SSH key to connect to the hosts and register them in a single call. We need a separate call that ONLY checks the host connectivity feature without actually registering the hosts. This is required for the 'TEST CONNECTIVITY' feature for the Add Hosts Page h2. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22988) master-key option is missing from ambari-server setup action
[
https://issues.apache.org/jira/browse/AMBARI-22988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-22988:
Labels: pull-request-available (was: )
> master-key option is missing from ambari-server setup action
>
>
> Key: AMBARI-22988
> URL: https://issues.apache.org/jira/browse/AMBARI-22988
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Kishor Ramakrishnan
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
>
> {{ambari-server setup --enable-lzo-under-gpl-license}} failing with
> {{Unexpected AttibuteError}}
> {noformat}
> # ambari-server setup --enable-lzo-under-gpl-license -s
> Using python /usr/bin/python
> Setup ambari-server
> Checking SELinux...
> SELinux status is 'disabled'
> Customize user account for ambari-server daemon [y/n] (n)?
> Adjusting ambari-server permissions and ownership...
> Checking firewall status...
> Checking JDK...
> Do you want to change Oracle JDK [y/n] (n)?
> Check JDK version for Ambari Server...
> JDK version found: 8
> Minimum JDK version is 8 for Ambari. Skipping to setup different JDK for
> Ambari Server.
> Checking GPL software agreement...
> Completing setup...
> Configuring database...
> Enter advanced database configuration [y/n] (n)?
> Configuring database...
> ERROR: Unexpected AttributeError: Values instance has no attribute
> 'master_key'
> For more info run ambari-server with -v or --verbose option
> {noformat}
> *Note*: This occurs after encrypting passwords in the
> {{ambari_server.properties}} file:
> {noformat}
> # ambari-server setup-security
> Using python /usr/bin/python
> Security setup options...
> ===
> Choose one of the following options:
> [1] Enable HTTPS for Ambari server.
> [2] Encrypt passwords stored in ambari.properties file.
> [3] Setup Ambari kerberos JAAS configuration.
> [4] Setup truststore.
> [5] Import certificate to truststore.
> ===
> Enter choice, (1-5): 2
> Please provide master key for locking the credential store:
> Re-enter master key:
> Do you want to persist master key. If you choose not to persist, you need to
> provide the Master Key while starting the ambari server as an env variable
> named AMBARI_SECURITY_MASTER_KEY or the start will prompt for the master key.
> Persist [y/n] (y)? y
> Adjusting ambari-server permissions and ownership...
> Ambari Server 'setup-security' completed successfully.
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22988) master-key option is missing from ambari-server setup action
[
https://issues.apache.org/jira/browse/AMBARI-22988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-22988:
--
Status: Patch Available (was: In Progress)
> master-key option is missing from ambari-server setup action
>
>
> Key: AMBARI-22988
> URL: https://issues.apache.org/jira/browse/AMBARI-22988
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Kishor Ramakrishnan
>Assignee: Robert Levas
>Priority: Critical
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{ambari-server setup --enable-lzo-under-gpl-license}} failing with
> {{Unexpected AttibuteError}}
> {noformat}
> # ambari-server setup --enable-lzo-under-gpl-license -s
> Using python /usr/bin/python
> Setup ambari-server
> Checking SELinux...
> SELinux status is 'disabled'
> Customize user account for ambari-server daemon [y/n] (n)?
> Adjusting ambari-server permissions and ownership...
> Checking firewall status...
> Checking JDK...
> Do you want to change Oracle JDK [y/n] (n)?
> Check JDK version for Ambari Server...
> JDK version found: 8
> Minimum JDK version is 8 for Ambari. Skipping to setup different JDK for
> Ambari Server.
> Checking GPL software agreement...
> Completing setup...
> Configuring database...
> Enter advanced database configuration [y/n] (n)?
> Configuring database...
> ERROR: Unexpected AttributeError: Values instance has no attribute
> 'master_key'
> For more info run ambari-server with -v or --verbose option
> {noformat}
> *Note*: This occurs after encrypting passwords in the
> {{ambari_server.properties}} file:
> {noformat}
> # ambari-server setup-security
> Using python /usr/bin/python
> Security setup options...
> ===
> Choose one of the following options:
> [1] Enable HTTPS for Ambari server.
> [2] Encrypt passwords stored in ambari.properties file.
> [3] Setup Ambari kerberos JAAS configuration.
> [4] Setup truststore.
> [5] Import certificate to truststore.
> ===
> Enter choice, (1-5): 2
> Please provide master key for locking the credential store:
> Re-enter master key:
> Do you want to persist master key. If you choose not to persist, you need to
> provide the Master Key while starting the ambari server as an env variable
> named AMBARI_SECURITY_MASTER_KEY or the start will prompt for the master key.
> Persist [y/n] (y)? y
> Adjusting ambari-server permissions and ownership...
> Ambari Server 'setup-security' completed successfully.
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22989) Refactor stack settings
[ https://issues.apache.org/jira/browse/AMBARI-22989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Madhuvanthi Radhakrishnan updated AMBARI-22989: --- Summary: Refactor stack settings (was: Include stack_settings.xml in hdpcore mpack definictions) > Refactor stack settings > --- > > Key: AMBARI-22989 > URL: https://issues.apache.org/jira/browse/AMBARI-22989 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 3.0.0 >Reporter: Madhuvanthi Radhakrishnan >Assignee: Madhuvanthi Radhakrishnan >Priority: Major > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22989) Include stack_settings.xml in hdpcore mpack definictions
Madhuvanthi Radhakrishnan created AMBARI-22989: -- Summary: Include stack_settings.xml in hdpcore mpack definictions Key: AMBARI-22989 URL: https://issues.apache.org/jira/browse/AMBARI-22989 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0 Reporter: Madhuvanthi Radhakrishnan Assignee: Madhuvanthi Radhakrishnan Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22988) master-key option is missing from ambari-server setup action
Robert Levas created AMBARI-22988:
-
Summary: master-key option is missing from ambari-server setup
action
Key: AMBARI-22988
URL: https://issues.apache.org/jira/browse/AMBARI-22988
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Kishor Ramakrishnan
Assignee: Robert Levas
Fix For: 2.7.0
{{ambari-server setup --enable-lzo-under-gpl-license}} failing with
{{Unexpected AttibuteError}}
{noformat}
# ambari-server setup --enable-lzo-under-gpl-license -s
Using python /usr/bin/python
Setup ambari-server
Checking SELinux...
SELinux status is 'disabled'
Customize user account for ambari-server daemon [y/n] (n)?
Adjusting ambari-server permissions and ownership...
Checking firewall status...
Checking JDK...
Do you want to change Oracle JDK [y/n] (n)?
Check JDK version for Ambari Server...
JDK version found: 8
Minimum JDK version is 8 for Ambari. Skipping to setup different JDK for Ambari
Server.
Checking GPL software agreement...
Completing setup...
Configuring database...
Enter advanced database configuration [y/n] (n)?
Configuring database...
ERROR: Unexpected AttributeError: Values instance has no attribute 'master_key'
For more info run ambari-server with -v or --verbose option
{noformat}
*Note*: This occurs after encrypting passwords in the
{{ambari_server.properties}} file:
{noformat}
# ambari-server setup-security
Using python /usr/bin/python
Security setup options...
===
Choose one of the following options:
[1] Enable HTTPS for Ambari server.
[2] Encrypt passwords stored in ambari.properties file.
[3] Setup Ambari kerberos JAAS configuration.
[4] Setup truststore.
[5] Import certificate to truststore.
===
Enter choice, (1-5): 2
Please provide master key for locking the credential store:
Re-enter master key:
Do you want to persist master key. If you choose not to persist, you need to
provide the Master Key while starting the ambari server as an env variable
named AMBARI_SECURITY_MASTER_KEY or the start will prompt for the master key.
Persist [y/n] (y)? y
Adjusting ambari-server permissions and ownership...
Ambari Server 'setup-security' completed successfully.
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22972) yum install ambari-server*.rpm Is not working
[ https://issues.apache.org/jira/browse/AMBARI-22972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16364385#comment-16364385 ] Doroszlai, Attila commented on AMBARI-22972: Hi [~ursdeepak2000], I'd guess step #1 failed to create RPMs due to Python version problem (AMBARI-22516). Can you please provide relevant parts of the output from Maven? Thanks. > yum install ambari-server*.rpm Is not working > - > > Key: AMBARI-22972 > URL: https://issues.apache.org/jira/browse/AMBARI-22972 > Project: Ambari > Issue Type: Bug > Environment: *- Platform: redhat* > *- Platform Version: 7.4* > *- Virtulization...: vmware* > *- CPU Total...: 12* > *- Managed BY..: Chef* >Reporter: Deepak Agrawal >Priority: Major > > I was installing apache Ambari on my REDHAT Lunix machine. I did follow all > the steps mentioned in below link. > [https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.6.1.] > It's not able to run step 2: 'yum install ambari-server*.rpm''. It's > throwing following error . 'Loaded plugins: langpacks, product-id, > search-disabled-repos, subscription-manager'. > Hence i had created account on Redhat portal and tried to subscribe manager. > there by seeing following error.'cannot register with any organizations.'. > Also I can see 'ambari-server'.rmp is not exist on Redhat repository . > I need help to solve Install Apache Ambari. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22984) Old mpacks broken
[ https://issues.apache.org/jira/browse/AMBARI-22984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16364383#comment-16364383 ] Hudson commented on AMBARI-22984: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8726 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8726/]) AMBARI-22984. Old mpacks broken (echekanskiy) (echekanskiy: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=dc697410dd7e48e4e3705b81e8342a4b0f812769]) * (edit) ambari-server/src/main/resources/custom_actions/scripts/install_packages.py > Old mpacks broken > -- > > Key: AMBARI-22984 > URL: https://issues.apache.org/jira/browse/AMBARI-22984 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.6.2 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Old mpacks or custom stacks may not have "component" filed > stack_packages.json and package install will be broken. We need to fallback > to old behavior if this field is missing -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22984) Old mpacks broken
[ https://issues.apache.org/jira/browse/AMBARI-22984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16364369#comment-16364369 ] Hudson commented on AMBARI-22984: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #609 (See [https://builds.apache.org/job/Ambari-branch-2.6/609/]) AMBARI-22984. Old mpacks broken (echekanskiy) (echekanskiy: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=96cee1d8ff785c88422cf0c9a1ca0bab70910346]) * (edit) ambari-server/src/main/resources/custom_actions/scripts/install_packages.py > Old mpacks broken > -- > > Key: AMBARI-22984 > URL: https://issues.apache.org/jira/browse/AMBARI-22984 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.6.2 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Old mpacks or custom stacks may not have "component" filed > stack_packages.json and package install will be broken. We need to fallback > to old behavior if this field is missing -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-22984) Old mpacks broken
[ https://issues.apache.org/jira/browse/AMBARI-22984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Chekanskiy resolved AMBARI-22984. Resolution: Fixed > Old mpacks broken > -- > > Key: AMBARI-22984 > URL: https://issues.apache.org/jira/browse/AMBARI-22984 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.6.2 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Old mpacks or custom stacks may not have "component" filed > stack_packages.json and package install will be broken. We need to fallback > to old behavior if this field is missing -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22491) Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
[ https://issues.apache.org/jira/browse/AMBARI-22491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22491: Labels: pull-request-available (was: ) > Moving Metrics Collector Forces ZooKeeper Server Install on Target Host > --- > > Key: AMBARI-22491 > URL: https://issues.apache.org/jira/browse/AMBARI-22491 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Labels: pull-request-available > Fix For: 2.6.1 > > Attachments: AMBARI-22491.patch > > > When moving a Metrics Collector, a ZooKeeper Server is installed on the > target host along with the Metrics Collector. This ZooKeeper Server is added > and quorum can be upset in large clusters, and the customer was not intending > to have a ZooKeeper server on the target directory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (AMBARI-22491) Moving Metrics Collector Forces ZooKeeper Server Install on Target Host
[ https://issues.apache.org/jira/browse/AMBARI-22491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander reopened AMBARI-22491: -- Reopening this as this task was not fully resolved, if component is in started state UI still is trying to force install it on target host > Moving Metrics Collector Forces ZooKeeper Server Install on Target Host > --- > > Key: AMBARI-22491 > URL: https://issues.apache.org/jira/browse/AMBARI-22491 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.5.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Blocker > Fix For: 2.6.1 > > Attachments: AMBARI-22491.patch > > > When moving a Metrics Collector, a ZooKeeper Server is installed on the > target host along with the Metrics Collector. This ZooKeeper Server is added > and quorum can be upset in large clusters, and the customer was not intending > to have a ZooKeeper server on the target directory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22987) Fix Ambari doc site to fix errors from https://whimsy.apache.org/site/project/ambari
[ https://issues.apache.org/jira/browse/AMBARI-22987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated AMBARI-22987: -- Status: Patch Available (was: In Progress) Patch submitted for review > Fix Ambari doc site to fix errors from > https://whimsy.apache.org/site/project/ambari > > > Key: AMBARI-22987 > URL: https://issues.apache.org/jira/browse/AMBARI-22987 > Project: Ambari > Issue Type: Bug > Components: site >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > Attachments: > 0001-AMBARI-22987-fixes-to-errors-shown-from-whimsy.apach.patch > > > Fix errors shown in https://whimsy.apache.org/site/project/ambari -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22987) Fix Ambari doc site to fix errors from https://whimsy.apache.org/site/project/ambari
[ https://issues.apache.org/jira/browse/AMBARI-22987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Selvamohan Neethiraj updated AMBARI-22987: -- Attachment: 0001-AMBARI-22987-fixes-to-errors-shown-from-whimsy.apach.patch > Fix Ambari doc site to fix errors from > https://whimsy.apache.org/site/project/ambari > > > Key: AMBARI-22987 > URL: https://issues.apache.org/jira/browse/AMBARI-22987 > Project: Ambari > Issue Type: Bug > Components: site >Reporter: Selvamohan Neethiraj >Assignee: Selvamohan Neethiraj >Priority: Major > Attachments: > 0001-AMBARI-22987-fixes-to-errors-shown-from-whimsy.apach.patch > > > Fix errors shown in https://whimsy.apache.org/site/project/ambari -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22987) Fix Ambari doc site to fix errors from https://whimsy.apache.org/site/project/ambari
Selvamohan Neethiraj created AMBARI-22987: - Summary: Fix Ambari doc site to fix errors from https://whimsy.apache.org/site/project/ambari Key: AMBARI-22987 URL: https://issues.apache.org/jira/browse/AMBARI-22987 Project: Ambari Issue Type: Bug Components: site Reporter: Selvamohan Neethiraj Assignee: Selvamohan Neethiraj Fix errors shown in https://whimsy.apache.org/site/project/ambari -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-2298) YARN/MR2 do not start after reconfiguring
[
https://issues.apache.org/jira/browse/AMBARI-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-2298:
---
Labels: pull-request-available (was: )
> YARN/MR2 do not start after reconfiguring
> -
>
> Key: AMBARI-2298
> URL: https://issues.apache.org/jira/browse/AMBARI-2298
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 1.4.0
>Reporter: Andrii Tkach
>Assignee: Andrii Tkach
>Priority: Critical
> Labels: pull-request-available
> Fix For: 1.4.0
>
> Attachments: AMBARI-2298_branch-1.4.0.patch
>
>
> After successfully installing a cluster, I saved YARN configs (changed only 1
> property). YARN service would not start with ResourceManager saying it cannot
> bind to port.
> Turns out that certain properties in {{yarn-site.xml}} were set to null value.
> {noformat}
> "yarn.resourcemanager.admin.address" : "null",
> "yarn.resourcemanager.resource-tracker.address" : "null",
> "yarn.resourcemanager.scheduler.address" : "null",
> "yarn.resourcemanager.address" : "null",
> "yarn.log.server.url" : "null",
> {noformat}
> Similar problem with MR2 also. The {{mapred-site.xml}} had 19 properties
> which were null.
> {noformat}
> "mapred.jobtracker.taskScheduler" : "null",
> "mapred.tasktracker.map.tasks.maximum" : "null",
> "mapred.hosts.exclude" : "null",
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22983) Add Hosts is Failing with - Error while bootstrapping: Cannot run program "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py"
[
https://issues.apache.org/jira/browse/AMBARI-22983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16364169#comment-16364169
]
Hudson commented on AMBARI-22983:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8725 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8725/])
AMBARI-22983. Add Hosts is Failing with Error while bootstrapping: (aonishuk:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=8c91055596d26cab6838f86f86ff031d2f1a21f3])
* (edit) ambari-server/src/main/python/ambari_server/serverConfiguration.py
> Add Hosts is Failing with - Error while bootstrapping: Cannot run program
> "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py"
> ---
>
> Key: AMBARI-22983
> URL: https://issues.apache.org/jira/browse/AMBARI-22983
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.2
> Environment: CentOS 7
>Reporter: Jasmeen Kaur
>Assignee: Andrew Onischuk
>Priority: Blocker
> Labels: pull-request-available
> Attachments: AMBARI-22983.patch
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Add Hosts(UI/API) is broken and the following error is seen .
> {code:java}
> Error while bootstrapping:
> Cannot run program
> "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py": error=2, No
> such file or directory
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22986) Not able to add Livy2 after doing rolling upgrade to M21
[ https://issues.apache.org/jira/browse/AMBARI-22986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-22986: Affects Version/s: 2.6.1 > Not able to add Livy2 after doing rolling upgrade to M21 > > > Key: AMBARI-22986 > URL: https://issues.apache.org/jira/browse/AMBARI-22986 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Blocker > Fix For: 2.6.2 > > > Steps to reproduce : > 1) Create a cluster with ambari-2.4.3+HDP-2.5.3 > 2) Do ambari upgrade to ambari-2.6.1 > 3) Do stack upgrade to HDP-2.6.4 > After upgrade its not possible to add livy2(Livy2 is a spark2 component). > This issue is specific to rolling upgrade. I am able to add livy2 in express > upgraded cluster > Also in EU cluster I see 'Upgrade service configs' step , this step is likely > updating the spark2 livy2 configs. But I am not seeing this in RU cluster. > The reason is that the desired version of a cluster is not updated (only > during cross-stack rolling upgrade) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22986) Not able to add Livy2 after doing rolling upgrade to M21
[ https://issues.apache.org/jira/browse/AMBARI-22986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-22986: Fix Version/s: 2.6.2 > Not able to add Livy2 after doing rolling upgrade to M21 > > > Key: AMBARI-22986 > URL: https://issues.apache.org/jira/browse/AMBARI-22986 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.6.1 >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Blocker > Fix For: 2.6.2 > > > Steps to reproduce : > 1) Create a cluster with ambari-2.4.3+HDP-2.5.3 > 2) Do ambari upgrade to ambari-2.6.1 > 3) Do stack upgrade to HDP-2.6.4 > After upgrade its not possible to add livy2(Livy2 is a spark2 component). > This issue is specific to rolling upgrade. I am able to add livy2 in express > upgraded cluster > Also in EU cluster I see 'Upgrade service configs' step , this step is likely > updating the spark2 livy2 configs. But I am not seeing this in RU cluster. > The reason is that the desired version of a cluster is not updated (only > during cross-stack rolling upgrade) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22986) Not able to add Livy2 after doing rolling upgrade to M21
Dmitry Lysnichenko created AMBARI-22986: --- Summary: Not able to add Livy2 after doing rolling upgrade to M21 Key: AMBARI-22986 URL: https://issues.apache.org/jira/browse/AMBARI-22986 Project: Ambari Issue Type: Bug Reporter: Dmitry Lysnichenko Assignee: Dmitry Lysnichenko Steps to reproduce : 1) Create a cluster with ambari-2.4.3+HDP-2.5.3 2) Do ambari upgrade to ambari-2.6.1 3) Do stack upgrade to HDP-2.6.4 After upgrade its not possible to add livy2(Livy2 is a spark2 component). This issue is specific to rolling upgrade. I am able to add livy2 in express upgraded cluster Also in EU cluster I see 'Upgrade service configs' step , this step is likely updating the spark2 livy2 configs. But I am not seeing this in RU cluster. The reason is that the desired version of a cluster is not updated (only during cross-stack rolling upgrade) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22986) Not able to add Livy2 after doing rolling upgrade to M21
[ https://issues.apache.org/jira/browse/AMBARI-22986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Lysnichenko updated AMBARI-22986: Component/s: ambari-server > Not able to add Livy2 after doing rolling upgrade to M21 > > > Key: AMBARI-22986 > URL: https://issues.apache.org/jira/browse/AMBARI-22986 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Reporter: Dmitry Lysnichenko >Assignee: Dmitry Lysnichenko >Priority: Blocker > > Steps to reproduce : > 1) Create a cluster with ambari-2.4.3+HDP-2.5.3 > 2) Do ambari upgrade to ambari-2.6.1 > 3) Do stack upgrade to HDP-2.6.4 > After upgrade its not possible to add livy2(Livy2 is a spark2 component). > This issue is specific to rolling upgrade. I am able to add livy2 in express > upgraded cluster > Also in EU cluster I see 'Upgrade service configs' step , this step is likely > updating the spark2 livy2 configs. But I am not seeing this in RU cluster. > The reason is that the desired version of a cluster is not updated (only > during cross-stack rolling upgrade) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22983) Add Hosts is Failing with - Error while bootstrapping: Cannot run program "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py"
[
https://issues.apache.org/jira/browse/AMBARI-22983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16364156#comment-16364156
]
Hudson commented on AMBARI-22983:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #608 (See
[https://builds.apache.org/job/Ambari-branch-2.6/608/])
AMBARI-22983. Add Hosts is Failing with Error while bootstrapping: (aonishuk:
[https://gitbox.apache.org/repos/asf?p=ambari.git=commit=333292fa0e9e9ff6dc95f28bdeb3e2bd6c3ad3cf])
* (edit) ambari-server/src/main/python/ambari_server/serverConfiguration.py
> Add Hosts is Failing with - Error while bootstrapping: Cannot run program
> "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py"
> ---
>
> Key: AMBARI-22983
> URL: https://issues.apache.org/jira/browse/AMBARI-22983
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.2
> Environment: CentOS 7
>Reporter: Jasmeen Kaur
>Assignee: Andrew Onischuk
>Priority: Blocker
> Labels: pull-request-available
> Attachments: AMBARI-22983.patch
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Add Hosts(UI/API) is broken and the following error is seen .
> {code:java}
> Error while bootstrapping:
> Cannot run program
> "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py": error=2, No
> such file or directory
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22983) Add Hosts is Failing with - Error while bootstrapping: Cannot run program "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py"
[
https://issues.apache.org/jira/browse/AMBARI-22983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-22983:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk and branch-2.6
> Add Hosts is Failing with - Error while bootstrapping: Cannot run program
> "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py"
> ---
>
> Key: AMBARI-22983
> URL: https://issues.apache.org/jira/browse/AMBARI-22983
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.2
> Environment: CentOS 7
>Reporter: Jasmeen Kaur
>Assignee: Andrew Onischuk
>Priority: Blocker
> Labels: pull-request-available
> Attachments: AMBARI-22983.patch
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Add Hosts(UI/API) is broken and the following error is seen .
> {code:java}
> Error while bootstrapping:
> Cannot run program
> "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py": error=2, No
> such file or directory
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22951) Export JAVA_HOME env variable in shell script for Ranger
[ https://issues.apache.org/jira/browse/AMBARI-22951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16364055#comment-16364055 ] Hudson commented on AMBARI-22951: - FAILURE: Integrated in Jenkins build Ambari-branch-2.6 #607 (See [https://builds.apache.org/job/Ambari-branch-2.6/607/]) AMBARI-22951 Export JAVA_HOME env variable in shell script for Ranger (jonathanhurley: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=8e0a6d1274951af18616afdf828b3981b443ab35]) * (edit) ambari-server/src/test/python/stacks/2.5/RANGER_KMS/test_kms_server.py * (edit) ambari-server/src/test/python/stacks/2.5/RANGER/test_ranger_admin.py * (edit) ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/kms.py * (edit) ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py * (edit) ambari-server/src/test/python/stacks/2.6/RANGER/test_ranger_admin.py > Export JAVA_HOME env variable in shell script for Ranger > > > Key: AMBARI-22951 > URL: https://issues.apache.org/jira/browse/AMBARI-22951 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.6.0, 2.6.1 >Reporter: Mugdha Varadkar >Assignee: Mugdha Varadkar >Priority: Major > Labels: pull-request-available > Fix For: 2.6.2 > > Attachments: AMBARI-22951.patch > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Need to export JAVA_HOME variable in ranger-admin-env.sh, so that > [ranger-admin-services.sh|https://github.com/apache/ranger/blob/master/embeddedwebserver/scripts/ranger-admin-services.sh] > knows which java to be used for processing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-1831) mvn install in the Dev Setup document throws errors.
[ https://issues.apache.org/jira/browse/AMBARI-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363906#comment-16363906 ] kiruba sekar commented on AMBARI-1831: -- Does any workaround found for this issue? > mvn install in the Dev Setup document throws errors. > > > Key: AMBARI-1831 > URL: https://issues.apache.org/jira/browse/AMBARI-1831 > Project: Ambari > Issue Type: Bug > Environment: Rhel6 2.6 64 bit >Reporter: sandeepbaldawa >Priority: Critical > > In document > https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development > while running mvn -X -B -e clean install package rpm:rpm -DskipTests > -Dpython.ver="python >= 2.6" a bunch of errors are thrown. A work around > which worked for the same was to run "mvn -X -B -e clean install package > rpm:rpm" which seems to work fine. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AMBARI-22978) Mandatory configs warning in Ambari while editing the config of HDFS
[ https://issues.apache.org/jira/browse/AMBARI-22978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Endre Major resolved AMBARI-22978. -- Resolution: Invalid The problematic config has been removed in the meantime. > Mandatory configs warning in Ambari while editing the config of HDFS > > > Key: AMBARI-22978 > URL: https://issues.apache.org/jira/browse/AMBARI-22978 > Project: Ambari > Issue Type: Bug >Reporter: Endre Major >Assignee: Endre Major >Priority: Blocker > > On the GUI HDFS advanced settings indicates to problems, that it should not. > This is caused by a bad ssl-client.xml at > /var/lib/ambari-server/resources/common-services/HDFS/3.0.0.3.0/configuration/ssl-client.xml > > ssl.client.keystore.password > > > true > > PASSWORD > Password to open the keystore file. > > password > > > > There are 2 value-attributes section. Merging them solves this problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22985) Quick links should be grouped by namespace
[ https://issues.apache.org/jira/browse/AMBARI-22985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22985: Labels: pull-request-available (was: ) > Quick links should be grouped by namespace > -- > > Key: AMBARI-22985 > URL: https://issues.apache.org/jira/browse/AMBARI-22985 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > > Currently quick links are grouped by host. These groups in their part should > be grouped by namespace (if any). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22985) Quick links should be grouped by namespace
Andrii Babiichuk created AMBARI-22985: - Summary: Quick links should be grouped by namespace Key: AMBARI-22985 URL: https://issues.apache.org/jira/browse/AMBARI-22985 Project: Ambari Issue Type: Task Components: ambari-web Affects Versions: 2.7.0 Reporter: Andrii Babiichuk Assignee: Andrii Babiichuk Fix For: 2.7.0 Currently quick links are grouped by host. These groups in their part should be grouped by namespace (if any). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22984) Old mpacks broken
[ https://issues.apache.org/jira/browse/AMBARI-22984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22984: Labels: pull-request-available (was: ) > Old mpacks broken > -- > > Key: AMBARI-22984 > URL: https://issues.apache.org/jira/browse/AMBARI-22984 > Project: Ambari > Issue Type: Bug > Components: ambari-agent >Affects Versions: 2.6.2 >Reporter: Eugene Chekanskiy >Assignee: Eugene Chekanskiy >Priority: Critical > Labels: pull-request-available > Fix For: 2.6.2 > > > Old mpacks or custom stacks may not have "component" filed > stack_packages.json and package install will be broken. We need to fallback > to old behavior if this field is missing -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22983) Add Hosts is Failing with - Error while bootstrapping: Cannot run program "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py"
[
https://issues.apache.org/jira/browse/AMBARI-22983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated AMBARI-22983:
Labels: pull-request-available (was: )
> Add Hosts is Failing with - Error while bootstrapping: Cannot run program
> "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py"
> ---
>
> Key: AMBARI-22983
> URL: https://issues.apache.org/jira/browse/AMBARI-22983
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.2
> Environment: CentOS 7
>Reporter: Jasmeen Kaur
>Assignee: Andrew Onischuk
>Priority: Blocker
> Labels: pull-request-available
> Attachments: AMBARI-22983.patch
>
>
> Add Hosts(UI/API) is broken and the following error is seen .
> {code:java}
> Error while bootstrapping:
> Cannot run program
> "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py": error=2, No
> such file or directory
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22983) Add Hosts is Failing with - Error while bootstrapping: Cannot run program "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py"
[
https://issues.apache.org/jira/browse/AMBARI-22983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-22983:
-
Attachment: AMBARI-22983.patch
> Add Hosts is Failing with - Error while bootstrapping: Cannot run program
> "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py"
> ---
>
> Key: AMBARI-22983
> URL: https://issues.apache.org/jira/browse/AMBARI-22983
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.2
> Environment: CentOS 7
>Reporter: Jasmeen Kaur
>Assignee: Andrew Onischuk
>Priority: Blocker
> Attachments: AMBARI-22983.patch
>
>
> Add Hosts(UI/API) is broken and the following error is seen .
> {code:java}
> Error while bootstrapping:
> Cannot run program
> "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py": error=2, No
> such file or directory
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (AMBARI-22983) Add Hosts is Failing with - Error while bootstrapping: Cannot run program "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py"
[
https://issues.apache.org/jira/browse/AMBARI-22983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk reassigned AMBARI-22983:
Assignee: Andrew Onischuk
> Add Hosts is Failing with - Error while bootstrapping: Cannot run program
> "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py"
> ---
>
> Key: AMBARI-22983
> URL: https://issues.apache.org/jira/browse/AMBARI-22983
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.2
> Environment: CentOS 7
>Reporter: Jasmeen Kaur
>Assignee: Andrew Onischuk
>Priority: Blocker
> Attachments: AMBARI-22983.patch
>
>
> Add Hosts(UI/API) is broken and the following error is seen .
> {code:java}
> Error while bootstrapping:
> Cannot run program
> "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py": error=2, No
> such file or directory
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22983) Add Hosts is Failing with - Error while bootstrapping: Cannot run program "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py"
[
https://issues.apache.org/jira/browse/AMBARI-22983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-22983:
-
Status: Patch Available (was: Open)
> Add Hosts is Failing with - Error while bootstrapping: Cannot run program
> "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py"
> ---
>
> Key: AMBARI-22983
> URL: https://issues.apache.org/jira/browse/AMBARI-22983
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.6.2
> Environment: CentOS 7
>Reporter: Jasmeen Kaur
>Assignee: Andrew Onischuk
>Priority: Blocker
> Attachments: AMBARI-22983.patch
>
>
> Add Hosts(UI/API) is broken and the following error is seen .
> {code:java}
> Error while bootstrapping:
> Cannot run program
> "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py": error=2, No
> such file or directory
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AMBARI-22984) Old mpacks broken
Eugene Chekanskiy created AMBARI-22984: -- Summary: Old mpacks broken Key: AMBARI-22984 URL: https://issues.apache.org/jira/browse/AMBARI-22984 Project: Ambari Issue Type: Bug Components: ambari-agent Affects Versions: 2.6.2 Reporter: Eugene Chekanskiy Assignee: Eugene Chekanskiy Fix For: 2.6.2 Old mpacks or custom stacks may not have "component" filed stack_packages.json and package install will be broken. We need to fallback to old behavior if this field is missing -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22809) Tez shown in red in the left nav for no apparent reason
[ https://issues.apache.org/jira/browse/AMBARI-22809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22809: - Resolution: Fixed Status: Resolved (was: Patch Available) > Tez shown in red in the left nav for no apparent reason > --- > > Key: AMBARI-22809 > URL: https://issues.apache.org/jira/browse/AMBARI-22809 > Project: Ambari > Issue Type: Bug > Components: ambari-client >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Tez is showing in red because it is in "INSTALLED" state, but it is client > only service. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22807) Admin View: Add/Delete Group succeeds, but the group table does not refresh automatically
[ https://issues.apache.org/jira/browse/AMBARI-22807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22807: - Resolution: Fixed Status: Resolved (was: Patch Available) > Admin View: Add/Delete Group succeeds, but the group table does not refresh > automatically > - > > Key: AMBARI-22807 > URL: https://issues.apache.org/jira/browse/AMBARI-22807 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-21682) Patched Service Doesn't Display Correct Hadoop Version on Stacks Page
[
https://issues.apache.org/jira/browse/AMBARI-21682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonenko Alexander updated AMBARI-21682:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Patched Service Doesn't Display Correct Hadoop Version on Stacks Page
> -
>
> Key: AMBARI-21682
> URL: https://issues.apache.org/jira/browse/AMBARI-21682
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.3
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Major
> Fix For: 2.5.3
>
> Attachments: AMBARI-21682.patch
>
>
> STR:
> - Install ZK, YARN, HDFS with HDP 2.5.0.0
> - Apply a {{PATCH}} VDF for ZooKeeper for 2.5.4.0
> Notice that on the stacks/versions page, the columns show ZooKeeper as green
> for both versions.
> Also - notice that when clicking on the hosts number to see where a
> particular repository is installed, the text that is displayed sounds a
> little off. It says
> {quote}
> "HDP-2.5.4.0-121 Version is Current on 3 hosts"
> {quote}
> We can probably just drop the word "version". And maybe change the word
> "Current" to applied. Something like this:
> {quote}
> "HDP-2.5.4.0-121 is applied to 3 hosts"
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AMBARI-22809) Tez shown in red in the left nav for no apparent reason
[ https://issues.apache.org/jira/browse/AMBARI-22809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363807#comment-16363807 ] Antonenko Alexander commented on AMBARI-22809: -- Committed to trunk > Tez shown in red in the left nav for no apparent reason > --- > > Key: AMBARI-22809 > URL: https://issues.apache.org/jira/browse/AMBARI-22809 > Project: Ambari > Issue Type: Bug > Components: ambari-client >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Tez is showing in red because it is in "INSTALLED" state, but it is client > only service. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22923) Cover add_component_config_initializer with tests
[ https://issues.apache.org/jira/browse/AMBARI-22923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22923: - Resolution: Fixed Status: Resolved (was: Patch Available) > Cover add_component_config_initializer with tests > - > > Key: AMBARI-22923 > URL: https://issues.apache.org/jira/browse/AMBARI-22923 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22796) Widget menu goes out of bounds
[ https://issues.apache.org/jira/browse/AMBARI-22796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363805#comment-16363805 ] Antonenko Alexander commented on AMBARI-22796: -- Committed to trunk > Widget menu goes out of bounds > -- > > Key: AMBARI-22796 > URL: https://issues.apache.org/jira/browse/AMBARI-22796 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Attachments: widget-menu-oob.png > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22807) Admin View: Add/Delete Group succeeds, but the group table does not refresh automatically
[ https://issues.apache.org/jira/browse/AMBARI-22807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363806#comment-16363806 ] Antonenko Alexander commented on AMBARI-22807: -- Committed to trunk > Admin View: Add/Delete Group succeeds, but the group table does not refresh > automatically > - > > Key: AMBARI-22807 > URL: https://issues.apache.org/jira/browse/AMBARI-22807 > Project: Ambari > Issue Type: Bug > Components: ambari-admin >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22796) Widget menu goes out of bounds
[ https://issues.apache.org/jira/browse/AMBARI-22796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22796: - Resolution: Fixed Status: Resolved (was: Patch Available) > Widget menu goes out of bounds > -- > > Key: AMBARI-22796 > URL: https://issues.apache.org/jira/browse/AMBARI-22796 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 3.0.0 > > Attachments: widget-menu-oob.png > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22923) Cover add_component_config_initializer with tests
[ https://issues.apache.org/jira/browse/AMBARI-22923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363804#comment-16363804 ] Antonenko Alexander commented on AMBARI-22923: -- Commited to trunk > Cover add_component_config_initializer with tests > - > > Key: AMBARI-22923 > URL: https://issues.apache.org/jira/browse/AMBARI-22923 > Project: Ambari > Issue Type: Task > Components: ambari-web >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22976) Unable to create new user after fresh install of Ambari
[ https://issues.apache.org/jira/browse/AMBARI-22976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363780#comment-16363780 ] Antonenko Alexander commented on AMBARI-22976: -- Pull request for this bug by mistake was linked to AMBARI-22076, pull reqest was successfully merged into trunk. SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8721 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8721/]) AMBARI-22076. Unable to create new user after fresh install of Ambari (hiveww: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=6686d11b114f32e999df25deda5a890b1f0bd1c5]) (edit) ambari-admin/src/main/resources/ui/admin-web/app/views/userManagement/modals/userCreate.html > Unable to create new user after fresh install of Ambari > --- > > Key: AMBARI-22976 > URL: https://issues.apache.org/jira/browse/AMBARI-22976 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.0 > > > Unable to add a user, upon clicking Save the page just does not respond - no > API call, nothing in server logs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22976) Unable to create new user after fresh install of Ambari
[ https://issues.apache.org/jira/browse/AMBARI-22976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-22976: - Resolution: Fixed Status: Resolved (was: Patch Available) > Unable to create new user after fresh install of Ambari > --- > > Key: AMBARI-22976 > URL: https://issues.apache.org/jira/browse/AMBARI-22976 > Project: Ambari > Issue Type: Task > Components: ambari-admin >Affects Versions: 2.7.0 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Major > Fix For: 2.7.0 > > > Unable to add a user, upon clicking Save the page just does not respond - no > API call, nothing in server logs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22982) Logsearch and Kafka broker fails to start
[ https://issues.apache.org/jira/browse/AMBARI-22982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated AMBARI-22982: Labels: pull-request-available (was: ) > Logsearch and Kafka broker fails to start > - > > Key: AMBARI-22982 > URL: https://issues.apache.org/jira/browse/AMBARI-22982 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Labels: pull-request-available > Fix For: 2.7.0 > > Attachments: AMBARI-22982.patch, AMBARI-22982.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22982) Logsearch and Kafka broker fails to start
[ https://issues.apache.org/jira/browse/AMBARI-22982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22982: - Attachment: AMBARI-22982.patch > Logsearch and Kafka broker fails to start > - > > Key: AMBARI-22982 > URL: https://issues.apache.org/jira/browse/AMBARI-22982 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-22982.patch, AMBARI-22982.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AMBARI-22927) Hive View 1.5 Upload Table - not able to change datatype from the dropdown for a wide file
[ https://issues.apache.org/jira/browse/AMBARI-22927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363756#comment-16363756 ] Hudson commented on AMBARI-22927: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1850 (See [https://builds.apache.org/job/Ambari-branch-2.5/1850/]) AMBARI-22927.Hive View 1.5 Upload Table - not able to change datatype (prabhjyotsingh: [https://gitbox.apache.org/repos/asf?p=ambari.git=commit=70fc45c3d0522dd3f1b5baa22e64c03de9c5e4ff]) * (edit) contrib/views/hive-next/src/main/resources/ui/hive-web/app/components/typeahead-widget.js > Hive View 1.5 Upload Table - not able to change datatype from the dropdown > for a wide file > -- > > Key: AMBARI-22927 > URL: https://issues.apache.org/jira/browse/AMBARI-22927 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat >Priority: Blocker > Labels: pull-request-available > Fix For: 2.5.2 > > Time Spent: 3h > Remaining Estimate: 0h > > Steps: > # Go to Hive view 1.5, > # Select type CSV > # Upload the attached file > # Try to change the datatype of last column > # The UI comes back to the leftmost column, showing the first few columns -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22983) Add Hosts is Failing with - Error while bootstrapping: Cannot run program "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py"
Jasmeen Kaur created AMBARI-22983:
-
Summary: Add Hosts is Failing with - Error while bootstrapping:
Cannot run program "/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py"
Key: AMBARI-22983
URL: https://issues.apache.org/jira/browse/AMBARI-22983
Project: Ambari
Issue Type: Bug
Affects Versions: 2.6.2
Environment: CentOS 7
Reporter: Jasmeen Kaur
Add Hosts(UI/API) is broken and the following error is seen .
{code:java}
Error while bootstrapping:
Cannot run program
"/usr/lib/python2.6/site-packages/ambari_server/bootstrap.py": error=2, No such
file or directory
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22927) Hive View 1.5 Upload Table - not able to change datatype from the dropdown for a wide file
[ https://issues.apache.org/jira/browse/AMBARI-22927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-22927: Resolution: Fixed Status: Resolved (was: Patch Available) > Hive View 1.5 Upload Table - not able to change datatype from the dropdown > for a wide file > -- > > Key: AMBARI-22927 > URL: https://issues.apache.org/jira/browse/AMBARI-22927 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat >Priority: Blocker > Labels: pull-request-available > Fix For: 2.5.2 > > Time Spent: 3h > Remaining Estimate: 0h > > Steps: > # Go to Hive view 1.5, > # Select type CSV > # Upload the attached file > # Try to change the datatype of last column > # The UI comes back to the leftmost column, showing the first few columns -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22927) Hive View 1.5 Upload Table - not able to change datatype from the dropdown for a wide file
[ https://issues.apache.org/jira/browse/AMBARI-22927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] venkat updated AMBARI-22927: Status: Patch Available (was: Open) > Hive View 1.5 Upload Table - not able to change datatype from the dropdown > for a wide file > -- > > Key: AMBARI-22927 > URL: https://issues.apache.org/jira/browse/AMBARI-22927 > Project: Ambari > Issue Type: Bug > Components: ambari-views >Affects Versions: 2.5.2 >Reporter: venkat >Assignee: venkat >Priority: Blocker > Labels: pull-request-available > Fix For: 2.5.2 > > Time Spent: 1.5h > Remaining Estimate: 0h > > Steps: > # Go to Hive view 1.5, > # Select type CSV > # Upload the attached file > # Try to change the datatype of last column > # The UI comes back to the leftmost column, showing the first few columns -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22981) Update Hadoop RPC Encryption Properties During Upgrade
[
https://issues.apache.org/jira/browse/AMBARI-22981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated AMBARI-22981:
---
Description:
When *HDP 3.0.0* is installed, clients should have the ability to choose
encrypted communication over RPC when talking to core hadoop components. Today,
the properties that control this are:
- {{core-site.xml : hadoop.rpc.protection = authentication}}
- {{hdfs-site.xml : dfs.data.transfer.protection = authentication}}
The new value of {{privacy}} enables clients to choose an encrypted means of
communication. By keeping {{authentication}} first, it will be taken as the
default mechanism so that wire encryption is not automatically enabled by
accident.
The following properties should be changed to add {{privacy}}:
- {{core-site.xml : hadoop.rpc.protection = authentication,privacy}}
- {{hdfs-site.xml : dfs.data.transfer.protection = authentication,privacy}}
The following are cases when this needs to be performed:
- During Kerberization (this case is covered by AMBARI-22803)
- During a stack upgrade to any version of *HDP 3.0.0*, they should be
automatically merged
Blueprint deployment is not a scenario being covered here.
was:
When *HDP 3.0.0* is installed, clients should have the ability to choose
encrypted communication over RPC when talking to core hadoop components. Today,
the properties that control this are:
- {{core-site.xml : hadoop.rpc.protection = authentication}}
- {{hdfs-site.xml : dfs.data.transfer.protection = authentication}}
The new value of {{privacy}} enables clients to choose an encrypted means of
communication. By keeping {{authentication}} first, it will be taken as the
default mechanism so that wire encryption is not automatically enabled by
accident.
The following properties should be changed to add {{privacy}}:
- {{core-site.xml : hadoop.rpc.protection = authentication,privacy}}
- {{hdfs-site.xml : dfs.data.transfer.protection = authentication,privacy}}
The following are cases when this needs to be performed:
- During Kerberization, the above two properties should be automatically
reconfigured.
- During a stack upgrade to any version of *HDP 3.0.0*, they should be
automatically merged
Blueprint deployment is not a scenario being covered here.
> Update Hadoop RPC Encryption Properties During Upgrade
> --
>
> Key: AMBARI-22981
> URL: https://issues.apache.org/jira/browse/AMBARI-22981
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.7.0
>Reporter: Sandor Molnar
>Assignee: Sandor Molnar
>Priority: Critical
> Fix For: 2.7.0
>
>
> When *HDP 3.0.0* is installed, clients should have the ability to choose
> encrypted communication over RPC when talking to core hadoop components.
> Today, the properties that control this are:
> - {{core-site.xml : hadoop.rpc.protection = authentication}}
> - {{hdfs-site.xml : dfs.data.transfer.protection = authentication}}
> The new value of {{privacy}} enables clients to choose an encrypted means of
> communication. By keeping {{authentication}} first, it will be taken as the
> default mechanism so that wire encryption is not automatically enabled by
> accident.
> The following properties should be changed to add {{privacy}}:
> - {{core-site.xml : hadoop.rpc.protection = authentication,privacy}}
> - {{hdfs-site.xml : dfs.data.transfer.protection = authentication,privacy}}
> The following are cases when this needs to be performed:
> - During Kerberization (this case is covered by AMBARI-22803)
> - During a stack upgrade to any version of *HDP 3.0.0*, they should be
> automatically merged
> Blueprint deployment is not a scenario being covered here.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AMBARI-22982) Logsearch and Kafka broker fails to start
[ https://issues.apache.org/jira/browse/AMBARI-22982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22982: - Status: Patch Available (was: Open) > Logsearch and Kafka broker fails to start > - > > Key: AMBARI-22982 > URL: https://issues.apache.org/jira/browse/AMBARI-22982 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-22982.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AMBARI-22982) Logsearch and Kafka broker fails to start
Andrew Onischuk created AMBARI-22982: Summary: Logsearch and Kafka broker fails to start Key: AMBARI-22982 URL: https://issues.apache.org/jira/browse/AMBARI-22982 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk Fix For: 2.7.0 Attachments: AMBARI-22982.patch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-22982) Logsearch and Kafka broker fails to start
[ https://issues.apache.org/jira/browse/AMBARI-22982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Onischuk updated AMBARI-22982: - Attachment: AMBARI-22982.patch > Logsearch and Kafka broker fails to start > - > > Key: AMBARI-22982 > URL: https://issues.apache.org/jira/browse/AMBARI-22982 > Project: Ambari > Issue Type: Bug >Reporter: Andrew Onischuk >Assignee: Andrew Onischuk >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-22982.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
