Hi,
<br>I am getting the following error when running
<br>
<br>$ nova boot myserver --flavor 2 --key_name mykey --image 661bbe35-ebe5-4614-bdb2-3259ea507934
<br>
<br>+-------------------------------------+--------------------------------------+
<br>| Property | Value |
<br>+-------------------------------------+--------------------------------------+
<br>| OS-DCF:diskConfig | MANUAL |
<br>| OS-EXT-SRV-ATTR:host | None |
<br>| OS-EXT-SRV-ATTR:hypervisor_hostname | None |
<br>| OS-EXT-SRV-ATTR:instance_name | instance-00000005 |
<br>| OS-EXT-STS:power_state | 0 |
<br>| OS-EXT-STS:task_state | scheduling |
<br>| OS-EXT-STS:vm_state | building |
<br>| accessIPv4 | |
<br>| accessIPv6 | |
<br>| adminPass | mAnfCStaqWT2 |
<br>| config_drive | |
<br>| created | 2012-05-23T13:49:12Z |
<br>| flavor | m1.small |
<br>| hostId | |
<br>| id | 18cde301-e8c9-4721-928b-cd0daf63a4f0 |
<br>| image | f16-jeos |
<br>| key_name | mykey |
<br>| metadata | {} |
<br>| name | myserver |
<br>| progress | 0 |
<br>| status | BUILD |
<br>| tenant_id | 873855379940442797e53f2fa437893f |
<br>| updated | 2012-05-23T13:49:13Z |
<br>| user_id | 5677a018b8924cc58f993101c3024794 |
<br>+-------------------------------------+--------------------------------------+
<br>
<br>
<br>The image was obtained from following the Getting Started with OpenStack
on Fedora 17 tutorial
(<a class="moz-txt-link-freetext" href="http://fedoraproject.org/wiki/Getting_started_with_OpenStack_on_Fedora_17">http://fedoraproject.org/wiki/Getting_started_with_OpenStack_on_Fedora_17</a>).
So, I guess I am not the only one using it.
<br>
<br>$ glance index
<br>
<br>ID Name Disk Format Container Format Size
<br>
<br>------------------------------------ ------------------------------ -------------------- -------------------- --------------
<br>
<br>661bbe35-ebe5-4614-bdb2-3259ea507934 f16-jeos qcow2 ovf 213581824
<br>
<br>c15e90f2-e73e-4987-ad7a-11d87403012e cirros-0.3.0-x86_64-ari ari ari 2254249
<br>
<br>68ad4ece-6a56-4ac8-b112-1dd69283ea83 cirros-0.3.0-x86_64-ami ami ami 25165824
<br>
<br>6f5d8022-2dfe-406d-b391-fa0e48c175f3 cirros-0.3.0-x86_64-aki aki aki 4731440
<br>
<br>
<br>This is running on Nova Essex on Fedora 16.
<br>After a while I get:
<br>
<br>$ nova list
<br>
<br>+--------------------------------------+----------+--------+------------------+
<br>| ID | Name | Status | Networks |
<br>+--------------------------------------+----------+--------+------------------+
<br>| 18cde301-e8c9-4721-928b-cd0daf63a4f0 | myserver | ERROR | demonet=10.0.0.2 |
<br>+--------------------------------------+----------+--------+------------------+
<br>
<br>
<br>And so the log:
<br>
<br>2012-05-23 15:50:12 INFO nova.virt.libvirt.connection [-] Compute_service record updated for fedora.localdomain
<br>
<br>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 (
<br>
<br>--
<br>
<br>Failed to mount filesystem: Unexpected error while running command.
<br>
<br>Command: sudo nova-rootwrap mount /dev/mapper/nbd15p1 /tmp/tmpM9dOLC
<br>
<br>Exit code: 32
<br>
<br>Stdout: ''
<br>
<br>Stderr: 'mount: you must specify the filesystem type\n'
<br>
<br>--
<br>
<br>Failed to mount filesystem: Unexpected error while running command.
<br>
<br>Command: sudo nova-rootwrap guestmount --rw -a /var/lib/nova/instances/instance-00000005/disk -m /dev/sda1 /tmp/tmpM9dOLC
<br>
<br>Exit code: 1
<br>
<br>Stdout: ''
<br>
<br>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")
<br>
<br>
<br>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...
<br>
<br>$ cat /etc/filesystems
<br>ext4
<br>ext3
<br>ext2
<br>nodev proc
<br>nodev devpts
<br>iso9660
<br>vfat
<br>hfs
<br>hfsplus
<br>
<br>
<br>Any help to sort that problem out would be greatly appreciated.
<br>Thanks
<br>Patrick