Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.

  Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.

  Snippets are delimited with '================'.

  Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.

  Explanation of the issue, and recommended solution, should take a handful of sentences.

  Snippets:

  [---> 13:47:20     Starting MySQL server with disabled networking ...
---> 13:47:20     Waiting for MySQL to start ...
2025-04-14 13:47:20 0 [Note] Starting MariaDB 10.11.10-MariaDB-log source revision 3d0fb150289716ca75cd64d62823cf715ee47646 server_uid 2DAP7+jSGnuV6itoSPgUbQxL1/c= as process 59
2025-04-14 13:47:20 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2025-04-14 13:47:20 0 [Note] InnoDB: Number of transaction pools: 1
2025-04-14 13:47:20 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2025-04-14 13:47:20 0 [Note] mysqld: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
2025-04-14 13:47:20 0 [Note] InnoDB: Using Linux native AIO
2025-04-14 13:47:20 0 [Note] InnoDB: Initializing buffer pool, total size = 16.000MiB, chunk size = 1.000MiB
2025-04-14 13:47:20 0 [Note] InnoDB: Completed initialization of buffer pool
2025-04-14 13:47:20 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2025-04-14 13:47:20 0 [Note] InnoDB: End of log at LSN=46996
2025-04-14 13:47:20 0 [Note] InnoDB: 128 rollback segments are active.
2025-04-14 13:47:20 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2025-04-14 13:47:20 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2025-04-14 13:47:20 0 [Note] InnoDB: log sequence number 46996; transaction id 14
2025-04-14 13:47:20 0 [Note] Plugin 'FEEDBACK' is disabled.
2025-04-14 13:47:20 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/data/ib_buffer_pool
2025-04-14 13:47:20 0 [Warning] 'user' entry 'root@f388376d23f7' ignored in --skip-name-resolve mode.
2025-04-14 13:47:20 0 [Warning] 'proxies_priv' entry '@% root@f388376d23f7' ignored in --skip-name-resolve mode.
2025-04-14 13:47:20 0 [Note] InnoDB: Buffer pool(s) load completed at 250414 13:47:20
2025-04-14 13:47:20 0 [Note] /usr/libexec/mysqld: ready for connections.
Version: '10.11.10-MariaDB-log'  socket: '/tmp/mysql.sock'  port: 0  MariaDB Server
---> 13:47:21     MySQL started successfully
/usr/share/container-scripts/mysql/common.sh: line 107: mysql_upgrade: command not found
Test for image 'quay.io/sclorg/mariadb-1011-c9s:1' FAILED (exit code: 1)
Error: can only create exec sessions on running containers: container state improper
Error: can only create exec sessions on running containers: container state improper
]: [During the rpm package installation in container, someone removed package that provides 'mysql_upgrade' tool.]

Issue: The build failed because the mandatory tool 'mysql_upgrade' is missing.
Resolution: The fix is to install rpm package that contains 'mysql_upgrade' command. Use `dnf whatprovides mysql_upgrade` command