pytest-metadata plugin not being loaded in tox jobs

[Rafael Castillo]

A recent[1] release of pytest-metadata contains a change that causes the plugin to not be loaded by pytest. This is causing upstream tripleo molecule jobs to fail, as pytest-molecule depends on pytest-metadata.

Example failing job:
https://8afd41f5af3be665c38d-3116a0348a09f232bd7a29bf558c39ea.ssl.cf5.rackcdn.com/834611/1/gate/openstack-tox-molecule/c85e27b/job-output.txt

[1] https://pypi.org/project/pytest-metadata/2.0.0/

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/tripleo-quickstart-extras/+/834781

[Rafael Castillo (rafaelcastillo)]

Upstream library report: https://github.com/pytest-dev/pytest-metadata/issues/40

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/tripleo-quickstart-extras/+/834781
Committed: https://opendev.org/openstack/tripleo-quickstart-extras/commit/b8aec1e33dc8ef4eb5c1ca2acdc2baf02f0ac203
Submitter: "Zuul (22348)"
Branch: master

commit b8aec1e33dc8ef4eb5c1ca2acdc2baf02f0ac203
Author: Rafael Castillo <email address hidden>
Date: Tue Mar 22 12:24:31 2022 -0700

    Constrain pytest-metadata version

    pytest-metadata 2.0.0 contains a change that causes the plugin to not be
    loaded by pytest, breaking pytest-molecule.

    Closes-Bug: #1965979

    Change-Id: I76bfbbaa22e79df6b35d7bc01da7b1f95c1e2d48

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/tripleo-quickstart-extras/+/835513

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/tripleo-quickstart-extras/+/835513
Committed: https://opendev.org/openstack/tripleo-quickstart-extras/commit/bba48213514ba608eed164fd75840e5aae8f5f45
Submitter: "Zuul (22348)"
Branch: master

commit bba48213514ba608eed164fd75840e5aae8f5f45
Author: Rafael Castillo <email address hidden>
Date: Mon Mar 28 13:26:14 2022 -0700

    Upgrade pytest-metadata

    Following up on I76bfbbaa22e79df6b35d7bc01da7b1f95c1e2d48, upstream
    pytest-metadata has fixed the bug we were hitting[1] in version 2.0.1.

    [1] https://github.com/pytest-dev/pytest-metadata/issues/40
    Related-Bug: #1965979

    Change-Id: Ie3e43505b6868a3161e5c9481fa5a87ce733af50