RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1974824 - Latest zlib in ubi8-minimal image is causing failures on s390x
Summary: Latest zlib in ubi8-minimal image is causing failures on s390x
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: zlib
Version: 8.3
Hardware: s390x
OS: Linux
unspecified
high
Target Milestone: beta
: 8.5
Assignee: Lukas Javorsky
QA Contact: RHEL CS Apps Subsystem QE
URL:
Whiteboard:
Depends On:
Blocks: 1916117
TreeView+ depends on / blocked
 
Reported: 2021-06-22 15:45 UTC by lzhan
Modified: 2021-10-21 12:49 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-19 06:41:53 UTC
Type: Bug
Target Upstream Version:
Embargoed:
lzhan: needinfo+
pm-rhel: mirror+


Attachments (Terms of Use)
File to specify the problematic image (251 bytes, text/plain)
2021-06-22 15:45 UTC, lzhan
no flags Details


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 193386 0 None None None 2021-06-28 06:18:47 UTC

Description lzhan 2021-06-22 15:45:54 UTC
Created attachment 1793083 [details]
File to specify the problematic image

Description of problem:
Currently on s390x, build of Quarkus applications fails with the following error on the latest s2i java openshift images.

```
[ERROR] Failed to execute goal io.quarkus:quarkus-maven-plugin:1.11.7.Final-redhat-00009:build (default) on project todo-backend: Failed to build quarkus application: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
[ERROR] 	[error]: Build step io.quarkus.deployment.pkg.steps.JarResultBuildStep#buildRunnerJar threw an exception: java.lang.RuntimeException: java.util.zip.ZipException: invalid entry compressed size (expected 100 but got 102 bytes)
```
Early investigation seems to point to cve glib2 refresh on ubi8 Java S2I images causing some sort of zip bug on s390x. Doesn't seem to affect x86 and ppc64le at the moment. I will continue to investigate.

The cause of the issue seems to reside in libz.so.1.2.11 shipped from the ubi8-minimal base image. The openj9/openj9-11-rhel8:1.2-46.1622550125  build is based on a ubi8-minimal base image which contains a build of libz.so.1.2.11, which causes the failure. When manually replacing this libz.so with an older version, and injecting it to the openj9 image, the failure would be gone. Therefore, it doesn't seem to be related to openjdk11, not openj8, but seems to be a regression from base image, only on z/s390x.


Version-Release number of selected component (if applicable):
zlib-1.2.11-17.el8.s390x.rpm (possibly)

How reproducible:
Follow the steps below. We are testing Quarkus with the problematic s2i image defined in the yaml file. 

Steps to Reproduce:
1. checkout '1.11' branch of https://github.com/quarkus-qe/quarkus-openshift-test-suite. cd into the directory.
2. replace `external-applications/todo-demo-app/src/test/resources/openjdk-11.yaml` with the attached yaml
3. log in to your OCP cluster on IBM Z with `oc` and create a new project with `oc new-project test`
4. build the test suite libraries:
mvn clean install -DskipTests -DskipITs -B -V -pl app-metadata/deployment,app-metadata/runtime,common -fae
5. run the todo-demo-app tests:
mvn clean verify -B -V clean verify -pl app-metadata/deployment,app-metadata/runtime,common,external-applications/todo-demo-app -Dts.s2i.maven.remote.repository=http://10.0.139.54:8040/artifactory/quarkus-maven-repo-zip

Actual results:
It fails with follow reason:
```
[ERROR] Failed to execute goal io.quarkus:quarkus-maven-plugin:1.11.7.Final-redhat-00009:build (default) on project todo-backend: Failed to build quarkus application: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
[ERROR] 	[error]: Build step io.quarkus.deployment.pkg.steps.JarResultBuildStep#buildRunnerJar threw an exception: java.lang.RuntimeException: java.util.zip.ZipException: invalid entry compressed size (expected 100 but got 102 bytes)
```

Expected results:
It should pass.

Additional info:

Comment 1 Petr Kubat 2021-06-22 16:25:38 UTC
Hi Thomas, another issue that seems to have been hit as a result of the IBM Z patches that were part of the recent RHEL updates (BZ#1847438), can you take a look?

Comment 2 IBM Bug Proxy 2021-06-30 21:20:40 UTC
------- Comment From iii.com 2021-06-30 17:11 EDT-------
This looks like a quarkus bug to me.
I have proposed a fix to them: https://github.com/quarkusio/quarkus/pull/18283

Comment 3 Ondrej Dubaj 2021-07-02 08:44:35 UTC
Thank you very much for the fix!

Lei, can you please check if the fix solves your problem?

Thank you.

Comment 4 lzhan 2021-07-05 12:09:28 UTC
Ondrej, sure, this issue will be tracked/verified at https://issues.redhat.com/browse/QUARKUS-1140

Comment 5 Ondrej Dubaj 2021-07-19 05:23:05 UTC
Hello, is the fix already verified ? From the tracker is seems it should be.

Thank you.

Comment 6 lzhan 2021-07-19 11:57:21 UTC
Hi Ondrej, the fix will be verified for the next version release of RHBQ, which is around Sep this year.

Comment 7 Ondrej Dubaj 2021-09-15 05:55:37 UTC
Hi, I see that the resolution on the ticket is already Done, can we close this tracker? Thanks.

Comment 8 lzhan 2021-09-15 12:09:31 UTC
hi Ondrej, this fix was implemented but not yet verified. The verification will happen very soon. cc @

Comment 9 Ondrej Dubaj 2021-09-15 12:30:03 UTC
Thanks for your reply!

Comment 10 dafu 2021-10-18 18:14:40 UTC
Tested with Red Hat build of Quarkus 2.2.3.CR5 and this issue is no longer exists. Thanks for your help! We can resolve this issue.

Comment 11 Ondrej Dubaj 2021-10-19 06:41:53 UTC
Thank you for information! Closing this issue.


Note You need to log in before you can comment on or make changes to this bug.