settingsLogin | Registersettings

[Openstack] error creating instance

0 votes

Hi

Can someone please help on this matter?

I have installed and configured OpenStack(Juno) environment on Ubuntu(14.04).
We have currently 1 controller node, 3 network nodes and 4 compute nodes as well as 4 swift nodes.
I'm using OpenStack Networking (neutron).
I'v recently introduced VLANs for tunnel-, mgmt- and external networks.

When I try to create a instance, with this cmd:

nova boot --flavor m1.tiny --image cirros-0.3.3-x86_64 --nic net-id=7a344656-815c-4116-b697-b52f9fdc6e4c --security-group default --key-name demo-key demo-instance3

it fails. The status from nova list is :
root@controller2:/# nova list
+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+
| ca662fc0-2417-4da1-be2c-d6ccf90ed732 | demo-instance22 | ERROR | - | NOSTATE | |
| 17d26ca3-f56c-4a87-ae0a-acfafea4838c | demo-instance30 | ERROR | - | NOSTATE | demo-net=x.x.x.x |
+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

This error apperas in the /var/log/syslog file on the computer node:

Jun 26 14:55:04 compute5 kernel: [ 2187.597951] nbd8: p1
Jun 26 14:55:04 compute5 kernel: [ 2187.668430] EXT4-fs (nbd8): VFS: Can't find ext4 filesystem
Jun 26 14:55:04 compute5 kernel: [ 2187.668521] EXT4-fs (nbd8): VFS: Can't find ext4 filesystem
Jun 26 14:55:04 compute5 kernel: [ 2187.668583] EXT4-fs (nbd8): VFS: Can't find ext4 filesystem
Jun 26 14:55:04 compute5 kernel: [ 2187.668899] FAT-fs (nbd8): bogus number of reserved sectors
Jun 26 14:55:04 compute5 kernel: [ 2187.668936] FAT-fs (nbd8): Can't find a valid FAT filesystem
Jun 26 14:55:04 compute5 kernel: [ 2187.753989] block nbd8: NBD_DISCONNECT
Jun 26 14:55:04 compute5 kernel: [ 2187.754056] block nbd8: Receive control failed (result -32)
Jun 26 14:55:04 compute5 kernel: [ 2187.754161] block nbd8: queue cleared

Also, this is logged on the computer node, in /var/log/nova/nova-compute.log

2015-06-26 14:55:02.591 7961 AUDIT nova.compute.claims [-] [instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] disk limit not specified, defaulting to unlimited
2015-06-26 14:55:02.606 7961 AUDIT nova.compute.claims [-] [instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] Claim successful
2015-06-26 14:55:02.721 7961 INFO nova.scheduler.client.report [-] Computeservice record updated for ('compute5')
2015-06-26 14:55:02.836 7961 INFO nova.scheduler.client.report [-] Compute
service record updated for ('compute5')
2015-06-26 14:55:03.115 7961 INFO nova.virt.libvirt.driver [-] [instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] Creating image
2015-06-26 14:55:03.118 7961 INFO nova.openstack.common.lockutils [-] Created lock path: /var/lib/nova/instances/locks
2015-06-26 14:55:03.458 7961 INFO nova.scheduler.client.report [-] Computeservice record updated for ('compute5', 'compute5.siminn.is')
2015-06-26 14:55:04.088 7961 INFO nova.virt.disk.vfs.api [-] Unable to import guestfsfalling back to VFSLocalFS
2015-06-26 14:55:04.363 7961 ERROR nova.compute.manager [-] [instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] Instance failed to spawn
2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] Traceback (most recent call last):
2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2267, in _build
resources
2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] yield resources
2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2137, in buildandruninstance
2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] blockdeviceinfo=blockdeviceinfo)
2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2620, in spawn
2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] writetodisk=True)
2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 4159, in getguestxml
2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] context)
2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3937, in _get
guestconfig
2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] flavor, CONF.libvirt.virt
type)
2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 352, in getconfig
2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] _("Unexpected vif
type=%s") % viftype)
2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] NovaException: Unexpected vif
type=binding_failed
2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c]

Best regards
Yngvi


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
asked Jun 26, 2015 in openstack by Yngvi_Páll_Þorfinnss (3,100 points)   3 7

44 Responses

0 votes

The issue seems to be related to a neutron missconfiguration.
--> Unexpected viftype=bindingfailed

Please have a look at your neutron server config file in the network
node(s) and the l2 agent config files (ovs?). You should find additional
information there.

If this doesn't help, please provide these log files, the neutron config
files and a brief description of how your nodes network are set up.

Andreas

On Fr, 2015-06-26 at 15:05 +0000, Yngvi Páll Þorfinnsson wrote:
Hi

Can someone please help on this matter?

I have installed and configured OpenStack(Juno) environment on
Ubuntu(14.04).

We have currently 1 controller node, 3 network nodes and 4 compute
nodes as well as 4 swift nodes.

I'm using OpenStack Networking (neutron).

I‘v recently introduced VLANs for tunnel-, mgmt- and external
networks.

When I try to create a instance, with this cmd:

nova boot --flavor m1.tiny --image cirros-0.3.3-x86_64 --nic
net-id=7a344656-815c-4116-b697-b52f9fdc6e4c --security-group default
--key-name demo-key demo-instance3

it fails. The status from nova list is :

root@controller2:/# nova list

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

| ID | Name | Status |
Task State | Power State | Networks |

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

| ca662fc0-2417-4da1-be2c-d6ccf90ed732 | demo-instance22 | ERROR | -
| NOSTATE | |

| 17d26ca3-f56c-4a87-ae0a-acfafea4838c | demo-instance30 | ERROR | -
| NOSTATE | demo-net=x.x.x.x |

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

This error apperas in the /var/log/syslog file on the computer node:

Jun 26 14:55:04 compute5 kernel: [ 2187.597951] nbd8: p1

Jun 26 14:55:04 compute5 kernel: [ 2187.668430] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668521] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668583] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668899] FAT-fs (nbd8): bogus
number of reserved sectors

Jun 26 14:55:04 compute5 kernel: [ 2187.668936] FAT-fs (nbd8): Can't
find a valid FAT filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.753989] block nbd8:
NBD_DISCONNECT

Jun 26 14:55:04 compute5 kernel: [ 2187.754056] block nbd8: Receive
control failed (result -32)

Jun 26 14:55:04 compute5 kernel: [ 2187.754161] block nbd8: queue
cleared

Also, this is logged on the computer node,
in /var/log/nova/nova-compute.log

2015-06-26 14:55:02.591 7961 AUDIT nova.compute.claims [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] disk limit not specified,
defaulting to unlimited

2015-06-26 14:55:02.606 7961 AUDIT nova.compute.claims [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Claim successful

2015-06-26 14:55:02.721 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5')

2015-06-26 14:55:02.836 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5')

2015-06-26 14:55:03.115 7961 INFO nova.virt.libvirt.driver [-]
[instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] Creating image

2015-06-26 14:55:03.118 7961 INFO nova.openstack.common.lockutils [-]
Created lock path: /var/lib/nova/instances/locks

2015-06-26 14:55:03.458 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5', 'compute5.siminn.is')

2015-06-26 14:55:04.088 7961 INFO nova.virt.disk.vfs.api [-] Unable to
import guestfsfalling back to VFSLocalFS

2015-06-26 14:55:04.363 7961 ERROR nova.compute.manager [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Instance failed to spawn

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Traceback (most recent call
last):

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2267,
in buildresources

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] yield resources

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2137,
in buildandruninstance

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c]
blockdeviceinfo=blockdeviceinfo)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
2620, in spawn

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] writetodisk=True)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
4159, in getguest_xml

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] context)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
3937, in getguest_config

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] flavor,
CONF.libvirt.virt_type)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 352,
in get_config

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] ("Unexpected viftype=%s")
% vif_type)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] NovaException: Unexpected
viftype=bindingfailed

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c]

Best regards

Yngvi


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Andreas
(IRC: scheuran)

responded Jun 29, 2015 by Andreas_Scheuring (6,240 points)   1 9 14
0 votes

Hi Yngvi,

Can you please send us the nova-cpu logs?

On Mon, Jun 29, 2015 at 12:28 PM, Andreas Scheuring <
scheuran@linux.vnet.ibm.com> wrote:

The issue seems to be related to a neutron missconfiguration.
--> Unexpected viftype=bindingfailed

Please have a look at your neutron server config file in the network
node(s) and the l2 agent config files (ovs?). You should find additional
information there.

If this doesn't help, please provide these log files, the neutron config
files and a brief description of how your nodes network are set up.

Andreas

On Fr, 2015-06-26 at 15:05 +0000, Yngvi Páll Þorfinnsson wrote:

Hi

Can someone please help on this matter?

I have installed and configured OpenStack(Juno) environment on
Ubuntu(14.04).

We have currently 1 controller node, 3 network nodes and 4 compute
nodes as well as 4 swift nodes.

I'm using OpenStack Networking (neutron).

I‘v recently introduced VLANs for tunnel-, mgmt- and external
networks.

When I try to create a instance, with this cmd:

nova boot --flavor m1.tiny --image cirros-0.3.3-x86_64 --nic
net-id=7a344656-815c-4116-b697-b52f9fdc6e4c --security-group default
--key-name demo-key demo-instance3

it fails. The status from nova list is :

root@controller2:/# nova list

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

| ID | Name | Status |
Task State | Power State | Networks |

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

| ca662fc0-2417-4da1-be2c-d6ccf90ed732 | demo-instance22 | ERROR | -
| NOSTATE | |

| 17d26ca3-f56c-4a87-ae0a-acfafea4838c | demo-instance30 | ERROR | -
| NOSTATE | demo-net=x.x.x.x |

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

This error apperas in the /var/log/syslog file on the computer node:

Jun 26 14:55:04 compute5 kernel: [ 2187.597951] nbd8: p1

Jun 26 14:55:04 compute5 kernel: [ 2187.668430] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668521] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668583] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668899] FAT-fs (nbd8): bogus
number of reserved sectors

Jun 26 14:55:04 compute5 kernel: [ 2187.668936] FAT-fs (nbd8): Can't
find a valid FAT filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.753989] block nbd8:
NBD_DISCONNECT

Jun 26 14:55:04 compute5 kernel: [ 2187.754056] block nbd8: Receive
control failed (result -32)

Jun 26 14:55:04 compute5 kernel: [ 2187.754161] block nbd8: queue
cleared

Also, this is logged on the computer node,
in /var/log/nova/nova-compute.log

2015-06-26 14:55:02.591 7961 AUDIT nova.compute.claims [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] disk limit not specified,
defaulting to unlimited

2015-06-26 14:55:02.606 7961 AUDIT nova.compute.claims [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Claim successful

2015-06-26 14:55:02.721 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5')

2015-06-26 14:55:02.836 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5')

2015-06-26 14:55:03.115 7961 INFO nova.virt.libvirt.driver [-]
[instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] Creating image

2015-06-26 14:55:03.118 7961 INFO nova.openstack.common.lockutils [-]
Created lock path: /var/lib/nova/instances/locks

2015-06-26 14:55:03.458 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5', 'compute5.siminn.is')

2015-06-26 14:55:04.088 7961 INFO nova.virt.disk.vfs.api [-] Unable to
import guestfsfalling back to VFSLocalFS

2015-06-26 14:55:04.363 7961 ERROR nova.compute.manager [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Instance failed to spawn

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Traceback (most recent call
last):

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2267,
in buildresources

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] yield resources

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2137,
in buildandruninstance

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c]
blockdeviceinfo=blockdeviceinfo)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
2620, in spawn

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] writetodisk=True)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
4159, in getguest_xml

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] context)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
3937, in getguest_config

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] flavor,
CONF.libvirt.virt_type)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 352,
in get_config

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] ("Unexpected viftype=%s")
% vif_type)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] NovaException: Unexpected
viftype=bindingfailed

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c]

Best regards

Yngvi


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Andreas
(IRC: scheuran)


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--

Thanks & Regards,
Abhishek
*Cloudbyte Inc. *


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
responded Jun 29, 2015 by Abhishek_Shrivastava (3,180 points)   2 7
0 votes

Hi Andreas

I'v attached those files from a network node:

Ml2conf.ini
Neutron.conf
L3
agent.ini
Nova-compute.log

I've setup 3 vlans on one interface and configured bonding
It works and I have good connection between the servers:

root@network2:/# cat /proc/net/vlan/config
VLAN Dev name | VLAN ID
Name-Type: VLANNAMETYPERAWPLUSVIDNO_PAD
bond0.48 | 48 | bond0
bond0.47 | 47 | bond0
bond0.45 | 45 | bond0

Tunnel network -> bond0.47
Mgmt network -> bond0.48
Extrenal network -> bond0.45

And when I check for bridges and ports on the network node:

root@network2:/# ovs-vsctl list-br
br-ex
br-int
br-tun

root@network2:/# ovs-vsctl list-ports br-ex
bond0.45
phy-br-ex
qg-eb22e091-62

best regards
Yngvi

-----Original Message-----
From: Andreas Scheuring [mailto:scheuran@linux.vnet.ibm.com]
Sent: 29. júní 2015 06:59
To: Yngvi Páll Þorfinnsson
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] error creating instance

The issue seems to be related to a neutron missconfiguration.
--> Unexpected viftype=bindingfailed

Please have a look at your neutron server config file in the network
node(s) and the l2 agent config files (ovs?). You should find additional information there.

If this doesn't help, please provide these log files, the neutron config files and a brief description of how your nodes network are set up.

Andreas

On Fr, 2015-06-26 at 15:05 +0000, Yngvi Páll Þorfinnsson wrote:
Hi

Can someone please help on this matter?

I have installed and configured OpenStack(Juno) environment on
Ubuntu(14.04).

We have currently 1 controller node, 3 network nodes and 4 compute
nodes as well as 4 swift nodes.

I'm using OpenStack Networking (neutron).

I‘v recently introduced VLANs for tunnel-, mgmt- and external
networks.

When I try to create a instance, with this cmd:

nova boot --flavor m1.tiny --image cirros-0.3.3-x86_64 --nic
net-id=7a344656-815c-4116-b697-b52f9fdc6e4c --security-group default
--key-name demo-key demo-instance3

it fails. The status from nova list is :

root@controller2:/# nova list

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

| ID | Name | Status |
Task State | Power State | Networks |

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

| ca662fc0-2417-4da1-be2c-d6ccf90ed732 | demo-instance22 | ERROR | -
| NOSTATE | |

| 17d26ca3-f56c-4a87-ae0a-acfafea4838c | demo-instance30 | ERROR | -
| NOSTATE | demo-net=x.x.x.x |

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

This error apperas in the /var/log/syslog file on the computer node:

Jun 26 14:55:04 compute5 kernel: [ 2187.597951] nbd8: p1

Jun 26 14:55:04 compute5 kernel: [ 2187.668430] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668521] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668583] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668899] FAT-fs (nbd8): bogus
number of reserved sectors

Jun 26 14:55:04 compute5 kernel: [ 2187.668936] FAT-fs (nbd8): Can't
find a valid FAT filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.753989] block nbd8:
NBD_DISCONNECT

Jun 26 14:55:04 compute5 kernel: [ 2187.754056] block nbd8: Receive
control failed (result -32)

Jun 26 14:55:04 compute5 kernel: [ 2187.754161] block nbd8: queue
cleared

Also, this is logged on the computer node, in
/var/log/nova/nova-compute.log

2015-06-26 14:55:02.591 7961 AUDIT nova.compute.claims [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] disk limit not specified,
defaulting to unlimited

2015-06-26 14:55:02.606 7961 AUDIT nova.compute.claims [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Claim successful

2015-06-26 14:55:02.721 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5')

2015-06-26 14:55:02.836 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5')

2015-06-26 14:55:03.115 7961 INFO nova.virt.libvirt.driver [-]
[instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] Creating image

2015-06-26 14:55:03.118 7961 INFO nova.openstack.common.lockutils [-]
Created lock path: /var/lib/nova/instances/locks

2015-06-26 14:55:03.458 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5', 'compute5.siminn.is')

2015-06-26 14:55:04.088 7961 INFO nova.virt.disk.vfs.api [-] Unable to
import guestfsfalling back to VFSLocalFS

2015-06-26 14:55:04.363 7961 ERROR nova.compute.manager [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Instance failed to spawn

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Traceback (most recent call
last):

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2267,
in buildresources

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] yield resources

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2137,
in buildandruninstance

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c]
blockdeviceinfo=blockdeviceinfo)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
2620, in spawn

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] writetodisk=True)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
4159, in getguest_xml

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] context)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
3937, in getguest_config

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] flavor,
CONF.libvirt.virt_type)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 352,
in get_config

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] ("Unexpected viftype=%s")
% vif_type)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] NovaException: Unexpected
viftype=bindingfailed

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c]

Best regards

Yngvi


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Andreas
(IRC: scheuran)


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

responded Jun 29, 2015 by Yngvi_Páll_Þorfinnss (3,100 points)   3 7
0 votes

The problem is same, the Unexpected viftype=bindingfailed because of
which the instance failed to swapn.

On Mon, Jun 29, 2015 at 2:42 PM, Yngvi Páll Þorfinnsson yngvith@siminn.is
wrote:

Hi Andreas

I'v attached those files from a network node:

Ml2conf.ini
Neutron.conf
L3
agent.ini
Nova-compute.log

I've setup 3 vlans on one interface and configured bonding
It works and I have good connection between the servers:

root@network2:/# cat /proc/net/vlan/config
VLAN Dev name | VLAN ID
Name-Type: VLANNAMETYPERAWPLUSVIDNO_PAD
bond0.48 | 48 | bond0
bond0.47 | 47 | bond0
bond0.45 | 45 | bond0

Tunnel network -> bond0.47
Mgmt network -> bond0.48
Extrenal network -> bond0.45

And when I check for bridges and ports on the network node:

root@network2:/# ovs-vsctl list-br
br-ex
br-int
br-tun

root@network2:/# ovs-vsctl list-ports br-ex
bond0.45
phy-br-ex
qg-eb22e091-62

best regards
Yngvi

-----Original Message-----
From: Andreas Scheuring [mailto:scheuran@linux.vnet.ibm.com]
Sent: 29. júní 2015 06:59
To: Yngvi Páll Þorfinnsson
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] error creating instance

The issue seems to be related to a neutron missconfiguration.
--> Unexpected viftype=bindingfailed

Please have a look at your neutron server config file in the network
node(s) and the l2 agent config files (ovs?). You should find additional
information there.

If this doesn't help, please provide these log files, the neutron config
files and a brief description of how your nodes network are set up.

Andreas

On Fr, 2015-06-26 at 15:05 +0000, Yngvi Páll Þorfinnsson wrote:

Hi

Can someone please help on this matter?

I have installed and configured OpenStack(Juno) environment on
Ubuntu(14.04).

We have currently 1 controller node, 3 network nodes and 4 compute
nodes as well as 4 swift nodes.

I'm using OpenStack Networking (neutron).

I‘v recently introduced VLANs for tunnel-, mgmt- and external
networks.

When I try to create a instance, with this cmd:

nova boot --flavor m1.tiny --image cirros-0.3.3-x86_64 --nic
net-id=7a344656-815c-4116-b697-b52f9fdc6e4c --security-group default
--key-name demo-key demo-instance3

it fails. The status from nova list is :

root@controller2:/# nova list

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

| ID | Name | Status |
Task State | Power State | Networks |

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

| ca662fc0-2417-4da1-be2c-d6ccf90ed732 | demo-instance22 | ERROR | -
| NOSTATE | |

| 17d26ca3-f56c-4a87-ae0a-acfafea4838c | demo-instance30 | ERROR | -
| NOSTATE | demo-net=x.x.x.x |

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

This error apperas in the /var/log/syslog file on the computer node:

Jun 26 14:55:04 compute5 kernel: [ 2187.597951] nbd8: p1

Jun 26 14:55:04 compute5 kernel: [ 2187.668430] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668521] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668583] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668899] FAT-fs (nbd8): bogus
number of reserved sectors

Jun 26 14:55:04 compute5 kernel: [ 2187.668936] FAT-fs (nbd8): Can't
find a valid FAT filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.753989] block nbd8:
NBD_DISCONNECT

Jun 26 14:55:04 compute5 kernel: [ 2187.754056] block nbd8: Receive
control failed (result -32)

Jun 26 14:55:04 compute5 kernel: [ 2187.754161] block nbd8: queue
cleared

Also, this is logged on the computer node, in
/var/log/nova/nova-compute.log

2015-06-26 14:55:02.591 7961 AUDIT nova.compute.claims [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] disk limit not specified,
defaulting to unlimited

2015-06-26 14:55:02.606 7961 AUDIT nova.compute.claims [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Claim successful

2015-06-26 14:55:02.721 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5')

2015-06-26 14:55:02.836 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5')

2015-06-26 14:55:03.115 7961 INFO nova.virt.libvirt.driver [-]
[instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] Creating image

2015-06-26 14:55:03.118 7961 INFO nova.openstack.common.lockutils [-]
Created lock path: /var/lib/nova/instances/locks

2015-06-26 14:55:03.458 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5', 'compute5.siminn.is')

2015-06-26 14:55:04.088 7961 INFO nova.virt.disk.vfs.api [-] Unable to
import guestfsfalling back to VFSLocalFS

2015-06-26 14:55:04.363 7961 ERROR nova.compute.manager [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Instance failed to spawn

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Traceback (most recent call
last):

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2267,
in buildresources

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] yield resources

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2137,
in buildandruninstance

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c]
blockdeviceinfo=blockdeviceinfo)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
2620, in spawn

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] writetodisk=True)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
4159, in getguest_xml

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] context)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
3937, in getguest_config

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] flavor,
CONF.libvirt.virt_type)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 352,
in get_config

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] ("Unexpected viftype=%s")
% vif_type)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] NovaException: Unexpected
viftype=bindingfailed

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c]

Best regards

Yngvi


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Andreas
(IRC: scheuran)


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--

Thanks & Regards,
Abhishek
*Cloudbyte Inc. *


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
responded Jun 29, 2015 by Abhishek_Shrivastava (3,180 points)   2 7
0 votes

Hi

I should add to this information,
I'm using VLANs on compute, network and swift nodes.

But not on the controller node.
I'm not sure if that causes problems ?

Best regards
Yngvi

Hi Andreas

I'v attached those files from a network node:

Ml2conf.ini
Neutron.conf
L3
agent.ini
Nova-compute.log

I've setup 3 vlans on one interface and configured bonding It works and I have good connection between the servers:

root@network2:/# cat /proc/net/vlan/config
VLAN Dev name | VLAN ID
Name-Type: VLANNAMETYPERAWPLUSVIDNO_PAD
bond0.48 | 48 | bond0
bond0.47 | 47 | bond0
bond0.45 | 45 | bond0

Tunnel network -> bond0.47
Mgmt network -> bond0.48
Extrenal network -> bond0.45

And when I check for bridges and ports on the network node:

root@network2:/# ovs-vsctl list-br
br-ex
br-int
br-tun

root@network2:/# ovs-vsctl list-ports br-ex
bond0.45
phy-br-ex
qg-eb22e091-62

best regards
Yngvi

-----Original Message-----
From: Andreas Scheuring [mailto:scheuran@linux.vnet.ibm.com]
Sent: 29. júní 2015 06:59
To: Yngvi Páll Þorfinnsson
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] error creating instance

The issue seems to be related to a neutron missconfiguration.
--> Unexpected viftype=bindingfailed

Please have a look at your neutron server config file in the network
node(s) and the l2 agent config files (ovs?). You should find additional information there.

If this doesn't help, please provide these log files, the neutron config files and a brief description of how your nodes network are set up.

Andreas

On Fr, 2015-06-26 at 15:05 +0000, Yngvi Páll Þorfinnsson wrote:
Hi

Can someone please help on this matter?

I have installed and configured OpenStack(Juno) environment on
Ubuntu(14.04).

We have currently 1 controller node, 3 network nodes and 4 compute
nodes as well as 4 swift nodes.

I'm using OpenStack Networking (neutron).

I‘v recently introduced VLANs for tunnel-, mgmt- and external
networks.

When I try to create a instance, with this cmd:

nova boot --flavor m1.tiny --image cirros-0.3.3-x86_64 --nic
net-id=7a344656-815c-4116-b697-b52f9fdc6e4c --security-group default
--key-name demo-key demo-instance3

it fails. The status from nova list is :

root@controller2:/# nova list

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

| ID | Name | Status |
Task State | Power State | Networks |

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

| ca662fc0-2417-4da1-be2c-d6ccf90ed732 | demo-instance22 | ERROR | -
| NOSTATE | |

| 17d26ca3-f56c-4a87-ae0a-acfafea4838c | demo-instance30 | ERROR | -
| NOSTATE | demo-net=x.x.x.x |

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

This error apperas in the /var/log/syslog file on the computer node:

Jun 26 14:55:04 compute5 kernel: [ 2187.597951] nbd8: p1

Jun 26 14:55:04 compute5 kernel: [ 2187.668430] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668521] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668583] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668899] FAT-fs (nbd8): bogus
number of reserved sectors

Jun 26 14:55:04 compute5 kernel: [ 2187.668936] FAT-fs (nbd8): Can't
find a valid FAT filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.753989] block nbd8:
NBD_DISCONNECT

Jun 26 14:55:04 compute5 kernel: [ 2187.754056] block nbd8: Receive
control failed (result -32)

Jun 26 14:55:04 compute5 kernel: [ 2187.754161] block nbd8: queue
cleared

Also, this is logged on the computer node, in
/var/log/nova/nova-compute.log

2015-06-26 14:55:02.591 7961 AUDIT nova.compute.claims [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] disk limit not specified,
defaulting to unlimited

2015-06-26 14:55:02.606 7961 AUDIT nova.compute.claims [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Claim successful

2015-06-26 14:55:02.721 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5')

2015-06-26 14:55:02.836 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5')

2015-06-26 14:55:03.115 7961 INFO nova.virt.libvirt.driver [-]
[instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] Creating image

2015-06-26 14:55:03.118 7961 INFO nova.openstack.common.lockutils [-]
Created lock path: /var/lib/nova/instances/locks

2015-06-26 14:55:03.458 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5', 'compute5.siminn.is')

2015-06-26 14:55:04.088 7961 INFO nova.virt.disk.vfs.api [-] Unable to
import guestfsfalling back to VFSLocalFS

2015-06-26 14:55:04.363 7961 ERROR nova.compute.manager [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Instance failed to spawn

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Traceback (most recent call
last):

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2267,
in buildresources

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] yield resources

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2137,
in buildandruninstance

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c]
blockdeviceinfo=blockdeviceinfo)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
2620, in spawn

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] writetodisk=True)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
4159, in getguest_xml

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] context)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
3937, in getguest_config

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] flavor,
CONF.libvirt.virt_type)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 352,
in get_config

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] ("Unexpected viftype=%s")
% vif_type)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] NovaException: Unexpected
viftype=bindingfailed

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c]

Best regards

Yngvi


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Andreas
(IRC: scheuran)


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
responded Jun 29, 2015 by Yngvi_Páll_Þorfinnss (3,100 points)   3 7
0 votes

Hi
Sorry for all this spamming.....
I have ERROR in log file
/var/log/nova-conductor.log
On the controller server.

2015-06-29 11:09:47.638 2326 ERROR nova.scheduler.utils [req-483ca3ce-c41b-4342-8f47-ef993ca03d85 None] [instance: 871c6af2-1673-4eb0-94a1-1ad07eb77ce5] Error from last host: compute5 (node compute5.siminn.is): [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2054, in dobuildandruninstance\n filterproperties)\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2185, in buildandruninstance\n instanceuuid=instance.uuid, reason=six.texttype(e))\n', u'RescheduledException: Build of instance 871c6af2-1673-4eb0-94a1-1ad07eb77ce5 was re-scheduled: Unexpected viftype=bindingfailed\n']
2015-06-29 11:09:47.661 2326 WARNING nova.scheduler.driver [req-483ca3ce-c41b-4342-8f47-ef993ca03d85 None] [instance: 871c6af2-1673-4eb0-94a1-1ad07eb77ce5] Setting instance to ERROR state.

Yngvi

-----Original Message-----
From: Yngvi Páll Þorfinnsson
Sent: 29. júní 2015 11:02
To: Andreas Scheuring
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] error creating instance

Hi

I should add to this information,
I'm using VLANs on compute, network and swift nodes.

But not on the controller node.
I'm not sure if that causes problems ?

Best regards
Yngvi

Hi Andreas

I'v attached those files from a network node:

Ml2conf.ini
Neutron.conf
L3
agent.ini
Nova-compute.log

I've setup 3 vlans on one interface and configured bonding It works and I have good connection between the servers:

root@network2:/# cat /proc/net/vlan/config
VLAN Dev name | VLAN ID
Name-Type: VLANNAMETYPERAWPLUSVIDNO_PAD
bond0.48 | 48 | bond0
bond0.47 | 47 | bond0
bond0.45 | 45 | bond0

Tunnel network -> bond0.47
Mgmt network -> bond0.48
Extrenal network -> bond0.45

And when I check for bridges and ports on the network node:

root@network2:/# ovs-vsctl list-br
br-ex
br-int
br-tun

root@network2:/# ovs-vsctl list-ports br-ex
bond0.45
phy-br-ex
qg-eb22e091-62

best regards
Yngvi

-----Original Message-----
From: Andreas Scheuring [mailto:scheuran@linux.vnet.ibm.com]
Sent: 29. júní 2015 06:59
To: Yngvi Páll Þorfinnsson
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] error creating instance

The issue seems to be related to a neutron missconfiguration.
--> Unexpected viftype=bindingfailed

Please have a look at your neutron server config file in the network
node(s) and the l2 agent config files (ovs?). You should find additional information there.

If this doesn't help, please provide these log files, the neutron config files and a brief description of how your nodes network are set up.

Andreas

On Fr, 2015-06-26 at 15:05 +0000, Yngvi Páll Þorfinnsson wrote:
Hi

Can someone please help on this matter?

I have installed and configured OpenStack(Juno) environment on
Ubuntu(14.04).

We have currently 1 controller node, 3 network nodes and 4 compute
nodes as well as 4 swift nodes.

I'm using OpenStack Networking (neutron).

I‘v recently introduced VLANs for tunnel-, mgmt- and external
networks.

When I try to create a instance, with this cmd:

nova boot --flavor m1.tiny --image cirros-0.3.3-x86_64 --nic
net-id=7a344656-815c-4116-b697-b52f9fdc6e4c --security-group default
--key-name demo-key demo-instance3

it fails. The status from nova list is :

root@controller2:/# nova list

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

| ID | Name | Status |
Task State | Power State | Networks |

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

| ca662fc0-2417-4da1-be2c-d6ccf90ed732 | demo-instance22 | ERROR | -
| NOSTATE | |

| 17d26ca3-f56c-4a87-ae0a-acfafea4838c | demo-instance30 | ERROR | -
| NOSTATE | demo-net=x.x.x.x |

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

This error apperas in the /var/log/syslog file on the computer node:

Jun 26 14:55:04 compute5 kernel: [ 2187.597951] nbd8: p1

Jun 26 14:55:04 compute5 kernel: [ 2187.668430] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668521] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668583] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668899] FAT-fs (nbd8): bogus
number of reserved sectors

Jun 26 14:55:04 compute5 kernel: [ 2187.668936] FAT-fs (nbd8): Can't
find a valid FAT filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.753989] block nbd8:
NBD_DISCONNECT

Jun 26 14:55:04 compute5 kernel: [ 2187.754056] block nbd8: Receive
control failed (result -32)

Jun 26 14:55:04 compute5 kernel: [ 2187.754161] block nbd8: queue
cleared

Also, this is logged on the computer node, in
/var/log/nova/nova-compute.log

2015-06-26 14:55:02.591 7961 AUDIT nova.compute.claims [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] disk limit not specified,
defaulting to unlimited

2015-06-26 14:55:02.606 7961 AUDIT nova.compute.claims [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Claim successful

2015-06-26 14:55:02.721 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5')

2015-06-26 14:55:02.836 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5')

2015-06-26 14:55:03.115 7961 INFO nova.virt.libvirt.driver [-]
[instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] Creating image

2015-06-26 14:55:03.118 7961 INFO nova.openstack.common.lockutils [-]
Created lock path: /var/lib/nova/instances/locks

2015-06-26 14:55:03.458 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5', 'compute5.siminn.is')

2015-06-26 14:55:04.088 7961 INFO nova.virt.disk.vfs.api [-] Unable to
import guestfsfalling back to VFSLocalFS

2015-06-26 14:55:04.363 7961 ERROR nova.compute.manager [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Instance failed to spawn

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Traceback (most recent call
last):

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2267,
in buildresources

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] yield resources

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2137,
in buildandruninstance

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c]
blockdeviceinfo=blockdeviceinfo)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
2620, in spawn

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] writetodisk=True)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
4159, in getguest_xml

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] context)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
3937, in getguest_config

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] flavor,
CONF.libvirt.virt_type)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 352,
in get_config

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] ("Unexpected viftype=%s")
% vif_type)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] NovaException: Unexpected
viftype=bindingfailed

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c]

Best regards

Yngvi


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Andreas
(IRC: scheuran)


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
responded Jun 29, 2015 by Yngvi_Páll_Þorfinnss (3,100 points)   3 7
0 votes

This message is a result of that some actions on the compute nodes
failed.

Could you please provide the log of the neutron-server as well? It
should provide additional information why the binding failed. You should
find it on the network (!!) node or on the controller node (!!). In
addition the log of the openvswitch agent of the compute node (!!) might
be helpful.

Your configuration looks fine - at least the one you posted. I assume
that this is the network node config. The same configuration has been
applied on all other nodes as well, right? If not, the ml2_conf file of
the compute node would be of interest.

Andreas

On Mo, 2015-06-29 at 11:13 +0000, Yngvi Páll Þorfinnsson wrote:
Hi
Sorry for all this spamming.....
I have ERROR in log file
/var/log/nova-conductor.log
On the controller server.

2015-06-29 11:09:47.638 2326 ERROR nova.scheduler.utils [req-483ca3ce-c41b-4342-8f47-ef993ca03d85 None] [instance: 871c6af2-1673-4eb0-94a1-1ad07eb77ce5] Error from last host: compute5 (node compute5.siminn.is): [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2054, in dobuildandruninstance\n filterproperties)\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2185, in buildandruninstance\n instanceuuid=instance.uuid, reason=six.texttype(e))\n', u'RescheduledException: Build of instance 871c6af2-1673-4eb0-94a1-1ad07eb77ce5 was re-scheduled: Unexpected viftype=bindingfailed\n']
2015-06-29 11:09:47.661 2326 WARNING nova.scheduler.driver [req-483ca3ce-c41b-4342-8f47-ef993ca03d85 None] [instance: 871c6af2-1673-4eb0-94a1-1ad07eb77ce5] Setting instance to ERROR state.

Yngvi

-----Original Message-----
From: Yngvi Páll Þorfinnsson
Sent: 29. júní 2015 11:02
To: Andreas Scheuring
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] error creating instance

Hi

I should add to this information,
I'm using VLANs on compute, network and swift nodes.

But not on the controller node.
I'm not sure if that causes problems ?

Best regards
Yngvi

Hi Andreas

I'v attached those files from a network node:

Ml2conf.ini
Neutron.conf
L3
agent.ini
Nova-compute.log

I've setup 3 vlans on one interface and configured bonding It works and I have good connection between the servers:

root@network2:/# cat /proc/net/vlan/config
VLAN Dev name | VLAN ID
Name-Type: VLANNAMETYPERAWPLUSVIDNO_PAD
bond0.48 | 48 | bond0
bond0.47 | 47 | bond0
bond0.45 | 45 | bond0

Tunnel network -> bond0.47
Mgmt network -> bond0.48
Extrenal network -> bond0.45

And when I check for bridges and ports on the network node:

root@network2:/# ovs-vsctl list-br
br-ex
br-int
br-tun

root@network2:/# ovs-vsctl list-ports br-ex
bond0.45
phy-br-ex
qg-eb22e091-62

best regards
Yngvi

-----Original Message-----
From: Andreas Scheuring [mailto:scheuran@linux.vnet.ibm.com]
Sent: 29. júní 2015 06:59
To: Yngvi Páll Þorfinnsson
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] error creating instance

The issue seems to be related to a neutron missconfiguration.
--> Unexpected viftype=bindingfailed

Please have a look at your neutron server config file in the network
node(s) and the l2 agent config files (ovs?). You should find additional information there.

If this doesn't help, please provide these log files, the neutron config files and a brief description of how your nodes network are set up.

Andreas

On Fr, 2015-06-26 at 15:05 +0000, Yngvi Páll Þorfinnsson wrote:

Hi

Can someone please help on this matter?

I have installed and configured OpenStack(Juno) environment on
Ubuntu(14.04).

We have currently 1 controller node, 3 network nodes and 4 compute
nodes as well as 4 swift nodes.

I'm using OpenStack Networking (neutron).

I‘v recently introduced VLANs for tunnel-, mgmt- and external
networks.

When I try to create a instance, with this cmd:

nova boot --flavor m1.tiny --image cirros-0.3.3-x86_64 --nic
net-id=7a344656-815c-4116-b697-b52f9fdc6e4c --security-group default
--key-name demo-key demo-instance3

it fails. The status from nova list is :

root@controller2:/# nova list

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

| ID | Name | Status |
Task State | Power State | Networks |

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

| ca662fc0-2417-4da1-be2c-d6ccf90ed732 | demo-instance22 | ERROR | -
| NOSTATE | |

| 17d26ca3-f56c-4a87-ae0a-acfafea4838c | demo-instance30 | ERROR | -
| NOSTATE | demo-net=x.x.x.x |

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

This error apperas in the /var/log/syslog file on the computer node:

Jun 26 14:55:04 compute5 kernel: [ 2187.597951] nbd8: p1

Jun 26 14:55:04 compute5 kernel: [ 2187.668430] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668521] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668583] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668899] FAT-fs (nbd8): bogus
number of reserved sectors

Jun 26 14:55:04 compute5 kernel: [ 2187.668936] FAT-fs (nbd8): Can't
find a valid FAT filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.753989] block nbd8:
NBD_DISCONNECT

Jun 26 14:55:04 compute5 kernel: [ 2187.754056] block nbd8: Receive
control failed (result -32)

Jun 26 14:55:04 compute5 kernel: [ 2187.754161] block nbd8: queue
cleared

Also, this is logged on the computer node, in
/var/log/nova/nova-compute.log

2015-06-26 14:55:02.591 7961 AUDIT nova.compute.claims [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] disk limit not specified,
defaulting to unlimited

2015-06-26 14:55:02.606 7961 AUDIT nova.compute.claims [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Claim successful

2015-06-26 14:55:02.721 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5')

2015-06-26 14:55:02.836 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5')

2015-06-26 14:55:03.115 7961 INFO nova.virt.libvirt.driver [-]
[instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] Creating image

2015-06-26 14:55:03.118 7961 INFO nova.openstack.common.lockutils [-]
Created lock path: /var/lib/nova/instances/locks

2015-06-26 14:55:03.458 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5', 'compute5.siminn.is')

2015-06-26 14:55:04.088 7961 INFO nova.virt.disk.vfs.api [-] Unable to
import guestfsfalling back to VFSLocalFS

2015-06-26 14:55:04.363 7961 ERROR nova.compute.manager [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Instance failed to spawn

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Traceback (most recent call
last):

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2267,
in buildresources

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] yield resources

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2137,
in buildandruninstance

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c]
blockdeviceinfo=blockdeviceinfo)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
2620, in spawn

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] writetodisk=True)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
4159, in getguest_xml

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] context)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
3937, in getguest_config

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] flavor,
CONF.libvirt.virt_type)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 352,
in get_config

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] ("Unexpected viftype=%s")
% vif_type)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] NovaException: Unexpected
viftype=bindingfailed

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c]

Best regards

Yngvi


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Andreas
(IRC: scheuran)


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Andreas
(IRC: scheuran)


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
responded Jun 29, 2015 by Andreas_Scheuring (6,240 points)   1 9 14
0 votes

Yes, that's correct, this was from the network node config.
Now, I've attached log file from the neutron server (controller node)
/var/log/neutron/server.log

I've attached the configuration file on the computer node:
/etc/neutron/plugins/ml2/ml2_conf.ini

It's not the same configuration file from server to server, no.
When going through the Juno Manual it seems it's different config ?
But this is maybe misunderstanding, I should deploy the ml2_conf.ini
from the network node, to the other servers?

Best regards
Yngvi

-----Original Message-----
From: Andreas Scheuring [mailto:scheuran@linux.vnet.ibm.com]
Sent: 29. júní 2015 11:17
To: Yngvi Páll Þorfinnsson
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] error creating instance

This message is a result of that some actions on the compute nodes failed.

Could you please provide the log of the neutron-server as well? It should provide additional information why the binding failed. You should find it on the network (!!) node or on the controller node (!!). In addition the log of the openvswitch agent of the compute node (!!) might be helpful.

Your configuration looks fine - at least the one you posted. I assume that this is the network node config. The same configuration has been applied on all other nodes as well, right? If not, the ml2_conf file of the compute node would be of interest.

Andreas

On Mo, 2015-06-29 at 11:13 +0000, Yngvi Páll Þorfinnsson wrote:
Hi
Sorry for all this spamming.....
I have ERROR in log file
/var/log/nova-conductor.log
On the controller server.

2015-06-29 11:09:47.638 2326 ERROR nova.scheduler.utils [req-483ca3ce-c41b-4342-8f47-ef993ca03d85 None] [instance: 871c6af2-1673-4eb0-94a1-1ad07eb77ce5] Error from last host: compute5 (node compute5.siminn.is): [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2054, in dobuildandruninstance\n filterproperties)\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2185, in buildandruninstance\n instanceuuid=instance.uuid, reason=six.texttype(e))\n', u'RescheduledException: Build of instance 871c6af2-1673-4eb0-94a1-1ad07eb77ce5 was re-scheduled: Unexpected viftype=bindingfailed\n']
2015-06-29 11:09:47.661 2326 WARNING nova.scheduler.driver [req-483ca3ce-c41b-4342-8f47-ef993ca03d85 None] [instance: 871c6af2-1673-4eb0-94a1-1ad07eb77ce5] Setting instance to ERROR state.

Yngvi

-----Original Message-----
From: Yngvi Páll Þorfinnsson
Sent: 29. júní 2015 11:02
To: Andreas Scheuring
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] error creating instance

Hi

I should add to this information,
I'm using VLANs on compute, network and swift nodes.

But not on the controller node.
I'm not sure if that causes problems ?

Best regards
Yngvi

Hi Andreas

I'v attached those files from a network node:

Ml2conf.ini
Neutron.conf
L3
agent.ini
Nova-compute.log

I've setup 3 vlans on one interface and configured bonding It works and I have good connection between the servers:

root@network2:/# cat /proc/net/vlan/config
VLAN Dev name | VLAN ID
Name-Type: VLANNAMETYPERAWPLUSVIDNO_PAD
bond0.48 | 48 | bond0
bond0.47 | 47 | bond0
bond0.45 | 45 | bond0

Tunnel network -> bond0.47
Mgmt network -> bond0.48
Extrenal network -> bond0.45

And when I check for bridges and ports on the network node:

root@network2:/# ovs-vsctl list-br
br-ex
br-int
br-tun

root@network2:/# ovs-vsctl list-ports br-ex
bond0.45
phy-br-ex
qg-eb22e091-62

best regards
Yngvi

-----Original Message-----
From: Andreas Scheuring [mailto:scheuran@linux.vnet.ibm.com]
Sent: 29. júní 2015 06:59
To: Yngvi Páll Þorfinnsson
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] error creating instance

The issue seems to be related to a neutron missconfiguration.
--> Unexpected viftype=bindingfailed

Please have a look at your neutron server config file in the network
node(s) and the l2 agent config files (ovs?). You should find additional information there.

If this doesn't help, please provide these log files, the neutron config files and a brief description of how your nodes network are set up.

Andreas

On Fr, 2015-06-26 at 15:05 +0000, Yngvi Páll Þorfinnsson wrote:

Hi

Can someone please help on this matter?

I have installed and configured OpenStack(Juno) environment on
Ubuntu(14.04).

We have currently 1 controller node, 3 network nodes and 4 compute
nodes as well as 4 swift nodes.

I'm using OpenStack Networking (neutron).

I‘v recently introduced VLANs for tunnel-, mgmt- and external
networks.

When I try to create a instance, with this cmd:

nova boot --flavor m1.tiny --image cirros-0.3.3-x86_64 --nic
net-id=7a344656-815c-4116-b697-b52f9fdc6e4c --security-group default
--key-name demo-key demo-instance3

it fails. The status from nova list is :

root@controller2:/# nova list

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

| ID | Name | Status |
Task State | Power State | Networks |

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

| ca662fc0-2417-4da1-be2c-d6ccf90ed732 | demo-instance22 | ERROR | -
| NOSTATE | |

| 17d26ca3-f56c-4a87-ae0a-acfafea4838c | demo-instance30 | ERROR | -
| NOSTATE | demo-net=x.x.x.x |

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

This error apperas in the /var/log/syslog file on the computer node:

Jun 26 14:55:04 compute5 kernel: [ 2187.597951] nbd8: p1

Jun 26 14:55:04 compute5 kernel: [ 2187.668430] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668521] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668583] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668899] FAT-fs (nbd8): bogus
number of reserved sectors

Jun 26 14:55:04 compute5 kernel: [ 2187.668936] FAT-fs (nbd8): Can't
find a valid FAT filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.753989] block nbd8:
NBD_DISCONNECT

Jun 26 14:55:04 compute5 kernel: [ 2187.754056] block nbd8: Receive
control failed (result -32)

Jun 26 14:55:04 compute5 kernel: [ 2187.754161] block nbd8: queue
cleared

Also, this is logged on the computer node, in
/var/log/nova/nova-compute.log

2015-06-26 14:55:02.591 7961 AUDIT nova.compute.claims [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] disk limit not specified,
defaulting to unlimited

2015-06-26 14:55:02.606 7961 AUDIT nova.compute.claims [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Claim successful

2015-06-26 14:55:02.721 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5')

2015-06-26 14:55:02.836 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5')

2015-06-26 14:55:03.115 7961 INFO nova.virt.libvirt.driver [-]
[instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] Creating image

2015-06-26 14:55:03.118 7961 INFO nova.openstack.common.lockutils
[-] Created lock path: /var/lib/nova/instances/locks

2015-06-26 14:55:03.458 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5',
'compute5.siminn.is')

2015-06-26 14:55:04.088 7961 INFO nova.virt.disk.vfs.api [-] Unable
to import guestfsfalling back to VFSLocalFS

2015-06-26 14:55:04.363 7961 ERROR nova.compute.manager [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Instance failed to spawn

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Traceback (most recent call
last):

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line
2267, in buildresources

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] yield resources

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line
2137, in buildandruninstance

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c]
blockdeviceinfo=blockdeviceinfo)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
2620, in spawn

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] writetodisk=True)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
4159, in getguest_xml

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] context)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
3937, in getguest_config

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] flavor,
CONF.libvirt.virt_type)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line
352, in get_config

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] ("Unexpected viftype=%s")
% vif_type)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] NovaException: Unexpected
viftype=bindingfailed

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c]

Best regards

Yngvi


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Andreas
(IRC: scheuran)


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Andreas
(IRC: scheuran)


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

responded Jun 29, 2015 by Yngvi_Páll_Þorfinnss (3,100 points)   3 7
0 votes

Hi,

I ran into a similar problem. Make sure that you include the

[ml2typevlan]
tenantnetworktype = vlan
networkvlanranges = physnet1:1501:1509

on your controller network (as the controller needs this info to make a proper decission on which VLAN IDs are available for
tenant networks).

On other trick that isn't mentioned in any documentation is:

Instead of symlinking /etc/neutron/plugins.ini -> /etc/neutron/plugins/ml2/ml2_conf.ini do it the other way around:
Keep your neutron plugin configuration centralized in /etc/neutron/plugin.ini and create one or two symlinks:

/etc/neutron/plugins/ml2/ml2conf.ini -> /etc/neutron/plugins.ini (on each host running a neutron service)
/etc/neutron/plugins/openvswitch/ovs
neutron_plugin.ini -> /etc/neutron/plugins.ini (on each host running neutron-openvswitch-agent)

Just make sure that /etc/neutron/plugins.ini keeps both ML2 and OpenVSwitch config options.

The whole trick works because Neutron services are started using the option "--config ". And it will only read the files
mentioned on the commandline / init script / systemd unit file.

Regards,

Uwe

Am 29.06.2015 um 13:01 schrieb Yngvi Páll Þorfinnsson:

Hi

I should add to this information,
I'm using VLANs on compute, network and swift nodes.

But not on the controller node.
I'm not sure if that causes problems ?

Best regards
Yngvi

Hi Andreas

I'v attached those files from a network node:

Ml2conf.ini
Neutron.conf
L3
agent.ini
Nova-compute.log

I've setup 3 vlans on one interface and configured bonding It works and I have good connection between the servers:

root@network2:/# cat /proc/net/vlan/config
VLAN Dev name | VLAN ID
Name-Type: VLANNAMETYPERAWPLUSVIDNO_PAD
bond0.48 | 48 | bond0
bond0.47 | 47 | bond0
bond0.45 | 45 | bond0

Tunnel network -> bond0.47
Mgmt network -> bond0.48
Extrenal network -> bond0.45

And when I check for bridges and ports on the network node:

root@network2:/# ovs-vsctl list-br
br-ex
br-int
br-tun

root@network2:/# ovs-vsctl list-ports br-ex
bond0.45
phy-br-ex
qg-eb22e091-62

best regards
Yngvi

-----Original Message-----
From: Andreas Scheuring [mailto:scheuran@linux.vnet.ibm.com]
Sent: 29. júní 2015 06:59
To: Yngvi Páll Þorfinnsson
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] error creating instance

The issue seems to be related to a neutron missconfiguration.
--> Unexpected viftype=bindingfailed

Please have a look at your neutron server config file in the network
node(s) and the l2 agent config files (ovs?). You should find additional information there.

If this doesn't help, please provide these log files, the neutron config files and a brief description of how your nodes network are set up.

Andreas

On Fr, 2015-06-26 at 15:05 +0000, Yngvi Páll Þorfinnsson wrote:

Hi

Can someone please help on this matter?

I have installed and configured OpenStack(Juno) environment on
Ubuntu(14.04).

We have currently 1 controller node, 3 network nodes and 4 compute
nodes as well as 4 swift nodes.

I'm using OpenStack Networking (neutron).

I‘v recently introduced VLANs for tunnel-, mgmt- and external
networks.

When I try to create a instance, with this cmd:

nova boot --flavor m1.tiny --image cirros-0.3.3-x86_64 --nic
net-id=7a344656-815c-4116-b697-b52f9fdc6e4c --security-group default
--key-name demo-key demo-instance3

it fails. The status from nova list is :

root@controller2:/# nova list

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

| ID | Name | Status |
Task State | Power State | Networks |

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

| ca662fc0-2417-4da1-be2c-d6ccf90ed732 | demo-instance22 | ERROR | -
| NOSTATE | |

| 17d26ca3-f56c-4a87-ae0a-acfafea4838c | demo-instance30 | ERROR | -
| NOSTATE | demo-net=x.x.x.x |

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

This error apperas in the /var/log/syslog file on the computer node:

Jun 26 14:55:04 compute5 kernel: [ 2187.597951] nbd8: p1

Jun 26 14:55:04 compute5 kernel: [ 2187.668430] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668521] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668583] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668899] FAT-fs (nbd8): bogus
number of reserved sectors

Jun 26 14:55:04 compute5 kernel: [ 2187.668936] FAT-fs (nbd8): Can't
find a valid FAT filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.753989] block nbd8:
NBD_DISCONNECT

Jun 26 14:55:04 compute5 kernel: [ 2187.754056] block nbd8: Receive
control failed (result -32)

Jun 26 14:55:04 compute5 kernel: [ 2187.754161] block nbd8: queue
cleared

Also, this is logged on the computer node, in
/var/log/nova/nova-compute.log

2015-06-26 14:55:02.591 7961 AUDIT nova.compute.claims [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] disk limit not specified,
defaulting to unlimited

2015-06-26 14:55:02.606 7961 AUDIT nova.compute.claims [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Claim successful

2015-06-26 14:55:02.721 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5')

2015-06-26 14:55:02.836 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5')

2015-06-26 14:55:03.115 7961 INFO nova.virt.libvirt.driver [-]
[instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] Creating image

2015-06-26 14:55:03.118 7961 INFO nova.openstack.common.lockutils [-]
Created lock path: /var/lib/nova/instances/locks

2015-06-26 14:55:03.458 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5', 'compute5.siminn.is')

2015-06-26 14:55:04.088 7961 INFO nova.virt.disk.vfs.api [-] Unable to
import guestfsfalling back to VFSLocalFS

2015-06-26 14:55:04.363 7961 ERROR nova.compute.manager [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Instance failed to spawn

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Traceback (most recent call
last):

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2267,
in buildresources

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] yield resources

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2137,
in buildandruninstance

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c]
blockdeviceinfo=blockdeviceinfo)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
2620, in spawn

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] writetodisk=True)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
4159, in getguest_xml

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] context)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
3937, in getguest_config

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] flavor,
CONF.libvirt.virt_type)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 352,
in get_config

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] ("Unexpected viftype=%s")
% vif_type)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] NovaException: Unexpected
viftype=bindingfailed

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c]

Best regards

Yngvi


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Andreas
(IRC: scheuran)


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
responded Jun 29, 2015 by Uwe_Sauter (2,580 points)   6 6
0 votes

Oh, and one other thing:

please do a

neutron agent-list

and for each entry with agent_type=="Open vSwitch agent" do a

neutron agent-show

and provide that information. This way we can see the actual running configuration…

Uwe

Am 29.06.2015 um 13:01 schrieb Yngvi Páll Þorfinnsson:
Hi

I should add to this information,
I'm using VLANs on compute, network and swift nodes.

But not on the controller node.
I'm not sure if that causes problems ?

Best regards
Yngvi

Hi Andreas

I'v attached those files from a network node:

Ml2conf.ini
Neutron.conf
L3
agent.ini
Nova-compute.log

I've setup 3 vlans on one interface and configured bonding It works and I have good connection between the servers:

root@network2:/# cat /proc/net/vlan/config
VLAN Dev name | VLAN ID
Name-Type: VLANNAMETYPERAWPLUSVIDNO_PAD
bond0.48 | 48 | bond0
bond0.47 | 47 | bond0
bond0.45 | 45 | bond0

Tunnel network -> bond0.47
Mgmt network -> bond0.48
Extrenal network -> bond0.45

And when I check for bridges and ports on the network node:

root@network2:/# ovs-vsctl list-br
br-ex
br-int
br-tun

root@network2:/# ovs-vsctl list-ports br-ex
bond0.45
phy-br-ex
qg-eb22e091-62

best regards
Yngvi

-----Original Message-----
From: Andreas Scheuring [mailto:scheuran@linux.vnet.ibm.com]
Sent: 29. júní 2015 06:59
To: Yngvi Páll Þorfinnsson
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] error creating instance

The issue seems to be related to a neutron missconfiguration.
--> Unexpected viftype=bindingfailed

Please have a look at your neutron server config file in the network
node(s) and the l2 agent config files (ovs?). You should find additional information there.

If this doesn't help, please provide these log files, the neutron config files and a brief description of how your nodes network are set up.

Andreas

On Fr, 2015-06-26 at 15:05 +0000, Yngvi Páll Þorfinnsson wrote:

Hi

Can someone please help on this matter?

I have installed and configured OpenStack(Juno) environment on
Ubuntu(14.04).

We have currently 1 controller node, 3 network nodes and 4 compute
nodes as well as 4 swift nodes.

I'm using OpenStack Networking (neutron).

I‘v recently introduced VLANs for tunnel-, mgmt- and external
networks.

When I try to create a instance, with this cmd:

nova boot --flavor m1.tiny --image cirros-0.3.3-x86_64 --nic
net-id=7a344656-815c-4116-b697-b52f9fdc6e4c --security-group default
--key-name demo-key demo-instance3

it fails. The status from nova list is :

root@controller2:/# nova list

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

| ID | Name | Status |
Task State | Power State | Networks |

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

| ca662fc0-2417-4da1-be2c-d6ccf90ed732 | demo-instance22 | ERROR | -
| NOSTATE | |

| 17d26ca3-f56c-4a87-ae0a-acfafea4838c | demo-instance30 | ERROR | -
| NOSTATE | demo-net=x.x.x.x |

+--------------------------------------+-----------------+--------+------------+-------------+-----------------------+

This error apperas in the /var/log/syslog file on the computer node:

Jun 26 14:55:04 compute5 kernel: [ 2187.597951] nbd8: p1

Jun 26 14:55:04 compute5 kernel: [ 2187.668430] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668521] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668583] EXT4-fs (nbd8): VFS:
Can't find ext4 filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.668899] FAT-fs (nbd8): bogus
number of reserved sectors

Jun 26 14:55:04 compute5 kernel: [ 2187.668936] FAT-fs (nbd8): Can't
find a valid FAT filesystem

Jun 26 14:55:04 compute5 kernel: [ 2187.753989] block nbd8:
NBD_DISCONNECT

Jun 26 14:55:04 compute5 kernel: [ 2187.754056] block nbd8: Receive
control failed (result -32)

Jun 26 14:55:04 compute5 kernel: [ 2187.754161] block nbd8: queue
cleared

Also, this is logged on the computer node, in
/var/log/nova/nova-compute.log

2015-06-26 14:55:02.591 7961 AUDIT nova.compute.claims [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] disk limit not specified,
defaulting to unlimited

2015-06-26 14:55:02.606 7961 AUDIT nova.compute.claims [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Claim successful

2015-06-26 14:55:02.721 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5')

2015-06-26 14:55:02.836 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5')

2015-06-26 14:55:03.115 7961 INFO nova.virt.libvirt.driver [-]
[instance: 17d26ca3-f56c-4a87-ae0a-acfafea4838c] Creating image

2015-06-26 14:55:03.118 7961 INFO nova.openstack.common.lockutils [-]
Created lock path: /var/lib/nova/instances/locks

2015-06-26 14:55:03.458 7961 INFO nova.scheduler.client.report [-]
Compute_service record updated for ('compute5', 'compute5.siminn.is')

2015-06-26 14:55:04.088 7961 INFO nova.virt.disk.vfs.api [-] Unable to
import guestfsfalling back to VFSLocalFS

2015-06-26 14:55:04.363 7961 ERROR nova.compute.manager [-] [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Instance failed to spawn

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] Traceback (most recent call
last):

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2267,
in buildresources

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] yield resources

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2137,
in buildandruninstance

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c]
blockdeviceinfo=blockdeviceinfo)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
2620, in spawn

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] writetodisk=True)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
4159, in getguest_xml

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] context)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line
3937, in getguest_config

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] flavor,
CONF.libvirt.virt_type)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 352,
in get_config

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] ("Unexpected viftype=%s")
% vif_type)

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c] NovaException: Unexpected
viftype=bindingfailed

2015-06-26 14:55:04.363 7961 TRACE nova.compute.manager [instance:
17d26ca3-f56c-4a87-ae0a-acfafea4838c]

Best regards

Yngvi


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Andreas
(IRC: scheuran)


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
responded Jun 29, 2015 by Uwe_Sauter (2,580 points)   6 6
...