I think we may also want to bring this up in a cross-project session at the PTG. We are definitely to blame for some of the instability, but towards the end of this cycle I have noticed lots of issues with HTTPS connection errors, etc that don't seem to be related to Neutron at all. The squad team will have to have members from other projects. :)
On Wed, Jan 25, 2017 at 10:29 AM, Ihar Hrachyshka <ihrac...@redhat.com> wrote: > On Tue, Jan 24, 2017 at 12:26 PM, Morales, Victor > <victor.mora...@intel.com> wrote: > > Given the latest issues related with the memory consumption[1] in CI > jobs, I’m just wondering if you have a plan to deal and/or improve it in > Neutron. > > AFAIU the root cause is still not clear, and we don't know if it's > Neutron or job setup that triggers the OOM. I think we all see that > the gate is not healthy lately (it's not just tempest, functional > failure rate is also pretty bad). We need a squad team with clear > ownership for failure tracking to get back to normal. > > Ihar > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
