Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-133029

oqsprovider build fails during %check: tests abort with "error registering mlkem512 with no hash"

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Undefined Undefined
    • None
    • rhel-10.1
    • oqsprovider
    • None
    • None
    • None
    • rhel-security-crypto-diamonds
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • All
    • None

      What were you trying to do that didn't work?

      Attempting to build the oqsprovider package. The build fails during the %check phase when running the test suite (ctest) because the tests cannot initialize the required OpenSSL providers. This failure occurs consistently in both Konflux and Koji build environments.

      What is the impact of this issue to you?

      Unable to successfully build and release the oqsprovider package for RHEL/CentOS Stream 10.

      Please provide the package NVR for which the bug is seen:

      oqsprovider-0.8.0-6.el10

      How reproducible is this bug?:

      Always (100%)

      Steps to reproduce

      1. Trigger an RPM build of oqsprovider.spec (via rpmbuild -ba, Koji, or Konflux).
      2. Wait for the build to reach the %check phase.
      3. Observe the failure in the CTest execution.

      Expected results

      The tests should pass by correctly loading both the locally built oqsprovider and the system's standard OpenSSL providers.

      Actual results

      The build fails during %check. All 6 tests abort immediately with the following error:

      error registering mlkem512 with no hash
      /builddir/build/BUILD/oqs-provider-0.8.0/test/test_common.c:55: OpenSSL internal error: OSSL_PROVIDER_available(libctx, modulename)
      

      Speculation: this appears to be caused by the OPENSSL_MODULES environment variable being set strictly to the build directory (.../redhat-linux-build/lib), which overwrites the system default path. As a result, the test binary cannot load the system default provider (needed for SHA-3/SHA-2 algorithms required by mlkem512), causing the registration to fail.

              dbelyavs@redhat.com Dmitry Belyavskiy
              rhn-support-dtodorov Djordje Todorovic
              Dmitry Belyavskiy Dmitry Belyavskiy
              Alicja Kario Alicja Kario
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: