Description of problem: enable_tempest in undercloud.conf seems to do nothing . I'm not sure if it's a documentation leftover and behavior change here or if it's a bug but I'm following that documentation and I'm still wondering why is there still manual steps for configuring any of that. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Install undercloud with enable_tempest = true 2. 3. Actual results: Does nothing Expected results: Does everything Additional info: Perhaps we should have a proper discussion here about the workflow required to install the test-suite. There're too many manual steps here.
Hello David, On doing enable_tempest= true in undercloud.conf, then during undercloud install phase, tempest container will be available there. We can check whether tempest container is there or not using $ sudo docker images | grep tempest. The tempest container contains openstack-tempest, python-tempestconf and all the required tempest plugins in that container. If user wants to run tempest using tempest container, then they can consume it manually. Here we have documented the steps: https://docs.openstack.org/tripleo-docs/latest/install/basic_deployment/tempest.html#running-containerized-tempest-manually There is already a bug for tempest doc update for RHOS-13: https://bugzilla.redhat.com/show_bug.cgi?id=1574931. We will soon update the same for RHOS-14. Thanks, Chandan Kumar
This Release is retired. If this bug is still relevant, please reopen and retarget to an open release.