openvswitch-agent unable to start because of timeout talking to ovsdb
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Neutron Gateway Charm |
Fix Released
|
Low
|
Felipe Reyes | ||
OpenStack Neutron Open vSwitch Charm |
Invalid
|
Undecided
|
Unassigned |
Bug Description
On a scaled out production deployment, we have encountered an issue were openvswitch-switch service was not able to start because the ovsdb query is exceeding the default 10 seconds allotted.
019-10-24 19:48:06.748 1144752 DEBUG ovsdbapp.
2019-10-24 19:48:06.753 1144752 ERROR ovsdbapp.
2019-10-24 19:48:06.753 1144752 ERROR ovsdbapp.
2019-10-24 19:48:06.753 1144752 ERROR ovsdbapp.
2019-10-24 19:48:06.753 1144752 ERROR ovsdbapp.
2019-10-24 19:48:06.753 1144752 ERROR ovsdbapp.
2019-10-24 19:48:06.753 1144752 ERROR ovsdbapp.
2019-10-24 19:48:06.753 1144752 ERROR ovsdbapp.
2019-10-24 19:48:06.753 1144752 ERROR ovsdbapp.
2019-10-24 19:48:06.753 1144752 ERROR ovsdbapp.
2019-10-24 19:48:06.753 1144752 ERROR ovsdbapp.
2019-10-24 19:48:06.753 1144752 ERROR ovsdbapp.
2019-10-24 19:48:06.753 1144752 ERROR ovsdbapp.
2019-10-24 19:48:06.753 1144752 ERROR ovsdbapp.
2019-10-24 19:48:06.753 1144752 ERROR ovsdbapp.
2019-10-24 19:48:06.754 1144752 ERROR neutron.
The issue was resolved by editing /etc/neutron/
If nothing else, this default should be set higher but we also expect that this should be tunable via charm config.
Changed in charm-neutron-openvswitch: | |
status: | New → Invalid |
Changed in charm-neutron-gateway: | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in charm-neutron-gateway: | |
assignee: | nobody → Felipe Reyes (freyes) |
Changed in charm-neutron-gateway: | |
milestone: | none → 20.01 |
Changed in charm-neutron-gateway: | |
status: | Fix Committed → Fix Released |
I think this may actually belong under neutron-gateway
The unit in question was running a charmed neutron-gateway 12.0.5 charm version 262.
We will need a back port for this fix.