Missing Standard ACLs in sys_security_acl on Yokohama Patch 5 with MariaDB 10.6 Community

Auverland
Tera Contributor

3 hours ago

Hi everyone,

Sorry in advance for the long post, but I’m trying to summarize an issue we’ve been struggling with.

 

We installed Vancouver on MariaDB 10.6 Community, then upgraded to Washington and finally Yokohama Patch 5 (YP5). We also created fresh YP5 environments. In these new instances, the sys_security_acl table is incomplete: several standard ACLs that exist in Vancouver are missing.

 

For example, this query should return 24 records, but we only get 2:

 

select * from sys_security_acl
where name like 'task.%'
and operation = 'write';

No errors appear in the zBoot logs. ServiceNow Support couldn’t reproduce the issue.

 

To isolate the cause, I built multiple test environments:

- Personal machine (RHEL 9.6) with a full MariaDB 10.6 install → YP5 and YP9 zBoot work fine.

- Internal lab with MariaDB 10.6 tarball (full install) → YP5 zBoot works fine.

- Corporate lab using our automated install of MariaDB 10.6 Community RPMs → ACLs missing.

 

Our automated install deploys only these RPMs:

MariaDB-shared-10.6.15
MariaDB-common-10.6.15
MariaDB-client-10.6.15
MariaDB-backup-10.6.15
MariaDB-server-10.6.15


MariaDB provides many other 10.6 packages, but they generally advise not installing everything (e.g., not installing MariaDB-test in production). ServiceNow documentation only lists required packages for MariaDB 10.4, not 10.6.

 

Question for other Self‑Hosted users:
1/ Which MariaDB 10.6 RPM packages are you using successfully with Yokohama Patch 5 (or later)?
2/ Have you ever seen missing ACLs after zBoot?

 

Thanks for your help, and again sorry for the long message.

0 Helpfuls
  • 113 Views
1 REPLY 1

Itallo Brandão
Tera Guru

an hour ago

Hi @Auverland ,

Based on your isolation tests, the issue is almost certainly a missing dependency in your minimal RPM list.

1. The Likely Missing Package: MariaDB-compat You listed shared, common, client, backup, and server. You are likely missing MariaDB-compat.

  • Why: The zBoot process often relies on legacy OS-level libraries (libmysqlclient) provided by this package to perform initial data seeding. Without it, specific table populations (like ACLs) can fail silently without crashing the whole installation.

2. How to Verify Since you have a working "Full Install" environment, run this command on both machines to see the exact difference: rpm -qa | grep MariaDB | sort

3. Configuration Check (MariaDB 10.6) Ensure innodb_strict_mode = OFF is set in your my.cnf. MariaDB 10.6 changed some defaults, and if this is ON, it can silently reject some data inserts during the zBoot.

If adding MariaDB-compat solves the missing ACLs, please mark it as Accepted Solution.

Best regards,
Brandão.

0 Helpfuls