server directory is missing pom.xml verified distro dir contains tomcat-6.0.53
On Wed, Jan 24, 2018 at 11:03 PM, satish saley <satishsale...@gmail.com> wrote: > Thank you Robert. I will add that patch.I have java 1.8.0_101-b13, but I > didn't face any issues. I will check with Java 8u91 before and after patch. > @Artem, you can use 4.3 branch https://github.com/ > apache/oozie/tree/branch-4.3 . I haven't created separate branch for this > release. > > > > On Wednesday, January 24, 2018 5:50 PM, Robert Kanter < > rkan...@cloudera.com> wrote: > > > Here's what I did: > - Verified md5 > - Verified signature (gpg) > - Looked at rat report > - Looked at release log > - Verified Tomcat is version 6.0.53 > - Built Oozie against Hadoop 2.7.2, using an empty local maven repo > > > I ran into another problem: OOZIE-2533. Basically, newer versions of Java > + newer versions of Tomcat 6 break JSP compilation so the Oozie Web UI is > completely broken. The JIRA cites Java 8u91 and later, but I still ran > into this even when I tried with Java 7u79. I guess whatever breaks this > in 8u91 must have been backported to 7u79. I heard that it was for some > Java security fix so there's not a lot of detail on it. Applying the patch > from OOZIE-2533 appears to fix it. We've actually been using that patch in > CDH for almost 2 years now. I apologize for forgetting about this when I > reported that we should upgrade Tomcat in RC1. The patch is pretty minor > and basically just replaces the jsp page with a static html page. The only > downside is that the SLA, Instrumentation, and Metrics pages are always > showing, even if those features are disabled (because that's what JSP was > used for). > > > - Robert > > On Wed, Jan 24, 2018 at 4:18 PM, Artem Ervits <artemerv...@gmail.com> > wrote: > > > Satish, I have ansible scripts to pull a git branch and run through > > mkdistro and install steps and I wrote another recipe to stand up a > cluster > > based on binary release. The problem I just realized is that my compile > > from source script relies on a branch which doesn't exist, is it your > > private repo? If so, can you publish that and I'll test it with my > script? > > Otherwise, can you publish the binary release and I'll try to test it as > > well. I have more confidence with compile from source script but that > won't > > work on 4.3.1 until you create the branch on github. That said, results > of > > my test are the following > > > > verified md5 +1 > > tried to build with > > > > *bin/mkdistro.sh -DskipTests -Dhadoop.version=2.7.5* > > > > found the following error > > > > Downloading: > > http://repo1.maven.org/maven2/org/apache/apache-jar- > > resource-bundle/1.4/apache-jar-resource-bundle-1.4.jar > > Downloaded: > > http://repo1.maven.org/maven2/org/apache/apache-jar- > > resource-bundle/1.4/apache-jar-resource-bundle-1.4.jar > > (13 KB at 325.1 KB/sec) > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] Reactor Summary: > > [INFO] > > [INFO] Apache Oozie Main ................................. FAILURE > > [24.265s] > > [INFO] Apache Oozie Hadoop Utils hadoop-2-4.3.1 .......... SKIPPED > > [INFO] Apache Oozie Hadoop Distcp hadoop-2-4.3.1 ......... SKIPPED > > [INFO] Apache Oozie Hadoop Auth hadoop-2-4.3.1 Test ...... SKIPPED > > [INFO] Apache Oozie Hadoop Libs .......................... SKIPPED > > [INFO] Apache Oozie Client ............................... SKIPPED > > [INFO] Apache Oozie Share Lib Oozie ...................... SKIPPED > > [INFO] Apache Oozie Share Lib HCatalog ................... SKIPPED > > [INFO] Apache Oozie Share Lib Distcp ..................... SKIPPED > > [INFO] Apache Oozie Core ................................. SKIPPED > > [INFO] Apache Oozie Share Lib Streaming .................. SKIPPED > > [INFO] Apache Oozie Share Lib Pig ........................ SKIPPED > > [INFO] Apache Oozie Share Lib Hive ....................... SKIPPED > > [INFO] Apache Oozie Share Lib Hive 2 ..................... SKIPPED > > [INFO] Apache Oozie Share Lib Sqoop ...................... SKIPPED > > [INFO] Apache Oozie Examples ............................. SKIPPED > > [INFO] Apache Oozie Share Lib Spark ...................... SKIPPED > > [INFO] Apache Oozie Share Lib ............................ SKIPPED > > [INFO] Apache Oozie Docs ................................. SKIPPED > > [INFO] Apache Oozie WebApp ............................... SKIPPED > > [INFO] Apache Oozie Tools ................................ SKIPPED > > [INFO] Apache Oozie MiniOozie ............................ SKIPPED > > [INFO] Apache Oozie Distro ............................... SKIPPED > > [INFO] Apache Oozie ZooKeeper Security Tests ............. SKIPPED > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] BUILD FAILURE > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] Total time: 55.955s > > [INFO] Finished at: Thu Jan 25 00:14:08 UTC 2018 > > [INFO] Final Memory: 20M/48M > > [INFO] > > ------------------------------------------------------------------------ > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process > > (default) on project oozie-main: Error finding remote resources > manifests: > > /opt/oozie/oozie-4.3.1/target/maven-shared-archive- > > resources/META-INF/NOTICE > > (No such file or directory) -> [Help 1] > > [ERROR] > > [ERROR] To see the full stack trace of the errors, re-run Maven with the > -e > > switch. > > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > > [ERROR] > > [ERROR] For more information about the errors and possible solutions, > > please read the following articles: > > [ERROR] [Help 1] > > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > > > > ERROR, Oozie distro creation failed > > > > again, I just wrote this ansible script and may have missed something. > > > > Thanks > > > > On Wed, Jan 24, 2018 at 2:05 PM, Rohini Palaniswamy <roh...@apache.org> > > wrote: > > > > > +1 (binding) > > > > > > - Verified md5, signature, release log and rat report > > > - Ran the unit tests and they are good. > > > - Executed a simple workflow > > > - Verified that the tomcat is now 6.0.53 > > > > > > Regards, > > > Rohini > > > > > > On Tue, Jan 23, 2018 at 4:27 PM, Satish Saley <satishsa...@apache.org> > > > wrote: > > > > > > > Hi, > > > > > > > > I have created a build for Oozie 4.3.1, candidate 2. > > > > > > > > It includes all the changes decided earlier except OOZIE-3018 and > > > > OOZIE-3072. OOZIE-3018 makes changes to SchemaCheckerService which we > > are > > > > not picking. OOZIE-3072 makes changes to files created in OOZIE-1770. > > > > > > > > Keys to verify the signature of the release artifact are available at > > > > http://www.apache.org/dist/oozie/KEYS > > > > > > > > Please download, test, and try it out: > > > > > > > > http://people.apache.org/~satishsaley/oozie-4.3.1-rc-2/ > > > > > > > > > > > > The release, md5 signature, gpg signature, and rat report can be > found > > at > > > > the above address. > > > > > > > > Vote closes on 01/26/2018 11:59 PM PT. > > > > > > > > > > > > >
