quantum-ovs-plugin service refresh after puppet install

[Daneyon Hansen]

quantum-ovs-plugin needs to be restarted after deploying Quantum networks using puppet manifests. Otherwise, networks appear as local instead of GRE or VLAN within Quantum.

[Mark T. Voelker (mvoelker)]

Edgar was unable to reproduce this. Daneyon is going to retry with the latest code. Shweta is also going to take a look.

[Daneyon Hansen (danehans)]

To reproduce:

1. Successfully deploy your Controller Node using COE Puppet manifests/modules.
2. Create quantum networks. Use this document for details: http://docs.openstack.org/trunk/openstack-network/admin/content/l3_workflow.html
3. You will see your tenant network get created with provider:network_type local instead of GRE:

root@control03:~# quantum net-create net1
Created a new network:
+---------------------------+--------------------------------------+
| Field | Value |
+---------------------------+--------------------------------------+
| admin_state_up | True |
| id | 78af2cde-cecc-447c-bf7d-0424862d898d |
| name | net1 |
| provider:network_type | local |
| provider:physical_network | |
| provider:segmentation_id | |
| router:external | False |
| shared | False |
| status | ACTIVE |
| subnets | |
| tenant_id | 6a6c12a1d6c144d595cccf4c688133c7 |
+---------------------------+--------------------------------------+

Even though the ovs_plugin.ini show the correct GRE configuration:

integration_bridge=br-int
tunnel_id_ranges=1:1000
network_vlan_ranges=default:1000:2000
enable_tunneling=True
bridge_mappings=default:br-ex
tunnel_bridge=br-tun
tenant_network_type=gre
local_ip=192.168.220.43

To fix the problem, I delete the qtm net, restart quantum-server and recreate. Now you will see the proper network type:

root@control03:~# service quantum-server restart
quantum-server stop/waiting
quantum-server start/running, process 8555

root@control03:~# service quantum-server status
quantum-server start/running, process 8555
root@control03:~# quantum net-list

root@control03:~# quantum net-create net1
Created a new network:
+---------------------------+--------------------------------------+
| Field | Value |
+---------------------------+--------------------------------------+
| admin_state_up | True |
| id | f1ff2488-a355-45f9-bfe0-d4a843bf4580 |
| name | net1 |
| provider:network_type | gre |
| provider:physical_network | |
| provider:segmentation_id | 1 |
| router:external | False |
| shared | False |
| status | ACTIVE |
| subnets | |
| tenant_id | 6a6c12a1d6c144d595cccf4c688133c7 |
+---------------------------+--------------------------------------+

[Shweta P (shweta-ap05)]

I am able to reproduce the bug. I am taking a look at the quantum service logs. The service comes up by using the default parameter settings. I am trying to identify why the config settings in the ovs_quantum_plugin.ini is not being picked up the first time quantum-service comes up.

[Shweta P (shweta-ap05)]

I do not need to explicitly restart the quantum service now. The networks created appear as GRE. Some other quantum/puppet related fix must have fixed this issue as well.

[Mark T. Voelker (mvoelker)]

Good to hear that @shweta-ap05 couldn't reproduce this any longer, but I'm loathe to close this until we have more confirmation since she doesn't actually know what fixed it. @danehans, are you still running into this?