[jira] [Updated] (AMBARI-18741) Not able to change the default port ambari server listens to
[ https://issues.apache.org/jira/browse/AMBARI-18741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18741: -- Status: Patch Available (was: Open) > Not able to change the default port ambari server listens to > > > Key: AMBARI-18741 > URL: https://issues.apache.org/jira/browse/AMBARI-18741 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-18741-oct31-updated.patch, AMBARI-18741.patch > > > After including client.api.port in ambari.properties, ambari-server still > tries to connect to port 8080 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18741) Not able to change the default port ambari server listens to
[ https://issues.apache.org/jira/browse/AMBARI-18741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18741: -- Attachment: (was: AMBARI-18741-Oct31.patch) > Not able to change the default port ambari server listens to > > > Key: AMBARI-18741 > URL: https://issues.apache.org/jira/browse/AMBARI-18741 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-18741-oct31-updated.patch, AMBARI-18741.patch > > > After including client.api.port in ambari.properties, ambari-server still > tries to connect to port 8080 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18741) Not able to change the default port ambari server listens to
[ https://issues.apache.org/jira/browse/AMBARI-18741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18741: -- Attachment: AMBARI-18741-oct31-updated.patch Updated the test cases > Not able to change the default port ambari server listens to > > > Key: AMBARI-18741 > URL: https://issues.apache.org/jira/browse/AMBARI-18741 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-18741-oct31-updated.patch, AMBARI-18741.patch > > > After including client.api.port in ambari.properties, ambari-server still > tries to connect to port 8080 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18741) Not able to change the default port ambari server listens to
[ https://issues.apache.org/jira/browse/AMBARI-18741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18741: -- Status: Open (was: Patch Available) > Not able to change the default port ambari server listens to > > > Key: AMBARI-18741 > URL: https://issues.apache.org/jira/browse/AMBARI-18741 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-18741-Oct31.patch, AMBARI-18741.patch > > > After including client.api.port in ambari.properties, ambari-server still > tries to connect to port 8080 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-14163) zookeeper session timeout for hbase should take zookeeper tickTime into account
[ https://issues.apache.org/jira/browse/AMBARI-14163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-14163: Description: With tickTime=2000 in zoo.cfg, I tried to set zookeeper.session.timeout value of 1 min 40 seconds. The change was accepted. However, such timeout is not reachable (it is > 20 times tickTime) Ambari should detect such scenario and warn user. was: With tickTime=2000 in zoo.cfg, I tried to set zookeeper.session.timeout value of 1 min 40 seconds. The change was accepted. However, such timeout is not reachable (it is > 20 times tickTime) Ambari should detect such scenario and warn user. > zookeeper session timeout for hbase should take zookeeper tickTime into > account > --- > > Key: AMBARI-14163 > URL: https://issues.apache.org/jira/browse/AMBARI-14163 > Project: Ambari > Issue Type: Bug >Reporter: Ted Yu > > With tickTime=2000 in zoo.cfg, I tried to set zookeeper.session.timeout value > of 1 min 40 seconds. > The change was accepted. > However, such timeout is not reachable (it is > 20 times tickTime) > Ambari should detect such scenario and warn user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-16278) Give more time for HBase system tables to be assigned
[ https://issues.apache.org/jira/browse/AMBARI-16278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated AMBARI-16278: Description: We have observed extended cluster downtime due to HBase system tables not being assigned at cluster start up. The default values for the following two parameters are too low: hbase.regionserver.executor.openregion.threads (default: 3) hbase.master.namespace.init.timeout (default: 30) We set hbase.regionserver.executor.openregion.threads=200 and hbase.master.namespace.init.timeout=240 in some case to work around HBASE-14190. Ambari can use 20 for hbase.regionserver.executor.openregion.threads and 240 for hbase.master.namespace.init.timeout as default value. was: We have observed extended cluster downtime due to HBase system tables not being assigned at cluster start up. The default values for the following two parameters are too low: hbase.regionserver.executor.openregion.threads (default: 3) hbase.master.namespace.init.timeout (default: 30) We set hbase.regionserver.executor.openregion.threads=200 and hbase.master.namespace.init.timeout=240 in some case to work around HBASE-14190. Ambari can use 20 for hbase.regionserver.executor.openregion.threads and 240 for hbase.master.namespace.init.timeout as default value. > Give more time for HBase system tables to be assigned > - > > Key: AMBARI-16278 > URL: https://issues.apache.org/jira/browse/AMBARI-16278 > Project: Ambari > Issue Type: Improvement >Reporter: Ted Yu > > We have observed extended cluster downtime due to HBase system tables not > being assigned at cluster start up. > The default values for the following two parameters are too low: > hbase.regionserver.executor.openregion.threads (default: 3) > hbase.master.namespace.init.timeout (default: 30) > We set hbase.regionserver.executor.openregion.threads=200 and > hbase.master.namespace.init.timeout=240 in some case to work around > HBASE-14190. > Ambari can use 20 for hbase.regionserver.executor.openregion.threads and > 240 for hbase.master.namespace.init.timeout as default value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AMBARI-18746) Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
[
https://issues.apache.org/jira/browse/AMBARI-18746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ying Cao reopened AMBARI-18746:
---
Click "Resolve" by mistake
> Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
> ---
>
> Key: AMBARI-18746
> URL: https://issues.apache.org/jira/browse/AMBARI-18746
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
> Environment: Redhat 6.6, Sqoop 1.4.6+Hadoop 2.7.2
>Reporter: Ying Cao
>Priority: Minor
> Fix For: 2.4.1
>
> Attachments: AMBARI-18746.1.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> The parameter hadoop_home is pointed to hbase-client in params_linux.py, and
> need to be updated.
> ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py
> # For stack versions supporting rolling upgrade
> if stack_version_formatted and
>
> hadoop_home = format("{stack_root}/current/hbase-client")
> ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18758) Livy configuration change for upgrade
[ https://issues.apache.org/jira/browse/AMBARI-18758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Zhang updated AMBARI-18758: Status: Patch Available (was: Open) > Livy configuration change for upgrade > - > > Key: AMBARI-18758 > URL: https://issues.apache.org/jira/browse/AMBARI-18758 > Project: Ambari > Issue Type: Bug >Affects Versions: 2.4.0 >Reporter: Jeff Zhang >Assignee: Jeff Zhang > Fix For: 2.5.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18758) Livy configuration change for upgrade
Jeff Zhang created AMBARI-18758: --- Summary: Livy configuration change for upgrade Key: AMBARI-18758 URL: https://issues.apache.org/jira/browse/AMBARI-18758 Project: Ambari Issue Type: Bug Affects Versions: 2.4.0 Reporter: Jeff Zhang Assignee: Jeff Zhang Fix For: 2.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18748) ambari-server upgrade fail (from 2.2.2.0/2.4.0.0/2.4.0.1/2.4.1.0 to 2.4.2.0 )
[
https://issues.apache.org/jira/browse/AMBARI-18748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18748:
---
Attachment: AMBARI-18748.patch
> ambari-server upgrade fail (from 2.2.2.0/2.4.0.0/2.4.0.1/2.4.1.0 to 2.4.2.0 )
> -
>
> Key: AMBARI-18748
> URL: https://issues.apache.org/jira/browse/AMBARI-18748
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.2
>
> Attachments: AMBARI-18748.patch
>
>
> 1)Install old version regarding env.
> 2)Make ambari only upgrade
> Actual result:
> ambari-server upgrade fell
> {code}
> 2016-10-28 01:20:19,601 ERROR
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
> *Command '[ambari-server upgrade --verbose, ]'
> failed with exitcode 11 ***
> 2016-10-28 01:20:19,603 INFO
> com.hw.ambari.ui.util.cluster_managers.UpgradeClusterManager.upgrade_schema():
> Result of ambari-server upgrade command:
> 2016-10-28 01:20:19,603 INFO
> com.hw.ambari.ui.util.cluster_managers.UpgradeClusterManager.upgrade_schema():
> [OUTPUT STREAM]
> Using python /usr/bin/python
> Upgrading ambari-server
> Updating properties in ambari.properties ...
> WARNING: Original file ambari-env.sh kept
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: No mpack replay logs found. Skipping replaying mpack commands
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Fixing database objects owner
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Ambari Server configured for MySQL. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? INFO: Loading properties from
> /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Upgrading database schema
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: /usr/lib/jvm/java-7-openjdk-amd64/bin/java -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/mysql-connector-java.jar'
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
> /var/log/ambari-server/ambari-server.out 2>&1
> INFO: Return code from schema upgrade command, retcode = 1
> Error output from schema upgrade command:
> Exception in thread "main" org.apache.ambari.server.AmbariException: Entity
> must be managed to call remove:
> org.apache.ambari.server.orm.entities.PrincipalEntity@5e81dbde, try merging
> the detached and try the remove again.
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:356)
> Caused by: java.lang.IllegalArgumentException: Entity must be managed to call
> remove: org.apache.ambari.server.orm.entities.PrincipalEntity@5e81dbde, try
> merging the detached and try the remove again.
> at
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.performRemove(UnitOfWorkImpl.java:3578)
> at
> org.eclipse.persistence.internal.jpa.EntityManagerImpl.remove(EntityManagerImpl.java:574)
> at
> org.apache.ambari.server.orm.dao.PrincipalDAO.remove(PrincipalDAO.java:132)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:128)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog242.convertRolePrincipals(UpgradeCatalog242.java:213)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog242.executeDMLUpdates(UpgradeCatalog242.java:122)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:908)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> ... 1 more
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Ambari server upgrade failed. Please look at
> /var/log/ambari-server/ambari-server.log, for more details.
> ERROR: Exiting
[jira] [Updated] (AMBARI-18748) ambari-server upgrade fail (from 2.2.2.0/2.4.0.0/2.4.0.1/2.4.1.0 to 2.4.2.0 )
[
https://issues.apache.org/jira/browse/AMBARI-18748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18748:
---
Attachment: (was: AMBARI-18748.patch)
> ambari-server upgrade fail (from 2.2.2.0/2.4.0.0/2.4.0.1/2.4.1.0 to 2.4.2.0 )
> -
>
> Key: AMBARI-18748
> URL: https://issues.apache.org/jira/browse/AMBARI-18748
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.2
>
> Attachments: AMBARI-18748.patch
>
>
> 1)Install old version regarding env.
> 2)Make ambari only upgrade
> Actual result:
> ambari-server upgrade fell
> {code}
> 2016-10-28 01:20:19,601 ERROR
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
> *Command '[ambari-server upgrade --verbose, ]'
> failed with exitcode 11 ***
> 2016-10-28 01:20:19,603 INFO
> com.hw.ambari.ui.util.cluster_managers.UpgradeClusterManager.upgrade_schema():
> Result of ambari-server upgrade command:
> 2016-10-28 01:20:19,603 INFO
> com.hw.ambari.ui.util.cluster_managers.UpgradeClusterManager.upgrade_schema():
> [OUTPUT STREAM]
> Using python /usr/bin/python
> Upgrading ambari-server
> Updating properties in ambari.properties ...
> WARNING: Original file ambari-env.sh kept
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: No mpack replay logs found. Skipping replaying mpack commands
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Fixing database objects owner
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Ambari Server configured for MySQL. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? INFO: Loading properties from
> /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Upgrading database schema
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: /usr/lib/jvm/java-7-openjdk-amd64/bin/java -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/mysql-connector-java.jar'
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
> /var/log/ambari-server/ambari-server.out 2>&1
> INFO: Return code from schema upgrade command, retcode = 1
> Error output from schema upgrade command:
> Exception in thread "main" org.apache.ambari.server.AmbariException: Entity
> must be managed to call remove:
> org.apache.ambari.server.orm.entities.PrincipalEntity@5e81dbde, try merging
> the detached and try the remove again.
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:356)
> Caused by: java.lang.IllegalArgumentException: Entity must be managed to call
> remove: org.apache.ambari.server.orm.entities.PrincipalEntity@5e81dbde, try
> merging the detached and try the remove again.
> at
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.performRemove(UnitOfWorkImpl.java:3578)
> at
> org.eclipse.persistence.internal.jpa.EntityManagerImpl.remove(EntityManagerImpl.java:574)
> at
> org.apache.ambari.server.orm.dao.PrincipalDAO.remove(PrincipalDAO.java:132)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:128)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog242.convertRolePrincipals(UpgradeCatalog242.java:213)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog242.executeDMLUpdates(UpgradeCatalog242.java:122)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:908)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> ... 1 more
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Ambari server upgrade failed. Please look at
> /var/log/ambari-server/ambari-server.log, for more details.
> ERROR:
[jira] [Commented] (AMBARI-18757) DB configs consistency check failed after upgrade from 2.1.1 to 2.4.2 (stack 2.3)
[
https://issues.apache.org/jira/browse/AMBARI-18757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623971#comment-15623971
]
Hadoop QA commented on AMBARI-18757:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836247/AMBARI-18757.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9071//console
This message is automatically generated.
> DB configs consistency check failed after upgrade from 2.1.1 to 2.4.2 (stack
> 2.3)
> -
>
> Key: AMBARI-18757
> URL: https://issues.apache.org/jira/browse/AMBARI-18757
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.2
>
> Attachments: AMBARI-18757.patch
>
>
> 1)Install old version regarding env. (enable AD security)
> 2)Make ambari only upgrade
> Actual result:
> DB configs consistency check failed after upgrade from 2.1.1 to 2.4.2 (stack
> 2.3)
> {code}
> 2016-10-28 02:43:15,878 ERROR - Required config(s):
> storm-cluster-log4j,storm-worker-log4j is(are) not available for service
> STORM with service config version 4 in cluster cl1
> 2016-10-28 02:43:15,917 INFO - *** Check
> database completed ***
> 2016-10-28 02:47:01,109 INFO - *** Check
> database started ***
> 2016-10-28 02:47:12,523 INFO - Checking for configs not mapped to any cluster
> 2016-10-28 02:47:12,538 INFO - Checking for configs selected more than once
> 2016-10-28 02:47:12,541 INFO - Checking for hosts without state
> 2016-10-28 02:47:12,544 INFO - Checking host component states count equals
> host component desired states count
> 2016-10-28 02:47:12,548 INFO - Checking services and their configs
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / PIG
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / SPARK
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / MAPREDUCE2
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / YARN
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / FALCON
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / SLIDER
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / HIVE
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / TEZ
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / ZOOKEEPER
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / STORM
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / SQOOP
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / HBASE
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / OOZIE
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / FLUME
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / KNOX
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / KERBEROS
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / HDFS
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / AMBARI_METRICS
> 2016-10-28 02:47:17,682 ERROR - Required config(s): sqoop-site is(are) not
> available for service SQOOP with service config version 1 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> falcon-client.properties,falcon-log4j is(are) not available for service
> FALCON with service config version 3 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> spark-thrift-sparkconf,spark-hive-site-override is(are) not available for
> service SPARK with service config version 3 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> knoxsso-topology,admin-topology is(are) not available for service KNOX with
> service config version 3 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> ams-ssl-client,ams-ssl-server,ams-grafana-env,ams-grafana-ini is(are) not
> available for service AMBARI_METRICS with service config version 3 in cluster
> cl1
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18355) Introduce conditional dependencies in stack defition to handle blueprint validation gracefully
[
https://issues.apache.org/jira/browse/AMBARI-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623968#comment-15623968
]
Hadoop QA commented on AMBARI-18355:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836253/AMBARI-18355_v8.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.agent.TestHeartbeatHandler
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9070//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9070//console
This message is automatically generated.
> Introduce conditional dependencies in stack defition to handle blueprint
> validation gracefully
> --
>
> Key: AMBARI-18355
> URL: https://issues.apache.org/jira/browse/AMBARI-18355
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: trunk
>Reporter: Amruta Borkar
>Assignee: Amruta Borkar
> Fix For: trunk
>
> Attachments: AMBARI-18355.patch, AMBARI-18355_v6.patch,
> AMBARI-18355_v7.patch, AMBARI-18355_v8.patch, Adding Conditional
> Dependencies.pdf
>
>
> Currently stack definitions do not list conditional dependencies, adding
> those to the stack definitions would make it easy to validate errors in case
> of blueprint deployment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18743) Improve wizard styles and apply on Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623928#comment-15623928 ] Hudson commented on AMBARI-18743: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5897 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5897/]) AMBARI-18743. Improve wizard styles and apply on Ambari.(xiwang) (xiwang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=334d4ccd3d54035b5bc6bfc23ab4548366f37c0d]) * (edit) ambari-web/app/templates/main/admin/highAvailability/hawq/addStandby/wizard.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/hawq/removeStandby/wizard.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/hawq/addStandby/step1.hbs * (edit) ambari-web/app/templates/main/admin/kerberos/step2.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/resourceManager/wizard.hbs * (edit) ambari-web/app/templates/main/alerts/add_alert_definition/step3.hbs * (edit) ambari-web/app/templates/common/progress.hbs * (edit) ambari-web/app/templates/main/admin/kerberos/step5.hbs * (edit) ambari-web/app/templates/wizard/step6.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/nameNode/rollbackHA/rollback_wizard.hbs * (edit) ambari-web/app/templates/wizard/step2.hbs * (edit) ambari-web/app/templates/wizard/step1.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/journalNode/step2.hbs * (edit) ambari-web/app/templates/main/admin/kerberos/step3.hbs * (edit) ambari-web/app/templates/main/service/widgets/create/step3.hbs * (edit) ambari-web/app/templates/main/alerts/add_alert_definition/add_alert_definition.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/nameNode/step4.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/nameNode/wizard.hbs * (edit) ambari-web/app/templates/main/alerts/add_alert_definition/step1.hbs * (edit) ambari-web/app/templates/main/service/reassign.hbs * (edit) ambari-web/app/templates/wizard/step4.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/rangerAdmin/step3.hbs * (edit) ambari-web/app/templates/main/service/widgets/create/step2_number.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/hawq/removeStandby/step1.hbs * (edit) ambari-web/app/templates/main/service/add.hbs * (edit) ambari-web/app/templates/main/service/widgets/create/step1.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/hawq/addStandby/step3.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/journalNode/step1.hbs * (edit) ambari-web/app/templates/wizard/step8.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/journalNode/wizard.hbs * (edit) ambari-web/app/templates/wizard/step7.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/rangerAdmin/wizard.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/nameNode/step8.hbs * (edit) ambari-web/app/templates/wizard/step10.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/resourceManager/step3.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/rangerAdmin/step1.hbs * (edit) ambari-web/app/templates/installer.hbs * (edit) ambari-web/app/templates/wizard/step3.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/nameNode/step1.hbs * (edit) ambari-web/app/templates/main/admin/kerberos/wizard.hbs * (edit) ambari-web/app/templates/common/assign_master_components.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/hawq/activateStandby/step1.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/nameNode/rollbackHA/step1.hbs * (edit) ambari-web/app/templates/main/host/add.hbs * (edit) ambari-web/app/templates/main/admin/kerberos/step1.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/nameNode/step3.hbs * (edit) ambari-web/app/templates/main/service/widgets/create/wizard.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/nameNode/step6.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/hawq/activateStandby/step2.hbs * (edit) ambari-web/app/templates/main/admin/kerberos/step4.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/nameNode/rollbackHA/step2.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/hawq/activateStandby/wizard.hbs * (edit) ambari-web/app/templates/main/alerts/add_alert_definition/step2.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/journalNode/step5.hbs * (edit) ambari-web/app/templates/main/service/widgets/create/step2_graph.hbs * (edit) ambari-web/app/templates/wizard/step0.hbs * (edit) ambari-web/app/templates/main/service/widgets/create/step2.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/hawq/removeStandby/step2.hbs * (edit) ambari-web/app/templates/main/admin/highAvailability/nameNode/rollbackHA/step3.hbs * (edit)
[jira] [Updated] (AMBARI-18355) Introduce conditional dependencies in stack defition to handle blueprint validation gracefully
[ https://issues.apache.org/jira/browse/AMBARI-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-18355: --- Status: Patch Available (was: In Progress) > Introduce conditional dependencies in stack defition to handle blueprint > validation gracefully > -- > > Key: AMBARI-18355 > URL: https://issues.apache.org/jira/browse/AMBARI-18355 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-18355.patch, AMBARI-18355_v6.patch, > AMBARI-18355_v7.patch, AMBARI-18355_v8.patch, Adding Conditional > Dependencies.pdf > > > Currently stack definitions do not list conditional dependencies, adding > those to the stack definitions would make it easy to validate errors in case > of blueprint deployment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18355) Introduce conditional dependencies in stack defition to handle blueprint validation gracefully
[ https://issues.apache.org/jira/browse/AMBARI-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-18355: --- Status: Open (was: Patch Available) > Introduce conditional dependencies in stack defition to handle blueprint > validation gracefully > -- > > Key: AMBARI-18355 > URL: https://issues.apache.org/jira/browse/AMBARI-18355 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-18355.patch, AMBARI-18355_v6.patch, > AMBARI-18355_v7.patch, AMBARI-18355_v8.patch, Adding Conditional > Dependencies.pdf > > > Currently stack definitions do not list conditional dependencies, adding > those to the stack definitions would make it easy to validate errors in case > of blueprint deployment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18355) Introduce conditional dependencies in stack defition to handle blueprint validation gracefully
[ https://issues.apache.org/jira/browse/AMBARI-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-18355: --- Attachment: AMBARI-18355_v8.patch > Introduce conditional dependencies in stack defition to handle blueprint > validation gracefully > -- > > Key: AMBARI-18355 > URL: https://issues.apache.org/jira/browse/AMBARI-18355 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-18355.patch, AMBARI-18355_v6.patch, > AMBARI-18355_v7.patch, AMBARI-18355_v8.patch, Adding Conditional > Dependencies.pdf > > > Currently stack definitions do not list conditional dependencies, adding > those to the stack definitions would make it easy to validate errors in case > of blueprint deployment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18355) Introduce conditional dependencies in stack defition to handle blueprint validation gracefully
[ https://issues.apache.org/jira/browse/AMBARI-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-18355: --- Attachment: (was: AMBARI-18355_v5.patch) > Introduce conditional dependencies in stack defition to handle blueprint > validation gracefully > -- > > Key: AMBARI-18355 > URL: https://issues.apache.org/jira/browse/AMBARI-18355 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-18355.patch, AMBARI-18355_v6.patch, > AMBARI-18355_v7.patch, AMBARI-18355_v8.patch, Adding Conditional > Dependencies.pdf > > > Currently stack definitions do not list conditional dependencies, adding > those to the stack definitions would make it easy to validate errors in case > of blueprint deployment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18355) Introduce conditional dependencies in stack defition to handle blueprint validation gracefully
[ https://issues.apache.org/jira/browse/AMBARI-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amruta Borkar updated AMBARI-18355: --- Attachment: (was: AMBARI-18355_v4.patch) > Introduce conditional dependencies in stack defition to handle blueprint > validation gracefully > -- > > Key: AMBARI-18355 > URL: https://issues.apache.org/jira/browse/AMBARI-18355 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: trunk >Reporter: Amruta Borkar >Assignee: Amruta Borkar > Fix For: trunk > > Attachments: AMBARI-18355.patch, AMBARI-18355_v6.patch, > AMBARI-18355_v7.patch, AMBARI-18355_v8.patch, Adding Conditional > Dependencies.pdf > > > Currently stack definitions do not list conditional dependencies, adding > those to the stack definitions would make it easy to validate errors in case > of blueprint deployment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (AMBARI-17126) Provide Ambari Server HA (active-passive)
[
https://issues.apache.org/jira/browse/AMBARI-17126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623872#comment-15623872
]
Swapan Shridhar edited comment on AMBARI-17126 at 11/1/16 12:13 AM:
[~allmusic76]
{quote}
1.) Is this actively being looked at for 2.5? (Is there an estimated release
date for 2.5?)
{quote}
- It is not for Ambari-2.5.
{quote}
2.) Also, why exactly was AMBARI-7896 closed and being tracked here?
Active-Passive fault tolerance/redundancy isn't necessarily the same concept as
high availability.
{quote}
- Here also, we are working on having one Ambari server active at one point of
time and other passive/non-active, and we are not doing the load balancing part
as part of this JIRA.
was (Author: swapanshridhar):
[~allmusic76]
{quote}
1.) Is this actively being looked at for 2.5? (Is there an estimated release
date for 2.5?)
{quote}
- It is not for Ambari-2.5.
{quote}
2.) Also, why exactly was AMBARI-7896 closed and being tracked here?
Active-Passive fault tolerance/redundancy isn't necessarily the same concept as
high availability.
{quote}
Here also, we are working on having one Ambari server active at one point of
time and other passive/non-active, and we are not doing the load balancing part
as part of this JIRA.
> Provide Ambari Server HA (active-passive)
> -
>
> Key: AMBARI-17126
> URL: https://issues.apache.org/jira/browse/AMBARI-17126
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jeff Sposetti
>Assignee: Swapan Shridhar
> Fix For: trunk
>
>
> Ability to configure Ambari Server active-passive setup behind Load balancer.
> -Both servers should point to the same database (external to Ambari Server) .
> Preferably Server.jdbc.hostname should point to a HA DB Cluster from both
> server's ambari.properties.
> -Load Balancer (preferably an external solution, like F5, Cisco, Brocade etc)
> to create VIP and use the Ambari server as Real to direct traffic to either
> host rather than keeping one as Standby (Agent ini file should point to DNS
> of VIP rather than to a server directly)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-17126) Provide Ambari Server HA (active-passive)
[
https://issues.apache.org/jira/browse/AMBARI-17126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623872#comment-15623872
]
Swapan Shridhar commented on AMBARI-17126:
--
[~allmusic76]
{quote}
1.) Is this actively being looked at for 2.5? (Is there an estimated release
date for 2.5?)
{quote}
- It is not for Ambari-2.5.
{quote}
2.) Also, why exactly was AMBARI-7896 closed and being tracked here?
Active-Passive fault tolerance/redundancy isn't necessarily the same concept as
high availability.
{quote}
Here also, we are working on having one Ambari server active at one point of
time and other passive/non-active, and we are not doing the load balancing part
as part of this JIRA.
> Provide Ambari Server HA (active-passive)
> -
>
> Key: AMBARI-17126
> URL: https://issues.apache.org/jira/browse/AMBARI-17126
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jeff Sposetti
>Assignee: Swapan Shridhar
> Fix For: trunk
>
>
> Ability to configure Ambari Server active-passive setup behind Load balancer.
> -Both servers should point to the same database (external to Ambari Server) .
> Preferably Server.jdbc.hostname should point to a HA DB Cluster from both
> server's ambari.properties.
> -Load Balancer (preferably an external solution, like F5, Cisco, Brocade etc)
> to create VIP and use the Ambari server as Real to direct traffic to either
> host rather than keeping one as Standby (Agent ini file should point to DNS
> of VIP rather than to a server directly)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18743) Improve wizard styles and apply on Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623863#comment-15623863 ] Xi Wang commented on AMBARI-18743: -- Got +1 from review board. Committed to trunk. > Improve wizard styles and apply on Ambari > - > > Key: AMBARI-18743 > URL: https://issues.apache.org/jira/browse/AMBARI-18743 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-18743.patch > > > Wizard improvements on Ambari UI: > The footer of the wizard (back & next button area) should be separated, not > with the content panel > The content panel should be on a white canvas, separated from step > title/description. > Changes from the style guides: > 1. Narrow down wizard nav items. > 2. In wizard header and footer, should reduce the padding > 3. In wizard content, there should be no border for content panel, also > should reduce step title margin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-18743) Improve wizard styles and apply on Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang resolved AMBARI-18743. -- Resolution: Fixed > Improve wizard styles and apply on Ambari > - > > Key: AMBARI-18743 > URL: https://issues.apache.org/jira/browse/AMBARI-18743 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-18743.patch > > > Wizard improvements on Ambari UI: > The footer of the wizard (back & next button area) should be separated, not > with the content panel > The content panel should be on a white canvas, separated from step > title/description. > Changes from the style guides: > 1. Narrow down wizard nav items. > 2. In wizard header and footer, should reduce the padding > 3. In wizard content, there should be no border for content panel, also > should reduce step title margin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18743) Improve wizard styles and apply on Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623858#comment-15623858 ] Xi Wang commented on AMBARI-18743: -- 26147 tests complete (20 seconds) 57 tests pending > Improve wizard styles and apply on Ambari > - > > Key: AMBARI-18743 > URL: https://issues.apache.org/jira/browse/AMBARI-18743 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-18743.patch > > > Wizard improvements on Ambari UI: > The footer of the wizard (back & next button area) should be separated, not > with the content panel > The content panel should be on a white canvas, separated from step > title/description. > Changes from the style guides: > 1. Narrow down wizard nav items. > 2. In wizard header and footer, should reduce the padding > 3. In wizard content, there should be no border for content panel, also > should reduce step title margin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18743) Improve wizard styles and apply on Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang updated AMBARI-18743: - Attachment: AMBARI-18743.patch > Improve wizard styles and apply on Ambari > - > > Key: AMBARI-18743 > URL: https://issues.apache.org/jira/browse/AMBARI-18743 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Xi Wang >Assignee: Xi Wang > Fix For: 3.0.0 > > Attachments: AMBARI-18743.patch > > > Wizard improvements on Ambari UI: > The footer of the wizard (back & next button area) should be separated, not > with the content panel > The content panel should be on a white canvas, separated from step > title/description. > Changes from the style guides: > 1. Narrow down wizard nav items. > 2. In wizard header and footer, should reduce the padding > 3. In wizard content, there should be no border for content panel, also > should reduce step title margin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18757) DB configs consistency check failed after upgrade from 2.1.1 to 2.4.2 (stack 2.3)
[
https://issues.apache.org/jira/browse/AMBARI-18757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18757:
---
Status: Patch Available (was: Open)
> DB configs consistency check failed after upgrade from 2.1.1 to 2.4.2 (stack
> 2.3)
> -
>
> Key: AMBARI-18757
> URL: https://issues.apache.org/jira/browse/AMBARI-18757
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.2
>
> Attachments: AMBARI-18757.patch
>
>
> 1)Install old version regarding env. (enable AD security)
> 2)Make ambari only upgrade
> Actual result:
> DB configs consistency check failed after upgrade from 2.1.1 to 2.4.2 (stack
> 2.3)
> {code}
> 2016-10-28 02:43:15,878 ERROR - Required config(s):
> storm-cluster-log4j,storm-worker-log4j is(are) not available for service
> STORM with service config version 4 in cluster cl1
> 2016-10-28 02:43:15,917 INFO - *** Check
> database completed ***
> 2016-10-28 02:47:01,109 INFO - *** Check
> database started ***
> 2016-10-28 02:47:12,523 INFO - Checking for configs not mapped to any cluster
> 2016-10-28 02:47:12,538 INFO - Checking for configs selected more than once
> 2016-10-28 02:47:12,541 INFO - Checking for hosts without state
> 2016-10-28 02:47:12,544 INFO - Checking host component states count equals
> host component desired states count
> 2016-10-28 02:47:12,548 INFO - Checking services and their configs
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / PIG
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / SPARK
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / MAPREDUCE2
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / YARN
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / FALCON
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / SLIDER
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / HIVE
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / TEZ
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / ZOOKEEPER
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / STORM
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / SQOOP
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / HBASE
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / OOZIE
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / FLUME
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / KNOX
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / KERBEROS
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / HDFS
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / AMBARI_METRICS
> 2016-10-28 02:47:17,682 ERROR - Required config(s): sqoop-site is(are) not
> available for service SQOOP with service config version 1 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> falcon-client.properties,falcon-log4j is(are) not available for service
> FALCON with service config version 3 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> spark-thrift-sparkconf,spark-hive-site-override is(are) not available for
> service SPARK with service config version 3 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> knoxsso-topology,admin-topology is(are) not available for service KNOX with
> service config version 3 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> ams-ssl-client,ams-ssl-server,ams-grafana-env,ams-grafana-ini is(are) not
> available for service AMBARI_METRICS with service config version 3 in cluster
> cl1
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18757) DB configs consistency check failed after upgrade from 2.1.1 to 2.4.2 (stack 2.3)
[
https://issues.apache.org/jira/browse/AMBARI-18757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18757:
---
Attachment: AMBARI-18757.patch
> DB configs consistency check failed after upgrade from 2.1.1 to 2.4.2 (stack
> 2.3)
> -
>
> Key: AMBARI-18757
> URL: https://issues.apache.org/jira/browse/AMBARI-18757
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.2
>
> Attachments: AMBARI-18757.patch
>
>
> 1)Install old version regarding env. (enable AD security)
> 2)Make ambari only upgrade
> Actual result:
> DB configs consistency check failed after upgrade from 2.1.1 to 2.4.2 (stack
> 2.3)
> {code}
> 2016-10-28 02:43:15,878 ERROR - Required config(s):
> storm-cluster-log4j,storm-worker-log4j is(are) not available for service
> STORM with service config version 4 in cluster cl1
> 2016-10-28 02:43:15,917 INFO - *** Check
> database completed ***
> 2016-10-28 02:47:01,109 INFO - *** Check
> database started ***
> 2016-10-28 02:47:12,523 INFO - Checking for configs not mapped to any cluster
> 2016-10-28 02:47:12,538 INFO - Checking for configs selected more than once
> 2016-10-28 02:47:12,541 INFO - Checking for hosts without state
> 2016-10-28 02:47:12,544 INFO - Checking host component states count equals
> host component desired states count
> 2016-10-28 02:47:12,548 INFO - Checking services and their configs
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / PIG
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / SPARK
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / MAPREDUCE2
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / YARN
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / FALCON
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / SLIDER
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / HIVE
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / TEZ
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / ZOOKEEPER
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / STORM
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / SQOOP
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / HBASE
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / OOZIE
> 2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / FLUME
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / KNOX
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / KERBEROS
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / HDFS
> 2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / AMBARI_METRICS
> 2016-10-28 02:47:17,682 ERROR - Required config(s): sqoop-site is(are) not
> available for service SQOOP with service config version 1 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> falcon-client.properties,falcon-log4j is(are) not available for service
> FALCON with service config version 3 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> spark-thrift-sparkconf,spark-hive-site-override is(are) not available for
> service SPARK with service config version 3 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> knoxsso-topology,admin-topology is(are) not available for service KNOX with
> service config version 3 in cluster cl1
> 2016-10-28 02:47:17,682 ERROR - Required config(s):
> ams-ssl-client,ams-ssl-server,ams-grafana-env,ams-grafana-ini is(are) not
> available for service AMBARI_METRICS with service config version 3 in cluster
> cl1
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18757) DB configs consistency check failed after upgrade from 2.1.1 to 2.4.2 (stack 2.3)
Vitaly Brodetskyi created AMBARI-18757:
--
Summary: DB configs consistency check failed after upgrade from
2.1.1 to 2.4.2 (stack 2.3)
Key: AMBARI-18757
URL: https://issues.apache.org/jira/browse/AMBARI-18757
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.2
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Blocker
Fix For: 2.4.2
1)Install old version regarding env. (enable AD security)
2)Make ambari only upgrade
Actual result:
DB configs consistency check failed after upgrade from 2.1.1 to 2.4.2 (stack
2.3)
{code}
2016-10-28 02:43:15,878 ERROR - Required config(s):
storm-cluster-log4j,storm-worker-log4j is(are) not available for service STORM
with service config version 4 in cluster cl1
2016-10-28 02:43:15,917 INFO - *** Check database
completed ***
2016-10-28 02:47:01,109 INFO - *** Check database
started ***
2016-10-28 02:47:12,523 INFO - Checking for configs not mapped to any cluster
2016-10-28 02:47:12,538 INFO - Checking for configs selected more than once
2016-10-28 02:47:12,541 INFO - Checking for hosts without state
2016-10-28 02:47:12,544 INFO - Checking host component states count equals
host component desired states count
2016-10-28 02:47:12,548 INFO - Checking services and their configs
2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / PIG
2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / SPARK
2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / MAPREDUCE2
2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / YARN
2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / FALCON
2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / SLIDER
2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / HIVE
2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / TEZ
2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / ZOOKEEPER
2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / STORM
2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / SQOOP
2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / HBASE
2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / OOZIE
2016-10-28 02:47:17,674 INFO - Processing HDP-2.3 / FLUME
2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / KNOX
2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / KERBEROS
2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / HDFS
2016-10-28 02:47:17,675 INFO - Processing HDP-2.3 / AMBARI_METRICS
2016-10-28 02:47:17,682 ERROR - Required config(s): sqoop-site is(are) not
available for service SQOOP with service config version 1 in cluster cl1
2016-10-28 02:47:17,682 ERROR - Required config(s):
falcon-client.properties,falcon-log4j is(are) not available for service FALCON
with service config version 3 in cluster cl1
2016-10-28 02:47:17,682 ERROR - Required config(s):
spark-thrift-sparkconf,spark-hive-site-override is(are) not available for
service SPARK with service config version 3 in cluster cl1
2016-10-28 02:47:17,682 ERROR - Required config(s):
knoxsso-topology,admin-topology is(are) not available for service KNOX with
service config version 3 in cluster cl1
2016-10-28 02:47:17,682 ERROR - Required config(s):
ams-ssl-client,ams-ssl-server,ams-grafana-env,ams-grafana-ini is(are) not
available for service AMBARI_METRICS with service config version 3 in cluster
cl1
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18756) Grafana failed to start after enabling Wire Encryption
Vivek Rathod created AMBARI-18756:
-
Summary: Grafana failed to start after enabling Wire Encryption
Key: AMBARI-18756
URL: https://issues.apache.org/jira/browse/AMBARI-18756
Project: Ambari
Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Vivek Rathod
Fix For: 2.5.0
Grafana failed to start after enabling Wire Encryption
{code}
Traceback (most recent call last):
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
line 69, in
AmsGrafana().execute()
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 280, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana.py",
line 50, in start
create_ams_datasource()
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
line 205, in create_ams_datasource
response = perform_grafana_get_call(GRAFANA_DATASOURCE_URL, server)
File
"/var/lib/ambari-agent/cache/common-services/AMBARI_METRICS/0.1.0/package/scripts/metrics_grafana_util.py",
line 67, in perform_grafana_get_call
raise Fail("Ambari Metrics Grafana update failed due to: %s" % str(ex))
resource_management.core.exceptions.Fail: Ambari Metrics Grafana update failed
due to: [Errno 111] Connection refused
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-17126) Provide Ambari Server HA (active-passive)
[ https://issues.apache.org/jira/browse/AMBARI-17126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapan Shridhar updated AMBARI-17126: - Fix Version/s: (was: 2.5.0) trunk > Provide Ambari Server HA (active-passive) > - > > Key: AMBARI-17126 > URL: https://issues.apache.org/jira/browse/AMBARI-17126 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Jeff Sposetti >Assignee: Swapan Shridhar > Fix For: trunk > > > Ability to configure Ambari Server active-passive setup behind Load balancer. > -Both servers should point to the same database (external to Ambari Server) . > Preferably Server.jdbc.hostname should point to a HA DB Cluster from both > server's ambari.properties. > -Load Balancer (preferably an external solution, like F5, Cisco, Brocade etc) > to create VIP and use the Ambari server as Real to direct traffic to either > host rather than keeping one as Standby (Agent ini file should point to DNS > of VIP rather than to a server directly) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18754) Pig, Tez service checks getting timed out after Wire Encryption
[
https://issues.apache.org/jira/browse/AMBARI-18754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Rathod updated AMBARI-18754:
--
Description:
Piz, Tez service checks are getting timed out after Enabling Wire Encryption.
was:
Piz, Tez service checks are getting timed out after Enabling Wire Encryption.
{code}
2016-10-31 21:27:31,791 [PigTezLauncher-0] INFO
org.apache.tez.client.TezClient - Stage directory /tmp/ambari-qa/staging
doesn't exist and is created
2016-10-31 21:27:31,837 [PigTezLauncher-0] INFO
org.apache.tez.client.TezClient - Tez system stage directory
hdfs://nat-r7-bwqs-spark2hive-3.openstacklocal:8020/tmp/ambari-qa/staging/.tez/application_1477948526225_0004
doesn't exist and is created
2016-10-31 21:27:31,912 [PigTezLauncher-0] INFO
org.apache.tez.dag.history.ats.acls.ATSV15HistoryACLPolicyManager - Created
Timeline Domain for History ACLs,
domainId=Tez_ATS_application_1477948526225_0004
2016-10-31 21:27:32,980 [PigTezLauncher-0] INFO
org.apache.hadoop.yarn.client.api.impl.YarnClientImpl - Submitted application
application_1477948526225_0004
2016-10-31 21:27:32,990 [PigTezLauncher-0] INFO
org.apache.tez.client.TezClient - The url to track the Tez Session:
https://nat-r7-bwqs-spark2hive-3.openstacklocal:8090/proxy/application_1477948526225_0004/
Command failed after 1 tries
{code}
> Pig, Tez service checks getting timed out after Wire Encryption
>
>
> Key: AMBARI-18754
> URL: https://issues.apache.org/jira/browse/AMBARI-18754
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
> Fix For: 2.5.0
>
>
> Piz, Tez service checks are getting timed out after Enabling Wire Encryption.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18755) Deployment failing at creating principal
Vivek Rathod created AMBARI-18755: - Summary: Deployment failing at creating principal Key: AMBARI-18755 URL: https://issues.apache.org/jira/browse/AMBARI-18755 Project: Ambari Issue Type: Bug Affects Versions: 2.5.0 Reporter: Vivek Rathod Fix For: 2.5.0 Cluster deployment via blueprint failed at creating principals -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18754) Pig, Tez service checks getting timed out after Wire Encryption
[
https://issues.apache.org/jira/browse/AMBARI-18754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Rathod updated AMBARI-18754:
--
Summary: Pig, Tez service checks getting timed out after Wire Encryption
(was: Pig, Tez service checks getting timed out after Wire Encryption 1 of
276 Return to search Edit CommentAssignStart ProgressResolve Issue Workflow
Details)
> Pig, Tez service checks getting timed out after Wire Encryption
>
>
> Key: AMBARI-18754
> URL: https://issues.apache.org/jira/browse/AMBARI-18754
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.5.0
>Reporter: Vivek Rathod
> Fix For: 2.5.0
>
>
> Piz, Tez service checks are getting timed out after Enabling Wire Encryption.
> {code}
> 2016-10-31 21:27:31,791 [PigTezLauncher-0] INFO
> org.apache.tez.client.TezClient - Stage directory /tmp/ambari-qa/staging
> doesn't exist and is created
> 2016-10-31 21:27:31,837 [PigTezLauncher-0] INFO
> org.apache.tez.client.TezClient - Tez system stage directory
> hdfs://nat-r7-bwqs-spark2hive-3.openstacklocal:8020/tmp/ambari-qa/staging/.tez/application_1477948526225_0004
> doesn't exist and is created
> 2016-10-31 21:27:31,912 [PigTezLauncher-0] INFO
> org.apache.tez.dag.history.ats.acls.ATSV15HistoryACLPolicyManager - Created
> Timeline Domain for History ACLs,
> domainId=Tez_ATS_application_1477948526225_0004
> 2016-10-31 21:27:32,980 [PigTezLauncher-0] INFO
> org.apache.hadoop.yarn.client.api.impl.YarnClientImpl - Submitted application
> application_1477948526225_0004
> 2016-10-31 21:27:32,990 [PigTezLauncher-0] INFO
> org.apache.tez.client.TezClient - The url to track the Tez Session:
> https://nat-r7-bwqs-spark2hive-3.openstacklocal:8090/proxy/application_1477948526225_0004/
> Command failed after 1 tries
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18754) Pig, Tez service checks getting timed out after Wire Encryption 1 of 276 Return to search Edit CommentAssignStart ProgressResolve Issue Workflow Details
Vivek Rathod created AMBARI-18754:
-
Summary: Pig, Tez service checks getting timed out after Wire
Encryption1 of 276 Return to search Edit CommentAssignStart
ProgressResolve Issue Workflow Details
Key: AMBARI-18754
URL: https://issues.apache.org/jira/browse/AMBARI-18754
Project: Ambari
Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Vivek Rathod
Fix For: 2.5.0
Piz, Tez service checks are getting timed out after Enabling Wire Encryption.
{code}
2016-10-31 21:27:31,791 [PigTezLauncher-0] INFO
org.apache.tez.client.TezClient - Stage directory /tmp/ambari-qa/staging
doesn't exist and is created
2016-10-31 21:27:31,837 [PigTezLauncher-0] INFO
org.apache.tez.client.TezClient - Tez system stage directory
hdfs://nat-r7-bwqs-spark2hive-3.openstacklocal:8020/tmp/ambari-qa/staging/.tez/application_1477948526225_0004
doesn't exist and is created
2016-10-31 21:27:31,912 [PigTezLauncher-0] INFO
org.apache.tez.dag.history.ats.acls.ATSV15HistoryACLPolicyManager - Created
Timeline Domain for History ACLs,
domainId=Tez_ATS_application_1477948526225_0004
2016-10-31 21:27:32,980 [PigTezLauncher-0] INFO
org.apache.hadoop.yarn.client.api.impl.YarnClientImpl - Submitted application
application_1477948526225_0004
2016-10-31 21:27:32,990 [PigTezLauncher-0] INFO
org.apache.tez.client.TezClient - The url to track the Tez Session:
https://nat-r7-bwqs-spark2hive-3.openstacklocal:8090/proxy/application_1477948526225_0004/
Command failed after 1 tries
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18753) Host goes into HEARTBEAT_LOST state during cluster Install
Vivek Rathod created AMBARI-18753:
-
Summary: Host goes into HEARTBEAT_LOST state during cluster Install
Key: AMBARI-18753
URL: https://issues.apache.org/jira/browse/AMBARI-18753
Project: Ambari
Issue Type: Bug
Affects Versions: 2.5.0
Reporter: Vivek Rathod
Fix For: 2.5.0
During cluster install, one of the host goes into HEARTBEAT_LOST state.
{code}
31 Oct 2016 20:52:56,624 WARN [qtp-ambari-agent-150] HeartBeatHandler:235 -
Host is in HEARTBEAT_LOST state - sending register command
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18706) Ranger Audit Handler not working as expected as NN HA wizard does not set a few properties correctly
[
https://issues.apache.org/jira/browse/AMBARI-18706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623486#comment-15623486
]
Hudson commented on AMBARI-18706:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5896 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5896/])
AMBARI-18706. Ranger Audit Handler not working as expected as NN HA (jaimin:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4ffc8ffb4b92f7c78ad4edf27636555fcd1db2be])
* (edit) ambari-web/app/messages.js
* (edit)
ambari-web/app/controllers/main/admin/highAvailability/nameNode/step3_controller.js
* (edit)
ambari-web/app/controllers/main/admin/highAvailability/nameNode/step7_controller.js
* (edit) ambari-web/app/data/HDP2/ha_properties.js
* (edit) ambari-web/app/utils/ajax/ajax.js
* (edit) ambari-web/app/utils/configs/nn_ha_config_initializer.js
* (edit) ambari-web/app/routes/high_availability_routes.js
* (edit)
ambari-web/app/controllers/main/admin/highAvailability/nameNode/wizard_controller.js
* (edit)
ambari-web/test/controllers/main/admin/highAvailability/nameNode/step3_controller_test.js
* (edit)
ambari-web/app/controllers/main/admin/highAvailability/nameNode/step5_controller.js
* (edit)
ambari-web/app/controllers/main/admin/highAvailability/nameNode/step9_controller.js
> Ranger Audit Handler not working as expected as NN HA wizard does not set a
> few properties correctly
>
>
> Key: AMBARI-18706
> URL: https://issues.apache.org/jira/browse/AMBARI-18706
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18706.v1.patch, AMBARI-18706.v2.patch
>
>
> When Ranger is installed and the user tries to enable NamenodeHA in HDFS, the
> following exception is encountered since a property is not configured
> properly in all the dependent services.
> {code}
> 2016-08-23 00:24:42,923 INFO hdfs.StateChange
> (FSNamesystem.java:completeFile(3503)) - DIR* completeFile:
> /spark-history/.7927fb59-c4fe-4328-9b7a-0d435df56690 is closed by
> DFSClient_NONMAPREDUCE_-1097091097_1
> 2016-08-23 00:24:43,801 INFO BlockStateChange
> (UnderReplicatedBlocks.java:chooseUnderReplicatedBlocks(394)) -
> chooseUnderReplicatedBlocks selected Total=0 Reset bookmarks? true
> 2016-08-23 00:24:43,802 INFO BlockStateChange
> (BlockManager.java:computeReplicationWorkForBlocks(1527)) - BLOCK*
> neededReplications = 0, pendingReplications = 0.
> 2016-08-23 00:24:46,802 INFO BlockStateChange
> (UnderReplicatedBlocks.java:chooseUnderReplicatedBlocks(394)) -
> chooseUnderReplicatedBlocks selected Total=0 Reset bookmarks? true
> 2016-08-23 00:24:46,802 INFO BlockStateChange
> (BlockManager.java:computeReplicationWorkForBlocks(1527)) - BLOCK*
> neededReplications = 0, pendingReplications = 0.
> 2016-08-23 00:24:49,498 INFO ipc.Server (Server.java:saslProcess(1386)) -
> Auth successful for
> hive/natr76-swxs-dgtoeriesecha-r7-11.openstacklo...@example.com
> (auth:KERBEROS)
> 2016-08-23 00:24:49,533 INFO authorize.ServiceAuthorizationManager
> (ServiceAuthorizationManager.java:authorize(135)) - Authorization successful
> for hive/natr76-swxs-dgtoeriesecha-r7-11.openstacklo...@example.com
> (auth:KERBEROS) for protocol=interface
> org.apache.hadoop.hdfs.protocol.ClientProtocol
> 2016-08-23 00:24:49,804 INFO BlockStateChange
> (UnderReplicatedBlocks.java:chooseUnderReplicatedBlocks(394)) -
> chooseUnderReplicatedBlocks selected Total=0 Reset bookmarks? true
> 2016-08-23 00:24:49,805 INFO BlockStateChange
> (BlockManager.java:computeReplicationWorkForBlocks(1527)) - BLOCK*
> neededReplications = 0, pendingReplications = 0.
> 2016-08-23 00:24:50,362 INFO provider.BaseAuditHandler
> (BaseAuditHandler.java:logStatus(312)) - Audit Status Log:
> name=hdfs.async.multi_dest.batch.hdfs, interval=01:00.130 minutes, events=1,
> deferredCount=1, totalEvents=4, totalDeferredCount=4
> 2016-08-23 00:24:50,363 INFO destination.HDFSAuditDestination
> (HDFSAuditDestination.java:createConfiguration(263)) - Returning HDFS
> Filesystem Config: Configuration: core-default.xml, core-site.xml,
> hdfs-default.xml, hdfs-site.xml, mapred-default.xml, mapred-site.xml,
> yarn-default.xml, yarn-site.xml
> 2016-08-23 00:24:50,444 INFO destination.HDFSAuditDestination
> (HDFSAuditDestination.java:getLogFileStream(224)) - Checking whether log file
> exists.
> hdfPath=hdfs://natr76-swxs-dgtoeriesecha-r7-14.openstacklocal:8020/ranger/audit/hdfs/20160823/hdfs_ranger_audit_natr76-swxs-dgtoeriesecha-r7-10.openstacklocal.log,
>
[jira] [Commented] (AMBARI-18706) Ranger Audit Handler not working as expected as NN HA wizard does not set a few properties correctly
[
https://issues.apache.org/jira/browse/AMBARI-18706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623478#comment-15623478
]
Hudson commented on AMBARI-18706:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #233 (See
[https://builds.apache.org/job/Ambari-branch-2.5/233/])
AMBARI-18706. Ranger Audit Handler not working as expected as NN HA (jaimin:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=06c07edaf7f216a1a9344889ac61e0277a9657b4])
* (edit)
ambari-web/app/controllers/main/admin/highAvailability/nameNode/step7_controller.js
* (edit) ambari-web/app/routes/high_availability_routes.js
* (edit)
ambari-web/app/controllers/main/admin/highAvailability/nameNode/wizard_controller.js
* (edit) ambari-web/app/utils/configs/nn_ha_config_initializer.js
* (edit) ambari-web/app/data/HDP2/ha_properties.js
* (edit) ambari-web/app/utils/ajax/ajax.js
* (edit)
ambari-web/app/controllers/main/admin/highAvailability/nameNode/step9_controller.js
* (edit)
ambari-web/app/controllers/main/admin/highAvailability/nameNode/step3_controller.js
* (edit) ambari-web/app/messages.js
* (edit)
ambari-web/test/controllers/main/admin/highAvailability/nameNode/step3_controller_test.js
* (edit)
ambari-web/app/controllers/main/admin/highAvailability/nameNode/step5_controller.js
> Ranger Audit Handler not working as expected as NN HA wizard does not set a
> few properties correctly
>
>
> Key: AMBARI-18706
> URL: https://issues.apache.org/jira/browse/AMBARI-18706
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18706.v1.patch, AMBARI-18706.v2.patch
>
>
> When Ranger is installed and the user tries to enable NamenodeHA in HDFS, the
> following exception is encountered since a property is not configured
> properly in all the dependent services.
> {code}
> 2016-08-23 00:24:42,923 INFO hdfs.StateChange
> (FSNamesystem.java:completeFile(3503)) - DIR* completeFile:
> /spark-history/.7927fb59-c4fe-4328-9b7a-0d435df56690 is closed by
> DFSClient_NONMAPREDUCE_-1097091097_1
> 2016-08-23 00:24:43,801 INFO BlockStateChange
> (UnderReplicatedBlocks.java:chooseUnderReplicatedBlocks(394)) -
> chooseUnderReplicatedBlocks selected Total=0 Reset bookmarks? true
> 2016-08-23 00:24:43,802 INFO BlockStateChange
> (BlockManager.java:computeReplicationWorkForBlocks(1527)) - BLOCK*
> neededReplications = 0, pendingReplications = 0.
> 2016-08-23 00:24:46,802 INFO BlockStateChange
> (UnderReplicatedBlocks.java:chooseUnderReplicatedBlocks(394)) -
> chooseUnderReplicatedBlocks selected Total=0 Reset bookmarks? true
> 2016-08-23 00:24:46,802 INFO BlockStateChange
> (BlockManager.java:computeReplicationWorkForBlocks(1527)) - BLOCK*
> neededReplications = 0, pendingReplications = 0.
> 2016-08-23 00:24:49,498 INFO ipc.Server (Server.java:saslProcess(1386)) -
> Auth successful for
> hive/natr76-swxs-dgtoeriesecha-r7-11.openstacklo...@example.com
> (auth:KERBEROS)
> 2016-08-23 00:24:49,533 INFO authorize.ServiceAuthorizationManager
> (ServiceAuthorizationManager.java:authorize(135)) - Authorization successful
> for hive/natr76-swxs-dgtoeriesecha-r7-11.openstacklo...@example.com
> (auth:KERBEROS) for protocol=interface
> org.apache.hadoop.hdfs.protocol.ClientProtocol
> 2016-08-23 00:24:49,804 INFO BlockStateChange
> (UnderReplicatedBlocks.java:chooseUnderReplicatedBlocks(394)) -
> chooseUnderReplicatedBlocks selected Total=0 Reset bookmarks? true
> 2016-08-23 00:24:49,805 INFO BlockStateChange
> (BlockManager.java:computeReplicationWorkForBlocks(1527)) - BLOCK*
> neededReplications = 0, pendingReplications = 0.
> 2016-08-23 00:24:50,362 INFO provider.BaseAuditHandler
> (BaseAuditHandler.java:logStatus(312)) - Audit Status Log:
> name=hdfs.async.multi_dest.batch.hdfs, interval=01:00.130 minutes, events=1,
> deferredCount=1, totalEvents=4, totalDeferredCount=4
> 2016-08-23 00:24:50,363 INFO destination.HDFSAuditDestination
> (HDFSAuditDestination.java:createConfiguration(263)) - Returning HDFS
> Filesystem Config: Configuration: core-default.xml, core-site.xml,
> hdfs-default.xml, hdfs-site.xml, mapred-default.xml, mapred-site.xml,
> yarn-default.xml, yarn-site.xml
> 2016-08-23 00:24:50,444 INFO destination.HDFSAuditDestination
> (HDFSAuditDestination.java:getLogFileStream(224)) - Checking whether log file
> exists.
> hdfPath=hdfs://natr76-swxs-dgtoeriesecha-r7-14.openstacklocal:8020/ranger/audit/hdfs/20160823/hdfs_ranger_audit_natr76-swxs-dgtoeriesecha-r7-10.openstacklocal.log,
>
[jira] [Updated] (AMBARI-18706) Ranger Audit Handler not working as expected as NN HA wizard does not set a few properties correctly
[
https://issues.apache.org/jira/browse/AMBARI-18706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin Jetly updated AMBARI-18706:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Patch received +1 on ReviewBoard.
Patch has been committed to branch-2.5 and trunk.
> Ranger Audit Handler not working as expected as NN HA wizard does not set a
> few properties correctly
>
>
> Key: AMBARI-18706
> URL: https://issues.apache.org/jira/browse/AMBARI-18706
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18706.v1.patch, AMBARI-18706.v2.patch
>
>
> When Ranger is installed and the user tries to enable NamenodeHA in HDFS, the
> following exception is encountered since a property is not configured
> properly in all the dependent services.
> {code}
> 2016-08-23 00:24:42,923 INFO hdfs.StateChange
> (FSNamesystem.java:completeFile(3503)) - DIR* completeFile:
> /spark-history/.7927fb59-c4fe-4328-9b7a-0d435df56690 is closed by
> DFSClient_NONMAPREDUCE_-1097091097_1
> 2016-08-23 00:24:43,801 INFO BlockStateChange
> (UnderReplicatedBlocks.java:chooseUnderReplicatedBlocks(394)) -
> chooseUnderReplicatedBlocks selected Total=0 Reset bookmarks? true
> 2016-08-23 00:24:43,802 INFO BlockStateChange
> (BlockManager.java:computeReplicationWorkForBlocks(1527)) - BLOCK*
> neededReplications = 0, pendingReplications = 0.
> 2016-08-23 00:24:46,802 INFO BlockStateChange
> (UnderReplicatedBlocks.java:chooseUnderReplicatedBlocks(394)) -
> chooseUnderReplicatedBlocks selected Total=0 Reset bookmarks? true
> 2016-08-23 00:24:46,802 INFO BlockStateChange
> (BlockManager.java:computeReplicationWorkForBlocks(1527)) - BLOCK*
> neededReplications = 0, pendingReplications = 0.
> 2016-08-23 00:24:49,498 INFO ipc.Server (Server.java:saslProcess(1386)) -
> Auth successful for
> hive/natr76-swxs-dgtoeriesecha-r7-11.openstacklo...@example.com
> (auth:KERBEROS)
> 2016-08-23 00:24:49,533 INFO authorize.ServiceAuthorizationManager
> (ServiceAuthorizationManager.java:authorize(135)) - Authorization successful
> for hive/natr76-swxs-dgtoeriesecha-r7-11.openstacklo...@example.com
> (auth:KERBEROS) for protocol=interface
> org.apache.hadoop.hdfs.protocol.ClientProtocol
> 2016-08-23 00:24:49,804 INFO BlockStateChange
> (UnderReplicatedBlocks.java:chooseUnderReplicatedBlocks(394)) -
> chooseUnderReplicatedBlocks selected Total=0 Reset bookmarks? true
> 2016-08-23 00:24:49,805 INFO BlockStateChange
> (BlockManager.java:computeReplicationWorkForBlocks(1527)) - BLOCK*
> neededReplications = 0, pendingReplications = 0.
> 2016-08-23 00:24:50,362 INFO provider.BaseAuditHandler
> (BaseAuditHandler.java:logStatus(312)) - Audit Status Log:
> name=hdfs.async.multi_dest.batch.hdfs, interval=01:00.130 minutes, events=1,
> deferredCount=1, totalEvents=4, totalDeferredCount=4
> 2016-08-23 00:24:50,363 INFO destination.HDFSAuditDestination
> (HDFSAuditDestination.java:createConfiguration(263)) - Returning HDFS
> Filesystem Config: Configuration: core-default.xml, core-site.xml,
> hdfs-default.xml, hdfs-site.xml, mapred-default.xml, mapred-site.xml,
> yarn-default.xml, yarn-site.xml
> 2016-08-23 00:24:50,444 INFO destination.HDFSAuditDestination
> (HDFSAuditDestination.java:getLogFileStream(224)) - Checking whether log file
> exists.
> hdfPath=hdfs://natr76-swxs-dgtoeriesecha-r7-14.openstacklocal:8020/ranger/audit/hdfs/20160823/hdfs_ranger_audit_natr76-swxs-dgtoeriesecha-r7-10.openstacklocal.log,
> UGI=nn/natr76-swxs-dgtoeriesecha-r7-10.openstacklo...@example.com
> (auth:KERBEROS)
> 2016-08-23 00:24:50,622 ERROR provider.BaseAuditHandler
> (BaseAuditHandler.java:logError(329)) - Error writing to log file.
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
> Operation category READ is not supported in state standby
> at
> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1932)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:1313)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getFileInfo(FSNamesystem.java:3861)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.getFileInfo(NameNodeRpcServer.java:1076)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.getFileInfo(ClientNamenodeProtocolServerSideTranslatorPB.java:843)
> at
[jira] [Updated] (AMBARI-18741) Not able to change the default port ambari server listens to
[ https://issues.apache.org/jira/browse/AMBARI-18741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18741: -- Attachment: (was: AMBARI-18741-Oct31.patch) > Not able to change the default port ambari server listens to > > > Key: AMBARI-18741 > URL: https://issues.apache.org/jira/browse/AMBARI-18741 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-18741-Oct31.patch, AMBARI-18741.patch > > > After including client.api.port in ambari.properties, ambari-server still > tries to connect to port 8080 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18741) Not able to change the default port ambari server listens to
[ https://issues.apache.org/jira/browse/AMBARI-18741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18741: -- Attachment: AMBARI-18741-Oct31.patch > Not able to change the default port ambari server listens to > > > Key: AMBARI-18741 > URL: https://issues.apache.org/jira/browse/AMBARI-18741 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-18741-Oct31.patch, AMBARI-18741.patch > > > After including client.api.port in ambari.properties, ambari-server still > tries to connect to port 8080 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18741) Not able to change the default port ambari server listens to
[ https://issues.apache.org/jira/browse/AMBARI-18741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18741: -- Status: Patch Available (was: Open) > Not able to change the default port ambari server listens to > > > Key: AMBARI-18741 > URL: https://issues.apache.org/jira/browse/AMBARI-18741 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-18741-Oct31.patch, AMBARI-18741.patch > > > After including client.api.port in ambari.properties, ambari-server still > tries to connect to port 8080 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18741) Not able to change the default port ambari server listens to
[ https://issues.apache.org/jira/browse/AMBARI-18741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18741: -- Attachment: AMBARI-18741-Oct31.patch > Not able to change the default port ambari server listens to > > > Key: AMBARI-18741 > URL: https://issues.apache.org/jira/browse/AMBARI-18741 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-18741-Oct31.patch, AMBARI-18741.patch > > > After including client.api.port in ambari.properties, ambari-server still > tries to connect to port 8080 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18741) Not able to change the default port ambari server listens to
[ https://issues.apache.org/jira/browse/AMBARI-18741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anita Gnanamalar Jebaraj updated AMBARI-18741: -- Status: Open (was: Patch Available) > Not able to change the default port ambari server listens to > > > Key: AMBARI-18741 > URL: https://issues.apache.org/jira/browse/AMBARI-18741 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Anita Gnanamalar Jebaraj >Assignee: Anita Gnanamalar Jebaraj > Fix For: trunk > > Attachments: AMBARI-18741-Oct31.patch, AMBARI-18741.patch > > > After including client.api.port in ambari.properties, ambari-server still > tries to connect to port 8080 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18706) Ranger Audit Handler not working as expected as NN HA wizard does not set a few properties correctly
[
https://issues.apache.org/jira/browse/AMBARI-18706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623343#comment-15623343
]
Hadoop QA commented on AMBARI-18706:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836203/AMBARI-18706.v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9066//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9066//console
This message is automatically generated.
> Ranger Audit Handler not working as expected as NN HA wizard does not set a
> few properties correctly
>
>
> Key: AMBARI-18706
> URL: https://issues.apache.org/jira/browse/AMBARI-18706
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18706.v1.patch, AMBARI-18706.v2.patch
>
>
> When Ranger is installed and the user tries to enable NamenodeHA in HDFS, the
> following exception is encountered since a property is not configured
> properly in all the dependent services.
> {code}
> 2016-08-23 00:24:42,923 INFO hdfs.StateChange
> (FSNamesystem.java:completeFile(3503)) - DIR* completeFile:
> /spark-history/.7927fb59-c4fe-4328-9b7a-0d435df56690 is closed by
> DFSClient_NONMAPREDUCE_-1097091097_1
> 2016-08-23 00:24:43,801 INFO BlockStateChange
> (UnderReplicatedBlocks.java:chooseUnderReplicatedBlocks(394)) -
> chooseUnderReplicatedBlocks selected Total=0 Reset bookmarks? true
> 2016-08-23 00:24:43,802 INFO BlockStateChange
> (BlockManager.java:computeReplicationWorkForBlocks(1527)) - BLOCK*
> neededReplications = 0, pendingReplications = 0.
> 2016-08-23 00:24:46,802 INFO BlockStateChange
> (UnderReplicatedBlocks.java:chooseUnderReplicatedBlocks(394)) -
> chooseUnderReplicatedBlocks selected Total=0 Reset bookmarks? true
> 2016-08-23 00:24:46,802 INFO BlockStateChange
> (BlockManager.java:computeReplicationWorkForBlocks(1527)) - BLOCK*
> neededReplications = 0, pendingReplications = 0.
> 2016-08-23 00:24:49,498 INFO ipc.Server (Server.java:saslProcess(1386)) -
> Auth successful for
> hive/natr76-swxs-dgtoeriesecha-r7-11.openstacklo...@example.com
> (auth:KERBEROS)
> 2016-08-23 00:24:49,533 INFO authorize.ServiceAuthorizationManager
> (ServiceAuthorizationManager.java:authorize(135)) - Authorization successful
> for hive/natr76-swxs-dgtoeriesecha-r7-11.openstacklo...@example.com
> (auth:KERBEROS) for protocol=interface
> org.apache.hadoop.hdfs.protocol.ClientProtocol
> 2016-08-23 00:24:49,804 INFO BlockStateChange
> (UnderReplicatedBlocks.java:chooseUnderReplicatedBlocks(394)) -
> chooseUnderReplicatedBlocks selected Total=0 Reset bookmarks? true
> 2016-08-23 00:24:49,805 INFO BlockStateChange
> (BlockManager.java:computeReplicationWorkForBlocks(1527)) - BLOCK*
> neededReplications = 0, pendingReplications = 0.
> 2016-08-23 00:24:50,362 INFO provider.BaseAuditHandler
> (BaseAuditHandler.java:logStatus(312)) - Audit Status Log:
> name=hdfs.async.multi_dest.batch.hdfs, interval=01:00.130 minutes, events=1,
> deferredCount=1, totalEvents=4, totalDeferredCount=4
> 2016-08-23 00:24:50,363 INFO destination.HDFSAuditDestination
> (HDFSAuditDestination.java:createConfiguration(263)) - Returning HDFS
> Filesystem Config: Configuration: core-default.xml, core-site.xml,
> hdfs-default.xml, hdfs-site.xml, mapred-default.xml, mapred-site.xml,
> yarn-default.xml, yarn-site.xml
> 2016-08-23 00:24:50,444 INFO destination.HDFSAuditDestination
> (HDFSAuditDestination.java:getLogFileStream(224)) - Checking whether log file
> exists.
> hdfPath=hdfs://natr76-swxs-dgtoeriesecha-r7-14.openstacklocal:8020/ranger/audit/hdfs/20160823/hdfs_ranger_audit_natr76-swxs-dgtoeriesecha-r7-10.openstacklocal.log,
> UGI=nn/natr76-swxs-dgtoeriesecha-r7-10.openstacklo...@example.com
> (auth:KERBEROS)
> 2016-08-23 00:24:50,622 ERROR provider.BaseAuditHandler
> (BaseAuditHandler.java:logError(329)) - Error writing to log file.
>
[jira] [Updated] (AMBARI-18744) Ambari-server: REST API changes to GET and PUT credential store information
[
https://issues.apache.org/jira/browse/AMBARI-18744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nahappan Somasundaram updated AMBARI-18744:
---
Description:
*Support stack definition for credential store information*
To support backward compatibility, services must be tagged to indicate whether
they support credential store backed passwords. This requires changes in the
stack definition object model.
{code}
SERVICE_NAME
:
true
false
:
:
{code}
*REST API support is required to GET _credential_store_supported_ and
_credential_store_enabled_ values for a service:*
{quote}api/v1/clusters//services?fields=ServiceInfo/service_name,ServiceInfo/credential_store_supported,ServiceInfo/credential_store_enabled{quote}
*REST API support is required to PUT _credential_store_enabled_ value for a
service:*
{quote}api/v1/clusters//services?ServiceInfo/service_name.in(RANGER,HIVE)
{
ServiceInfo: {
credential_store_enabled: “true”
}
}{quote}
{quote}api/v1/clusters/testcluster/services/RANGER -X PUT -d '{"ServiceInfo" :
{"credential_store_enabled":"true"}}'
{quote}
{quote}api/v1/clusters/testcluster/services?ServiceInfo/service_name=ZOOKEEPER
-X PUT -d '{"ServiceInfo" : {"credential_store_enabled":"false"}}'{quote}
*REST API to get Stack definition*
{quote}
curl -u admin:admin -H "X-Requested-By: ambari" -X GET
http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services
{quote}
{quote}
{
"href" : "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/;,
{
"href" :
"http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/YARN;,
"StackServices" : {
"service_name" : "YARN",
"stack_name" : "HDP",
"stack_version" : "2.0",
"credential_store_supported" : "false",
"credential_store_enabled" : "false"
}
},
{
"href" :
"http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/ZOOKEEPER;,
"StackServices" : {
"service_name" : "ZOOKEEPER",
"stack_name" : "HDP",
"stack_version" : "2.0",
"credential_store_supported" : "false",
"credential_store_enabled" : "false"
}
}
]
}
{quote}
was:
*REST API support is required to GET _credential_store_supported_ and
_credential_store_enabled_ values for a service:*
{quote}api/v1/clusters//services?fields=ServiceInfo/service_name,ServiceInfo/credential_store_supported,ServiceInfo/credential_store_enabled{quote}
*REST API support is required to PUT _credential_store_enabled_ value for a
service:*
{quote}api/v1/clusters//services?ServiceInfo/service_name.in(RANGER,HIVE)
{
ServiceInfo: {
credential_store_enabled: “true”
}
}{quote}
{quote}api/v1/clusters/testcluster/services/RANGER -X PUT -d '{"ServiceInfo" :
{"credential_store_enabled":"true"}}'
{quote}
{quote}api/v1/clusters/testcluster/services?ServiceInfo/service_name=ZOOKEEPER
-X PUT -d '{"ServiceInfo" : {"credential_store_enabled":"false"}}'{quote}
*REST API to get Stack definition*
{quote}
curl -u admin:admin -H "X-Requested-By: ambari" -X GET
http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services
{quote}
{quote}
{
"href" : "http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/;,
{
"href" :
"http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/YARN;,
"StackServices" : {
"service_name" : "YARN",
"stack_name" : "HDP",
"stack_version" : "2.0",
"credential_store_supported" : "false",
"credential_store_enabled" : "false"
}
},
{
"href" :
"http://localhost:8080/api/v1/stacks/HDP/versions/2.0/services/ZOOKEEPER;,
"StackServices" : {
"service_name" : "ZOOKEEPER",
"stack_name" : "HDP",
"stack_version" : "2.0",
"credential_store_supported" : "false",
"credential_store_enabled" : "false"
}
}
]
}
{quote}
> Ambari-server: REST API changes to GET and PUT credential store information
> ---
>
> Key: AMBARI-18744
> URL: https://issues.apache.org/jira/browse/AMBARI-18744
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53283.patch
>
>
> *Support stack definition for credential store information*
> To support backward compatibility, services must be tagged to indicate
> whether they support credential store backed passwords. This requires changes
> in the stack definition object model.
> {code}
>
> SERVICE_NAME
> :
>
> true
> false
>
> :
> :
>
> {code}
> *REST API support is required to GET _credential_store_supported_ and
>
[jira] [Updated] (AMBARI-18711) Ambari-server: DB changes to enable/disable credential store support
[ https://issues.apache.org/jira/browse/AMBARI-18711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18711: --- Status: Patch Available (was: Open) > Ambari-server: DB changes to enable/disable credential store support > > > Key: AMBARI-18711 > URL: https://issues.apache.org/jira/browse/AMBARI-18711 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.5.0 > > Attachments: rb53216.patch > > > To enable or disable a component to use credential store, changes are > required in the DB to keep track of this information. The > _servicedesiredstate_ table can keep track of this information using a new > *credential_store_enabled* column. > If a service supports reading passwords from the configuration's JCEKS file, > then it will specify this information in its stack definition. Services that > support using the credential store can be enabled or disabled to use it. > Services that do not, will always be disabled from using the credential store. > The option to enable or disable the components of a service that has > credential store support is provided via the UI and blueprint. This > information will then be captured in the _servicedesiredstate_ table in the > *credential_store_enabled* column. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18711) Ambari-server: DB changes to enable/disable credential store support
[ https://issues.apache.org/jira/browse/AMBARI-18711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18711: --- Attachment: (was: rb53216.patch) > Ambari-server: DB changes to enable/disable credential store support > > > Key: AMBARI-18711 > URL: https://issues.apache.org/jira/browse/AMBARI-18711 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.5.0 > > > To enable or disable a component to use credential store, changes are > required in the DB to keep track of this information. The > _servicedesiredstate_ table can keep track of this information using a new > *credential_store_enabled* column. > If a service supports reading passwords from the configuration's JCEKS file, > then it will specify this information in its stack definition. Services that > support using the credential store can be enabled or disabled to use it. > Services that do not, will always be disabled from using the credential store. > The option to enable or disable the components of a service that has > credential store support is provided via the UI and blueprint. This > information will then be captured in the _servicedesiredstate_ table in the > *credential_store_enabled* column. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18711) Ambari-server: DB changes to enable/disable credential store support
[ https://issues.apache.org/jira/browse/AMBARI-18711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18711: --- Status: Open (was: Patch Available) > Ambari-server: DB changes to enable/disable credential store support > > > Key: AMBARI-18711 > URL: https://issues.apache.org/jira/browse/AMBARI-18711 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.5.0 > > > To enable or disable a component to use credential store, changes are > required in the DB to keep track of this information. The > _servicedesiredstate_ table can keep track of this information using a new > *credential_store_enabled* column. > If a service supports reading passwords from the configuration's JCEKS file, > then it will specify this information in its stack definition. Services that > support using the credential store can be enabled or disabled to use it. > Services that do not, will always be disabled from using the credential store. > The option to enable or disable the components of a service that has > credential store support is provided via the UI and blueprint. This > information will then be captured in the _servicedesiredstate_ table in the > *credential_store_enabled* column. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18749) Hosts paging works incorrectly with service and component filters
[ https://issues.apache.org/jira/browse/AMBARI-18749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623288#comment-15623288 ] Hudson commented on AMBARI-18749: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5895 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5895/]) AMBARI-18749. Hosts paging works incorrectly with service and component (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=166e87816e20399df14b36bc5c250f74996cba23]) * (edit) ambari-web/app/views/common/table_view.js * (edit) ambari-web/app/controllers/global/update_controller.js > Hosts paging works incorrectly with service and component filters > - > > Key: AMBARI-18749 > URL: https://issues.apache.org/jira/browse/AMBARI-18749 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18749.patch > > > Steps: > # Go to Hosts page. > # Set page size to 10 rows. > # Set filter hosts by any component/service in any state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18752) Popover dialog displays raw html instead of rendering it
[
https://issues.apache.org/jira/browse/AMBARI-18752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623277#comment-15623277
]
Hadoop QA commented on AMBARI-18752:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836207/AMBARI-18752.v0.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9065//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9065//console
This message is automatically generated.
> Popover dialog displays raw html instead of rendering it
>
>
> Key: AMBARI-18752
> URL: https://issues.apache.org/jira/browse/AMBARI-18752
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
> Fix For: 3.0.0
>
> Attachments: AMBARI-18752.v0.patch, Screen Shot 2016-10-31 at
> 12.16.47 PM.png
>
>
> Popover dialog displays raw html instead of rendering it as shown in the
> screen-shot
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18749) Hosts paging works incorrectly with service and component filters
[ https://issues.apache.org/jira/browse/AMBARI-18749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623210#comment-15623210 ] Hudson commented on AMBARI-18749: - FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #232 (See [https://builds.apache.org/job/Ambari-branch-2.5/232/]) AMBARI-18749. Hosts paging works incorrectly with service and component (hiveww: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=da0d6051e91afd996c58ff9b098eb5750df26b45]) * (edit) ambari-web/app/views/common/table_view.js * (edit) ambari-web/app/controllers/global/update_controller.js > Hosts paging works incorrectly with service and component filters > - > > Key: AMBARI-18749 > URL: https://issues.apache.org/jira/browse/AMBARI-18749 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18749.patch > > > Steps: > # Go to Hosts page. > # Set page size to 10 rows. > # Set filter hosts by any component/service in any state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18732) Perf: Create PERF stack with mix of HDP core services and dummy services
[ https://issues.apache.org/jira/browse/AMBARI-18732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18732: - Attachment: AMBARI-18732.patch > Perf: Create PERF stack with mix of HDP core services and dummy services > > > Key: AMBARI-18732 > URL: https://issues.apache.org/jira/browse/AMBARI-18732 > Project: Ambari > Issue Type: Story > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-18732.patch > > > We need a fake stack that will make it easier to perform lifecycle commands > such as Start, Stop, Restart, Status, Service Checks etc. > This stack will eventually support UI themes, Kerberos, Alerts, etc. > For now, the PERF stack should have 8+ services (HDFS, YARN, MR, ZK, plus > dummy ones like Happy, Sleepy, Grumpy, etc). > We do want some of the complexity of the Hadoop core services and their > configs, and we also want really simple services (like the dwarfs) that can > be deployed on their own. > This stack should serve as a sample for how to implement a new stack, and > also abstract some of the complexity of the HDP stack in order to run > performance tests that stress the server by overloading it with heartbeats, > alerts, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18732) Perf: Create PERF stack with mix of HDP core services and dummy services
[ https://issues.apache.org/jira/browse/AMBARI-18732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-18732: - Status: Patch Available (was: Open) > Perf: Create PERF stack with mix of HDP core services and dummy services > > > Key: AMBARI-18732 > URL: https://issues.apache.org/jira/browse/AMBARI-18732 > Project: Ambari > Issue Type: Story > Components: ambari-agent >Affects Versions: 2.5.0 >Reporter: Alejandro Fernandez >Assignee: Alejandro Fernandez > Fix For: 2.5.0 > > Attachments: AMBARI-18732.patch > > > We need a fake stack that will make it easier to perform lifecycle commands > such as Start, Stop, Restart, Status, Service Checks etc. > This stack will eventually support UI themes, Kerberos, Alerts, etc. > For now, the PERF stack should have 8+ services (HDFS, YARN, MR, ZK, plus > dummy ones like Happy, Sleepy, Grumpy, etc). > We do want some of the complexity of the Hadoop core services and their > configs, and we also want really simple services (like the dwarfs) that can > be deployed on their own. > This stack should serve as a sample for how to implement a new stack, and > also abstract some of the complexity of the HDP stack in order to run > performance tests that stress the server by overloading it with heartbeats, > alerts, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18574) Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
[
https://issues.apache.org/jira/browse/AMBARI-18574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu updated AMBARI-18574:
Description:
The default value for hbase.hregion.memstore.chunkpool.maxsize is:
{code}
final static float POOL_MAX_SIZE_DEFAULT = 0.0f;
{code}
This would result in chunk pool being disabled, leading to excessive
MemStoreLAB chunk allocations.
Ambari should set the value to 1.0
was:
The default value for hbase.hregion.memstore.chunkpool.maxsize is:
{code}
final static float POOL_MAX_SIZE_DEFAULT = 0.0f;
{code}
This would result in chunk pool being disabled, leading to excessive
MemStoreLAB chunk allocations.
Ambari should set the value to 1.0
> Set hbase.hregion.memstore.chunkpool.maxsize to 1.0
> ---
>
> Key: AMBARI-18574
> URL: https://issues.apache.org/jira/browse/AMBARI-18574
> Project: Ambari
> Issue Type: Bug
>Reporter: Ted Yu
>
> The default value for hbase.hregion.memstore.chunkpool.maxsize is:
> {code}
> final static float POOL_MAX_SIZE_DEFAULT = 0.0f;
> {code}
> This would result in chunk pool being disabled, leading to excessive
> MemStoreLAB chunk allocations.
> Ambari should set the value to 1.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18749) Hosts paging works incorrectly with service and component filters
[ https://issues.apache.org/jira/browse/AMBARI-18749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-18749: - Resolution: Fixed Status: Resolved (was: Patch Available) committed to 2.4, 2.5, trunk > Hosts paging works incorrectly with service and component filters > - > > Key: AMBARI-18749 > URL: https://issues.apache.org/jira/browse/AMBARI-18749 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18749.patch > > > Steps: > # Go to Hosts page. > # Set page size to 10 rows. > # Set filter hosts by any component/service in any state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-17126) Provide Ambari Server HA (active-passive)
[ https://issues.apache.org/jira/browse/AMBARI-17126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15623099#comment-15623099 ] Edward Mangini commented on AMBARI-17126: - I have two questions: 1.) Is this actively being looked at for 2.5? (Is there an estimated release date for 2.5?) 2.) Also, why exactly was AMBARI-7896 closed and being tracked here? Active-Passive fault tolerance/redundancy isn't necessarily the same concept as high availability. > Provide Ambari Server HA (active-passive) > - > > Key: AMBARI-17126 > URL: https://issues.apache.org/jira/browse/AMBARI-17126 > Project: Ambari > Issue Type: Improvement > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Jeff Sposetti >Assignee: Swapan Shridhar > Fix For: 2.5.0 > > > Ability to configure Ambari Server active-passive setup behind Load balancer. > -Both servers should point to the same database (external to Ambari Server) . > Preferably Server.jdbc.hostname should point to a HA DB Cluster from both > server's ambari.properties. > -Load Balancer (preferably an external solution, like F5, Cisco, Brocade etc) > to create VIP and use the Ambari server as Real to direct traffic to either > host rather than keeping one as Standby (Agent ini file should point to DNS > of VIP rather than to a server directly) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18752) Popover dialog displays raw html instead of rendering it
[ https://issues.apache.org/jira/browse/AMBARI-18752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18752: Attachment: AMBARI-18752.v0.patch > Popover dialog displays raw html instead of rendering it > > > Key: AMBARI-18752 > URL: https://issues.apache.org/jira/browse/AMBARI-18752 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 3.0.0 > > Attachments: AMBARI-18752.v0.patch, Screen Shot 2016-10-31 at > 12.16.47 PM.png > > > Popover dialog displays raw html instead of rendering it as shown in the > screen-shot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18752) Popover dialog displays raw html instead of rendering it
[ https://issues.apache.org/jira/browse/AMBARI-18752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18752: Status: Patch Available (was: In Progress) > Popover dialog displays raw html instead of rendering it > > > Key: AMBARI-18752 > URL: https://issues.apache.org/jira/browse/AMBARI-18752 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 3.0.0 > > Attachments: AMBARI-18752.v0.patch, Screen Shot 2016-10-31 at > 12.16.47 PM.png > > > Popover dialog displays raw html instead of rendering it as shown in the > screen-shot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18752) Popover dialog displays raw html instead of rendering it
[ https://issues.apache.org/jira/browse/AMBARI-18752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian updated AMBARI-18752: Attachment: Screen Shot 2016-10-31 at 12.16.47 PM.png > Popover dialog displays raw html instead of rendering it > > > Key: AMBARI-18752 > URL: https://issues.apache.org/jira/browse/AMBARI-18752 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Vivek Ratnavel Subramanian >Assignee: Vivek Ratnavel Subramanian > Fix For: 3.0.0 > > Attachments: Screen Shot 2016-10-31 at 12.16.47 PM.png > > > Popover dialog displays raw html instead of rendering it as shown in the > screen-shot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18752) Popover dialog displays raw html instead of rendering it
Vivek Ratnavel Subramanian created AMBARI-18752: --- Summary: Popover dialog displays raw html instead of rendering it Key: AMBARI-18752 URL: https://issues.apache.org/jira/browse/AMBARI-18752 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 3.0.0 Reporter: Vivek Ratnavel Subramanian Assignee: Vivek Ratnavel Subramanian Fix For: 3.0.0 Popover dialog displays raw html instead of rendering it as shown in the screen-shot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18706) Ranger Audit Handler not working as expected as NN HA wizard does not set a few properties correctly
[
https://issues.apache.org/jira/browse/AMBARI-18706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian updated AMBARI-18706:
Status: Patch Available (was: Open)
> Ranger Audit Handler not working as expected as NN HA wizard does not set a
> few properties correctly
>
>
> Key: AMBARI-18706
> URL: https://issues.apache.org/jira/browse/AMBARI-18706
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18706.v1.patch, AMBARI-18706.v2.patch
>
>
> When Ranger is installed and the user tries to enable NamenodeHA in HDFS, the
> following exception is encountered since a property is not configured
> properly in all the dependent services.
> {code}
> 2016-08-23 00:24:42,923 INFO hdfs.StateChange
> (FSNamesystem.java:completeFile(3503)) - DIR* completeFile:
> /spark-history/.7927fb59-c4fe-4328-9b7a-0d435df56690 is closed by
> DFSClient_NONMAPREDUCE_-1097091097_1
> 2016-08-23 00:24:43,801 INFO BlockStateChange
> (UnderReplicatedBlocks.java:chooseUnderReplicatedBlocks(394)) -
> chooseUnderReplicatedBlocks selected Total=0 Reset bookmarks? true
> 2016-08-23 00:24:43,802 INFO BlockStateChange
> (BlockManager.java:computeReplicationWorkForBlocks(1527)) - BLOCK*
> neededReplications = 0, pendingReplications = 0.
> 2016-08-23 00:24:46,802 INFO BlockStateChange
> (UnderReplicatedBlocks.java:chooseUnderReplicatedBlocks(394)) -
> chooseUnderReplicatedBlocks selected Total=0 Reset bookmarks? true
> 2016-08-23 00:24:46,802 INFO BlockStateChange
> (BlockManager.java:computeReplicationWorkForBlocks(1527)) - BLOCK*
> neededReplications = 0, pendingReplications = 0.
> 2016-08-23 00:24:49,498 INFO ipc.Server (Server.java:saslProcess(1386)) -
> Auth successful for
> hive/natr76-swxs-dgtoeriesecha-r7-11.openstacklo...@example.com
> (auth:KERBEROS)
> 2016-08-23 00:24:49,533 INFO authorize.ServiceAuthorizationManager
> (ServiceAuthorizationManager.java:authorize(135)) - Authorization successful
> for hive/natr76-swxs-dgtoeriesecha-r7-11.openstacklo...@example.com
> (auth:KERBEROS) for protocol=interface
> org.apache.hadoop.hdfs.protocol.ClientProtocol
> 2016-08-23 00:24:49,804 INFO BlockStateChange
> (UnderReplicatedBlocks.java:chooseUnderReplicatedBlocks(394)) -
> chooseUnderReplicatedBlocks selected Total=0 Reset bookmarks? true
> 2016-08-23 00:24:49,805 INFO BlockStateChange
> (BlockManager.java:computeReplicationWorkForBlocks(1527)) - BLOCK*
> neededReplications = 0, pendingReplications = 0.
> 2016-08-23 00:24:50,362 INFO provider.BaseAuditHandler
> (BaseAuditHandler.java:logStatus(312)) - Audit Status Log:
> name=hdfs.async.multi_dest.batch.hdfs, interval=01:00.130 minutes, events=1,
> deferredCount=1, totalEvents=4, totalDeferredCount=4
> 2016-08-23 00:24:50,363 INFO destination.HDFSAuditDestination
> (HDFSAuditDestination.java:createConfiguration(263)) - Returning HDFS
> Filesystem Config: Configuration: core-default.xml, core-site.xml,
> hdfs-default.xml, hdfs-site.xml, mapred-default.xml, mapred-site.xml,
> yarn-default.xml, yarn-site.xml
> 2016-08-23 00:24:50,444 INFO destination.HDFSAuditDestination
> (HDFSAuditDestination.java:getLogFileStream(224)) - Checking whether log file
> exists.
> hdfPath=hdfs://natr76-swxs-dgtoeriesecha-r7-14.openstacklocal:8020/ranger/audit/hdfs/20160823/hdfs_ranger_audit_natr76-swxs-dgtoeriesecha-r7-10.openstacklocal.log,
> UGI=nn/natr76-swxs-dgtoeriesecha-r7-10.openstacklo...@example.com
> (auth:KERBEROS)
> 2016-08-23 00:24:50,622 ERROR provider.BaseAuditHandler
> (BaseAuditHandler.java:logError(329)) - Error writing to log file.
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
> Operation category READ is not supported in state standby
> at
> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1932)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:1313)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getFileInfo(FSNamesystem.java:3861)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.getFileInfo(NameNodeRpcServer.java:1076)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.getFileInfo(ClientNamenodeProtocolServerSideTranslatorPB.java:843)
> at
>
[jira] [Updated] (AMBARI-18706) Ranger Audit Handler not working as expected as NN HA wizard does not set a few properties correctly
[
https://issues.apache.org/jira/browse/AMBARI-18706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian updated AMBARI-18706:
Attachment: AMBARI-18706.v2.patch
> Ranger Audit Handler not working as expected as NN HA wizard does not set a
> few properties correctly
>
>
> Key: AMBARI-18706
> URL: https://issues.apache.org/jira/browse/AMBARI-18706
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.5.0
>Reporter: Vivek Ratnavel Subramanian
>Assignee: Vivek Ratnavel Subramanian
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18706.v1.patch, AMBARI-18706.v2.patch
>
>
> When Ranger is installed and the user tries to enable NamenodeHA in HDFS, the
> following exception is encountered since a property is not configured
> properly in all the dependent services.
> {code}
> 2016-08-23 00:24:42,923 INFO hdfs.StateChange
> (FSNamesystem.java:completeFile(3503)) - DIR* completeFile:
> /spark-history/.7927fb59-c4fe-4328-9b7a-0d435df56690 is closed by
> DFSClient_NONMAPREDUCE_-1097091097_1
> 2016-08-23 00:24:43,801 INFO BlockStateChange
> (UnderReplicatedBlocks.java:chooseUnderReplicatedBlocks(394)) -
> chooseUnderReplicatedBlocks selected Total=0 Reset bookmarks? true
> 2016-08-23 00:24:43,802 INFO BlockStateChange
> (BlockManager.java:computeReplicationWorkForBlocks(1527)) - BLOCK*
> neededReplications = 0, pendingReplications = 0.
> 2016-08-23 00:24:46,802 INFO BlockStateChange
> (UnderReplicatedBlocks.java:chooseUnderReplicatedBlocks(394)) -
> chooseUnderReplicatedBlocks selected Total=0 Reset bookmarks? true
> 2016-08-23 00:24:46,802 INFO BlockStateChange
> (BlockManager.java:computeReplicationWorkForBlocks(1527)) - BLOCK*
> neededReplications = 0, pendingReplications = 0.
> 2016-08-23 00:24:49,498 INFO ipc.Server (Server.java:saslProcess(1386)) -
> Auth successful for
> hive/natr76-swxs-dgtoeriesecha-r7-11.openstacklo...@example.com
> (auth:KERBEROS)
> 2016-08-23 00:24:49,533 INFO authorize.ServiceAuthorizationManager
> (ServiceAuthorizationManager.java:authorize(135)) - Authorization successful
> for hive/natr76-swxs-dgtoeriesecha-r7-11.openstacklo...@example.com
> (auth:KERBEROS) for protocol=interface
> org.apache.hadoop.hdfs.protocol.ClientProtocol
> 2016-08-23 00:24:49,804 INFO BlockStateChange
> (UnderReplicatedBlocks.java:chooseUnderReplicatedBlocks(394)) -
> chooseUnderReplicatedBlocks selected Total=0 Reset bookmarks? true
> 2016-08-23 00:24:49,805 INFO BlockStateChange
> (BlockManager.java:computeReplicationWorkForBlocks(1527)) - BLOCK*
> neededReplications = 0, pendingReplications = 0.
> 2016-08-23 00:24:50,362 INFO provider.BaseAuditHandler
> (BaseAuditHandler.java:logStatus(312)) - Audit Status Log:
> name=hdfs.async.multi_dest.batch.hdfs, interval=01:00.130 minutes, events=1,
> deferredCount=1, totalEvents=4, totalDeferredCount=4
> 2016-08-23 00:24:50,363 INFO destination.HDFSAuditDestination
> (HDFSAuditDestination.java:createConfiguration(263)) - Returning HDFS
> Filesystem Config: Configuration: core-default.xml, core-site.xml,
> hdfs-default.xml, hdfs-site.xml, mapred-default.xml, mapred-site.xml,
> yarn-default.xml, yarn-site.xml
> 2016-08-23 00:24:50,444 INFO destination.HDFSAuditDestination
> (HDFSAuditDestination.java:getLogFileStream(224)) - Checking whether log file
> exists.
> hdfPath=hdfs://natr76-swxs-dgtoeriesecha-r7-14.openstacklocal:8020/ranger/audit/hdfs/20160823/hdfs_ranger_audit_natr76-swxs-dgtoeriesecha-r7-10.openstacklocal.log,
> UGI=nn/natr76-swxs-dgtoeriesecha-r7-10.openstacklo...@example.com
> (auth:KERBEROS)
> 2016-08-23 00:24:50,622 ERROR provider.BaseAuditHandler
> (BaseAuditHandler.java:logError(329)) - Error writing to log file.
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ipc.StandbyException):
> Operation category READ is not supported in state standby
> at
> org.apache.hadoop.hdfs.server.namenode.ha.StandbyState.checkOperation(StandbyState.java:87)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNode$NameNodeHAContext.checkOperation(NameNode.java:1932)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkOperation(FSNamesystem.java:1313)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getFileInfo(FSNamesystem.java:3861)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.getFileInfo(NameNodeRpcServer.java:1076)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.getFileInfo(ClientNamenodeProtocolServerSideTranslatorPB.java:843)
> at
>
[jira] [Commented] (AMBARI-18711) Ambari-server: DB changes to enable/disable credential store support
[
https://issues.apache.org/jira/browse/AMBARI-18711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15622956#comment-15622956
]
Hadoop QA commented on AMBARI-18711:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836174/rb53216.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.controller.metrics.JMXPropertyProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9064//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9064//console
This message is automatically generated.
> Ambari-server: DB changes to enable/disable credential store support
>
>
> Key: AMBARI-18711
> URL: https://issues.apache.org/jira/browse/AMBARI-18711
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Nahappan Somasundaram
>Assignee: Nahappan Somasundaram
> Fix For: 2.5.0
>
> Attachments: rb53216.patch
>
>
> To enable or disable a component to use credential store, changes are
> required in the DB to keep track of this information. The
> _servicedesiredstate_ table can keep track of this information using a new
> *credential_store_enabled* column.
> If a service supports reading passwords from the configuration's JCEKS file,
> then it will specify this information in its stack definition. Services that
> support using the credential store can be enabled or disabled to use it.
> Services that do not, will always be disabled from using the credential store.
> The option to enable or disable the components of a service that has
> credential store support is provided via the UI and blueprint. This
> information will then be captured in the _servicedesiredstate_ table in the
> *credential_store_enabled* column.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18750) Test and fix new tables styles on Ambari (part 3)
[ https://issues.apache.org/jira/browse/AMBARI-18750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15622887#comment-15622887 ] Hudson commented on AMBARI-18750: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5894 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5894/]) AMBARI-18750 Test and fix new tables styles on Ambari (part 3). (ababiichuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=0dfc3377d24a0aeea7d54c5a56b27cdcdbf0d326]) * (edit) ambari-web/app/views/wizard/step3_view.js * (edit) ambari-web/app/styles/application.less * (edit) ambari-web/app/templates/wizard/step1.hbs * (edit) ambari-web/app/templates/main/admin/stack_upgrade/upgrade_configs_merge_table.hbs * (edit) ambari-web/app/templates/wizard/step3.hbs * (edit) ambari-web/app/views/wizard/step1_view.js > Test and fix new tables styles on Ambari (part 3) > - > > Key: AMBARI-18750 > URL: https://issues.apache.org/jira/browse/AMBARI-18750 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-18750.patch > > > - Make basic restyling of Repositories table (step 1 of installer) > - Replace Remove button on Confirm Hosts step of installer with icon > - Fix space between header and body in Configuration Changes table -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18750) Test and fix new tables styles on Ambari (part 3)
[
https://issues.apache.org/jira/browse/AMBARI-18750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15622771#comment-15622771
]
Hadoop QA commented on AMBARI-18750:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836170/AMBARI-18750.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9062//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9062//console
This message is automatically generated.
> Test and fix new tables styles on Ambari (part 3)
> -
>
> Key: AMBARI-18750
> URL: https://issues.apache.org/jira/browse/AMBARI-18750
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 3.0.0
>Reporter: Andrii Babiichuk
>Assignee: Andrii Babiichuk
> Fix For: 3.0.0
>
> Attachments: AMBARI-18750.patch
>
>
> - Make basic restyling of Repositories table (step 1 of installer)
> - Replace Remove button on Confirm Hosts step of installer with icon
> - Fix space between header and body in Configuration Changes table
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18749) Hosts paging works incorrectly with service and component filters
[
https://issues.apache.org/jira/browse/AMBARI-18749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15622716#comment-15622716
]
Hadoop QA commented on AMBARI-18749:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836168/AMBARI-18749.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9061//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9061//console
This message is automatically generated.
> Hosts paging works incorrectly with service and component filters
> -
>
> Key: AMBARI-18749
> URL: https://issues.apache.org/jira/browse/AMBARI-18749
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
>Affects Versions: 2.4.2
>Reporter: Antonenko Alexander
>Assignee: Antonenko Alexander
>Priority: Critical
> Fix For: 2.4.2
>
> Attachments: AMBARI-18749.patch
>
>
> Steps:
> # Go to Hosts page.
> # Set page size to 10 rows.
> # Set filter hosts by any component/service in any state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18751) Upgrade Fails From 2.4.2 to 2.5 Due To Existing Role Authorizations
Robert Levas created AMBARI-18751:
-
Summary: Upgrade Fails From 2.4.2 to 2.5 Due To Existing Role
Authorizations
Key: AMBARI-18751
URL: https://issues.apache.org/jira/browse/AMBARI-18751
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.2
Reporter: Robert Levas
Assignee: Robert Levas
Priority: Blocker
Fix For: 2.4.2
STR:
- Install Ambari 2.4.2 (from branch-2.4)
- Upgrade to Ambari 2.5.0
The following exception fails the upgrade. It appears as though this is from [a
recent
commit|https://github.com/apache/ambari/commit/57116b774c62e5ff6ce22de70458e7c01cccdb07]
into {{branch-2.4}}: AMBARI-18433
When the upgrade runs, it assumes that the role authorizations need to be
added. In existing 2.4.0 and 2.4.1 installations, this is true. But since this
code is now in the 2.4 branch, 2.4.2+ installations will already have the
required data seeded.
{code}
2016-10-31 11:12:01,193 WARN [main] (Slf4jMLog.java:220) log() - [c3p0] A
PooledConnection that has already signalled a Connection error is still in use!
2016-10-31 11:12:01,193 WARN [main] (Slf4jMLog.java:223) log() - [c3p0]
Another error has occurred [ org.postgresql.util.PSQLException: ERROR: current
transaction is aborted, commands ignored until end of transaction block ] which
will not be reported to listeners!
org.postgresql.util.PSQLException: ERROR: current transaction is aborted,
commands ignored until end of transaction block
at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2161)
at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1890)
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:559)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:417)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:302)
at
com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeQuery(NewProxyPreparedStatement.java:353)
at
org.eclipse.persistence.internal.databaseaccess.DatabasePlatform.wasFailureCommunicationBased(DatabasePlatform.java:2914)
at
org.eclipse.persistence.platform.server.ServerPlatformBase.wasFailureCommunicationBased(ServerPlatformBase.java:546)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.processExceptionForCommError(DatabaseAccessor.java:1616)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:900)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:964)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:633)
at
org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:149)
at
org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatchedStatements(ParameterizedSQLBatchWritingMechanism.java:134)
at
org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.writesCompleted(DatabaseAccessor.java:1845)
at
org.eclipse.persistence.internal.sessions.AbstractSession.writesCompleted(AbstractSession.java:4300)
at
org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.writesCompleted(UnitOfWorkImpl.java:5592)
at
org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.acquireWriteLocks(UnitOfWorkImpl.java:1646)
at
org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitTransactionAfterWriteChanges(UnitOfWorkImpl.java:1614)
at
org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.commitRootUnitOfWork(RepeatableWriteUnitOfWork.java:285)
at
org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitAndResume(UnitOfWorkImpl.java:1169)
at
org.eclipse.persistence.internal.jpa.transaction.EntityTransactionImpl.commit(EntityTransactionImpl.java:134)
at
org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:153)
at
com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:72)
at
com.google.inject.internal.InterceptorStackCallback.intercept(InterceptorStackCallback.java:52)
at
org.apache.ambari.server.orm.dao.PermissionDAO$$EnhancerByGuice$$abe53a1.merge()
at
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.addAuthorizationToRole(AbstractUpgradeCatalog.java:888)
at
[jira] [Commented] (AMBARI-18713) use exclude list of mount device types on docker containers
[
https://issues.apache.org/jira/browse/AMBARI-18713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15622661#comment-15622661
]
Hadoop QA commented on AMBARI-18713:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836143/AMBARI-18713.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9060//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9060//console
This message is automatically generated.
> use exclude list of mount device types on docker containers
> ---
>
> Key: AMBARI-18713
> URL: https://issues.apache.org/jira/browse/AMBARI-18713
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Dmytro Grinenko
>Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18713.patch
>
>
> * Remove logic from UI that picks a single host to represent the entire
> cluster
> * Have each host report their mount devices and how much space is available
> in each one, so Ambari can store this in the DB (this will affect new
> installs only or newly registered hosts)
> * Move logic to Stack Advisor
> * Use exclude list
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18711) Ambari-server: DB changes to enable/disable credential store support
[ https://issues.apache.org/jira/browse/AMBARI-18711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18711: --- Attachment: (was: rb53216.patch) > Ambari-server: DB changes to enable/disable credential store support > > > Key: AMBARI-18711 > URL: https://issues.apache.org/jira/browse/AMBARI-18711 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.5.0 > > Attachments: rb53216.patch > > > To enable or disable a component to use credential store, changes are > required in the DB to keep track of this information. The > _servicedesiredstate_ table can keep track of this information using a new > *credential_store_enabled* column. > If a service supports reading passwords from the configuration's JCEKS file, > then it will specify this information in its stack definition. Services that > support using the credential store can be enabled or disabled to use it. > Services that do not, will always be disabled from using the credential store. > The option to enable or disable the components of a service that has > credential store support is provided via the UI and blueprint. This > information will then be captured in the _servicedesiredstate_ table in the > *credential_store_enabled* column. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18711) Ambari-server: DB changes to enable/disable credential store support
[ https://issues.apache.org/jira/browse/AMBARI-18711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18711: --- Attachment: rb53216.patch > Ambari-server: DB changes to enable/disable credential store support > > > Key: AMBARI-18711 > URL: https://issues.apache.org/jira/browse/AMBARI-18711 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.5.0 > > Attachments: rb53216.patch > > > To enable or disable a component to use credential store, changes are > required in the DB to keep track of this information. The > _servicedesiredstate_ table can keep track of this information using a new > *credential_store_enabled* column. > If a service supports reading passwords from the configuration's JCEKS file, > then it will specify this information in its stack definition. Services that > support using the credential store can be enabled or disabled to use it. > Services that do not, will always be disabled from using the credential store. > The option to enable or disable the components of a service that has > credential store support is provided via the UI and blueprint. This > information will then be captured in the _servicedesiredstate_ table in the > *credential_store_enabled* column. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18711) Ambari-server: DB changes to enable/disable credential store support
[ https://issues.apache.org/jira/browse/AMBARI-18711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nahappan Somasundaram updated AMBARI-18711: --- Status: Patch Available (was: Open) > Ambari-server: DB changes to enable/disable credential store support > > > Key: AMBARI-18711 > URL: https://issues.apache.org/jira/browse/AMBARI-18711 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.5.0 > > Attachments: rb53216.patch > > > To enable or disable a component to use credential store, changes are > required in the DB to keep track of this information. The > _servicedesiredstate_ table can keep track of this information using a new > *credential_store_enabled* column. > If a service supports reading passwords from the configuration's JCEKS file, > then it will specify this information in its stack definition. Services that > support using the credential store can be enabled or disabled to use it. > Services that do not, will always be disabled from using the credential store. > The option to enable or disable the components of a service that has > credential store support is provided via the UI and blueprint. This > information will then be captured in the _servicedesiredstate_ table in the > *credential_store_enabled* column. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18750) Test and fix new tables styles on Ambari (part 3)
[ https://issues.apache.org/jira/browse/AMBARI-18750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15622607#comment-15622607 ] Aleksandr Kovalenko commented on AMBARI-18750: -- +1 for the patch > Test and fix new tables styles on Ambari (part 3) > - > > Key: AMBARI-18750 > URL: https://issues.apache.org/jira/browse/AMBARI-18750 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-18750.patch > > > - Make basic restyling of Repositories table (step 1 of installer) > - Replace Remove button on Confirm Hosts step of installer with icon > - Fix space between header and body in Configuration Changes table -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18748) ambari-server upgrade fail (from 2.2.2.0/2.4.0.0/2.4.0.1/2.4.1.0 to 2.4.2.0 )
[
https://issues.apache.org/jira/browse/AMBARI-18748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15622602#comment-15622602
]
Hadoop QA commented on AMBARI-18748:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836166/AMBARI-18748.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9059//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9059//console
This message is automatically generated.
> ambari-server upgrade fail (from 2.2.2.0/2.4.0.0/2.4.0.1/2.4.1.0 to 2.4.2.0 )
> -
>
> Key: AMBARI-18748
> URL: https://issues.apache.org/jira/browse/AMBARI-18748
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.2
>
> Attachments: AMBARI-18748.patch
>
>
> 1)Install old version regarding env.
> 2)Make ambari only upgrade
> Actual result:
> ambari-server upgrade fell
> {code}
> 2016-10-28 01:20:19,601 ERROR
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
> *Command '[ambari-server upgrade --verbose, ]'
> failed with exitcode 11 ***
> 2016-10-28 01:20:19,603 INFO
> com.hw.ambari.ui.util.cluster_managers.UpgradeClusterManager.upgrade_schema():
> Result of ambari-server upgrade command:
> 2016-10-28 01:20:19,603 INFO
> com.hw.ambari.ui.util.cluster_managers.UpgradeClusterManager.upgrade_schema():
> [OUTPUT STREAM]
> Using python /usr/bin/python
> Upgrading ambari-server
> Updating properties in ambari.properties ...
> WARNING: Original file ambari-env.sh kept
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: No mpack replay logs found. Skipping replaying mpack commands
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Fixing database objects owner
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Ambari Server configured for MySQL. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? INFO: Loading properties from
> /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Upgrading database schema
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: /usr/lib/jvm/java-7-openjdk-amd64/bin/java -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/mysql-connector-java.jar'
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
> /var/log/ambari-server/ambari-server.out 2>&1
> INFO: Return code from schema upgrade command, retcode = 1
> Error output from schema upgrade command:
> Exception in thread "main" org.apache.ambari.server.AmbariException: Entity
> must be managed to call remove:
> org.apache.ambari.server.orm.entities.PrincipalEntity@5e81dbde, try merging
> the detached and try the remove again.
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:356)
> Caused by: java.lang.IllegalArgumentException: Entity must be managed to call
> remove: org.apache.ambari.server.orm.entities.PrincipalEntity@5e81dbde, try
> merging the detached and try the remove again.
>
[jira] [Commented] (AMBARI-18747) Ambari Upgrade Failed from 2.4.1 to 2.5
[
https://issues.apache.org/jira/browse/AMBARI-18747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15622578#comment-15622578
]
Hudson commented on AMBARI-18747:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5893 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5893/])
AMBARI-18747 - Ambari Upgrade Failed from 2.4.1 to 2.5 (jonathanhurley)
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=edd558874488d64814cbda44c3d1c25fb02d467e])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalogTest.java
> Ambari Upgrade Failed from 2.4.1 to 2.5
> ---
>
> Key: AMBARI-18747
> URL: https://issues.apache.org/jira/browse/AMBARI-18747
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18747.patch
>
>
> {code}Exception in thread "main" org.apache.ambari.server.AmbariException:
> Guice provision errors:
> 1) Tried proxying org.apache.ambari.server.state.ConfigHelper to support a
> circular dependency, but it is not an interface.
> at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
> while locating org.apache.ambari.server.state.ConfigHelper
> for field at
> org.apache.ambari.server.state.cluster.ClusterImpl.configHelper(ClusterImpl.java:162)
> while locating
> org.apache.ambari.server.state.cluster.ClusterImpl$$EnhancerByGuice$$7fe3f0d9
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.(ClusterImpl.java:315)
> while locating org.apache.ambari.server.state.Cluster annotated with
> interface com.google.inject.assistedinject.Assisted
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:102)
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
> while locating org.apache.ambari.server.state.cluster.ClustersImpl
> while locating org.apache.ambari.server.state.Clusters
> for parameter 0 at
> org.apache.ambari.server.state.ConfigHelper.(ConfigHelper.java:103)
> at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
> while locating org.apache.ambari.server.state.ConfigHelper
> 1 error
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:244)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:363)
> Caused by: com.google.inject.ProvisionException: Guice provision errors:
> 1) Tried proxying org.apache.ambari.server.state.ConfigHelper to support a
> circular dependency, but it is not an interface.
> at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
> while locating org.apache.ambari.server.state.ConfigHelper
> for field at
> org.apache.ambari.server.state.cluster.ClusterImpl.configHelper(ClusterImpl.java:162)
> while locating
> org.apache.ambari.server.state.cluster.ClusterImpl$$EnhancerByGuice$$7fe3f0d9
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.(ClusterImpl.java:315)
> while locating org.apache.ambari.server.state.Cluster annotated with
> interface com.google.inject.assistedinject.Assisted
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:102)
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
> while locating org.apache.ambari.server.state.cluster.ClustersImpl
> while locating org.apache.ambari.server.state.Clusters
> for parameter 0 at
> org.apache.ambari.server.state.ConfigHelper.(ConfigHelper.java:103)
> at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
> while locating org.apache.ambari.server.state.ConfigHelper
> 1 error
> at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:987)
> at
> com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1013)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.addNewConfigurationsFromXml(AbstractUpgradeCatalog.java:381)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog242.executeDMLUpdates(UpgradeCatalog242.java:121)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:954)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:241)
> ... 1 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18711) Ambari-server: DB changes to enable/disable credential store support
[ https://issues.apache.org/jira/browse/AMBARI-18711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15622576#comment-15622576 ] Hudson commented on AMBARI-18711: - FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5893 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5893/]) Revert "AMBARI-18711: Ambari-server: DB changes to enable/disable (nsomasundaram: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=59430dccc51490d0868b87f6cc63e970947e182a]) * (edit) ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLAnywhere-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/Service.java * (edit) ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/state/ServiceImpl.java * (edit) ambari-server/src/main/resources/Ambari-DDL-Derby-CREATE.sql * (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql * (edit) ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ServiceDesiredStateEntity.java > Ambari-server: DB changes to enable/disable credential store support > > > Key: AMBARI-18711 > URL: https://issues.apache.org/jira/browse/AMBARI-18711 > Project: Ambari > Issue Type: Task > Components: ambari-server >Affects Versions: 2.4.2 >Reporter: Nahappan Somasundaram >Assignee: Nahappan Somasundaram > Fix For: 2.5.0 > > Attachments: rb53216.patch > > > To enable or disable a component to use credential store, changes are > required in the DB to keep track of this information. The > _servicedesiredstate_ table can keep track of this information using a new > *credential_store_enabled* column. > If a service supports reading passwords from the configuration's JCEKS file, > then it will specify this information in its stack definition. Services that > support using the credential store can be enabled or disabled to use it. > Services that do not, will always be disabled from using the credential store. > The option to enable or disable the components of a service that has > credential store support is provided via the UI and blueprint. This > information will then be captured in the _servicedesiredstate_ table in the > *credential_store_enabled* column. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18747) Ambari Upgrade Failed from 2.4.1 to 2.5
[
https://issues.apache.org/jira/browse/AMBARI-18747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15622545#comment-15622545
]
Hudson commented on AMBARI-18747:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #231 (See
[https://builds.apache.org/job/Ambari-branch-2.5/231/])
AMBARI-18747 - Ambari Upgrade Failed from 2.4.1 to 2.5 (jonathanhurley)
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=726b0605fc484f9422ef1a2bb975a2e4f220afd2])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalogTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/AbstractUpgradeCatalog.java
> Ambari Upgrade Failed from 2.4.1 to 2.5
> ---
>
> Key: AMBARI-18747
> URL: https://issues.apache.org/jira/browse/AMBARI-18747
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18747.patch
>
>
> {code}Exception in thread "main" org.apache.ambari.server.AmbariException:
> Guice provision errors:
> 1) Tried proxying org.apache.ambari.server.state.ConfigHelper to support a
> circular dependency, but it is not an interface.
> at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
> while locating org.apache.ambari.server.state.ConfigHelper
> for field at
> org.apache.ambari.server.state.cluster.ClusterImpl.configHelper(ClusterImpl.java:162)
> while locating
> org.apache.ambari.server.state.cluster.ClusterImpl$$EnhancerByGuice$$7fe3f0d9
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.(ClusterImpl.java:315)
> while locating org.apache.ambari.server.state.Cluster annotated with
> interface com.google.inject.assistedinject.Assisted
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:102)
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
> while locating org.apache.ambari.server.state.cluster.ClustersImpl
> while locating org.apache.ambari.server.state.Clusters
> for parameter 0 at
> org.apache.ambari.server.state.ConfigHelper.(ConfigHelper.java:103)
> at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
> while locating org.apache.ambari.server.state.ConfigHelper
> 1 error
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:244)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:363)
> Caused by: com.google.inject.ProvisionException: Guice provision errors:
> 1) Tried proxying org.apache.ambari.server.state.ConfigHelper to support a
> circular dependency, but it is not an interface.
> at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
> while locating org.apache.ambari.server.state.ConfigHelper
> for field at
> org.apache.ambari.server.state.cluster.ClusterImpl.configHelper(ClusterImpl.java:162)
> while locating
> org.apache.ambari.server.state.cluster.ClusterImpl$$EnhancerByGuice$$7fe3f0d9
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.(ClusterImpl.java:315)
> while locating org.apache.ambari.server.state.Cluster annotated with
> interface com.google.inject.assistedinject.Assisted
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:102)
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
> while locating org.apache.ambari.server.state.cluster.ClustersImpl
> while locating org.apache.ambari.server.state.Clusters
> for parameter 0 at
> org.apache.ambari.server.state.ConfigHelper.(ConfigHelper.java:103)
> at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
> while locating org.apache.ambari.server.state.ConfigHelper
> 1 error
> at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:987)
> at
> com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1013)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.addNewConfigurationsFromXml(AbstractUpgradeCatalog.java:381)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog242.executeDMLUpdates(UpgradeCatalog242.java:121)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:954)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:241)
> ... 1 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18750) Test and fix new tables styles on Ambari (part 3)
[ https://issues.apache.org/jira/browse/AMBARI-18750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-18750: -- Status: Patch Available (was: Open) > Test and fix new tables styles on Ambari (part 3) > - > > Key: AMBARI-18750 > URL: https://issues.apache.org/jira/browse/AMBARI-18750 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-18750.patch > > > - Make basic restyling of Repositories table (step 1 of installer) > - Replace Remove button on Confirm Hosts step of installer with icon > - Fix space between header and body in Configuration Changes table -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18750) Test and fix new tables styles on Ambari (part 3)
[ https://issues.apache.org/jira/browse/AMBARI-18750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Babiichuk updated AMBARI-18750: -- Attachment: AMBARI-18750.patch > Test and fix new tables styles on Ambari (part 3) > - > > Key: AMBARI-18750 > URL: https://issues.apache.org/jira/browse/AMBARI-18750 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 3.0.0 >Reporter: Andrii Babiichuk >Assignee: Andrii Babiichuk > Fix For: 3.0.0 > > Attachments: AMBARI-18750.patch > > > - Make basic restyling of Repositories table (step 1 of installer) > - Replace Remove button on Confirm Hosts step of installer with icon > - Fix space between header and body in Configuration Changes table -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-18749) Hosts paging works incorrectly with service and component filters
[ https://issues.apache.org/jira/browse/AMBARI-18749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15622502#comment-15622502 ] Andrii Tkach commented on AMBARI-18749: --- +1 for the patch > Hosts paging works incorrectly with service and component filters > - > > Key: AMBARI-18749 > URL: https://issues.apache.org/jira/browse/AMBARI-18749 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18749.patch > > > Steps: > # Go to Hosts page. > # Set page size to 10 rows. > # Set filter hosts by any component/service in any state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18749) Hosts paging works incorrectly with service and component filters
[ https://issues.apache.org/jira/browse/AMBARI-18749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-18749: - Attachment: AMBARI-18749.patch > Hosts paging works incorrectly with service and component filters > - > > Key: AMBARI-18749 > URL: https://issues.apache.org/jira/browse/AMBARI-18749 > Project: Ambari > Issue Type: Bug > Components: ambari-web >Affects Versions: 2.4.2 >Reporter: Antonenko Alexander >Assignee: Antonenko Alexander >Priority: Critical > Fix For: 2.4.2 > > Attachments: AMBARI-18749.patch > > > Steps: > # Go to Hosts page. > # Set page size to 10 rows. > # Set filter hosts by any component/service in any state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AMBARI-18749) Hosts paging works incorrectly with service and component filters
Antonenko Alexander created AMBARI-18749: Summary: Hosts paging works incorrectly with service and component filters Key: AMBARI-18749 URL: https://issues.apache.org/jira/browse/AMBARI-18749 Project: Ambari Issue Type: Bug Components: ambari-web Affects Versions: 2.4.2 Reporter: Antonenko Alexander Assignee: Antonenko Alexander Priority: Critical Fix For: 2.4.2 Steps: # Go to Hosts page. # Set page size to 10 rows. # Set filter hosts by any component/service in any state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18747) Ambari Upgrade Failed from 2.4.1 to 2.5
[
https://issues.apache.org/jira/browse/AMBARI-18747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-18747:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Ambari Upgrade Failed from 2.4.1 to 2.5
> ---
>
> Key: AMBARI-18747
> URL: https://issues.apache.org/jira/browse/AMBARI-18747
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18747.patch
>
>
> {code}Exception in thread "main" org.apache.ambari.server.AmbariException:
> Guice provision errors:
> 1) Tried proxying org.apache.ambari.server.state.ConfigHelper to support a
> circular dependency, but it is not an interface.
> at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
> while locating org.apache.ambari.server.state.ConfigHelper
> for field at
> org.apache.ambari.server.state.cluster.ClusterImpl.configHelper(ClusterImpl.java:162)
> while locating
> org.apache.ambari.server.state.cluster.ClusterImpl$$EnhancerByGuice$$7fe3f0d9
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.(ClusterImpl.java:315)
> while locating org.apache.ambari.server.state.Cluster annotated with
> interface com.google.inject.assistedinject.Assisted
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:102)
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
> while locating org.apache.ambari.server.state.cluster.ClustersImpl
> while locating org.apache.ambari.server.state.Clusters
> for parameter 0 at
> org.apache.ambari.server.state.ConfigHelper.(ConfigHelper.java:103)
> at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
> while locating org.apache.ambari.server.state.ConfigHelper
> 1 error
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:244)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:363)
> Caused by: com.google.inject.ProvisionException: Guice provision errors:
> 1) Tried proxying org.apache.ambari.server.state.ConfigHelper to support a
> circular dependency, but it is not an interface.
> at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
> while locating org.apache.ambari.server.state.ConfigHelper
> for field at
> org.apache.ambari.server.state.cluster.ClusterImpl.configHelper(ClusterImpl.java:162)
> while locating
> org.apache.ambari.server.state.cluster.ClusterImpl$$EnhancerByGuice$$7fe3f0d9
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.(ClusterImpl.java:315)
> while locating org.apache.ambari.server.state.Cluster annotated with
> interface com.google.inject.assistedinject.Assisted
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:102)
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
> while locating org.apache.ambari.server.state.cluster.ClustersImpl
> while locating org.apache.ambari.server.state.Clusters
> for parameter 0 at
> org.apache.ambari.server.state.ConfigHelper.(ConfigHelper.java:103)
> at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
> while locating org.apache.ambari.server.state.ConfigHelper
> 1 error
> at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:987)
> at
> com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1013)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.addNewConfigurationsFromXml(AbstractUpgradeCatalog.java:381)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog242.executeDMLUpdates(UpgradeCatalog242.java:121)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:954)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:241)
> ... 1 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18748) ambari-server upgrade fail (from 2.2.2.0/2.4.0.0/2.4.0.1/2.4.1.0 to 2.4.2.0 )
[
https://issues.apache.org/jira/browse/AMBARI-18748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18748:
---
Status: Patch Available (was: Open)
> ambari-server upgrade fail (from 2.2.2.0/2.4.0.0/2.4.0.1/2.4.1.0 to 2.4.2.0 )
> -
>
> Key: AMBARI-18748
> URL: https://issues.apache.org/jira/browse/AMBARI-18748
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.2
>
> Attachments: AMBARI-18748.patch
>
>
> 1)Install old version regarding env.
> 2)Make ambari only upgrade
> Actual result:
> ambari-server upgrade fell
> {code}
> 2016-10-28 01:20:19,601 ERROR
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
> *Command '[ambari-server upgrade --verbose, ]'
> failed with exitcode 11 ***
> 2016-10-28 01:20:19,603 INFO
> com.hw.ambari.ui.util.cluster_managers.UpgradeClusterManager.upgrade_schema():
> Result of ambari-server upgrade command:
> 2016-10-28 01:20:19,603 INFO
> com.hw.ambari.ui.util.cluster_managers.UpgradeClusterManager.upgrade_schema():
> [OUTPUT STREAM]
> Using python /usr/bin/python
> Upgrading ambari-server
> Updating properties in ambari.properties ...
> WARNING: Original file ambari-env.sh kept
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: No mpack replay logs found. Skipping replaying mpack commands
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Fixing database objects owner
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Ambari Server configured for MySQL. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? INFO: Loading properties from
> /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Upgrading database schema
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: /usr/lib/jvm/java-7-openjdk-amd64/bin/java -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/mysql-connector-java.jar'
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
> /var/log/ambari-server/ambari-server.out 2>&1
> INFO: Return code from schema upgrade command, retcode = 1
> Error output from schema upgrade command:
> Exception in thread "main" org.apache.ambari.server.AmbariException: Entity
> must be managed to call remove:
> org.apache.ambari.server.orm.entities.PrincipalEntity@5e81dbde, try merging
> the detached and try the remove again.
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:356)
> Caused by: java.lang.IllegalArgumentException: Entity must be managed to call
> remove: org.apache.ambari.server.orm.entities.PrincipalEntity@5e81dbde, try
> merging the detached and try the remove again.
> at
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.performRemove(UnitOfWorkImpl.java:3578)
> at
> org.eclipse.persistence.internal.jpa.EntityManagerImpl.remove(EntityManagerImpl.java:574)
> at
> org.apache.ambari.server.orm.dao.PrincipalDAO.remove(PrincipalDAO.java:132)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:128)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog242.convertRolePrincipals(UpgradeCatalog242.java:213)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog242.executeDMLUpdates(UpgradeCatalog242.java:122)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:908)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> ... 1 more
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Ambari server upgrade failed. Please look at
> /var/log/ambari-server/ambari-server.log, for more details.
> ERROR:
[jira] [Updated] (AMBARI-18748) ambari-server upgrade fail (from 2.2.2.0/2.4.0.0/2.4.0.1/2.4.1.0 to 2.4.2.0 )
[
https://issues.apache.org/jira/browse/AMBARI-18748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitaly Brodetskyi updated AMBARI-18748:
---
Attachment: AMBARI-18748.patch
> ambari-server upgrade fail (from 2.2.2.0/2.4.0.0/2.4.0.1/2.4.1.0 to 2.4.2.0 )
> -
>
> Key: AMBARI-18748
> URL: https://issues.apache.org/jira/browse/AMBARI-18748
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Blocker
> Fix For: 2.4.2
>
> Attachments: AMBARI-18748.patch
>
>
> 1)Install old version regarding env.
> 2)Make ambari only upgrade
> Actual result:
> ambari-server upgrade fell
> {code}
> 2016-10-28 01:20:19,601 ERROR
> com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
> *Command '[ambari-server upgrade --verbose, ]'
> failed with exitcode 11 ***
> 2016-10-28 01:20:19,603 INFO
> com.hw.ambari.ui.util.cluster_managers.UpgradeClusterManager.upgrade_schema():
> Result of ambari-server upgrade command:
> 2016-10-28 01:20:19,603 INFO
> com.hw.ambari.ui.util.cluster_managers.UpgradeClusterManager.upgrade_schema():
> [OUTPUT STREAM]
> Using python /usr/bin/python
> Upgrading ambari-server
> Updating properties in ambari.properties ...
> WARNING: Original file ambari-env.sh kept
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: No mpack replay logs found. Skipping replaying mpack commands
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Fixing database objects owner
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Ambari Server configured for MySQL. Confirm you have made a backup of the
> Ambari Server database [y/n] (y)? INFO: Loading properties from
> /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> Upgrading database schema
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
> INFO: about to run command: /usr/lib/jvm/java-7-openjdk-amd64/bin/java -cp
> '/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/mysql-connector-java.jar'
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
> /var/log/ambari-server/ambari-server.out 2>&1
> INFO: Return code from schema upgrade command, retcode = 1
> Error output from schema upgrade command:
> Exception in thread "main" org.apache.ambari.server.AmbariException: Entity
> must be managed to call remove:
> org.apache.ambari.server.orm.entities.PrincipalEntity@5e81dbde, try merging
> the detached and try the remove again.
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:356)
> Caused by: java.lang.IllegalArgumentException: Entity must be managed to call
> remove: org.apache.ambari.server.orm.entities.PrincipalEntity@5e81dbde, try
> merging the detached and try the remove again.
> at
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.performRemove(UnitOfWorkImpl.java:3578)
> at
> org.eclipse.persistence.internal.jpa.EntityManagerImpl.remove(EntityManagerImpl.java:574)
> at
> org.apache.ambari.server.orm.dao.PrincipalDAO.remove(PrincipalDAO.java:132)
> at
> org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:128)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog242.convertRolePrincipals(UpgradeCatalog242.java:213)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog242.executeDMLUpdates(UpgradeCatalog242.java:122)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:908)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
> ... 1 more
> ERROR: Error executing schema upgrade, please check the server logs.
> ERROR: Ambari server upgrade failed. Please look at
> /var/log/ambari-server/ambari-server.log, for more details.
> ERROR: Exiting
[jira] [Created] (AMBARI-18748) ambari-server upgrade fail (from 2.2.2.0/2.4.0.0/2.4.0.1/2.4.1.0 to 2.4.2.0 )
Vitaly Brodetskyi created AMBARI-18748:
--
Summary: ambari-server upgrade fail (from
2.2.2.0/2.4.0.0/2.4.0.1/2.4.1.0 to 2.4.2.0 )
Key: AMBARI-18748
URL: https://issues.apache.org/jira/browse/AMBARI-18748
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.2
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Blocker
Fix For: 2.4.2
1)Install old version regarding env.
2)Make ambari only upgrade
Actual result:
ambari-server upgrade fell
{code}
2016-10-28 01:20:19,601 ERROR
com.hw.ambari.ui.util.cluster_managers.CommandExecutor.executeCommandSequence():
*Command '[ambari-server upgrade --verbose, ]' failed
with exitcode 11 ***
2016-10-28 01:20:19,603 INFO
com.hw.ambari.ui.util.cluster_managers.UpgradeClusterManager.upgrade_schema():
Result of ambari-server upgrade command:
2016-10-28 01:20:19,603 INFO
com.hw.ambari.ui.util.cluster_managers.UpgradeClusterManager.upgrade_schema():
[OUTPUT STREAM]
Using python /usr/bin/python
Upgrading ambari-server
Updating properties in ambari.properties ...
WARNING: Original file ambari-env.sh kept
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
INFO: No mpack replay logs found. Skipping replaying mpack commands
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
Fixing database objects owner
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
Ambari Server configured for MySQL. Confirm you have made a backup of the
Ambari Server database [y/n] (y)? INFO: Loading properties from
/etc/ambari-server/conf/ambari.properties
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
Upgrading database schema
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
INFO: AMBARI_SERVER_LIB is not set, using default /usr/lib/ambari-server
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
INFO: Loading properties from /etc/ambari-server/conf/ambari.properties
INFO: about to run command: /usr/lib/jvm/java-7-openjdk-amd64/bin/java -cp
'/etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/mysql-connector-java.jar'
org.apache.ambari.server.upgrade.SchemaUpgradeHelper >
/var/log/ambari-server/ambari-server.out 2>&1
INFO: Return code from schema upgrade command, retcode = 1
Error output from schema upgrade command:
Exception in thread "main" org.apache.ambari.server.AmbariException: Entity
must be managed to call remove:
org.apache.ambari.server.orm.entities.PrincipalEntity@5e81dbde, try merging the
detached and try the remove again.
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:240)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:356)
Caused by: java.lang.IllegalArgumentException: Entity must be managed to call
remove: org.apache.ambari.server.orm.entities.PrincipalEntity@5e81dbde, try
merging the detached and try the remove again.
at
org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.performRemove(UnitOfWorkImpl.java:3578)
at
org.eclipse.persistence.internal.jpa.EntityManagerImpl.remove(EntityManagerImpl.java:574)
at
org.apache.ambari.server.orm.dao.PrincipalDAO.remove(PrincipalDAO.java:132)
at
org.apache.ambari.server.orm.AmbariJpaLocalTxnInterceptor.invoke(AmbariJpaLocalTxnInterceptor.java:128)
at
org.apache.ambari.server.upgrade.UpgradeCatalog242.convertRolePrincipals(UpgradeCatalog242.java:213)
at
org.apache.ambari.server.upgrade.UpgradeCatalog242.executeDMLUpdates(UpgradeCatalog242.java:122)
at
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:908)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:237)
... 1 more
ERROR: Error executing schema upgrade, please check the server logs.
ERROR: Ambari server upgrade failed. Please look at
/var/log/ambari-server/ambari-server.log, for more details.
ERROR: Exiting with exit code 11.
REASON: Schema upgrade failed.
[ERROR STREAM]
stdin: is not a tty
[EXIT CODE]
11
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18700) Add HDFS resources for HBase, Spark, Spark2, Zeppelin to AmbariPreupload script
[
https://issues.apache.org/jira/browse/AMBARI-18700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15622193#comment-15622193
]
Hadoop QA commented on AMBARI-18700:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12835987/AMBARI-18700.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9058//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9058//console
This message is automatically generated.
> Add HDFS resources for HBase, Spark, Spark2, Zeppelin to AmbariPreupload
> script
> ---
>
> Key: AMBARI-18700
> URL: https://issues.apache.org/jira/browse/AMBARI-18700
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Reporter: Doroszlai, Attila
>Assignee: Doroszlai, Attila
>Priority: Critical
> Fix For: 3.0.0, 2.5.0
>
> Attachments: AMBARI-18700.patch
>
>
> # Create more directories in {{Ambaripreupload.py}}:
> #* HBase: {{/hbase}}, {{/apps/hbase/staging}} and {{/user/hbase}}
> #* Spark: {{/user/spark}}, {{/user/livy}}
> #* Spark2: {{/hdp/spark2-events}}
> #* Zeppelin: {{/user/zeppelin}}, {{/user/zeppelin/test}}, {{/apps/zeppelin}}
> # Copy {{zeppelin-spark-dependencies}} jar to HDFS in {{Ambaripreupload.py}}
> # Skip {{make_tarfile}} call in {{spark_service.py}} for sysprepped host
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18670) Hive view 1.5 does not refresh LDAP credentials for user
[
https://issues.apache.org/jira/browse/AMBARI-18670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15622127#comment-15622127
]
Hadoop QA commented on AMBARI-18670:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836047/AMBARI-18670.trunk.2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
contrib/views/hive-next
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9057//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9057//console
This message is automatically generated.
> Hive view 1.5 does not refresh LDAP credentials for user
>
>
> Key: AMBARI-18670
> URL: https://issues.apache.org/jira/browse/AMBARI-18670
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Ashwin Rajeev
>Assignee: Ashwin Rajeev
> Fix For: 2.5.0
>
> Attachments: AMBARI-18670.trunk.2.patch, AMBARI-18670.trunk.patch
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Hive view 1.5 has not support for LDAP authentication.
> * Ask LDAP password during splash screen
> * Ask LDAP password if password changed
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18623) NPE when a non-existent host is provided as part of the host filter
[
https://issues.apache.org/jira/browse/AMBARI-18623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15622114#comment-15622114
]
Hudson commented on AMBARI-18623:
-
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5892 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5892/])
AMBARI-18623. NPE when a non-existent host is provided as part of the
(aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=40637b16746ea4e2eb772e909cee83989ec08d7e])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java
> NPE when a non-existent host is provided as part of the host filter
> ---
>
> Key: AMBARI-18623
> URL: https://issues.apache.org/jira/browse/AMBARI-18623
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-18623.patch
>
>
> When a non-existent host is provided as part of the host filter then server
> throws an NPE.
> API call
>
>
>
> curl -u admin:admin -H "X-Requested-By: ambari" -X POST -d
> '{"RequestInfo":{"context":"YARN Service
> Check","command":"YARN_SERVICE_CHECK"},"Requests/resource_filters":[{"service_name":"YARN","hosts":"hn0-d7d2bf.hdinsight.net"}]}'
> http://localhost:8080/api/v1/clusters/jeezraspark2zeppelin18/requests
> {
> "status": 500,
> "message": "Server Error"
> }
>
>
>
>
> 15 Oct 2016 01:10:28,655 INFO [ambari-client-thread-1378]
> AmbariManagementControllerImpl:3762 - Received action execution request,
> clusterName=jeezraspark2zeppelin18, request=isCommand :true, action :null,
> command :YARN_SERVICE_CHECK, inputs :{}, resourceFilters:
> [RequestResourceFilter{serviceName='YARN', componentName='null',
> hostNames=[hn0-d7d2bf.hdinsight.net]}], exclusive: false, clusterName
> :jeezraspark2zeppelin18
> 15 Oct 2016 01:10:28,658 ERROR [ambari-client-thread-1378]
> BaseManagementHandler:71 - Caught a runtime exception while attempting to
> create a resource: null
> java.lang.NullPointerException
> at
> org.apache.ambari.server.controller.AmbariCustomCommandExecutionHelper.findHostAndAddServiceCheckAction(AmbariCustomCommandExecutionHelper.java:557)
> at
> org.apache.ambari.server.controller.AmbariCustomCommandExecutionHelper.addExecutionCommandsToStage(AmbariCustomCommandExecutionHelper.java:997)
> at
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.createAction(AmbariManagementControllerImpl.java:3818)
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18623) NPE when a non-existent host is provided as part of the host filter
[
https://issues.apache.org/jira/browse/AMBARI-18623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15622105#comment-15622105
]
Hudson commented on AMBARI-18623:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #230 (See
[https://builds.apache.org/job/Ambari-branch-2.5/230/])
AMBARI-18623. NPE when a non-existent host is provided as part of the
(aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=6dc5a23a76ad3053c2df884f49c6d9cabbd1999d])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java
> NPE when a non-existent host is provided as part of the host filter
> ---
>
> Key: AMBARI-18623
> URL: https://issues.apache.org/jira/browse/AMBARI-18623
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-18623.patch
>
>
> When a non-existent host is provided as part of the host filter then server
> throws an NPE.
> API call
>
>
>
> curl -u admin:admin -H "X-Requested-By: ambari" -X POST -d
> '{"RequestInfo":{"context":"YARN Service
> Check","command":"YARN_SERVICE_CHECK"},"Requests/resource_filters":[{"service_name":"YARN","hosts":"hn0-d7d2bf.hdinsight.net"}]}'
> http://localhost:8080/api/v1/clusters/jeezraspark2zeppelin18/requests
> {
> "status": 500,
> "message": "Server Error"
> }
>
>
>
>
> 15 Oct 2016 01:10:28,655 INFO [ambari-client-thread-1378]
> AmbariManagementControllerImpl:3762 - Received action execution request,
> clusterName=jeezraspark2zeppelin18, request=isCommand :true, action :null,
> command :YARN_SERVICE_CHECK, inputs :{}, resourceFilters:
> [RequestResourceFilter{serviceName='YARN', componentName='null',
> hostNames=[hn0-d7d2bf.hdinsight.net]}], exclusive: false, clusterName
> :jeezraspark2zeppelin18
> 15 Oct 2016 01:10:28,658 ERROR [ambari-client-thread-1378]
> BaseManagementHandler:71 - Caught a runtime exception while attempting to
> create a resource: null
> java.lang.NullPointerException
> at
> org.apache.ambari.server.controller.AmbariCustomCommandExecutionHelper.findHostAndAddServiceCheckAction(AmbariCustomCommandExecutionHelper.java:557)
> at
> org.apache.ambari.server.controller.AmbariCustomCommandExecutionHelper.addExecutionCommandsToStage(AmbariCustomCommandExecutionHelper.java:997)
> at
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.createAction(AmbariManagementControllerImpl.java:3818)
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18747) Ambari Upgrade Failed from 2.4.1 to 2.5
[
https://issues.apache.org/jira/browse/AMBARI-18747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-18747:
-
Status: Patch Available (was: Open)
> Ambari Upgrade Failed from 2.4.1 to 2.5
> ---
>
> Key: AMBARI-18747
> URL: https://issues.apache.org/jira/browse/AMBARI-18747
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18747.patch
>
>
> {code}Exception in thread "main" org.apache.ambari.server.AmbariException:
> Guice provision errors:
> 1) Tried proxying org.apache.ambari.server.state.ConfigHelper to support a
> circular dependency, but it is not an interface.
> at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
> while locating org.apache.ambari.server.state.ConfigHelper
> for field at
> org.apache.ambari.server.state.cluster.ClusterImpl.configHelper(ClusterImpl.java:162)
> while locating
> org.apache.ambari.server.state.cluster.ClusterImpl$$EnhancerByGuice$$7fe3f0d9
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.(ClusterImpl.java:315)
> while locating org.apache.ambari.server.state.Cluster annotated with
> interface com.google.inject.assistedinject.Assisted
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:102)
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
> while locating org.apache.ambari.server.state.cluster.ClustersImpl
> while locating org.apache.ambari.server.state.Clusters
> for parameter 0 at
> org.apache.ambari.server.state.ConfigHelper.(ConfigHelper.java:103)
> at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
> while locating org.apache.ambari.server.state.ConfigHelper
> 1 error
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:244)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:363)
> Caused by: com.google.inject.ProvisionException: Guice provision errors:
> 1) Tried proxying org.apache.ambari.server.state.ConfigHelper to support a
> circular dependency, but it is not an interface.
> at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
> while locating org.apache.ambari.server.state.ConfigHelper
> for field at
> org.apache.ambari.server.state.cluster.ClusterImpl.configHelper(ClusterImpl.java:162)
> while locating
> org.apache.ambari.server.state.cluster.ClusterImpl$$EnhancerByGuice$$7fe3f0d9
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.(ClusterImpl.java:315)
> while locating org.apache.ambari.server.state.Cluster annotated with
> interface com.google.inject.assistedinject.Assisted
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:102)
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
> while locating org.apache.ambari.server.state.cluster.ClustersImpl
> while locating org.apache.ambari.server.state.Clusters
> for parameter 0 at
> org.apache.ambari.server.state.ConfigHelper.(ConfigHelper.java:103)
> at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
> while locating org.apache.ambari.server.state.ConfigHelper
> 1 error
> at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:987)
> at
> com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1013)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.addNewConfigurationsFromXml(AbstractUpgradeCatalog.java:381)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog242.executeDMLUpdates(UpgradeCatalog242.java:121)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:954)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:241)
> ... 1 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18747) Ambari Upgrade Failed from 2.4.1 to 2.5
[
https://issues.apache.org/jira/browse/AMBARI-18747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-18747:
-
Attachment: AMBARI-18747.patch
> Ambari Upgrade Failed from 2.4.1 to 2.5
> ---
>
> Key: AMBARI-18747
> URL: https://issues.apache.org/jira/browse/AMBARI-18747
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.5.0
>Reporter: Jonathan Hurley
>Assignee: Jonathan Hurley
>Priority: Blocker
> Fix For: 2.5.0
>
> Attachments: AMBARI-18747.patch
>
>
> {code}Exception in thread "main" org.apache.ambari.server.AmbariException:
> Guice provision errors:
> 1) Tried proxying org.apache.ambari.server.state.ConfigHelper to support a
> circular dependency, but it is not an interface.
> at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
> while locating org.apache.ambari.server.state.ConfigHelper
> for field at
> org.apache.ambari.server.state.cluster.ClusterImpl.configHelper(ClusterImpl.java:162)
> while locating
> org.apache.ambari.server.state.cluster.ClusterImpl$$EnhancerByGuice$$7fe3f0d9
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.(ClusterImpl.java:315)
> while locating org.apache.ambari.server.state.Cluster annotated with
> interface com.google.inject.assistedinject.Assisted
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:102)
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
> while locating org.apache.ambari.server.state.cluster.ClustersImpl
> while locating org.apache.ambari.server.state.Clusters
> for parameter 0 at
> org.apache.ambari.server.state.ConfigHelper.(ConfigHelper.java:103)
> at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
> while locating org.apache.ambari.server.state.ConfigHelper
> 1 error
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:244)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:363)
> Caused by: com.google.inject.ProvisionException: Guice provision errors:
> 1) Tried proxying org.apache.ambari.server.state.ConfigHelper to support a
> circular dependency, but it is not an interface.
> at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
> while locating org.apache.ambari.server.state.ConfigHelper
> for field at
> org.apache.ambari.server.state.cluster.ClusterImpl.configHelper(ClusterImpl.java:162)
> while locating
> org.apache.ambari.server.state.cluster.ClusterImpl$$EnhancerByGuice$$7fe3f0d9
> at
> org.apache.ambari.server.state.cluster.ClusterImpl.(ClusterImpl.java:315)
> while locating org.apache.ambari.server.state.Cluster annotated with
> interface com.google.inject.assistedinject.Assisted
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:102)
> at
> org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
> while locating org.apache.ambari.server.state.cluster.ClustersImpl
> while locating org.apache.ambari.server.state.Clusters
> for parameter 0 at
> org.apache.ambari.server.state.ConfigHelper.(ConfigHelper.java:103)
> at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
> while locating org.apache.ambari.server.state.ConfigHelper
> 1 error
> at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:987)
> at
> com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1013)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.addNewConfigurationsFromXml(AbstractUpgradeCatalog.java:381)
> at
> org.apache.ambari.server.upgrade.UpgradeCatalog242.executeDMLUpdates(UpgradeCatalog242.java:121)
> at
> org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:954)
> at
> org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:241)
> ... 1 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18747) Ambari Upgrade Failed from 2.4.1 to 2.5
Jonathan Hurley created AMBARI-18747:
Summary: Ambari Upgrade Failed from 2.4.1 to 2.5
Key: AMBARI-18747
URL: https://issues.apache.org/jira/browse/AMBARI-18747
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.5.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Blocker
Fix For: 2.5.0
{code}Exception in thread "main" org.apache.ambari.server.AmbariException:
Guice provision errors:
1) Tried proxying org.apache.ambari.server.state.ConfigHelper to support a
circular dependency, but it is not an interface.
at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
while locating org.apache.ambari.server.state.ConfigHelper
for field at
org.apache.ambari.server.state.cluster.ClusterImpl.configHelper(ClusterImpl.java:162)
while locating
org.apache.ambari.server.state.cluster.ClusterImpl$$EnhancerByGuice$$7fe3f0d9
at
org.apache.ambari.server.state.cluster.ClusterImpl.(ClusterImpl.java:315)
while locating org.apache.ambari.server.state.Cluster annotated with
interface com.google.inject.assistedinject.Assisted
at
org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:102)
at
org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
while locating org.apache.ambari.server.state.cluster.ClustersImpl
while locating org.apache.ambari.server.state.Clusters
for parameter 0 at
org.apache.ambari.server.state.ConfigHelper.(ConfigHelper.java:103)
at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
while locating org.apache.ambari.server.state.ConfigHelper
1 error
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:244)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:363)
Caused by: com.google.inject.ProvisionException: Guice provision errors:
1) Tried proxying org.apache.ambari.server.state.ConfigHelper to support a
circular dependency, but it is not an interface.
at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
while locating org.apache.ambari.server.state.ConfigHelper
for field at
org.apache.ambari.server.state.cluster.ClusterImpl.configHelper(ClusterImpl.java:162)
while locating
org.apache.ambari.server.state.cluster.ClusterImpl$$EnhancerByGuice$$7fe3f0d9
at
org.apache.ambari.server.state.cluster.ClusterImpl.(ClusterImpl.java:315)
while locating org.apache.ambari.server.state.Cluster annotated with
interface com.google.inject.assistedinject.Assisted
at
org.apache.ambari.server.state.cluster.ClustersImpl.loadClustersAndHosts(ClustersImpl.java:102)
at
org.apache.ambari.server.state.cluster.ClustersImpl.class(ClustersImpl.java:102)
while locating org.apache.ambari.server.state.cluster.ClustersImpl
while locating org.apache.ambari.server.state.Clusters
for parameter 0 at
org.apache.ambari.server.state.ConfigHelper.(ConfigHelper.java:103)
at org.apache.ambari.server.state.ConfigHelper.class(ConfigHelper.java:61)
while locating org.apache.ambari.server.state.ConfigHelper
1 error
at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:987)
at
com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1013)
at
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.addNewConfigurationsFromXml(AbstractUpgradeCatalog.java:381)
at
org.apache.ambari.server.upgrade.UpgradeCatalog242.executeDMLUpdates(UpgradeCatalog242.java:121)
at
org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeData(AbstractUpgradeCatalog.java:954)
at
org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeDMLUpdates(SchemaUpgradeHelper.java:241)
... 1 more
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-18745) Logs wont display for users in Ambari hive view after job completion
[
https://issues.apache.org/jira/browse/AMBARI-18745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15622078#comment-15622078
]
Hadoop QA commented on AMBARI-18745:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836048/AMBARI-18745.trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
contrib/views/hive-next
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9056//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9056//console
This message is automatically generated.
> Logs wont display for users in Ambari hive view after job completion
>
>
> Key: AMBARI-18745
> URL: https://issues.apache.org/jira/browse/AMBARI-18745
> Project: Ambari
> Issue Type: Bug
>Affects Versions: 2.4.0
>Reporter: Ashwin Rajeev
>Assignee: Ashwin Rajeev
> Fix For: 2.4.0
>
> Attachments: AMBARI-18745.trunk.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18713) use exclude list of mount device types on docker containers
[ https://issues.apache.org/jira/browse/AMBARI-18713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-18713: - Status: Patch Available (was: Open) > use exclude list of mount device types on docker containers > --- > > Key: AMBARI-18713 > URL: https://issues.apache.org/jira/browse/AMBARI-18713 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Grinenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18713.patch > > > * Remove logic from UI that picks a single host to represent the entire > cluster > * Have each host report their mount devices and how much space is available > in each one, so Ambari can store this in the DB (this will affect new > installs only or newly registered hosts) > * Move logic to Stack Advisor > * Use exclude list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-18713) use exclude list of mount device types on docker containers
[ https://issues.apache.org/jira/browse/AMBARI-18713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Grinenko updated AMBARI-18713: - Attachment: AMBARI-18713.patch > use exclude list of mount device types on docker containers > --- > > Key: AMBARI-18713 > URL: https://issues.apache.org/jira/browse/AMBARI-18713 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: 2.5.0 >Reporter: Dmytro Grinenko >Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18713.patch > > > * Remove logic from UI that picks a single host to represent the entire > cluster > * Have each host report their mount devices and how much space is available > in each one, so Ambari can store this in the DB (this will affect new > installs only or newly registered hosts) > * Move logic to Stack Advisor > * Use exclude list -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AMBARI-18623) NPE when a non-existent host is provided as part of the host filter
[
https://issues.apache.org/jira/browse/AMBARI-18623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk resolved AMBARI-18623.
--
Resolution: Fixed
Committed to trunk and branch-2.5
> NPE when a non-existent host is provided as part of the host filter
> ---
>
> Key: AMBARI-18623
> URL: https://issues.apache.org/jira/browse/AMBARI-18623
> Project: Ambari
> Issue Type: Bug
>Reporter: Andrew Onischuk
>Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-18623.patch
>
>
> When a non-existent host is provided as part of the host filter then server
> throws an NPE.
> API call
>
>
>
> curl -u admin:admin -H "X-Requested-By: ambari" -X POST -d
> '{"RequestInfo":{"context":"YARN Service
> Check","command":"YARN_SERVICE_CHECK"},"Requests/resource_filters":[{"service_name":"YARN","hosts":"hn0-d7d2bf.hdinsight.net"}]}'
> http://localhost:8080/api/v1/clusters/jeezraspark2zeppelin18/requests
> {
> "status": 500,
> "message": "Server Error"
> }
>
>
>
>
> 15 Oct 2016 01:10:28,655 INFO [ambari-client-thread-1378]
> AmbariManagementControllerImpl:3762 - Received action execution request,
> clusterName=jeezraspark2zeppelin18, request=isCommand :true, action :null,
> command :YARN_SERVICE_CHECK, inputs :{}, resourceFilters:
> [RequestResourceFilter{serviceName='YARN', componentName='null',
> hostNames=[hn0-d7d2bf.hdinsight.net]}], exclusive: false, clusterName
> :jeezraspark2zeppelin18
> 15 Oct 2016 01:10:28,658 ERROR [ambari-client-thread-1378]
> BaseManagementHandler:71 - Caught a runtime exception while attempting to
> create a resource: null
> java.lang.NullPointerException
> at
> org.apache.ambari.server.controller.AmbariCustomCommandExecutionHelper.findHostAndAddServiceCheckAction(AmbariCustomCommandExecutionHelper.java:557)
> at
> org.apache.ambari.server.controller.AmbariCustomCommandExecutionHelper.addExecutionCommandsToStage(AmbariCustomCommandExecutionHelper.java:997)
> at
> org.apache.ambari.server.controller.AmbariManagementControllerImpl.createAction(AmbariManagementControllerImpl.java:3818)
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AMBARI-18746) Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
[
https://issues.apache.org/jira/browse/AMBARI-18746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ying Cao updated AMBARI-18746:
--
Attachment: AMBARI-18746.1.patch
> Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
> ---
>
> Key: AMBARI-18746
> URL: https://issues.apache.org/jira/browse/AMBARI-18746
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
>Affects Versions: 2.4.0
> Environment: Redhat 6.6, Sqoop 1.4.6+Hadoop 2.7.2
>Reporter: Ying Cao
>Priority: Minor
> Fix For: 2.4.1
>
> Attachments: AMBARI-18746.1.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> The parameter hadoop_home is pointed to hbase-client in params_linux.py, and
> need to be updated.
> ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py
> # For stack versions supporting rolling upgrade
> if stack_version_formatted and
>
> hadoop_home = format("{stack_root}/current/hbase-client")
> ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (AMBARI-18746) Sqoop parameter hadoop_home is pointed to incorrect path in params_linux.py
Ying Cao created AMBARI-18746:
-
Summary: Sqoop parameter hadoop_home is pointed to incorrect path
in params_linux.py
Key: AMBARI-18746
URL: https://issues.apache.org/jira/browse/AMBARI-18746
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.4.0
Environment: Redhat 6.6, Sqoop 1.4.6+Hadoop 2.7.2
Reporter: Ying Cao
Priority: Minor
Fix For: 2.4.1
The parameter hadoop_home is pointed to hbase-client in params_linux.py, and
need to be updated.
ambari-server/src/main/resources/common-services/SQOOP/1.4.4.2.0/package/scripts/params_linux.py
# For stack versions supporting rolling upgrade
if stack_version_formatted and
hadoop_home = format("{stack_root}/current/hbase-client")
...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
