Hide Forgot
Description of problem: The Tempest config script depends on the inputs provided by tripleo, tempest usually assumes a feature is available in order not miss real failures. Version-Release number of selected component (if applicable): openstack-tripleo.noarch 0.0.1-0.20160916135259.4de13b3.el7ost openstack-tripleo-common.noarch 5.2.1-0.20160930023248.848ec90.el7ost openstack-tripleo-heat-templates.noarch openstack-tripleo-image-elements.noarch openstack-tripleo-puppet-elements.noarch openstack-tripleo-ui.noarch 1.0.3-0.20160929175454.f7297c3.el7ost puppet-tripleo.noarch 5.2.0-1.el7ost @rhelosp-10.0-puddle python-tripleoclient.noarch 5.2.0-1.el7ost @rhelosp-10.0-puddle How reproducible: always Steps to Reproduce: default setup Actual results: tempest-deployer-input.conf: .... [volume-feature-enabled] bootable = true ..... Expected results: in addition [volume-feature-enabled] backup=false Additional info: The backup feature can be enabled by: https://github.com/openstack/tripleo-heat-templates/blob/master/environments/cinder-backup.yaml in this case the 'backup' must be true. The tempest-deployer-input.conf usually used in a similar way: /usr/share/openstack-tempest-*/tools/config_tempest.py --create --deployer-input $HOME/tempest-deployer-input.conf --out $HOME/tempest/etc/tempest.conf --debug identity.uri "http://$ENDPOINT_IP:35357/v2.0" identity.admin_password "$OS_PASSWORD" object-storage.operator_role SwiftOperator tempest-deployer-input.conf created by the 'openstack overcloud deploy' . The deployer input.conf requested via : https://bugzilla.redhat.com/show_bug.cgi?id=1230840
this is handled by python-tripleoclient, moving to DFG:Workflows
This is specific to the tripleoclient code and not to anything dealing with workflows. Sending to DFG:UI for further disposition.
Sounds like this is the same problem than bug 1484419, just for a different component. At this point this probably needs to be made into an RFE to make tripleo client more intelligent when creating the Tempest file.
*** This bug has been marked as a duplicate of bug 1484419 ***