Refactor those fixtures in a more general way, so they can be used in
any test, not only netchecker one.
Just set class variables required_files and required_settings to use them
In that way all required files and settings will be in the test class, and not
in the fixture itself.
Change-Id: I27eb98e46978205f4a4e9769e368d4720e2f8b55
Since we deploy and run netchecker applications
by tests for Calico, disable its deployment in
kargo.
Change-Id: I2946e8db3aa63c49ddd8ed03287a16b9619c3141
* moved methods for netchecker setup/start/stop
to the helpers;
* added a possiblity to install netchecker to k8s
cluster w/o fetching additional repositories;
* resolved #TODO (work with nodes labes via API).
Change-Id: Ic6a8470ff53d7e95c36240d25d816db3c5a0d89d
Added a new step:
3. Check that netchecker-server returns 400: 'There are no pods'
before starting netchecker-agent pods.
Merge only after https://review.fuel-infra.org/#/c/26973/
Change-Id: I69fd456274707c9f55302d39c8818a460d2cc0c5
There is a patch which changes success code response
from the server to '200':
https://review.fuel-infra.org/#/c/26745/
Tests should accept both for backward compatibility.
Change-Id: Ibcdcb89547179dc5e96c7d045d04b3ae2e31635d
The tests for 'mcp-netchecker' and calico are designed
to be executed on CI with custom artifacts set via
parameters. So they can't be run together with rest
component tests without affecting them. That's why
'component' mark was removed.
A separate test/method for network verification after
deployment in BVT is going to be added by another patch.
Also renamed tests method TestFuelCCPNetChecker.test_k8s_netchecker_calico
to TestFuelCCPNetChecker.test_k8s_netchecker, because there
is another test method in another class with the same name:
TestFuelCCPCalico.test_k8s_netchecker_calico.
Closes-bug: #1628512
Change-Id: I5cd7d5f6133a97645676b592fa7628380548e209
Sometimes tests hang while performing requests to the
netchecker. To prevent that 5 seconds connection timeout
is added. Also @retry decorator is used for re-trying
connection if it fails.
Change-Id: Iea90a04fc713304fb98807488021be9971273280
Scenario:
1. Install k8s with Calico network plugin.
2. Run netchecker-server service.
3. Run netchecker-agent daemon set.
4. Get network verification status.
Check status is 'OK'.
New test depends on mcp-netchecker tool. Some
related to network checker stuff was moved and
refactored.
Change-Id: I1f1c85a943a937e11f1e61df046d3c1425dd3643
Add a few improvements to the test for the netchecker:
* do not build Docker images manually, take ready
artifacts from the registry;
* remove redundant sleeps and netcheker-server restart;
* fix minor typos and wrong copy-paste.
Change-Id: I3a9cbbb670689e5e389e71ce12c0e1b591f5e5d3
We have plugin for LVM usage in k8s, this patch adds basic test using
this plugin.
This test creates an environment (which should have extra storage),
installs required software to use LVM on nodes, uploads a plugin to
each node and then creates nginx pod using this plugin to create its
storage.
Sample command to run test:
ENV_NAME="lvm_usage"\
CONF_PATH=fuel_ccp_tests/templates/default-with-storage.yaml\
IMAGE_PATH=/path/to/image LVM_PLUGIN_PATH=/path/to/plugin/binary\
DEPLOY_SCRIPT=/path/to/fuel-ccp-installer/utils/jenkins/kargo_deploy.sh\
py.test -s fuel_ccp_tests/tests/system/test_k8s_lvm_plugin_usage.py
Change-Id: I0a31324e445902774f35b6cf2af1d9d43e74f53e
Netchecker functionality was extended, currently it
can provide overall network connectivity status (works
or not). Updated tests to use appropriate API call.
Also changed an aproach for simulation of network
connectivity failure: now tests use more suitable
Calico policy feature instead of iptables.
Change-Id: I15e89810348ca34588ab61f2b0669dc6ef4c9953
Added new fixture 'show_step' which provides an
access to the 'log_step' helper, used to log
tests steps specified in the function doc string.
Change-Id: I814684e4b5d8ba3e73ef6dd461d671f25f9b1c6c
Andreas Jaeger