The issue is fixed only partially. tempest cleanup doesn't fail on NotImplemented error anymore and continues cleaning resources as expected, however, the return code of 'tempest cleanup --init-saved-state' is not appropriate and causes issues from automation perspective. This return code issue is tracked separately here https://bugzilla.redhat.com/show_bug.cgi?id=1737757
Tested with:
- package with the bug (openstack-tempest-19.0.0-4.el7ost)
- package with the fix (openstack-tempest-19.0.0-5.el7ost)
When tested with the package with the fix the bug was not reproduced as shown in the attached log file (bug_1722147.log).
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2019:3747