[Bug 1630891] Re: unable to start lxd container instances after host reboot

2022-01-27 Thread James Page
** Changed in: nova-lxd (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630891 Title: unable to start lxd container instances after host reboot To man

[Bug 1630891] Re: unable to start lxd container instances after host reboot

2016-12-15 Thread James Page
** Changed in: nova-lxd (Ubuntu) Status: Confirmed => Triaged ** Changed in: nova-lxd (Ubuntu) Importance: Undecided => Medium ** No longer affects: cloud-archive ** Changed in: nova-lxd (Ubuntu) Importance: Medium => Low ** Changed in: nova-lxd (Ubuntu) Status: Triaged => I

[Bug 1630891] Re: unable to start lxd container instances after host reboot

2016-11-09 Thread Kevin Metz
Version was LXD 2.3.0, and Openstack Mitaka. nova-compute-lxd nodes have been removed so not able to replicate exact issue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630891 Title: unable to star

[Bug 1630891] Re: unable to start lxd container instances after host reboot

2016-11-09 Thread James Page
I tried to reproduce this on xenial-mitaka - on reboot, the instance is in the shutdown state, but I was able to start it and confirm that networking was OK. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bu

[Bug 1630891] Re: unable to start lxd container instances after host reboot

2016-11-09 Thread James Page
from stable/newton branch: commit c3ed3574a5c0aa59c9e68e6ac4ab2bff1fce3ca0 Author: Chuck Short Date: Thu Oct 6 09:08:37 2016 -0400 Reset vifs after reboot When a host is rebooted instances are set into a shutdown instance state, which is the correct thing. However whe

[Bug 1630891] Re: unable to start lxd container instances after host reboot

2016-11-09 Thread Chuck Short
** Also affects: nova-lxd Importance: Undecided Status: New ** Changed in: nova-lxd Status: New => Fix Released ** Changed in: nova-lxd (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subs

[Bug 1630891] Re: unable to start lxd container instances after host reboot

2016-11-09 Thread James Page
Kevin - can you confirm versions please? This issue was quite specific to OpenStack Newton - you might be seeing the same symptom but the underlying cause may be different. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.l

[Bug 1630891] Re: unable to start lxd container instances after host reboot

2016-11-03 Thread Kevin Metz
This issue still exists. This also effects instances starting automatically after a reboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630891 Title: unable to start lxd container instances after

[Bug 1630891] Re: unable to start lxd container instances after host reboot

2016-10-13 Thread Chuck Short
** Changed in: nova-lxd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630891 Title: unable to start lxd container instances after host reboot To manage