Override quantum services autostart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Critical
|
Andrey Korolyov |
Bug Description
Currently we have quantum agents autostart override in Ubuntu only for HA mode. We need to fix it to add override file for upstart and remove it after.
The discovery of error was the following:
deploy was successful, even VMs started and get IP. However, metadata service was inaccessible. When we logged in to the controller host, there was no l3-agent process running and no namespace qrouter-XXX.
RabbitMQ had following errors in logs:
=ERROR REPORT==== 3-Dec-2013:
closing AMQP connection <0.1239.0> (127.0.0.1:60060 -> 127.0.0.1:5672):
{channel0_
When l3-agent was restored, metadata service became accessible but returning 401 Authorized error. Restart of metadata fixed the issue.
So the issue happens because puppet changes config after service starts with old config (service starts automatically by upstart).
Changed in fuel: | |
assignee: | nobody → Andrey Korolyov (xdeller) |
description: | updated |
Changed in fuel: | |
status: | Triaged → Fix Committed |
Changed in fuel: | |
status: | Fix Committed → Fix Released |
This is ISO #89, simple Ubuntu deployment with Neutron VLAN mode.