>> (1) could you please provide which version of Neutron you are using? master branch I guess?
It's not latest master branch but latest promoted packages in RDO:
>> (3) from what you described, you stopped all 3 containers running l3 agent, which means you do not have any running l3 agents now, shouldn't this lead to dataplane downtime for sure?
In non-containerized environments, if everything is up and running and you stop l3 agents, dataplane remains working (namespaces are still there, ports are connected, flows installed, etc.). Obviously you'll lose control plane for L3 but that's expected. The scenario I'm describing is different since dataplane is lost as well which IMO it's a regression.
@Lujin:
>> (1) could you please provide which version of Neutron you are using? master branch I guess?
It's not latest master branch but latest promoted packages in RDO:
openstack- tripleo- common- 8.1.1-0. 20171130034833. 0e92cba. el7.centos. noarch tripleo- puppet- elements- 8.0.0-0. 20171127180031. cc2c715. el7.centos. noarch tripleo- ui-8.0. 1-0.20171129193 834.1e42711. el7.centos. noarch tripleo- common- containers- 8.1.1-0. 20171130034833. 0e92cba. el7.centos. noarch tripleo- validations- 8.0.1-0. 20171129140336. c1f2069. el7.centos. noarch tripleo- heat-templates- 8.0.0-0. 20171130031741. 4df242c. el7.centos. noarch tripleo- image-elements- 8.0.0-0. 20171118092222. 90b9a25. el7.centos. noarch kolla-5. 0.0-0.201711070 75441.61495b1. el7.centos. noarch
openstack-
openstack-
openstack-
openstack-
openstack-
openstack-
openstack-
()[root@ overcloud- controller- 2 /]# rpm -qa | grep neutron neutron- 12.0.0- 0.2017120614420 9.1ca38a1. el7.centos. noarch neutron- lbaas-12. 0.0-0.201712060 32035.0c76484. el7.centos. noarch neutron- lbaas-12. 0.0-0.201712060 32035.0c76484. el7.centos. noarch neutronclient- 6.5.0-0. 20171023215239. 355983d. el7.centos. noarch neutron- common- 12.0.0- 0.2017120614420 9.1ca38a1. el7.centos. noarch neutron- fwaas-12. 0.0-0.201712060 94459.b5b4491. el7.centos. noarch neutron- fwaas-12. 0.0-0.201712060 94459.b5b4491. el7.centos. noarch neutron- ml2-12. 0.0-0.201712061 44209.1ca38a1. el7.centos. noarch neutron- lib-1.11. 0-0.20171129185 804.ff5ee17. el7.centos. noarch neutron- 12.0.0- 0.2017120614420 9.1ca38a1. el7.centos. noarch
python-
python-
openstack-
python2-
openstack-
python-
openstack-
openstack-
python2-
openstack-
>> (2) i think you forgot to paste the references you mentioned in #1
Right:
[0] https:/ /bugs.launchpad .net/kolla/ +bug/1616268 /bugs.launchpad .net/tripleo/ +bug/1734333 /github. com/openstack/ tripleo- heat-templates/ commit/ 2e3a91f58bb48d4 e7ab88258fbd704 975cf1c79c
[1] https:/
[2] https:/
>> (3) from what you described, you stopped all 3 containers running l3 agent, which means you do not have any running l3 agents now, shouldn't this lead to dataplane downtime for sure?
In non-containerized environments, if everything is up and running and you stop l3 agents, dataplane remains working (namespaces are still there, ports are connected, flows installed, etc.). Obviously you'll lose control plane for L3 but that's expected. The scenario I'm describing is different since dataplane is lost as well which IMO it's a regression.
Thanks,
Daniel