Compute node failing with Designate enabled
Bug #1811134 reported by
Ben Nemec
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Ben Nemec |
Bug Description
I just tried to deploy Designate locally on a two node virt environment and the compute node failed configuration. I'm not sure why this just started happening, but it looks like the problem is that we're including the neutron::designate class in the base neutron manifest, when in reality it only needs to be in neutron-server (the service that actually uses those settings). Including it for neutron-ovs-agent on the compute node causes configuration to fail because that node doesn't have the necessary designate hieradata.
I've already tested a fix locally and will push it for review in a moment.
Changed in tripleo: | |
milestone: | stein-2 → stein-3 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/629645
Review: https:/