[stable/train] neutron-tempest-plugin-designate-scenario-train fails with AttributeError: 'Manager' object has no attribute 'zones_client'

[Bernard Cafarelli]

This is kind of a follow-up to neutron-tempest-plugin jobs failing in https://bugs.launchpad.net/neutron/+bug/1948804 as I see that designate jobs all fail on train branch.

Recent backport example and relevant logs:
https://review.opendev.org/c/openstack/neutron/+/816518/
https://zuul.opendev.org/t/openstack/build/a6a1142368b742248be710f902f541f5

    Traceback (most recent call last):

      File "/opt/stack/tempest/tempest/test.py", line 181, in setUpClass
    raise value.with_traceback(trace)

      File "/opt/stack/tempest/tempest/test.py", line 171, in setUpClass
    cls.setup_clients()

      File "/opt/stack/tempest/.tox/tempest/lib/python3.6/site-packages/neutron_tempest_plugin/scenario/test_dns_integration.py", line 50, in setup_clients
    cls.dns_client = cls.os_tempest.zones_client

    AttributeError: 'Manager' object has no attribute 'zones_client'

I did not see it when testing the fix for 1948804 as DNM patch to run it did not trigger designate job

[Lajos Katona (lajos-katona)]

This patch causes the failure on older branches/jobs:
https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/800291

Not sure why it happens, perhaps we have to add openstack/designate-tempest-plugin as required project to train job....

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/817465

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/817465
Committed: https://opendev.org/openstack/neutron-tempest-plugin/commit/82cd7afa96a03d14660810889e4486cb6f560081
Submitter: "Zuul (22348)"
Branch: master

commit 82cd7afa96a03d14660810889e4486cb6f560081
Author: elajkat <email address hidden>
Date: Wed Nov 10 19:04:35 2021 +0100

    [train]: add designate-tempest-plugin as req

    Add designate-tempest-plugin to required-projects of
    neutron-tempest-plugin-designate-scenario-train and pin it to 0.7.0.
    This should avoid the client initialization issue bring in by [1].

    [1]: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/800291

    Change-Id: Ib58f0cf251b84c21db0f4b8defd213c770739134
    Closes-Bug: #1950346

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron-tempest-plugin 1.8.0 release.