ovn service agent lost for 20.04 + Ussuri deployment
Bug #2070332 reported by
Zhanglei Mao
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
charm-ovn-chassis |
New
|
Undecided
|
Unassigned |
Bug Description
In my all 4 deployments, one of host was not listed in "openstack network agent list" and launch VM on this host would fail, the most related effor info is:
Error executing command: ovsdbapp.
find Chassis_Private with name=nc7.maas
The lost host was random and to redeploy after remove this node can fix.
ovn-chassis: #pure ovn nodes interface- mappings: br-provider:bond1 bridge- mappings: physnet1: br-provider physnet2: br-provider chassis- as-gw: True dpdk-bond- config: ":balance- tcp:active: fast" #default&recommend bridge- mappings: physnet2: br-provider interface- mappings: br-provider: dpdk-bond1 bond-mappings: >
dpdk-bond1: xxxx # hiddened socket- cores: 2 #charm default is 1 per NUMA socket- memory: 2048 #charm default is 1G per NUMA;
bindings:
? ''
: oam-space
certificates: internal-space
data: oam-space
channel: 22.03/stable
charm: ovn-chassis
options:
bridge-
ovn-
enable-dpdk: False
prefer-
-----------
ovn-chassis-dpdk: #for dpdk+ovn nodes
bindings:
? ''
: oam-space
certificates: internal-space
data: oam-space
channel: 22.03/stable
charm: ovn-chassis
options:
enable-dpdk: True
#
ovn-
bridge-
dpdk-
dpdk-driver: vfio-pci #
dpdk-
dpdk-