Martin Pitt
efafddcfbc
When connection errors or token refreshes used up the retries, the request
previously failed with the generic `io.systemd.System` error. In indirect
mode the parent forwards only the error name, so clients saw no reason at
all.
Running out of retries means that IMDS did not answer in time, which the
overall timeout already reports as `io.systemd.InstanceMetadata.Timeout`.
Use that for exhausted retries as well.
Signed-off-by: Martin Pitt <martin@amutable.com>
(cherry picked from commit 84c768e83b)
System and Service Manager
Details
Most documentation is available on systemd's website.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS, and also repositories with packages built from the latest stable release