Bug 1699566 - neutron_api container won't start when deploying with ovn driver
Summary: neutron_api container won't start when deploying with ovn driver
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tripleoclient
Version: 14.0 (Rocky)
Hardware: x86_64
OS: All
urgent
urgent
Target Milestone: z3
: 14.0 (Rocky)
Assignee: Rabi Mishra
QA Contact: Victor Voronkov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-13 17:52 UTC by David Hill
Modified: 2019-07-02 20:08 UTC (History)
12 users (show)

Fixed In Version: python-tripleoclient-10.6.1-0.20190303235859.ab72340.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-02 20:08:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
RDO 20245 0 None None None 2019-04-17 13:04:19 UTC
Red Hat Product Errata RHBA-2019:1672 0 None None None 2019-07-02 20:08:35 UTC

Description David Hill 2019-04-13 17:52:17 UTC
Description of problem:
neutron_api container won't start when deploying with ovn driver

2019-04-13 17:49:59.002 1 CRITICAL neutron.plugins.ml2.managers [-] The following mechanism drivers were not found: set(['ovn'])


Version-Release number of selected component (if applicable):
latest docker container images, latest osp14 

How reproducible:
Constantly

Steps to Reproduce:
1. Deploy osp14 with OVN
2.
3.

Actual results:
neutron_api don't start

Expected results:
Should start

Additional info:

Comment 1 David Hill 2019-04-13 17:57:15 UTC
[root@overcloud-controller-0 ~]# docker ps | egrep "ovn|neutron"
c2311a97d5fa        192.0.2.1:8787/rhosp14/openstack-ovn-controller:14.0-99             "kolla_start"            21 hours ago        Up 21 hours (healthy)                              ovn_controller
b9fb92967512        192.0.2.1:8787/rhosp14/openstack-neutron-server:14.0-98             "kolla_start"            21 hours ago        Restarting (1) 2 minutes ago                       neutron_api
c1e17f4d7e61        192.0.2.1:8787/rhosp14/openstack-nova-novncproxy:14.0-105           "kolla_start"            21 hours ago        Up 21 hours (healthy)                              nova_vnc_proxy
98e77a00246e        192.0.2.1:8787/rhosp14/openstack-ovn-northd:pcmklatest              "/bin/bash /usr/lo..."   21 hours ago        Up 21 hours                                        ovn-dbs-bundle-docker-0


[root@overcloud-controller-0 ~]# docker logs neutron_api | tail -4
+ echo 'Running command: '\''/usr/bin/neutron-server --config-file /usr/share/neutron/neutron-dist.conf --config-dir /usr/share/neutron/server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini --config-dir /etc/neutron/conf.d/common --config-dir /etc/neutron/conf.d/neutron-server --log-file=/var/log/neutron/server.log'\'''
+ exec /usr/bin/neutron-server --config-file /usr/share/neutron/neutron-dist.conf --config-dir /usr/share/neutron/server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini --config-dir /etc/neutron/conf.d/common --config-dir /etc/neutron/conf.d/neutron-server --log-file=/var/log/neutron/server.log
Running command: '/usr/bin/neutron-server --config-file /usr/share/neutron/neutron-dist.conf --config-dir /usr/share/neutron/server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini --config-dir /etc/neutron/conf.d/common --config-dir /etc/neutron/conf.d/neutron-server --log-file=/var/log/neutron/server.log'
The following mechanism drivers were not found: set(['ovn'])

Comment 3 David Hill 2019-04-14 13:27:25 UTC
This appears to be properly set here [1] so what are we missing ?

https://github.com/openstack/tripleo-common/blob/master/container-images/overcloud_containers.yaml.j2#L520

Comment 4 David Hill 2019-04-14 13:39:09 UTC
I think we're both still including overcloud_images.yaml that was previously generated... I guess this is what comes back biting us am I right ?

Comment 5 David Hill 2019-04-14 17:55:13 UTC
So as soon as we include the previously generated overcloud_images.yaml, neutron-onv is not used even if we included containers-prepare-parameter.yaml after.  This is more of a "we used to do that in osp13 and now it breaks everything in osp14" kind of issues.   Perhaps we should override the content of overcloud_images.yaml if containers-prepare-parameter.yaml is provided ?  This will probably cause issues with customer later on.

Comment 17 Victor Voronkov 2019-06-19 05:15:05 UTC
Verified on compose 2019-06-17.2

[heat-admin@controller-0 ~]$ sudo docker ps | egrep "ovn|neutron"
a6f63b7c3441        192.168.24.1:8787/rhosp14/openstack-ovn-controller:2019-06-17.2            "kolla_start"            15 hours ago        Up 15 hours (healthy)                       ovn_controller
97678facc413        192.168.24.1:8787/rhosp14/openstack-neutron-server-ovn:2019-06-17.2        "kolla_start"            15 hours ago        Up 15 hours (healthy)                       neutron_api
8584cc4ad217        192.168.24.1:8787/rhosp14/openstack-nova-novncproxy:2019-06-17.2           "kolla_start"            15 hours ago        Up 15 hours (healthy)                       nova_vnc_proxy
68f2674f23f1        192.168.24.1:8787/rhosp14/openstack-ovn-northd:pcmklatest                  "/bin/bash /usr/lo..."   15 hours ago        Up 15 hours                                 ovn-dbs-bundle-docker-0

Comment 20 errata-xmlrpc 2019-07-02 20:08:27 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:1672


Note You need to log in before you can comment on or make changes to this bug.