Uploaded image for project: 'Quarkus'
  1. Quarkus
  2. QUARKUS-5984

MariaDB 11.x fails on FIPS enabled environment

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • 3.NEXT
    • 3.20-Jumanji.GA, 3.20.0.CR1
    • team/qe
    • False
    • Hide

      None

      Show
      None
    • False
    • +
    • ---

      Quarkus QE cannot run database test coverage with any of MariaDB 11.x images on FIPS, therefore we cannot verify that Quarkus works with MariaDB 11.x in FIPS-enabled environment.
      The problem is on the MariaDB developer side, container startup fails with “Segmentation fault” error.

      Logs example:

      2025-04-22 11:04:58,368 INFO  [tc.doc.io/.4] (main) Creating container for image: docker.io/library/mariadb:11.4
      2025-04-22 11:04:58,420 INFO  [tc.doc.io/.4] (main) Container docker.io/library/mariadb:11.4 is starting: 7b27b4f2d7777c397d424e572a0e344f738d8286d31934af8d91498e26b91c17
      11:05:02,395 INFO  [database] 2025-04-22 11:04:58+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.4.5+maria~ubu2404 started.
      11:05:02,395 INFO  [database] 2025-04-22 11:04:59+00:00 [Warn] [Entrypoint]: /sys/fs/cgroup/memory:/docker/7b27b4f2d7777c397d424e572a0e344f738d8286d31934af8d91498e26b91c17
      11:05:02,395 INFO  [database] 11:rdma:/docker/7b27b4f2d7777c397d424e572a0e344f738d8286d31934af8d91498e26b91c17
      11:05:02,395 INFO  [database] 10:cpu,cpuacct:/docker/7b27b4f2d7777c397d424e572a0e344f738d8286d31934af8d91498e26b91c17
      11:05:02,395 INFO  [database] 9:cpuset:/docker/7b27b4f2d7777c397d424e572a0e344f738d8286d31934af8d91498e26b91c17
      11:05:02,395 INFO  [database] 8:hugetlb:/docker/7b27b4f2d7777c397d424e572a0e344f738d8286d31934af8d91498e26b91c17
      11:05:02,395 INFO  [database] 7:pids:/docker/7b27b4f2d7777c397d424e572a0e344f738d8286d31934af8d91498e26b91c17
      11:05:02,395 INFO  [database] 6:blkio:/docker/7b27b4f2d7777c397d424e572a0e344f738d8286d31934af8d91498e26b91c17
      11:05:02,395 INFO  [database] 5:freezer:/docker/7b27b4f2d7777c397d424e572a0e344f738d8286d31934af8d91498e26b91c17
      11:05:02,395 INFO  [database] 4:devices:/docker/7b27b4f2d7777c397d424e572a0e344f738d8286d31934af8d91498e26b91c17
      11:05:02,395 INFO  [database] 3:perf_event:/docker/7b27b4f2d7777c397d424e572a0e344f738d8286d31934af8d91498e26b91c17
      11:05:02,396 INFO  [database] 2:net_cls,net_prio:/docker/7b27b4f2d7777c397d424e572a0e344f738d8286d31934af8d91498e26b91c17
      11:05:02,396 INFO  [database] 1:name=systemd:/docker/7b27b4f2d7777c397d424e572a0e344f738d8286d31934af8d91498e26b91c17/memory.pressure not writable, functionality unavailable to MariaDB
      11:05:02,396 INFO  [database] 2025-04-22 11:04:59+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
      11:05:02,396 INFO  [database] 2025-04-22 11:04:59+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.4.5+maria~ubu2404 started.
      11:05:02,396 INFO  [database] 2025-04-22 11:05:00+00:00 [Note] [Entrypoint]: Initializing database files
      11:05:02,396 INFO  [database] 2025-04-22 11:05:00 0 [Warning] mariadbd: io_uring_queue_init() failed with errno 95
      11:05:02,396 INFO  [database] 2025-04-22 11:05:00 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF
      11:05:02,396 INFO  [database] 250422 11:05:01 [ERROR] /usr/sbin/mariadbd got signal 11 ; 

      Example test run on Jenkins:

      https://jenkins-csb-quarkusqe-main.dno.corp.redhat.com/view/rhbq-3.20-extended-platform/job/rhbq-3.20-baremetal-ts-jvm/15/jdk=openjdk-21,label=RHEL8_FIPS%20&&%20large%20&&%20docker,scenario=databases-modules/testReport/junit/io.quarkus.ts.sqldb.sqlapp/MariaDBDatabaseIT/___/

              rsvoboda@redhat.com Rostislav Svoboda
              rh-ee-gtroitsk Georgii Troitskii
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: