[ https://issues.apache.org/jira/browse/AMBARI-15348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hurley reopened AMBARI-15348: -------------------------------------- This commit breaks {{ambari-server setup}} {code} [root@c6401 yum.repos.d]# ambari-server setup Using python /usr/bin/python Setup ambari-server Checking SELinux... SELinux status is 'disabled' Customize user account for ambari-server daemon [y/n] (n)? Adjusting ambari-server permissions and ownership... Checking firewall status... Checking JDK... [1] Oracle JDK 1.8 + Java Cryptography Extension (JCE) Policy Files 8 [2] Oracle JDK 1.7 + Java Cryptography Extension (JCE) Policy Files 7 [3] Custom JDK ============================================================================== Enter choice (1): To download the Oracle JDK and the Java Cryptography Extension (JCE) Policy Files you must accept the license terms found at http://www.oracle.com/technetwork/java/javase/terms/license/index.html and not accepting will cancel the Ambari Server setup and you must install the JDK and JCE files manually. Do you accept the Oracle Binary Code License Agreement [y/n] (y)? Downloading JDK from http://public-repo-1.hortonworks.com/ARTIFACTS/jdk-8u60-linux-x64.tar.gz to //var/lib/ambari-server/resources/jdk-8u60-linux-x64.tar.gz jdk-8u60-linux-x64.tar.gz... 100% (172.8 MB of 172.8 MB) Successfully downloaded JDK distribution to //var/lib/ambari-server/resources/jdk-8u60-linux-x64.tar.gz Installing JDK to //usr/jdk64/ Successfully installed JDK to //usr/jdk64/ Downloading JCE Policy archive from http://public-repo-1.hortonworks.com/ARTIFACTS/jce_policy-8.zip to //var/lib/ambari-server/resources/jce_policy-8.zip Successfully downloaded JCE Policy archive to //var/lib/ambari-server/resources/jce_policy-8.zip Installing JCE policy... Completing setup... Configuring database... Enter advanced database configuration [y/n] (n)? Configuring database... Default properties detected. Using built-in database. WARNING: Command chown None //etc/ambari-server/conf/password.dat returned exit code //etc/ambari-server/conf/password.dat with message: chown: invalid user: `None' Configuring ambari database... Checking PostgreSQL... Running initdb: This may take up to a minute. Initializing database: [ OK ] About to start PostgreSQL Configuring local database... Connecting to local database...done. Configuring PostgreSQL... Restarting PostgreSQL Extracting system views... ERROR: Exiting with exit code 1. REASON: Multiple versions of javax.servlet.jsp.jstl.jar found in java class path (/usr/lib/ambari-server/javax.servlet.jsp.jstl-1.2.2.jar and /usr/lib/ambari-server/javax.servlet.jsp.jstl-1.2.0.v201105211821.jar). Make sure that you include only one javax.servlet.jsp.jstl.jar in the java class path '//etc/ambari-server/conf:/usr/lib/ambari-server/*:/usr/share/java/postgresql-jdbc.jar'. {code} Reverted from trunk and branch-2.2 {code} Author: Jonathan Hurley <jhur...@hortonworks.com> Date: Mon Mar 14 15:51:58 2016 -0400 Revert "AMBARI-15348 Ambari upgrade/start commands should detect any ambari-server hotfix and fail upgrade/start from proceeding (dsen)" This reverts commit 2b596be9b93682ed436837f4f2b75197ae4349c7. {code} > Ambari upgrade/start commands should detect any ambari-server hotfix and fail > upgrade/start from proceeding > ----------------------------------------------------------------------------------------------------------- > > Key: AMBARI-15348 > URL: https://issues.apache.org/jira/browse/AMBARI-15348 > Project: Ambari > Issue Type: Improvement > Components: ambari-server > Affects Versions: 2.0.0 > Reporter: Dmytro Sen > Assignee: Dmytro Sen > Priority: Critical > Fix For: 2.2.2 > > Attachments: AMBARI-15348-trunk.patch > > > If user copied hotfixed ambari-server.jar to /usr/lib/ambari-server and > didn't remove the hotfix, the upgrade will fails with error: > {code} > Internal Exception: Exception [EclipseLink-7250] (Eclipse Persistence > Services - 2.5.2.v20140319-9ad6abd): > org.eclipse.persistence.exceptions.ValidationException > Exception Description: [class > org.apache.ambari.server.orm.entities.HostEntity] uses a non-entity [class > org.apache.ambari.server.orm.entities.HostVersionEntity] as target entity in > the relationship attribute [field hostVersionEntities]. > at > org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.createPredeployFailedPersistenceException(EntityManagerSetupImpl.java:1954) > at > org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:1945) > at > org.eclipse.persistence.internal.jpa.deployment.JPAInitializer.callPredeploy(JPAInitializer.java:98) > at > org.eclipse.persistence.jpa.PersistenceProvider.createEntityManagerFactoryImpl(PersistenceProvider.java:96) > ... 15 more > Caused by: Exception [EclipseLink-28018] (Eclipse Persistence Services - > 2.5.2.v20140319-9ad6abd): > org.eclipse.persistence.exceptions.EntityManagerSetupException > Exception Description: Predeployment of PersistenceUnit [ambari-server] > failed. > {code} > As a workaround, user needs to restore all the database and configuration, > remove all the hotfix and run "ambari-server upgrade" again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)