Neutron role fails to properly disable neutron agents

Bug #1688014 reported by Michael Craft on 2017-05-03
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-ansible
Low
Unassigned

Bug Description

When using a different neutron_plugin_type: nuage for example, the play still leaves the l3 agent enabled. From what I gather with this previous change https://github.com/openstack/openstack-ansible-os_neutron/blob/master/releasenotes/notes/neutron-agent-dynamic-enable-47f0c709ef0dfe55.yaml it should only require the operator to change the one line and not have to do additional overrides.

This looks like it's due to the following being set.

neutron_plugin_base:
  - router
  - metering

and here is the logic that does the match and keeps the agent enabled that causes the play to fail.

neutron_l3: "{% if 'router' in neutron_plugin_base or 'neutron.services.l3_router.l3_router_plugin.L3RouterPlugin' in neutron_plugin_base or 'df-l3' in neutron_plugin_base %}True{% else %}False{% endif %}"

By doing an override and removing - router the play runs as expected.

tags: added: agents neutron nuage

We can indeed improve our documentation, or alternatively, make the code smarter.

Changed in openstack-ansible:
status: New → Confirmed
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers