Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782616
Title:
long
Right.
So we think this was actually just lack of external connection from the system.
This is still an issue though. There is no requirement on internet
connectivity for running a container ('lxc launch ubuntu-daily:bionic').
--
You received this bug notification because you are a member of Ub
Was maybe the proxy env missing (or ignored) that is neede don Diamond?
Still a bug to block the crit chain for 40s if that is the case, but maybe a
thought to check.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
possibly some relevant info, from journalctl -o short-monotonic
[ 540.929982] sstest-616 systemd[1]: snapd.seeded.service: Failed to reset
devices.list: Operation not permitted
[ 540.930083] sstest-616 sshd[257]: Server listening on 0.0.0.0 port 22.
[ 540.931309] sstest-616 sshd[257]: Server l
** Attachment added: "output of journalctl -o short-monotonic -xb"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1782616/+attachment/5165355/+files/journal-short-monotonic-xb.txt
** Description changed:
This is a default container (bionic) launched from a ppc64el host
inside I s
