The api documentation is now published on docs.openstack.org instead
of developer.openstack.org. Update all links that are changed to the
new location.
Note that redirects will be set up as well but let's point now to the
new location.
For details, see:
http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007828.html
Change-Id: I171eb7efc0e34b4451a1b3539ae6655f81dd2312
This commit will test for changes in congress nova driver
that adds addresses table.
Change-Id: Ib948d7be1dc28a49f36488eb0860d0839cbdee60
Partially-Implements: blueprint add-tacker-datasource-driver
Configure the replica server in the test to use a short PRC timeout.
The instability appears to arise as follows.
In starting the replica Congress instance:
If Congress API process starts before Congress policy engine process,
the call to check Congress started is processed by the API process,
which makes an RPC call to the policy engine process.
But the policy engine process may be a bit slower to start.
In that case, the RPC call may never reach the policy engine process
even if the policy engine process starts up just a few seconds later.
So the call times out according to the default 60 seconds, by which
point the entire retry period of the test is used up and the test
fails.
In this fix, the RPC timeout is set to a short 10 seconds on the
replica instance. That way, if the policy engine has not started
by the time of the first RPC call, the RPC call would time out with
time remaining on the test retry period for further retry.
The test retry period is also increased because occassionally the
replica policy engine takes longer than the allotted 60s to start up.
Change-Id: Ied8c95c4a60a3b6ea2c617fdfe94d4d7cf7a5822
Persistent instability in the test on queens branch and only in the
py35 job (py27 seems fine).
The instability makes the test more trouble than it's worth.
Because we are unlikely to make changes to queens going forward,
and even less likely that the changes would break murano integration,
it makes sense to simply disable to test for queens-py35 job, but
keeping it in all other jobs including queens-py27.
Also folding in the following patch resolving gate instability because
both patches are blocked on its own.
---------------------------------------
Increase policy rule create retry limit
Because in the vitrage pub-sub tests, occassionally the retry runs
out before the schema from the datasource is available to the
policy engine to allow the creation of the test rule.
https://review.openstack.org/#/c/637681/
Change-Id: I4915023258b455005e1ac2e2d1492beb368f0184
In current test setup, congress neutron driver uses admin credential
but the corresponding tempest test uses non-admin credential. As a
result, the driver and the test verifying the driver's data sometimes
see different data, causing false test failure.
This patch makes the test use admin credentials.
Change-Id: I6116e8027f5dfcceb6dd835de055cc3f8040d45c
This commit adds test for modified monasca webhook driver[0]
That will test for 3 different tables names alarm-notification,
metrics and dimensions.
[0] https://review.openstack.org/#/c/596698/
Depends-on: If6138710a0ee29320c3bdbefaffb9cc5df4b90c0
Depends-on: I1412840373fd8fe4e153e60d5ef85241c1a6e817
Change-Id: I77241a735e0f16a4617b9eb9fbd73afe426ed2f8
Partially-Implements: blueprint add-monasca-push-driver
Monasca webhook driver was released in rocky as 'unstable'.
As expected, backward incompatible changes are taking place.
To support tempest testing of the feature in Rocky, an additional
feature flag is needed to indicate the old Rocky schema is used.
Change-Id: Ie605a5d8427af6191a76dcf6ebfbc3e69e141248
To unblock gate for new schema of monasca webhook driver [0]
commenting test temporarily.
[0] https://review.openstack.org/#/c/596698/
Change-Id: I7966021c3f9c21d343ffc4412fe5f5b01cffe811
skipping vitrage_webhook and monasca_webhook based on feature flags.
skipping nova driver tests for queens
because congress nova driver in queens does not work with the new
novaclient 10.1.0 now part of upper-constraints
due to https://review.openstack.org/#/c/571540/
Change-Id: I199f329bc6eae2c4656daceda8bb978614d0d6cc
Tempest failures occassionally occur because when the
freshly started replica server is unresponsive,
the tempest code does not retry.
This patch adds the retry.
Depends-On: https://review.openstack.org/#/c/588847/
Change-Id: I5e01412d7dbd66e2ddae99860f0d58f5b2800ab0
Checks that a Z3 policy performs a simple computation as expected and that it can
query or send informations to other theories.
The test will be safely skipped if Z3 is not available.
Depends-On: https://review.openstack.org/586511
Partially-implements: blueprint alternative-engine-z3
Change-Id: I7568ed557f8aa013828e8a88ae668487479cea00
Changes to oslo_config caused test breakage.
Disable temporarily to allow changes to merge for feature freeze.
Change-Id: I34d1a392d4539ede01666002cfa301c21f9cd4bd
The test case uses 'fixed_ip' as a query parameter, but the usage
is not correct. In before, the test passed because neutron
server ignored this parameter, and returned all the
ports, which happened to make the test pass.
This patch fixes the usage of this parameter. If there is no ip_address
then not to filter the list using the filter. Otherwise,
we use 'fixed_ips' parameter and populate its value correctly.
Change-Id: If46d6a739ce6799d2bf13146cdb748af8759c932
current monascaclient version does not work with osc-lib 1.11.0
disabling the test for now until a new monascaclient is released
and put in upper constraints
Change-Id: Ib96f6e4d845c0e667540e3a92f9eb84cc38d0a61
An import cycle issue in eventlet caused failure when launching
replica congress instance for HA test. The HA test was skipped.
Now that we have a work-around, re-enable the HA test.
Related-Bug: 1746136
Closes-Bug: 1745112
Depends-On: I72c349e81dfc02136b22637c707ad4908c9f269e
Change-Id: Ieeb8db6e1b40192c4b877b556718d12f6254b399
below patch rename the aodh service_available
config option from 'aodh_plugin' to 'aodh'.
- I7739e0b672a7211a1d643543fdc79031affa0a0b
This patch make congress tempest test to use the
new name so that it can be fetched correctly from
devstack setting on tempest config file.
Depends-On: I7739e0b672a7211a1d643543fdc79031affa0a0b
Change-Id: Iccfc40cc738994d6c7d08cbea845e0c2f888b995
Related-Bug: #1743688
Nate Johnston