container failed to start

[Michael Foord]

Hey Huan Liu,

There is a known issue around LXD containers and auto-restart (due to an 
error in the way we configure lxd) that I'm working on right now. It's 
not *clear* to me that it's the same issue affecting you - and the error 
logs you show around the veth bridge would indicate that it looks like a 
different issue.

I thought it worth mentioning however: 
https://bugs.launchpad.net/juju/+bug/1631254

All the best,

Michael Foord


On 23/12/16 07:40, liuhuan (Q) wrote:
>
> Hi,
>
>    I have got a problem. when I try to reboot physical compute nodes, 
> all containers failed to start after compute nodes reboot while all 
> containers running well before reboot compute nodes.
>
>    Error log indicates the operation of attach veth to bridge was not 
> permitted, I don't know why? what possible reason could cause that?
>
>                 root at compute-01:~# lxc-start -F --name 
> juju-machine-4-lxc-0 --logfile output.log
>
> ovs-vsctl: no bridge named bond1-br0:1
>
> lxc-start: conf.c: instantiate_veth: 2604 failed to attach 
> 'vethWYX1IN' to the bridge 'bond1-br0:1': Operation not permitted
>
> lxc-start: conf.c: lxc_create_network: 2890 failed to create netdev
>
> lxc-start: start.c: lxc_spawn: 1081 failed to create the network
>
> lxc-start: start.c: __lxc_start: 1354 failed to spawn 
> 'juju-machine-4-lxc-0'
>
> lxc-start: tools/lxc_start.c: main: 344 The container failed to start.
>
> lxc-start: tools/lxc_start.c: main: 348 Additional information can be 
> obtained by setting the --logfile and --logpriority options.
>
> I'm Looking forward to your reply, thanks very much！
>
> Thanks
>
> Huan Liu
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20161223/d10264e7/attachment.html>