[Bug 1636706] Re: instances in ACTIVE/shutdown state just after creation
OpenStack Infra
1636706 at bugs.launchpad.net
Wed Oct 26 18:48:11 UTC 2016
Reviewed: https://review.openstack.org/390899
Committed: https://git.openstack.org/cgit/openstack/nova-lxd/commit/?id=f0d2ed9a388f1b7e1b19c8fd26f4e1f5505dfd33
Submitter: Jenkins
Branch: master
commit f0d2ed9a388f1b7e1b19c8fd26f4e1f5505dfd33
Author: Chuck Short <chuck.short at canonical.com>
Date: Wed Oct 26 11:32:32 2016 -0400
Wait for contianer to start before querying state
When spawning a container nova-lxd does not wait
for the container to spawn before querying the power
state. This results in false feedback to the user
when running 'nova list'.
To fix this use container.start(wait=True) to tell
the LXD API to wait for the instance to change its state.
If the container fails to boot the container will timeout
after 30 seconds.
Closes-Bug: #1636706
Change-Id: Ia089c6430af4d4aee4b3a9d319bc2ff1cfbe39a8
Signed-off-by: Chuck Short <chuck.short at canonical.com>
** Changed in: nova-lxd
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to nova-lxd in Ubuntu.
https://bugs.launchpad.net/bugs/1636706
Title:
instances in ACTIVE/shutdown state just after creation
Status in nova-lxd:
Fix Released
Status in nova-lxd package in Ubuntu:
New
Bug description:
I've seen this a few times when booting nova-lxd instances under
newton:
| 1ff6ffae-c39a-449f-994c-88ffed69063d | test-1 | ACTIVE | - | Running | private=172.16.0.21 |
| bc6dc3fd-332c-4b13-adef-5bc51482a034 | test-10 | ACTIVE | - | Running | private=172.16.0.7 |
| c4b569fd-b3c9-4763-98e7-67c5e99dc48c | test-11 | ACTIVE | - | Shutdown | private=172.16.0.23 |
| 7ac55fd4-51a4-4b9b-a9ff-031d9411e2f9 | test-12 | ACTIVE | - | Running | private=172.16.0.14 |
| 4e7dd704-e7db-4072-a098-ad0a1182e3ea | test-13 | ACTIVE | - | Running | private=172.16.0.32 |
| 1ddf7187-f17c-479f-ba08-2541506c67dc | test-14 | ACTIVE | - | Running | private=172.16.0.33 |
| e3f400b1-be4e-4d6c-9d6d-8a7e62e82e72 | test-15 | ACTIVE | - | Running | private=172.16.0.26 |
| 162fa110-7e46-448c-b731-6e3040baa8a9 | test-16 | ACTIVE | - | Running | private=172.16.0.40 |
| b5ed2fe2-9cce-4725-b391-aa4fe79533cf | test-17 | ACTIVE | - | Running | private=172.16.0.41 |
| ae4e7c14-6394-4888-9470-bc3f65ed5129 | test-18 | ACTIVE | - | Running | private=172.16.0.35 |
| d8f65ae9-0dd8-4e11-b54e-f63028e1c3d4 | test-19 | ACTIVE | - | Running | private=172.16.0.39 |
| 2c211b0e-1815-4698-b8be-94b79d31a0d5 | test-2 | ACTIVE | - | Running | private=172.16.0.11 |
| 20f837a3-b98c-49b8-8c6d-faebfdd54589 | test-20 | ACTIVE | - | Running | private=172.16.0.44 |
| e1a399dc-8143-418c-b912-d9ab6591c296 | test-3 | ACTIVE | - | Shutdown | private=172.16.0.27 |
| 773abca8-09c9-4f63-8242-5ef2432515b1 | test-4 | ACTIVE | - | Shutdown | private=172.16.0.28 |
| 4626b55d-f2ae-4997-b7dc-495ad3328f46 | test-5 | ACTIVE | - | Running | private=172.16.0.6 |
| 635b7c98-fbe4-472c-af72-49158c1dd0a9 | test-6 | ACTIVE | - | Running | private=172.16.0.10 |
| 1d02bf44-c0db-4459-a605-a579999deabe | test-7 | ACTIVE | - | Running | private=172.16.0.30 |
| eb7a1e69-8abc-4381-bc10-ccc53037fa4d | test-8 | ACTIVE | - | Shutdown | private=172.16.0.16 |
| a3ac2222-cec5-4e25-b92c-6043d397cbd3 | test-9 | ACTIVE | - | Running | private=172.16.0.20 |
+--------------------------------------+--------------------------+--------+------------+-------------+------------------------------------+
The instances is ACTIVE and is running, but the power state is
described as shutdown.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova-lxd/+bug/1636706/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list