CHW-8520 IndexSigningUnavailable
this repository signs its index, but no signed index is available yet; the proxy refuses to serve it unsigned. A re-sign has been scheduled — retry shortly. If this persists, the operator should …
Default message: this repository signs its index, but no signed index is available yet; the proxy refuses to serve it unsigned. A re-sign has been scheduled — retry shortly. If this persists, the operator should check the repository’s signing_key and the server log for the regen error
HTTP status:503(server)
Problem. A request for a repository index (dists/<suite>/Release,
InRelease, Release.gpg, or repodata/repomd.xml / .asc) was refused.
Cause. The repository is configured to sign its index, and no signed
index exists yet. Either signing was just switched on and no regeneration
has run since, or every regeneration since has failed because the signer
could not be used: the key file is missing or unreadable; the key is not
ECDSA P-256 or RSA of at least 2048 bits; the KMS named by a signing_key
URI (awskms://, gcpkms://, azurekms://, hashivault://) is
unreachable, rejects the server’s credential, or has no such key; or the
server is the free build, which links no KMS provider. The proxy refuses rather than hand
a client an index it cannot verify, and schedules a regeneration on every
refusal. Fix. Retry after a few seconds — a working signer heals the
repository on the next request. If it keeps failing, search the server
log for code=CHW-8520: the apt regen failed / rpm regen failed line
names the signer error. Correct the signing_key, or clear it to go back
to an unsigned index. HTTP 503.