boot failure when model-config sets snap-proxy

[Nicolas Bock]

When I set a snap proxy and then add a machine, i.e.

juju model-config snap-http-proxy="http://10.0.0.1:8000"
juju add-machine

The juju created user-data will configure snap in the bootcmd section. This fails since at the time bootcmd is run the snapd service is not running.

$ juju ssh 0 -- sudo head -n30 /var/lib/cloud/instances/nan7an/user-data.txt.i
Content-Type: multipart/mixed; boundary="===============8907033412026628814=="
MIME-Version: 1.0
Number-Attachments: 1

--===============8907033412026628814==
MIME-Version: 1.0
Content-Type: text/cloud-config
Content-Disposition: attachment; filename="part-001"

#cloud-config
apt_mirror: ""
bootcmd:
- |-
printf '%s
' 'Acquire::http::Proxy "http://10.0.0.2:8000";
Acquire::http::Proxy::"127.0.0.1" "DIRECT";
Acquire::https::Proxy::"127.0.0.1" "DIRECT";
Acquire::ftp::Proxy::"127.0.0.1" "DIRECT";
Acquire::http::Proxy::"localhost" "DIRECT";
Acquire::https::Proxy::"localhost" "DIRECT";
Acquire::ftp::Proxy::"localhost" "DIRECT";
Acquire::http::Proxy::"::1" "DIRECT";
Acquire::https::Proxy::"::1" "DIRECT";
Acquire::ftp::Proxy::"::1" "DIRECT";' > /etc/apt/apt.conf.d/95-juju-proxy-settings
- snap set system proxy.http="http://10.0.0.1:8000"
- snap set system proxy.https="https://10.0.0.1:8000"
output:
all: '| tee -a /var/log/cloud-init-output.log'
package_update: true
package_upgrade: true
packages:

$ juju ssh 0 -- sudo grep snapd /var/log/cloud-init-output.log
error: cannot communicate with server: Put http://localhost/v2/snaps/system/conf: dial unix /run/snapd.socket: connect: no such file or directory
error: cannot communicate with server: Put http://localhost/v2/snaps/system/conf: dial unix /run/snapd.socket: connect: no such file or directory

[Ian Booth (wallyworld)]

I was unable to reproduce this at all, but have done a small patch to defer the snap set commands to cloud init runcmds rather than bootcmds.

https://github.com/juju/juju/pull/13261

[Nicolas Bock (nicolasbock)]

Reproduces with juju-2.9.11 and AWS as cloud provider with default series focal.

I will test your patch now.

[Nicolas Bock (nicolasbock)]

I can confirm that with your change the issue is not reproducible anymore Ian.

[Ian Booth (wallyworld)]

Great, thanks for testing