This patch set modifies lines which are importing objects
instead of modules. As per openstack import guide lines, user should
import modules in a file not objects.
http://docs.openstack.org/developer/hacking/#imports
Change-Id: I5b4bdcb674b58ab419d00ca9c6bff105ce19aca8
nova service-list only needs to report the status
of online controllers. Down and deleted nodes should
not cause the test to fail.
Change-Id: I56765f6cf889b6afb9780b32857a164e2b62c340
Related-Bug: #1570847
* this change replaces occurrences of
`traceback.format_exc()` with the appropriate version of
`LOG.exception()` in fuel-ostf
* removes importing `traceback` module.
* incorporated review comments from fuel-dev team
Change-Id: I7055aeafdcb109bd3566f118379196ea6ca6037d
Closes-Bug: #1457397
Signed-off-by: Anil Belur <askb23@gmail.com>
python-nova 13.0.0~b3-0ubuntu1~cloud0 no longer reports
incorrect services as being available and down.
This reverts commit 1bccfe65f6.
Change-Id: I51369ee54ae8519c266f577b4abb6767ba7e52d0
nova service-list shows osapi_compute and metadata
services as down, when these are APIs, not RPC receivers,
which should not be reported by this command. The bug is
fixed upstream and in Fuel, but not in UCA Trusty packages.
blueprint deploy-with-uca-packages
Change-Id: I632051fb77d713cd8584bba398486f70cb8901d5
Currently OSTF tests use deprecated nova-manage command to check
nova-service status. Result of nova-manage command is incorrect:
it contains services which aren't enabled. We should switch on
nova service-list usage.
Change-Id: Ie52d9f6014201be9d8d4221b1611465c840793c1
Closes-bug: #1544981
Changed duration in test description.
Sometimes it tooks more time to update nova services state on slow environment.
120 seconds must be enough.
Closes-Bug: #1449995
Change-Id: I934ed7e1fddfb847d201913f8cea10c2a1fc943c
Fixed all places where hacking rules (v0.7) was failing
Replaced ''' with """ to make them consistent
Change-Id: I9c1c20f910df696056d2a6a91c33ff7bad266b9f
Related-Bug: #1404892
Closes-Bug: #1408240
Patch include:
* Deployment tag qemu|kvm
added in the sanity.test_sanity_infastructure for
tests: Check internet connectivity from a compute,
Check DNS resolution on compute node. This give for us
possibility not discover those tests in case if vcenter
is set as hypervisor
* Add parsing of hypervisor
date into fuel_plugin.ostf_adapter.mixin.py
* Add check for libvrt_data
Change-Id: Idce25c31c0f001aa1a71fb790b912cddea6fb85b
Related: blueprint vcenter-hv-full-scale-support
Because in the configuration with vCenter compute node is missing, added:
1. Getting type of virtualization from cluster settings
2. Processing case when the type of virtualization is vmvare (not checked for no compute node available)
3. In test_sanity_infrastructure compute node has been replaced by a controller because
for vmvare and neutron interaction occurs via controller node
Implements: blueprint vcenter-hv-full-scale-support
Change-Id: I4f74011de5548990f163f220632fbf4fe2ffa39e
Now tests that are supposed to be skipped in certain circumstances are
skipping using unittest native mechanism instead of just failing. Also
in db such tests are marked by 'skipped' status.
Change-Id: Icca993c1f9541b235e36e1d737e5704d07661990
Closes-Bug: #1338667
Ping retry was not run when ping command had finished with error code != 0.
It is fixed now. Number of packets to be received is decreased to 1.
Closes-Bug: #1322102
Change-Id: I5fe84387e8e23fb918da2d4cc0bb3e9cf0fe02f8
It's allowed now to get at least 3 answers for no more than 10 requests.
Interval between connectivity checks is increaced (30 -> 60 sec).
Closes-Bug: #1322102
Change-Id: I0b227e3426c3d8b453986e6545829a11e125ce0b
Correct message in sanity infrastructure tests
In case if there is no compute nodes
Change-Id: Ib6f9e21c5bc3a1885a065005ba3807771f1550ee
Closes-Bug: #1288660
Retries for transport operation was added previously
So in this patch test Duration, displaying
in Expected column on HealthCheck UI page was increased
Change-Id: I5b64eac6770ea5bce6d9eef22912cdb9afd9fb44
The presented patch provides several necessary lines of code that make it
possible to run the OSTF tests based on a config written in a file. All the
user has to do is to insert an instruction like
os.environ['CUSTOM_FUEL_CONFIG'] = 'path/to/config/file'
before the actual OSFT launch. Changing the FuelConfig() method
implementation as well as moving its call in the BaseTestCase class
into the setUpClass() method serves for this goal and ensures that
the config values will override the default ones.
* DNS availability test has been splitted into two tests
* constructions like len(<list>)>=0 were removed from
sanity test set. Scenarios were updated accordingly
* PEP8 issues were fixed in all the sanity tests
Andreas Jaeger