openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #12201
[Nova] Getting error when injecting data into an image
Hi,
I am getting the following error when running
$ nova boot myserver --flavor 2 --key_name mykey --image
661bbe35-ebe5-4614-bdb2-3259ea507934
+-------------------------------------+--------------------------------------+
| Property |
Value |
+-------------------------------------+--------------------------------------+
| OS-DCF:diskConfig |
MANUAL |
| OS-EXT-SRV-ATTR:host |
None |
| OS-EXT-SRV-ATTR:hypervisor_hostname |
None |
| OS-EXT-SRV-ATTR:instance_name |
instance-00000005 |
| OS-EXT-STS:power_state |
0 |
| OS-EXT-STS:task_state |
scheduling |
| OS-EXT-STS:vm_state |
building |
| accessIPv4
| |
| accessIPv6
| |
| adminPass |
mAnfCStaqWT2 |
| config_drive
| |
| created |
2012-05-23T13:49:12Z |
| flavor |
m1.small |
| hostId
| |
| id |
18cde301-e8c9-4721-928b-cd0daf63a4f0 |
| image |
f16-jeos |
| key_name |
mykey |
| metadata |
{} |
| name |
myserver |
| progress |
0 |
| status |
BUILD |
| tenant_id |
873855379940442797e53f2fa437893f |
| updated |
2012-05-23T13:49:13Z |
| user_id |
5677a018b8924cc58f993101c3024794 |
+-------------------------------------+--------------------------------------+
The image was obtained from following the Getting Started with OpenStack on
Fedora 17 tutorial (
http://fedoraproject.org/wiki/Getting_started_with_OpenStack_on_Fedora_17).
So, I guess I am not the only one using it.
$ glance index
ID Name Disk
Format Container Format Size
------------------------------------ ------------------------------
-------------------- -------------------- --------------
661bbe35-ebe5-4614-bdb2-3259ea507934 f16-jeos
qcow2 ovf 213581824
c15e90f2-e73e-4987-ad7a-11d87403012e cirros-0.3.0-x86_64-ari
ari ari 2254249
68ad4ece-6a56-4ac8-b112-1dd69283ea83 cirros-0.3.0-x86_64-ami
ami ami 25165824
6f5d8022-2dfe-406d-b391-fa0e48c175f3 cirros-0.3.0-x86_64-aki
aki aki 4731440
This is running on Nova Essex on Fedora 16.
After a while I get:
$ nova list
+--------------------------------------+----------+--------+------------------+
| ID | Name | Status |
Networks |
+--------------------------------------+----------+--------+------------------+
| 18cde301-e8c9-4721-928b-cd0daf63a4f0 | myserver | ERROR |
demonet=10.0.0.2 |
+--------------------------------------+----------+--------+------------------+
And so the log:
2012-05-23 15:50:12 INFO nova.virt.libvirt.connection [-] Compute_service
record updated for fedora.localdomain
2012-05-23 15:50:35 WARNING nova.virt.libvirt.connection
[req-dd9a661c-94d3-42e4-b7ba-699c7b41def4 5677a018b8924cc58f993101c3024794
873855379940442797e53f2fa437893f] [instance:
18cde301-e8c9-4721-928b-cd0daf63a4f0] Ignoring error injecting data into
image 661bbe35-ebe5-4614-bdb2-3259ea507934 (
--
Failed to mount filesystem: Unexpected error while running command.
Command: sudo nova-rootwrap mount /dev/mapper/nbd15p1 /tmp/tmpM9dOLC
Exit code: 32
Stdout: ''
Stderr: 'mount: you must specify the filesystem type\n'
--
Failed to mount filesystem: Unexpected error while running command.
Command: sudo nova-rootwrap guestmount --rw -a
/var/lib/nova/instances/instance-00000005/disk -m /dev/sda1 /tmp/tmpM9dOLC
Exit code: 1
Stdout: ''
Stderr: "libguestfs: error: mount_options: /dev/vda1 on /: mount: you must
specify the filesystem type\n/usr/bin/guestmount: '/dev/sda1' could not be
mounted. Did you mean one of these?\n\t/dev/sda1 (unknown)\n\t/dev/sda2
(ext4)\n")
Note that I get the same error with other images, so it's not specific to
f16-jeos. I am confused by this error. If the nova-rootwrap had to specify
a filesystem type for the mount to succeed that would be a longtime known
bug and so fixed bug right? The default filesystem types seem to be
configured properly on the system...
$ cat /etc/filesystems
ext4
ext3
ext2
nodev proc
nodev devpts
iso9660
vfat
hfs
hfsplus
Any help to sort that problem out would be greatly appreciated.
Thanks
Patrick
Follow ups