Bug #119850 Confusing note from component_keyring_file when audit log filter is installed

• Submitted: 6 Feb 9:40
• Reporter: Przemyslaw Malkowski
• Status: Open
• Category: MySQL Server: Components / Services
• Severity: S3 (Non-critical)
• Version: 8.4.7
• OS: Any
• CPU Architecture: Any
• Tags: audit log, keyring component

[6 Feb 9:40] Przemyslaw Malkowski

Description:
Hi, 
When the audit log filter component is installed, and then the keyring file component is added, the audit log filter keyring ID is added to keyring_file, i.e.:

$ cat keyring_file 
{"version":"1.0","elements":[{"user":"audit_log","data_id":"audit_log-20260206T101500-1","data_type":"SECRET","data":"7B2270617373776F7264223A226A6D787674766D4339313237714A4E6D30367347423852393271326A37765469694954524447584D395A4C7A6B64656B6257746D584B775A327147316C6C6B5277356D3944484F46696C4552456B3371376F6365384F3342454A4330776F4A736D36757A464145796E4C483278437377314B51316C54347A673972647842222C2273616C74223A2241433437354146353941413332324146222C22697465726174696F6E73223A3538333736347D","extension":[]}]}

The same key ID is listed as expected:
mysql > SELECT KEY_ID FROM performance_schema.keyring_keys;
+--------------------------------------------------+
| KEY_ID                                           |
+--------------------------------------------------+
| INNODBKey-00008409-0000-0000-0000-000000008409-1 |
| audit_log-20260206T101500-1                      |
+--------------------------------------------------+
2 rows in set (0.00 sec)

Although the keyring file works properly and table space encryption is fine, this confusing note gets printed on startup:

2026-02-06T09:28:47.364293Z 0 [Note] [MY-013726] [Server] Component component_keyring_file reported: 'Failed to get metadata from current keys metadata iterator position.'

How to repeat:
Install the audit log filter component, and then the component_keyring_file via the manifest file.

Suggested fix:
I see no reason for the scary note in the error log.