[jira] [Commented] (AMBARI-18751) Upgrade Fails From 2.4.2 to 2.5 Due To Existing Role Authorizations
[
https://issues.apache.org/jira/browse/AMBARI-18751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15629617#comment-15629617
]
Hudson commented on AMBARI-18751:
-
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #242 (See
[https://builds.apache.org/job/Ambari-branch-2.5/242/])
AMBARI-18751. Upgrade Fails From 2.4.2 to 2.5 Due To Existing Role (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3c88933456b4c2db24c157f7cff582758378bdd5])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog242.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog242Test.java
> 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
>
> Attachments: AMBARI-18751_branch-2.4_01.patch,
> AMBARI-18751_branch-2.4_02.patch, AMBARI-18751_branch-2.5_01.patch,
> AMBARI-18751_branch-2.5_02.patch, AMBARI-18751_trunk_01.patch,
> AMBARI-18751_trunk_02.patch
>
>
> 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
>
[jira] [Commented] (AMBARI-18751) Upgrade Fails From 2.4.2 to 2.5 Due To Existing Role Authorizations
[
https://issues.apache.org/jira/browse/AMBARI-18751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15629574#comment-15629574
]
Hudson commented on AMBARI-18751:
-
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5912 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5912/])
AMBARI-18751. Upgrade Fails From 2.4.2 to 2.5 Due To Existing Role (rlevas:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=3b2e103b7e36af9acd91fe3f6f057fb2163f7ef7])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog242Test.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog250.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog250Test.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog242.java
> 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
>
> Attachments: AMBARI-18751_branch-2.4_01.patch,
> AMBARI-18751_branch-2.4_02.patch, AMBARI-18751_branch-2.5_01.patch,
> AMBARI-18751_branch-2.5_02.patch, AMBARI-18751_trunk_01.patch,
> AMBARI-18751_trunk_02.patch
>
>
> 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
>
[jira] [Commented] (AMBARI-18751) Upgrade Fails From 2.4.2 to 2.5 Due To Existing Role Authorizations
[
https://issues.apache.org/jira/browse/AMBARI-18751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15625552#comment-15625552
]
Hadoop QA commented on AMBARI-18751:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12836350/AMBARI-18751_trunk_01.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.controller.metrics.JMXPropertyProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9079//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9079//console
This message is automatically generated.
> 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
>
> Attachments: AMBARI-18751_branch-2.4_01.patch,
> AMBARI-18751_branch-2.5_01.patch, AMBARI-18751_trunk_01.patch
>
>
> 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)
>
