Folsom l3 agent unable to connect to quantum service
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Invalid
|
High
|
Gary Kotton | ||
Folsom |
Fix Released
|
High
|
Gary Kotton |
Bug Description
If the quantum service and the l3 agent are on different hosts and the quantum service restarts then the l3 agent is unable to reconnect to the quantum service:
[root@dhcp-4-22 ~(keystone_admin)]$ tail /var/log/
headers=
File "/usr/lib/
headers=
File "/usr/lib/
self.
File "/usr/lib/
exception_
File "/usr/lib/
message=
QuantumClientEx
[root@dhcp-4-22 ~(keystone_admin)]$ tail /var/log/
headers=
File "/usr/lib/
headers=
File "/usr/lib/
self.
File "/usr/lib/
exception_
File "/usr/lib/
message=
QuantumClientEx
[root@dhcp-4-22 ~(keystone_admin)]$
This is only relevant to the stable folsom version
Changed in quantum: | |
assignee: | nobody → Gary Kotton (garyk) |
importance: | Undecided → High |
Changed in quantum: | |
status: | New → Fix Committed |
Changed in quantum: | |
status: | Fix Committed → Invalid |
tags: | removed: in-stable-folsom |
Fix proposed to branch: stable/folsom /review. openstack. org/24770
Review: https:/