Dropping lower constraints testing

We facing errors related to the new pip resolver, this
topic was discussed on the ML and QA team proposed to
to test lower-constraints [1].

I propose to drop this test because the complexity and recurring pain needed
to maintain that now exceeds the benefits provided by this mechanismes.

Conflicts:
  .zuul.yaml

NOTE(stephenfin): Conflicts are due to different base jobs between
stable branches.

[1] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019390.html

Change-Id: Icd090cf8a36fa560bf7b0c67d0e1c4923c221c65
(cherry picked from commit a53ec14ee073cb69e876c4ee29e10ba65b438076)
(cherry picked from commit 1c0062c6e9125fd9060f08d2d3966d2b4af254e4)

1 files changed, 0 insertions, 1 deletions

diff --git a/.zuul.yaml b/.zuul.yaml
index 2c16442..0a7246b 100644
--- a/.zuul.yaml
+++ b/.zuul.yaml
@@ -2,7 +2,6 @@
     templates:
       - check-requirements
       - lib-forward-testing-python3
-      - openstack-lower-constraints-jobs
       - openstack-python3-victoria-jobs
       - periodic-stable-jobs
       - publish-openstack-docs-pti