Red Hat provides support for the Tempest framework and any supplied tests. In practice this means that Red Hat will ensure that Tempest is working properly. When Tempest is working properly a customer may still have a Failed test - this is not a defect in Tempest. In fact, this likely means that Tempest is working properly.
Red Hat suggests that customers do not deploy to production until they have successfully run Tempest and passed the provided tests. Is is a Red Hat Best Practice to establish a baseline of successful tests prior to deploying to production.
Red Hat may be able to provide generic guidance on why a test is failing, but it is the responsibility of the customer to determine why their code is causing a Tempest failure. If Tempest was previously returned success and is now reporting failure after no significant changes were made, then Red Hat may want to investigate this with the customer.
Tempest is designed to work with the current release of Red Hat OpenStack Platform. Using Tempest with older Red Hat Openstack Platform releases may be possible - please review the product documentation to understand the limits.
Tempest is designed and optimized for use with Red Hat OpenStack Platform director-based installations. Tempest may not work with deployments installed using different methods. Red Hat will offer commercially-reasonable support in these situations but cannot guarantee full functionality.