Hello Carles,
The fact that the binaries does not match with md5 is completely normal.
EPEL rpms and EMI rpms are compiled from the same source but with two
different systems ( Koji for EPEL, mock for EMI 2 ...two different
compiler versions ... two different set of flags ).
If you have a look to the other packages, they have the same behavior :
EMI2 :
8572697f789a2e152b5a87a324c3aa1c lcgdm-libs-1.8.5-1.el5.x86_64.rpm
EPEL :
7a23ab24b81b68c57fc590b132742a9b lcgdm-libs-1.8.5-1.el5.x86_64.rpm
Anyway, for lcgutil, both repositories ( EPEL & EMI ) are synchronized,
compatible and with tested RPMs, it should not trigger any issue if you
mix them.
Please, could you open a GGUS ticket describing your long hold state
issue and your nagios problem, we will take care of this.
Regards,
Adrien.
On 17/12/2012 12:47, Carles Acosta wrote:
> Hello,
>
> We have found a strange issue related with the lcg-util package in our
> EMI2 WNs. The same last version of lcg-util package is available in
> both repositories (1.13.9).
>
> After some problems with Atlas jobs only in certain WNs (they were in
> hold state for long time), we have discovered that the package
> lcg-util-1.13.9-0.el5.x86_64 is not the same for EMI-2 and epel
> repositories.
>
> $ md5sum lcg-util-1.13.9-0.el5.x86_64.rpm-epel
> dffc87cb494bb7d5c1f5c4c4317c1f5a lcg-util-1.13.9-0.el5.x86_64.rpm-epel
> $ md5sum lcg-util-1.13.9-0.el5.x86_64.rpm-emi2
> 88fa157660d579006acf1977fb597454 lcg-util-1.13.9-0.el5.x86_64.rpm-emi2
>
> So, we would like to know if you are aware of this issue. Maybe it is
> not a relevant issue but we reinstalled the lcg-util package ensuring
> that it came from EMI-2 repositories and the Atlas problem disappeared.
>
> Although we have added a higher priority for EMI-2 repositories, it
> seems that during the installation process, the epel repository is
> generated before and, then, sometimes, the epel packages are installed
> and not the EMI-2 ones. We are checking our Puppet configuration to
> solve this problem.
>
> Anyway, we are experiencing another problem related with lcg binaries
> (the ops nagios test are flapping with the replicates and the reason
> is really not clear) and we do not know if this problem is related
> with the rest of lcg-util packages (libs and python).
>
> In conclusion, we would like to ask what repository we should trust
> and if anyone has found the same or similar problems.
>
> Thank you very much for your help!
>
> Regards,
>
> Carles
>
|