Snapd stuck after a request timeout error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Confirmed
|
Critical
|
Unassigned |
Bug Description
Today snapd is stucked refreshing a snap on my focal system
$ snap version
snap 2.45.1+
snapd 2.45.1+
series 16
ubuntu 20.04
kernel 5.6.0-1007-oem
$ snap changes
...
315 Doing today at 08:59 CEST - Actualiser automatiquement les paquets Snap "openstackclients", "ubuntu-
$ snap watch 315
Télécharger un paquet Snap "ubuntu-bug-triage" (205) à partir du canal "latest/stable" 56% 4.46MB/s 615ms
but it's stuck on 56% for over an hour now (on a 19M snap)
doing Ctrl-C doesn't exit the snap watch but just display a new line on the buffer and keeps updating the status
$ systemctl status snapd
...
snapd[1336]: 2020/08/14 09:00:03 Unsolicited response received on idle HTTP channel starting with "HTTP/1.0 408 Request Time-out\
Changed in snapd: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in snapd: | |
importance: | High → Critical |
Changed in snapd: | |
status: | Confirmed → Invalid |
status: | Invalid → Fix Released |
Changed in snapd: | |
status: | Fix Released → Confirmed |
This looks like a http / go bug:
snapd[1336]: 2020/08/14 09:00:03 Unsolicited response received on idle HTTP channel starting with "HTTP/1.0 408 Request Time-out\ r\nCache- Control: no-cache\ r\nConnection: close\r\ nContent- Type: text/html\ r\n\r\n< html><body> <h1>408 Request Time-out</h1>\nYour browser didn't send a complete request in time.\n< /body>< /html>\ n"; err=<nil>
It seems that we make a request, some part of the stack thinks that request has timed out and forgets about it but then we get a response that the stack thinks is unsolicited.