fail to launch instance (rootwrap mount failed)

Bug #1334121 reported by Chris
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Low
Unassigned

Bug Description

when I try to launch an instance, this error is logged in /var/log/nova/nova-compute.log

2014-06-25 04:40:57.614 8350 INFO nova.virt.libvirt.driver [req-10a54773-5c13-435e-a9d6-ea92df2e1e00 639d9bb856fe44a98b0f09cf503bc663 1bea54ab03b14b229437a95422a5c1df] [instance: 8e4146fa-ff59-4d5e-a27a-04c3c44df4eb] Creating image
2014-06-25 04:40:57.864 8350 WARNING nova.virt.disk.vfs.guestfs [req-10a54773-5c13-435e-a9d6-ea92df2e1e00 639d9bb856fe44a98b0f09cf503bc663 1bea54ab03b14b229437a95422a5c1df] Failed to close augeas aug_close: call launch before using this function
(in guestfish, don't forget to use the 'run' command)
2014-06-25 04:40:59.908 8350 ERROR nova.virt.disk.api [req-10a54773-5c13-435e-a9d6-ea92df2e1e00 639d9bb856fe44a98b0f09cf503bc663 1bea54ab03b14b229437a95422a5c1df] Failed to mount container filesystem '<nova.virt.disk.api._DiskImage object at 0x7f7a4412c390>' on '/var/lib/nova/instances/8e4146fa-ff59-4d5e-a27a-04c3c44df4eb/rootfs':
--
Failed to mount filesystem: Unexpected error while running command.
Command: sudo nova-rootwrap /etc/nova/rootwrap.conf mount /dev/nbd7 /var/lib/nova/instances/8e4146fa-ff59-4d5e-a27a-04c3c44df4eb/rootfs
Exit code: 32
Stdout: ''
Stderr: 'mount: you must specify the filesystem type\n'
2014-06-25 04:40:59.911 8350 ERROR nova.compute.manager [req-10a54773-5c13-435e-a9d6-ea92df2e1e00 639d9bb856fe44a98b0f09cf503bc663 1bea54ab03b14b229437a95422a5c1df] [instance: 8e4146fa-ff59-4d5e-a27a-04c3c44df4eb] Instance failed to spawn
2014-06-25 04:40:59.911 8350 TRACE nova.compute.manager [instance: 8e4146fa-ff59-4d5e-a27a-04c3c44df4eb] Traceback (most recent call last):
2014-06-25 04:40:59.911 8350 TRACE nova.compute.manager [instance: 8e4146fa-ff59-4d5e-a27a-04c3c44df4eb] File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1714, in _spawn
2014-06-25 04:40:59.911 8350 TRACE nova.compute.manager [instance: 8e4146fa-ff59-4d5e-a27a-04c3c44df4eb] block_device_info)
2014-06-25 04:40:59.911 8350 TRACE nova.compute.manager [instance: 8e4146fa-ff59-4d5e-a27a-04c3c44df4eb] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2266, in spawn
2014-06-25 04:40:59.911 8350 TRACE nova.compute.manager [instance: 8e4146fa-ff59-4d5e-a27a-04c3c44df4eb] block_device_info)
2014-06-25 04:40:59.911 8350 TRACE nova.compute.manager [instance: 8e4146fa-ff59-4d5e-a27a-04c3c44df4eb] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3669, in _create_domain_and_network
2014-06-25 04:40:59.911 8350 TRACE nova.compute.manager [instance: 8e4146fa-ff59-4d5e-a27a-04c3c44df4eb] domain.destroy()
2014-06-25 04:40:59.911 8350 TRACE nova.compute.manager [instance: 8e4146fa-ff59-4d5e-a27a-04c3c44df4eb] UnboundLocalError: local variable 'domain' referenced before assignment

this is the version of nova-compute:

root@compute2:/var/lib/nova# dpkg -l | grep nova-compute
ii nova-compute 1:2014.1.1-0ubuntu1 all OpenStack Compute - compute node base
ii nova-compute-libvirt 1:2014.1.1-0ubuntu1 all OpenStack Compute - compute node libvirt support
ii nova-compute-lxc 1:2014.1.1-0ubuntu1 all OpenStack Compute - compute node (LXC)

Tags: lxc rootwrap
Revision history for this message
Vladik Romanovsky (vladik-romanovsky) wrote :

Hi,

What type of an image are you trying to mount?
Looks like you are trying to mount a qcow2 file, however, what is the FS inside the image?

Thanks,
Vladik

Revision history for this message
Ray Chen (chenrano2002) wrote :

take 'Fedora-i386-20-20131211.1-sda.qcow2' for example, there is no partition inside. so kpartx can't get device map. it will fail to mount /dev/nbd0 /mnt

Revision history for this message
Sean Dague (sdague) wrote :

Which libvirt backend are you using? What's your nova.conf look like? What OS are you using?

Changed in nova:
status: New → Incomplete
importance: Undecided → Low
Revision history for this message
Sean Dague (sdague) wrote :

Please reopen if still an issue

Changed in nova:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.