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 1977914 - TestBoringServerCurves from crypto/tls fails when executed separately [rhel-9]
Summary: TestBoringServerCurves from crypto/tls fails when executed separately [rhel-9]
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: golang
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: ---
Assignee: David Benoit
QA Contact: Edjunior Barbosa Machado
URL:
Whiteboard:
Depends On: 1975830
Blocks: 1976168 2077782 2079073
TreeView+ depends on / blocked
 
Reported: 2021-06-30 17:20 UTC by Edjunior Barbosa Machado
Modified: 2022-04-26 20:38 UTC (History)
5 users (show)

Fixed In Version: go-toolset-1.16.6-1.el9
Doc Type: No Doc Update
Doc Text:
Clone Of: 1975830
Environment:
Last Closed: 2021-12-07 21:20:54 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Edjunior Barbosa Machado 2021-06-30 17:20:10 UTC 
This is also reproducible with go-toolset-1.16.4-1.el9 and golang-1.16.4-3.el9 on RHEL-9.0.0-20210621.3.

[root@sweetpig-17 ~]# rpm -qa golang go-toolset
golang-1.16.4-3.el9.x86_64
go-toolset-1.16.4-1.el9.x86_64
[root@sweetpig-17 ~]# uname -a
Linux sweetpig-17.4a2m.lab.eng.bos.redhat.com 5.13.0-0.rc4.33.el9.x86_64 #1 SMP Wed Jun 2 19:15:08 EDT 2021 x86_64 x86_64 x86_64 GNU/Linux
[root@sweetpig-17 ~]# OPENSSL_CONF=/openssl-boring.cnf GOLANG_FIPS=1 go test crypto/tls -timeout 50m -count=1 -v -v -v -run ^TestBoringServerCurves$
=== RUN   TestBoringServerCurves
=== RUN   TestBoringServerCurves/curve=29
    handshake_server_test.go:57: Got error: tls: no cipher suite supported by both client and server; expected to succeed
=== RUN   TestBoringServerCurves/curve=29/fipstls
=== RUN   TestBoringServerCurves/curve=23
=== RUN   TestBoringServerCurves/curve=23/fipstls
=== RUN   TestBoringServerCurves/curve=24
=== RUN   TestBoringServerCurves/curve=24/fipstls
=== RUN   TestBoringServerCurves/curve=25
=== RUN   TestBoringServerCurves/curve=25/fipstls
--- FAIL: TestBoringServerCurves (0.00s)
    --- FAIL: TestBoringServerCurves/curve=29 (0.00s)
        --- PASS: TestBoringServerCurves/curve=29/fipstls (0.00s)
    --- PASS: TestBoringServerCurves/curve=23 (0.00s)
        --- PASS: TestBoringServerCurves/curve=23/fipstls (0.00s)
    --- PASS: TestBoringServerCurves/curve=24 (0.00s)
        --- PASS: TestBoringServerCurves/curve=24/fipstls (0.00s)
    --- PASS: TestBoringServerCurves/curve=25 (0.00s)
        --- PASS: TestBoringServerCurves/curve=25/fipstls (0.00s)
FAIL
FAIL	crypto/tls	0.060s
FAIL


+++ This bug was initially created as a clone of Bug #1975830 +++

Description of problem:
TestBoringServerCurves from crypto/tls golang internal testsuite fails when executed separately from the other tests:

[root@sheep-2 ~]# GOLANG_FIPS=1 scl enable go-toolset-1.15 -- go test crypto/tls -timeout 50m -count=1 -v -v -v -run ^TestBoringServerCurves$
=== RUN   TestBoringServerCurves
=== RUN   TestBoringServerCurves/curve=29
    handshake_server_test.go:55: Got error: tls: no cipher suite supported by both client and server; expected to succeed
=== RUN   TestBoringServerCurves/curve=29/fipstls
=== RUN   TestBoringServerCurves/curve=23
=== RUN   TestBoringServerCurves/curve=23/fipstls
=== RUN   TestBoringServerCurves/curve=24
=== RUN   TestBoringServerCurves/curve=24/fipstls
=== RUN   TestBoringServerCurves/curve=25
=== RUN   TestBoringServerCurves/curve=25/fipstls
--- FAIL: TestBoringServerCurves (0.00s)
    --- FAIL: TestBoringServerCurves/curve=29 (0.00s)
        --- PASS: TestBoringServerCurves/curve=29/fipstls (0.00s)
    --- PASS: TestBoringServerCurves/curve=23 (0.00s)
        --- PASS: TestBoringServerCurves/curve=23/fipstls (0.00s)
    --- PASS: TestBoringServerCurves/curve=24 (0.00s)
        --- PASS: TestBoringServerCurves/curve=24/fipstls (0.00s)
    --- PASS: TestBoringServerCurves/curve=25 (0.00s)
        --- PASS: TestBoringServerCurves/curve=25/fipstls (0.00s)
FAIL
FAIL	crypto/tls	0.046s
FAIL
[root@sheep-2 ~]# 

The failure is not reproducible when run with other crypto/tls Boring tests (GOLANG_FIPS=1 scl enable go-toolset-1.15 -- go test crypto/tls -timeout 50m -count=1 -v -v -v -run Boring) or with FIPS disabled (GOLANG_FIPS=0).

Version-Release number of selected component (if applicable):
go-toolset-1.15-1.15.13-1.el7_9
go-toolset-1.15-golang-1.15.13-1.el7_9.x86_64
RHEL-7.9-updates-20210608.0

Steps to Reproduce:
1. GOLANG_FIPS=1 scl enable go-toolset-1.15 -- go test crypto/tls -timeout 50m -count=1 -v -v -v -run ^TestBoringServerCurves$

--- Additional comment from Edjunior Barbosa Machado on 2021-06-24 15:02:53 UTC ---

FWIW, this is also reproducible with previous go-toolset-1.15-golang-1.15.11-1.el7_9 released on devtools-2021.2.

--- Additional comment from Edjunior Barbosa Machado on 2021-06-25 09:14:45 UTC ---

Also reproducible with devtools-2021.4 go-toolset-1.16-golang-1.16.4-2.el7_9.
Note You need to log in before you can comment on or make changes to this bug.