Tempest Exits Prematurely With Return Code of Zero

Solution In Progress - Updated -

Issue

  • The tests test_shelve_unshelve_server and test_shelve_shelved_server cause Tempest to exit prematurely, but with a return code of 0. Most automated testing systems would assume all tests were passed based on a successful return code. The problem is compounded when running tests concurrently, as the amount of tests completed before exiting will vary. Concurrent testing is the default behavior.

Environment

  • Red Hat Openstack Platform 13

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content