snap find returns "no snaps found" when there is no network
Bug #1575252 reported by
Michael Vogt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Triaged
|
Low
|
Unassigned |
Bug Description
If there is no network `snap find` will not return a useful result:
```
ubuntu@
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:160 errors:0 dropped:0 overruns:0 frame:0
TX packets:160 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:12800 (12.8 KB) TX bytes:12800 (12.8 KB)
ubuntu@
error: no snaps found
```
It should return that it can not talk to the store instead.
Changed in snappy: | |
importance: | Undecided → Low |
status: | New → Triaged |
affects: | snappy → snapd |
To post a comment you must log in.