tripleo-buildimage-overcloud-full-centos-8 is failing on the update of libnghttp2 package

[Ronelle Landy]

This also shows up as a RETRY_LIMIT failure - but the package update is causing the error:

2020-06-26 14:10:11.274760 | TASK [tripleo-repos : Update all installed packages after new repos are setup]
2020-06-26 14:10:38.743109 | primary | ERROR
2020-06-26 14:10:38.746115 | primary | {
2020-06-26 14:10:38.746281 | primary | "failures": [],
2020-06-26 14:10:38.746437 | primary | "msg": "Depsolve Error occured: \n Problem: cannot install both libnghttp2-1.41.0-1.module_el8+9071+b2b61c14.x86_64 and libnghttp2-1.33.0-1.el8_0.1.x86_64\n - libnghttp2-1.33.0-1.el8_0.1.i686 has inferior architecture\n - cannot install the best update candidate for package libnghttp2-1.33.0-1.el8_0.1.x86_64\n - problem with installed package libnghttp2-1.33.0-1.el8_0.1.i686\n - package libnghttp2-1.33.0-1.el8_0.1.x86_64 is filtered out by modular filtering",
2020-06-26 14:10:38.746570 | primary | "rc": 1,
2020-06-26 14:10:38.746680 | primary | "results": []
2020-06-26 14:10:38.746786 | primary | }
2020-06-26 14:10:38.836553 |

Example logs:

https://e67888f71e3c619ed125-948b6a5ed4d9dccaba5208d54797c4a1.ssl.cf1.rackcdn.com/738194/1/check/tripleo-buildimage-overcloud-full-centos-8/6f5259e/job-output.txt

https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_362/738154/1/check/tripleo-buildimage-overcloud-full-centos-8/3625d73/job-output.txt

[Ronelle Landy (rlandy)]

Asked Chandan to look at this.

[chandan kumar (chkumar246)]

Based on error:
pdate candidate for package libnghttp2-1.33.0-1.el8_0.1.x86_64\n - problem with installed package libnghttp2-1.33.0-1.el8_0.1.i686\n

In system, libnghttp2-1.33.0-1.el8_0.1.i686 package, ie.e 32 bit package is installed, It needs to be x86_64 package. We need to find how we 32 bit is getting installed there.

[yatin (yatinkarel)]

The issue is happening as epel repo is enabled in job and it conflict with packages from CentOS8 base, disabling/removing epel repo should clear the issue.

[Manuel Torrinha (t0rrant)]

From what I can tell 4 days ago this was not happening as I was able to generate a CentOS 8 image with EPEL successfuly. Also, packages in the EPEL should never conflict with the ones in base for EL. That said, removing EPEL completely does not seem to be the right way as some packages may be needed from EPEL while generating images.

Looks like we should wait for EPEL to be fixed or force '--allowerasing' option for the conflicting package (which looks a bit hacky to me).

I would be glad to hear of other suggestions allowing EPEL to stay enabled.

[Carlos Goncalves (cgoncalves)]

I agree with Manuel. The community should strive to fix what's broken at source. I'm relatively certain this can impact anyone with CentOS + EPEL enabled.

[wes hayutin (weshayutin)]

EPEL should never be enabled in TripleO deployments or builds. <eom>

[Manuel Torrinha (t0rrant)]

I know this is a TripleO issue but I'll leave this here for someone who may stumble upon this while building CentOS 8 cloud images with EPEL https://<email address hidden>/thread/AFY7DL4FCH3ZOJZBVFA57MFEB2XWIMCS/