Hi Steve,
To answer the first question in your conclusion - I installed 1.16.2
on a brand-new SL6 system back in October and I don't recall any
significant issues.
John
On 07/02/2014 13:54, Stephen Jones wrote:
> All,
>
> We were at CREAM 1.15.1-2. We were advised today by Linda to upgrade
> Cream to 1.16.2. We had a whale of a time doing it. Here's the run down:
>
> --- PART 1 --- THE PROCESS ----------
>
> First, we tried to find all the packages that are on 1.15.1-2 and get
> them up to date, run YAIM, and restart tomcat; reboot etc.
>
> # yum update glite-ce-cream glite-ce-cream-api-java glite-ce-cream-core
> glite-ce-cream-es
> # yaim -c -s /root/glitecfg/site-info.def -n creamCE -n TORQUE_utils
> # /etc/init.d/tomcat6 stop
> # reboot
>
> Then it started to go horribly wrong. We found the following issue after
> upgrading:
>
> 7 Feb 2014 12:01:18,350 org.apache.axis2.deployment.ModuleDeployer - The
> glite-ce-cream-authorization.mar module, which is not valid, caused
> org/italiangrid/voms/store/VOMSTrustStore
> java.lang.NoClassDefFoundError: org/italiangrid/voms/store/VOMSTrustStore
>
> That is, the cream-authorization module wasn't loading, which caused the
> glite-ce-cream service to not work.
>
> --- PART 2 --- REPORTED BY ROB ----------
>
> Comparing this with a previous version of CREAM , we found the java
> class that provides "org/italiangrid/voms/store/VOMSTrustStore" was in
> voms-api-java.jar, provided by the voms-api-java RPM. This was
> installed, but a symbolic link was absent:
> /var/lib/tomcat6/webapps/ce-cream/WEB-INF/lib/voms-api-java.jar linked
> to /usr/share/java/voms-api-java.jar.
>
> So we tried restoring the link but that didn't work. But with further
> investigation we found that the voms-api-java RPM was no longer in the
> repository
> (http://repository.egi.eu/sw/production/umd/3/sl6/x86_64/updates/) and
> instead a voms-api-java3 RPM was there. This RPM was installed and
> contained a /usr/share/java/voms-api-java3.jar file. There was no
> symbolic link from /var/lib/tomcat6/webapps/ce-cream/WEB-INF/lib/ to
> this file either, so copying the previous logic, we created one. This
> did work, and cleared that particular error. voms-api-java appears to
> have been replaced by voms-api-java3, and the required symbolic link
> from /var/lib/tomcat6/webapps/ce-cream/WEB-INF/lib/ may not be present
> following an update.
>
> --- PART 3 --- REPORTED BY ROB ----------
>
> But that was not the end of it. There were other changes to the Java
> library structure. Additional similarly missing symbolic links (all
> from /var/lib/tomcat6/webapps/ce-cream/WEB-INF/lib/ to files under
> /usr/share/java/) were:
>
> bcmail.jar
> argus-pep-api-java.jar
> argus-pep-common.jar
>
> bcmail.jar is installed by the bouncycastle-mail RPM and provides the
> org.bouncycastle.operator.DigestAlgorithmIdentifierFinder class, this
> was not installed on the previous version of CREAM.
> argus-pep-api-java.jar is installed by the argus-pep-api-java RPM and
> provides the org/glite/authz/pep/client/config/PEPClientConfiguration
> class. This was not installed on the previous version of CREAM (which
> had instead a argus-pep-api-java-compat.jar, installed by the
> glite-ce-common-java RPM). argus-pep-common.jar provides the
> org/glite/authz/pep/PEPException class and is installed by the
> argus-pep-common RPM. This was similarly not installed on the previous
> version of CREAM, which had an argus-pep-common-compat.jar installed by
> the glite-ce-common-java RPM. Of course, it could be that it's a missing
> CLASSPATH somewhere rather than missing symbolic links, but either way
> adding the symbolic links fixes it.
>
> Conclusion:
>
> There are many changes to the java library structure in the new version
> of CREAM. A partial upgrade leaves them broken. I don't know yet if a
> full install works. There are also no release notes at
> http://repository.egi.eu/2013/09/12/cream-1-16-2, which is a mystery.
>
> There may be a better way to upgrading from CREAM 1.15.1-2 to 1.16.2-1,
> but I don't know what it is. In short, this approach to the upgrade is
> an adventure, so talk care. Best drain first, if this route is too
> screwy. We'll be doing so for the rest of our CEs!
>
>
> Cheers,
>
>
> Steve
>
|