Incorrect DVR resource registry deploys RPM based L3 and metadata agents

Bug #1779834 reported by Daniel Alvarez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Brent Eagles

Bug Description

Description of problem:

environments/neutron-ovs-dvr.yaml resource registry contains:

OS::TripleO::Services::ComputeNeutronL3Agent: ../puppet/services/neutron-l3-compute-dvr.yaml

This deploys RPM-based Neutron l3-agent on the compute node instead of containers during a new deploy with OVS DVR enabled.

It should point to:

/usr/share/openstack-tripleo-heat-templates/docker/services/neutron-l3.yaml

1. Deploy overcloud with DVR enabled on compute nodes
2. ssh to compute node and as root run:
3. docker ps -f name=neutron*
4. systemctl list-units | grep neutron
5. ps -ef | grep neutron

Actual results:

L3 agent process running outside a container managed by systemd

Revision history for this message
Brent Eagles (beagles) wrote :

This should have been addressed by https://review.openstack.org/#/c/537931/

Revision history for this message
Daniel Alvarez (dalvarezs) wrote :

Addressed by https://review.openstack.org/#/c/567813/
in stable/queens too...

Revision history for this message
Daniel Alvarez (dalvarezs) wrote :

Ack Brent thanks!

Changed in tripleo:
milestone: none → rocky-3
importance: Undecided → High
status: New → In Progress
assignee: nobody → Brent Eagles (beagles)
Brent Eagles (beagles)
Changed in tripleo:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.