[bug] network not found

[shaloulcy]

Ⅰ. Issue Description

When I reboot the OS, then start the pouchd and create a container, error happened

Ⅱ. Describe what happened

network 3fb0af2fde39fe401e102216bb4032e2fdba9d54afc49c6b53020e23788736fe not found

root@ubuntu-1:~# pouch run -d -t -v /data -v /test reg.docker.alibaba-inc.com/busybox:latest sh
Error: failed to run container 22cb4a: {"message":"failed to create endpoint 22cb4ac7 on network bridge: network 3fb0af2fde39fe401e102216bb4032e2fdba9d54afc49c6b53020e23788736fe does not exist"}

but network 3fb0af2fde exisit

root@ubuntu-1:~# pouch network ls
NETWORK ID   NAME     DRIVER   SCOPE
46d179a769   host     host     
76a68e7e71   none     null     
3fb0af2fde   bridge   bridge   

Ⅲ. Describe what you expected to happen

container is created successfully

Ⅳ. How to reproduce it (as minimally and precisely as possible)

1. run a container and reboot the OS

pouch run -d -t reg.docker.alibaba-inc.com/busybox:latest sh

reboot

2. start the container or create a new container

root@ubuntu-1:~# pouch ps -a
Name     ID       Status                   Created         Image                                       Runtime
c4c710   c4c710   Stopped (0) 21 seconds   3 minutes ago   reg.docker.alibaba-inc.com/busybox:latest   runc
root@ubuntu-1:~# pouch start c4c710
Error: failed to start containers: {"message":"failed to create endpoint c4c710da on network bridge: network 18ed57e98c871e65d8a45c5ad9eb8d10fb4e4382b38ca01a535ae8e4b51ce3bd does not exist"}


or run a new container

root@ubuntu-1:~# pouch run -d -t reg.docker.alibaba-inc.com/busybox:latest sh
Error: failed to run container 12717e: {"message":"failed to create endpoint 12717e90 on network bridge: network 18ed57e98c871e65d8a45c5ad9eb8d10fb4e4382b38ca01a535ae8e4b51ce3bd does not exist"}

Ⅴ. Anything else we need to know?

Ⅵ. Environment:

• pouch version (use pouch version):

root@ubuntu-1:~# pouch version
GoVersion:       go1.9.5
KernelVersion:   4.4.0-116-generic
Os:              linux
Version:         0.5.0
APIVersion:      1.24
Arch:            amd64
BuildTime:       2018-05-31T10:09:40+08:00
GitCommit:       0.4.0-341-g26cd5e3-dirty

• OS (e.g. from /etc/os-release):

NAME="Ubuntu"
VERSION="16.04.4 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.4 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

• Kernel (e.g. uname -a):

Linux ubuntu-1 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

• Install tools:
• Others:

[allencloud]

This is definitely a flaky test, right? @shaloulcy
I do not think you can reproduce this.
We should figure out one way to handle this situation.

[shaloulcy]

@allencloud @rudyfly we can reproduce it

[allencloud]

Actually I ran into this issue, too. Pity. @rudyfly