octavia should be in VM or disabe enable-local-dhcp-and-metadata
Bug #1824581 reported by
Narinder Gupta
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Neutron Open vSwitch Charm |
Triaged
|
Medium
|
Unassigned | ||
OpenStack Octavia Charm |
Invalid
|
Undecided
|
Unassigned |
Bug Description
In openstack deployment if we enabled octavia in lxd containers and enable enable-
Scenario:
Deploy openstack with octavia in container with enable-
We saw neutron created the dhcp on the octavia units which causes dhcp agents not to respond.
Solution:
1) do not enable enable-
2) convert the containers into VM.
Discussion is required and appropriate action has to be taken in this regard.
tags: | added: field-high |
To post a comment you must log in.
The ``neutron- openvswitch` ` charm needs to learn to deal with being deployed in a container differently than if it is on bare metal/in a VM.
As a workaround you can deploy a separate instance of ``neutron- openvswitch` ` application in your Juju model for use with Octavia. That will let you set up the neutron-openvswitch application used on metal as you see fit without impacting the octavia units.