Bug 2108086

Summary: Build is failing in %check section
Product: Red Hat Enterprise Linux 8 Reporter: Eduard Abdullin <ed.abdullin.1>
Component: perl-AnyEventAssignee: Michal Josef Spacek <mspacek>
Status: CLOSED MIGRATED QA Contact: Martin Kyral <mkyral>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: CentOS StreamCC: bstinson, jkejda, jplesnik, jwboyer, mkyral, mspacek
Target Milestone: rcKeywords: MigratedToJIRA, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: perl-AnyEvent-7.14-7.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-20 16:32:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
patch none

Description Eduard Abdullin 2022-07-18 12:26:00 UTC
Created attachment 1897924 [details]
patch

Description of problem:
Build is failing in %check section

dh params schmorp1539: failed to set DH parameters at t/80_ssltest.t line 14.

Patch is fixing this issue

Comment 1 Michal Josef Spacek 2022-07-18 15:34:59 UTC
@ed.abdullin.1 On which system is this failing?

Comment 2 Eduard Abdullin 2022-07-19 09:40:37 UTC
AlmaLinux8, but I think it can be reproduced in any system

Comment 3 Michal Josef Spacek 2023-08-09 08:58:48 UTC
The root cause of this issue is the default dh key (schmorp1539). 
Net::SSLeay will fail with this setting with the error "error:0A00018A:SSL routines::dh key too small" which is the setting of OpenSSL on these systems.

Comment 5 Michal Josef Spacek 2023-08-24 09:02:23 UTC
We don't need to deliver the new package build in case of this issue.
This is only a build issue, I am working on delivering to the repository only.

Comment 6 Michal Josef Spacek 2023-09-15 09:02:53 UTC
No test running, back to ASSIGNED.

Comment 7 RHEL Program Management 2023-09-20 16:29:42 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 8 RHEL Program Management 2023-09-20 16:32:26 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.