Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 1800250[details]
build.log.xz
A rebuild of postgresql-jdbc-42.2.18-4.el9 failed. I'm attaching the build log.
This may be a glibc/kernel problem. I will try to reproduce and investigate.
The tests throw this Java exception:
Caused by: java.net.ConnectException: Function not implemented (connect failed)
at org.postgresql.jdbc.NoColumnMetadataIssue1613Test.setUp(NoColumnMetadataIssue1613Test.java:30)
clock_gettime in glibc started clobbering errno, exposing an OpenJDK bug.
I managed to run a scratch build of postgresql-jdbc-42.2.18-4.el9 on an i686 builder, this time with glibc-2.33.9000-42.el9. The build passed, so this was really the glibc vDSO/ENOSYS issue.
However, a second build failed with a different error (“Connection refused”, not “Function not implemented”). Is the test suite known to be flaky?
The database password isn't random, so if a different buildroot running on the same builder picks the same buildroot, the tests could interfere with each other, without a clear error.
Currently I got 2 failed builds from 8. The problem does not seem to be bind to postgresql-jdbc as you said. Th problem is simple, during the testsuite, each test tries to connect to psql database and it fails. From this reason each test fails.
Made another ~20 builds and none of them failed. This issue seems to be resolved by postgresql update or fixing the glibc issue or something different, closing as NOTABUG. If the problem will be present and reproducible, please reopen this issue.
Created attachment 1800250 [details] build.log.xz A rebuild of postgresql-jdbc-42.2.18-4.el9 failed. I'm attaching the build log. This may be a glibc/kernel problem. I will try to reproduce and investigate.