| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Actually attach_detach_volume must be skipped because the device name
ain't reliable and that's using a hard-coded device name in config.
This test should just get the device info after the attach and use
that rather than the hard-coded config option in Tempest that ain't
likely to work - the test should have been written more dynamically.
However, set volume device name to "vdc" since "vdb" is used for config
drive when force_config_drive=True is in action.
Change-Id: Ic70de93a609df932c7749a94f71505e927df1b79
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
Refstack is the OpenStack project that provides the tooling
to run the approved specific tempest test cases (Defcore guidelines)
by the Interop working group and by the OpenStack board
for OpenStack certification purposes.
For more info: https://refstack.openstack.org/
This adds the possibility for a Functest user to run this list
of tempest test cases by just issuing the command:
functest testcase run tempest_defcore
The test will be run on daily loops with the scenario nosdn-nofeature
on any installer.
Change-Id: I920b2a44cff418116008fdf514425e69dc959412
Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
|
|
JIRA: FUNCTEST-579
Change-Id: Iaa545db70bfb76770df0a3d17871e29ce518ff2d
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
|
Michael Polenchuk
jose.lausuch
Morgan Richomme