Latest updates (October security releases) not all built and published

[rvagg]

Just a heads-up, there's been some trouble getting the security releases out via Snap, something about the snap store not responding properly. https://launchpad.net/~openjs/+snap/node12 https://launchpad.net/~openjs/+snap/node14 https://launchpad.net/~openjs/+snap/node15. I'll keep trying to repeat the builds, but the fact that Snapcraft says all systems are green have me concerned that we have a different problem to deal with: https://status.snapcraft.io/

Filling an issue here in case I don't get this done and it drops off my radar during the day, someone else can try or can keep me to account!

[rvagg]

Still failing, I've tried renewing the Snap store authorization for Launchpad for each of them but it doesn't seem to fix it.

FTR

Downloading core
[13/Oct/2021:01:48:49 +0000] "CONNECT canonical-lgw01.cdn.snapcraftcontent.com:443 HTTP/1.0" 403 1762 "-" "-"
Retrying (Retry(total=4, connect=None, read=None, redirect=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 403 Forbidden',))': /download-origin/canonical-lgw01/99T7MUlRhtI3U0QFgl5mXXESAiSwt776_11803.snap?token=1634101200_9fd193a978eee373950b1e4c3c68fb86c26c35a8
[13/Oct/2021:01:48:49 +0000] "CONNECT canonical-lgw01.cdn.snapcraftcontent.com:443 HTTP/1.0" 403 1762 "-" "-"
Retrying (Retry(total=3, connect=None, read=None, redirect=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 403 Forbidden',))': /download-origin/canonical-lgw01/99T7MUlRhtI3U0QFgl5mXXESAiSwt776_11803.snap?token=1634101200_9fd193a978eee373950b1e4c3c68fb86c26c35a8
[13/Oct/2021:01:48:53 +0000] "CONNECT canonical-lgw01.cdn.snapcraftcontent.com:443 HTTP/1.0" 403 1762 "-" "-"
[13/Oct/2021:01:48:54 +0000] "CONNECT api.snapcraft.io:443 HTTP/1.0" 200 4061 "-" "-"
[13/Oct/2021:01:48:54 +0000] "CONNECT api.snapcraft.io:443 HTTP/1.0" 200 5563 "-" "-"
Retrying (Retry(total=2, connect=None, read=None, redirect=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 403 Forbidden',))': /download-origin/canonical-lgw01/99T7MUlRhtI3U0QFgl5mXXESAiSwt776_11803.snap?token=1634101200_9fd193a978eee373950b1e4c3c68fb86c26c35a8
[13/Oct/2021:01:49:02 +0000] "CONNECT canonical-lgw01.cdn.snapcraftcontent.com:443 HTTP/1.0" 403 1762 "-" "-"
Retrying (Retry(total=1, connect=None, read=None, redirect=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 403 Forbidden',))': /download-origin/canonical-lgw01/99T7MUlRhtI3U0QFgl5mXXESAiSwt776_11803.snap?token=1634101200_9fd193a978eee373950b1e4c3c68fb86c26c35a8
[13/Oct/2021:01:49:18 +0000] "CONNECT canonical-lgw01.cdn.snapcraftcontent.com:443 HTTP/1.0" 403 1762 "-" "-"
Retrying (Retry(total=0, connect=None, read=None, redirect=None)) after connection broken by 'ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 403 Forbidden',))': /download-origin/canonical-lgw01/99T7MUlRhtI3U0QFgl5mXXESAiSwt776_11803.snap?token=1634101200_9fd193a978eee373950b1e4c3c68fb86c26c35a8
[13/Oct/2021:01:49:50 +0000] "CONNECT canonical-lgw01.cdn.snapcraftcontent.com:443 HTTP/1.0" 403 1762 "-" "-"
There seems to be a network error: maximum retries exceeded trying to reach the store.
Check your network connection, and check the store status at https://status.snapcraft.io/
Build failed

[rvagg]

Seems to be a known issue that's being addressed https://forum.snapcraft.io/t/error-downloading-snap-stage-snaps-on-remote-build/26894

[rvagg]

after a bunch of manual retries I got them all to build, the only one I can't get to build is v12.x for x86, I'm giving up on that and assuming it has near zero use

still a bug, I think we'll run into this again unless launchpad deals with it properly, 🤞 they will soon

[rvagg]

Same thing is happening now for the latest node14 builds. arm64 and armhf failed and I've retried 3 times and run out of patience. I'm going to write these off and assume they'll be fixed for the next release and that we don't have too many people using those architectures (or any) and this version of Node.js.

If someone is using them and finds this post, feel free to follow up and I can retry again at a later date and 🤞 .