Deployments trust the CA on RHEL-family systems too
CI / agent (push) Successful in 3s
CI / site (push) Successful in 2s
CI / go (push) Successful in 36s

cloud-init's ca_certs ran update-ca-certificates on Rocky and failed, so
those machines never trusted the Rollcall CA. The CA is now written into
both trust-anchor directories and a bootcmd rebuilds the store with
update-ca-trust or update-ca-certificates.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Ilker ManapandClaude Opus 5.5 committed 2026-10-28 19:38:46 +01:00
1 parent 996ecbd89d
commit e2102e1741
4 files changed
+21 -12

No files matched your search

+5 -3
View File
@@ -445,9 +445,11 @@ plane is: `ca_dir` (default `/etc/rollcall/ca`) holds `ca.pem` and
first connect and keeps the CA in `~/.config/rollcall/client.json` once you
confirm it (`rollcall ca show` prints it on the region). `/ca.pem` serves
the certificate; the web login links to it.
* **Machines** trust it: deployments add it with cloud-init `ca_certs`
(allowed on RHEL-family images, where cloud-init marks the module
unverified), stateless overlays get it as `.CA`. `rollcall ca issue NAME
* **Machines** trust it: deployments write the CA into the trust anchors of
both families (`/usr/local/share/ca-certificates`, `/etc/pki/ca-trust/source/anchors`)
and rebuild the store at every boot (`update-ca-certificates` or
`update-ca-trust`; cloud-init's `ca_certs` fails on RHEL-family systems);
stateless overlays get it as `.CA`. `rollcall ca issue NAME
-host h1,h2 [-client]` issues leaves for anything else (Slurm REST, a
registry, a web front end).
* **Delegation.** The root may sign one level of intermediate CAs, each