I faced a bug in latest nova network:
[root@host awasilyev]# /usr/bin/nova-manage network create novanetwork 172.26.0.0/24 --vlan 500
[root@host awasilyev]# /usr/bin/nova-manage network create novanetwork 172.26.1.0/24 --vlan 501
[root@host awasilyev]# /usr/bin/nova-manage network create novanetwork 172.26.2.0/24 --vlan 502
[root@host awasilyev]# nova-manage network list
id IPv4 IPv6 start address DNS1 DNS2 VlanID project uuid
64 172.26.0.0/24 None 172.26.0.3 8.8.4.4 None 500 None 225c8cbf-89bb-4171-b405-0047012a7803
65 172.26.1.0/24 None 172.26.1.3 8.8.4.4 None 502 None d461b285-d9c6-4a8c-ae39-5a657bb5926a
66 172.26.2.0/24 None 172.26.2.3 8.8.4.4 None 504 None 4c5a5d5b-24c8-4833-8bd0-6dcca11acb68
I try to create 3 networks, specifying exact vlan number for each network. But nova-manage creates networks using wrong vlan id's.
My previous openstack install (it was 3-4 monthes ago) does not have this bug.
There is a bug in the /usr/lib/ python2. 6/site- packages/ nova/network/ manager. py "vlan_start" ] = kwargs. get("vlan_ start") or CONF.vlan_start
on line 1066 'vlan_start' used as hash key:
kwargs[
than passing kwargs as argument: create_ networks( context, **kwargs)
return self._do_
But in the _do_create_networks (line 1188):
vlan = kwargs.get('vlan', None)
'vlan' used instead of 'vlan_start'!
As we can see on line 498 in /usr/lib/ python2. 6/site- packages/ nova/cmd/ manage. py, '--vlan' argument going to the 'vlan_start' variable, not 'vlan'.