| 2016-04-19 03:46:11 |
Nitish Krishna Kaveri |
bug |
|
|
added bug |
| 2016-04-19 03:46:30 |
Nitish Krishna Kaveri |
nominated for series |
|
juniperopenstack/trunk |
|
| 2016-04-19 03:46:30 |
Nitish Krishna Kaveri |
bug task added |
|
juniperopenstack/trunk |
|
| 2016-04-19 03:46:30 |
Nitish Krishna Kaveri |
nominated for series |
|
juniperopenstack/r3.0 |
|
| 2016-04-19 03:46:30 |
Nitish Krishna Kaveri |
bug task added |
|
juniperopenstack/r3.0 |
|
| 2016-04-19 03:46:35 |
Nitish Krishna Kaveri |
juniperopenstack/r3.0: importance |
Undecided |
Critical |
|
| 2016-04-19 03:46:37 |
Nitish Krishna Kaveri |
juniperopenstack/r3.0: assignee |
|
Nitish Krishna Kaveri (nitishk) |
|
| 2016-04-19 03:46:43 |
Nitish Krishna Kaveri |
juniperopenstack/r3.0: milestone |
|
r3.0.2.0 |
|
| 2016-04-19 03:47:43 |
Nitish Krishna Kaveri |
description |
In master branch, CI sanity has failed because of below check-in:
https://review.opencontrail.org/#/c/15523/
This has unearthed an existing bug in SM provisioning which caused service_provider to be set twice in neutron.conf
The reason for this is described below
Neutron DEFAULT config brings in two values for that key as seen below:
# --- Reference implementations ---
service_provider=LOADBALANCER:Haproxy:neutron.services.loadbalancer.drivers.haproxy.plugin_driver.HaproxyOnHostPluginDriver:default
service_provider=VPN:openswan:neutron.services.vpn.service_drivers.ipsec.IPsecVPNDriver:default
SM/Puppet uses augeas which sets BOTH of those keys to configured value.
When above check-in got merged it returned ALL values of the key from neutron.conf instead of previously returning a hard-coded value. Since it expects only one value, this causes neutron plugin to fail.
This was handled in fab by first deleting both keys and they setting once.
We are now doing same in SM. |
In master branch, CI sanity SM lite jobs have failed after below check-in got merged:
https://review.opencontrail.org/#/c/15523/
This has unearthed an existing bug in SM provisioning which caused service_provider to be set twice in neutron.conf
The reason for this is described below
Neutron DEFAULT config brings in two values for that key as seen below:
# --- Reference implementations ---
service_provider=LOADBALANCER:Haproxy:neutron.services.loadbalancer.drivers.haproxy.plugin_driver.HaproxyOnHostPluginDriver:default
service_provider=VPN:openswan:neutron.services.vpn.service_drivers.ipsec.IPsecVPNDriver:default
SM/Puppet uses Augeas which sets BOTH of those keys to configured value.
When above check-in got merged it returned ALL values of the key from neutron.conf instead of previously returning a hard-coded value. Since it expects only one value, this causes neutron plugin to fail.
This was handled in fab by first deleting both keys and they setting once.
We are now doing same in SM. |
|
| 2016-04-19 03:57:19 |
OpenContrail Admin |
juniperopenstack/trunk: status |
New |
In Progress |
|
| 2016-04-19 03:57:23 |
OpenContrail Admin |
juniperopenstack/r3.0: status |
New |
In Progress |
|
| 2016-04-19 13:55:41 |
OpenContrail Admin |
juniperopenstack/trunk: status |
In Progress |
Fix Committed |
|
| 2016-04-20 00:41:52 |
OpenContrail Admin |
juniperopenstack/r3.0: status |
In Progress |
Fix Committed |
|
