Subject: bug#33159: Despite --fallback, TLS error halted "guix system reconfigure"

From: [email-masked] (Ludovic Courtès)
Date: Fri, 26 Oct 2018 21:23:11 +0200

Hello,

Chris Marusich <[email-masked]> skribis:

> The following command failed:
>
> root@garuda /home/marusich# guix system --fallback --on-error=backtrace reconfigure /home/marusich/config.scm
> [...]
> substitute: updating substitutes from 'https://mirror.hydra.gnu.org'... 100.0%
> substitute: updating substitutes from 'https://hydra-mirror.marusich.info'... 100.0%
> substitute: updating substitutes from 'https://mirror.hydra.gnu.org'... 100.0%
> substitute: updating substitutes from 'https://hydra-mirror.marusich.info'... 100.0%
> substitute: updating substitutes from 'https://mirror.hydra.gnu.org'... 100.0%
> substitute: updating substitutes from 'https://hydra-mirror.marusich.info'... 100.0%
> substitute: updating substitutes from 'https://mirror.hydra.gnu.org'... 100.0%
> substitute: updating substitutes from 'https://hydra-mirror.marusich.info'... 100.0%
> substitute: updating substitutes from 'https://mirror.hydra.gnu.org'... 100.0%
> substitute: guix substitute: error: TLS error in procedure 'handshake': A TLS fatal alert has been received.
> guix system: error: build failed: substituter `substitute' died unexpectedly
> root@garuda /home/marusich#
>
> Is this expected behavior when --fallback is given?

Yes: --fallback is to fall back when substitution fail, but here we’re
not substituting yet, only querying ‘guix substitute’.

Now, what’s the story with that TLS handshake?  Any ideas?

Thanks,
Ludo’.