Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Hello,

I found out that the reason is because nova-manage cannot find my device "eth1", which I use it as a external interface. I did the steps the guide shows, but the eth1 isn't recognize by the system. I also use "ip a | grep state" , eth1 state isn't up and br100 is not bind.

Hello,

I found out that the reason is because nova-manage cannot find my device "eth1", which I use it as a external interface. I did the steps the guide shows, but the eth1 isn't recognize by the system. I also use "ip a | grep state" , eth1 state isn't up and br100 is not bind.

If I bind br100 to my active interface eno1, br100 state is up. But then I cannot ping to controller or other website. So, is there steps missing when I create external interface "eth1"? I only add a copy of eno1 in /etc/sysconfig/network-scripts/ifcfg-eno1 to ifcfg-eth1 and modify the content.

Hello,

I found out that the reason is because nova-manage cannot find my device "eth1", which I use it as a external interface. I did the steps the guide shows, but the eth1 isn't recognize by the system. I also use "ip a | grep state" , eth1 state isn't up and br100 is not bind.

If I bind br100 to my active interface eno1, br100 state is up. But then I cannot ping to controller or other website. So, is there steps missing when I create external interface "eth1"? I only add a copy of eno1 in /etc/sysconfig/network-scripts/ifcfg-eno1 to ifcfg-eth1 and modify the content.

Update================= I try to boot another instance and here is the compute log I found may be the root cause.

2014-09-19 05:29:24.212 4972 DEBUG nova.virt.disk.vfs.guestfs [req-55fa24cf-163d-47b5-a90b-92264dab990c 160c9c6f2bb44e41836462d78d53ace0 587a337af7884dd69b2a7d77eb68e572] Tearing down appliance teardown /usr/lib/python2.7/site-packages/nova/virt/disk/vfs/guestfs.py:141 2014-09-19 05:29:24.214 4972 WARNING nova.virt.disk.vfs.guestfs [req-55fa24cf-163d-47b5-a90b-92264dab990c 160c9c6f2bb44e41836462d78d53ace0 587a337af7884dd69b2a7d77eb68e572] Failed to close augeas aug_close: do_aug_close: you must call 'aug-init' first to initialize Augeas 2014-09-19 05:29:24.249 4972 DEBUG nova.virt.disk.api [req-55fa24cf-163d-47b5-a90b-92264dab990c 160c9c6f2bb44e41836462d78d53ace0 587a337af7884dd69b2a7d77eb68e572] Unable to mount image /var/lib/nova/instances/63ed8a3b-d11f-46ca-8a5d-cf8ad1a54c94/disk with error Error mounting /var/lib/nova/instances/63ed8a3b-d11f-46ca-8a5d-cf8ad1a54c94/disk with libguestfs (mount_options: /dev/sda on / (options: ''): mount: /dev/sda is write-protected, mounting read-only mount: unknown filesystem type '(null)'). Cannot resize. is_image_partitionless /usr/lib/python2.7/site-packages/nova/virt/disk/api.py:211 2014-09-19 05:29:24.249 4972 DEBUG nova.openstack.common.lockutils [req-55fa24cf-163d-47b5-a90b-92264dab990c 160c9c6f2bb44e41836462d78d53ace0 587a337af7884dd69b2a7d77eb68e572] Released file lock "e56d642d025882a2734f5d19747f23205f5c0cc8" at /var/lib/nova/instances/locks/nova-e56d642d025882a2734f5d19747f23205f5c0cc8 lock /usr/lib/python2.7/site-packages/nova/openstack/common/lockutils.py:210

Any solution??