Snappy

After a reboot store was not accessible

Bug #1667359 reported by Pat McGowan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snappy
Expired
Undecided
Unassigned

Bug Description

Xenial amd64
core 16.04.1
snapd 2.22.3

Rebooted the system and then any store command (snap refresh, snap find, ...) resulted in an error like the following

$ snap refresh
error: cannot refresh []: cannot refresh snap-declaration for "libreoffice": Get https://assertions.ubuntu.com/v1/assertions/snap-declaration/16/CpUkI0qPIIBVRsjy49adNq4D6Ra72y4v?max-format=1: dial tcp: lookup assertions.ubuntu.com on [::1]:53: read udp [::1]:40318->[::1]:53: read: connection refused

Doing a restart:
systemctl restart snapd
resolved the issue.

Pat McGowan (pat-mcgowan)
affects: snapd (Ubuntu) → snappy
Revision history for this message
Maciej Borzecki (maciek-borzecki) wrote :

Looks like a problem with DNS. Does the problem persist with recent versions of snapd?

Changed in snappy:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Snappy because there has been no activity for 60 days.]

Changed in snappy:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.