After releasing Pike M3, we need to bump the metadata version
information for the next release with a -dev.
Change-Id: Ia4a3eb5aac638821ad1657f804f2e83a39a393e3
Current scenario004 is not executing tests related
to Neutron BGPVPN since an extra package containing
the Tempest plugin was added.
Change-Id: I67b548cfe2801a134a4d1a142f30bd2557420e9d
Signed-off-by: Ricardo Noriega <rnoriega@redhat.com>
since Idf8c65ef9bbc11cadea236f0b1a491a0f82bb84b
is merged in Tempest, no compute/resize_available
option supported. Instead,
compute-feature-enabled/resize is used
Change-Id: Ib64a8cd9dba76c0b9281008e6d97c8acee85dcc7
As part of the docs migration work[0] for Pike we need to switch to use the
openstackdocstheme.
[0]https://review.openstack.org/#/c/472275/
Change-Id: I30be0d11d9407efa3f04819083cf16ff0040734c
Pin reno version to reno!=2.0.0,!=2.3.1,>=1.8.0
Pin sphinx version to sphinx!=1.6.1,>=1.5.1
reno=2.3.1 and sphinx=1.6.1 break releasenotes and doc tests.
Change-Id: If91dab1bc911d0839401da88bfc97dd75dd13606
Note: This uses a different layout than what has been done until
now by moving service-specific configuration to it's own class.
Change-Id: Ie7def5893bfdd3313b0434777e926dd0b078a36f
We're coming up on the Pike M2 release and we need to prepare the
metadata.json and reno configuration for the release.
Change-Id: If31bc77bfca22a6513ed6c827a82e69ef67a1e97
Update the tox configuration to pull in the openstack
upper-constraints.txt when running releasenotes. This will
fix the releasenotes job that is currently failing due to
a new version of sphinx. Additionally this change includes
updates from puppet-modulesync-configs.
Change-Id: If6000030e51a2380121586e24ff69a4ca7caf4d2
After releasing Pike M1, we need to bump the metadata version
information for the next release with a -dev.
Change-Id: I9f6f7b9259802f88e737a171a3ec2de263c5711b
ec2-api has its own package for tests, so we need to deploy it in order
to run Tempest tests for ec2api.
Change-Id: I7596f9285449b7c7b2571dabb600b7ccae3f33d3
If we don't override the value, it means that tempest will attempt to
execute all tests from the suite, which may be not want we want. For
example, setups with no qos ml2 extension driver enabled may not want to
execute qos tests, since they will probably fail.
It's good practice for tempest/neutron to configure api extensions to
test explicitly in tempest.conf, especially in gate environment where
new tests may land that may break previously working gate because there
is more configuration needed to pass them, or because the plugin used
does not support the feature at all.
Change-Id: I31105600dfd5632ec4341b35ca3e8a13af3bb945
The parameter name used to enforce package state is inconsistent across
manifests and modules. I settle on package_ensure since it's already
widely used.
Change-Id: I1338c2eef3eae705b90f2fbaa97d0734c1a2bc05
Closes-Bug: #1668732
As cwd is used to specifiy from which directory we need to run
the command. Since workspace is created once tempest command is present
and tempest is coming from package and so can be executed from anywhere
from the system otherwise cwd is give error stating directory not found.
so, removing it.
Change-Id: Ia9e48d951e0f37e985e628b7a49401d75c9e4729