No please revert back to the version with innodb_buffer_pool_size = {{ innodb_buffer_pool_size }}.

That will be useful to implement a bunch of values for T2337

I confirm we probably don't need it on WindRiver right now.

Tested, works fine.

Computed on db-B-001, got 1 Gb using POWER(1024,3) but only 139 Mb using POWER(1024,2), so we're good with the default value there for now.

I see 3 blocks with the same 302 redirect.

Instead of documenting the error in a warning block, I'd suggest we keep a primary callout block with directly the good instructions you wrote.

Works like a charm.

To help edit vhosts, I've used the following sed expressions:

We can live with that, as there is work in progress to:

• at Nasqueron, migrate certificates to acme.sh
• on FreeBSD ports, prepare Salt for Python 3.12

It could be solved upstream with 3006.26.

@yousra It seems better with last Salt versions on 3006 LTS branch.

Also, for reference, I solved the issue in a new Salt repo with 9002:9002

A quick note for reference, as I was looking this task to recreate the same issue in a new Salt environment, the core role provides:

Review assisted by LLM. Caught by Qwen3.7-Plus.

Confirming the SSH key request with MFA.