LXC instances cannot reboot (reboot from container)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
High
|
Unassigned |
Bug Description
I have an LXC compute node. I can create LXC containers, they work fine.
When I try to reboot containers (reboot initiated from inside the container), the container goes into "SHUTOFF" status / "Shutdown" power state, and does not come back.
If I do a "nova start", the container comes back to "RUNNING", but with the following exception in logs:
----------
ERROR nova.virt.disk.api [req-63630337-
TRACE nova.virt.disk.api Traceback (most recent call last):
TRACE nova.virt.disk.api File "/opt/stack/
TRACE nova.virt.disk.api run_as_root=True, attempts=3)
TRACE nova.virt.disk.api File "/opt/stack/
TRACE nova.virt.disk.api return RootwrapProcess
TRACE nova.virt.disk.api File "/opt/stack/
TRACE nova.virt.disk.api return processutils.
TRACE nova.virt.disk.api File "/usr/local/
TRACE nova.virt.disk.api cmd=sanitized_cmd)
TRACE nova.virt.disk.api ProcessExecutio
TRACE nova.virt.disk.api Command: sudo nova-rootwrap /etc/nova/
TRACE nova.virt.disk.api Exit code: 1
TRACE nova.virt.disk.api Stdout: u''
TRACE nova.virt.disk.api Stderr: u"loop: can't delete device /dev/loop0: No such device or address\n"
TRACE nova.virt.disk.api
----------
Tested on Juno/Kilo/
(note that in Juno, nova start does not even work)
Below is my Devstack recipe if needed:
---------
sudo mkdir -p /opt/stack
sudo chown $USER /opt/stack
git clone -b stable/liberty https:/
cat > /opt/stack/
[[local|localrc]]
VIRT_DRIVER=libvirt
LIBVIRT_TYPE=lxc
disable_service heat h-api h-api-cfn h-api-cw h-eng
disable_service horizon
disable_service tempest
disable_service c-sch c-api c-vol
disable_service s-proxy s-object s-container s-account
disable_service q-svc q-agt q-dhcp q-l3 q-meta neutron
disable_service tempest
DATABASE_
RABBIT_
SERVICE_
SERVICE_
ADMIN_PASSWORD=
END
cd /opt/stack/
./stack.sh
---------
Changed in nova: | |
importance: | Undecided → High |
Is this happening with a specific image? I tested with Cirros on a base install but wasn't able to replicate the issue.
Reboot within the Instance did put the instance in a shutdown state. Nova start was able to start the instance. I wasn't able to see any errors in the logs.