We had invalid procedure of handling stored SSH connections
when non-root access feature was enabled. This patch fixs that
and contains the following items:
* Use method `update_connection` when exist connection fails
* close current connection in method `update_connection`
* catch SSHException instead AuthenticationException
Change-Id: Id488abf5b21c3bf16f21546c5b26c16e29bc6a58
Closes-Bug: 1659747
(cherry picked from commit e4a2acfc23)
Current value is 6 processes.
Also deprecated function change.
Change-Id: I69ab82b332c6bfa7e00c9999a72b4225bddffcb3
Closes-Bug: 1654267
(cherry picked from commit 46d2680d9e)
Scope of IPv6 tests should be extended for case of
the deployment with OVS firewall driver. The changes
include a moving of common methods from test module and
a simple refactoring.
Change-Id: Ia78a36a7ab4dc41d2f8f83bc75ceb80e43ae6a0b
Do not use cat for file read:
it's difficult for debug operations with source data
YAMLEditor content calls get_content() if not loaded
Change-Id: I75061c067172085de0e5fb1baa051816a4a707eb
Add two tests with the following steps:
Deploy environment with enabled DMZ network for API.
Scenario:
1. Revert snapshot with ready master node
2. Create new environment
3. Run network verification
4. Deploy the environment
5. Run network verification
6. Run OSTF
7. Reboot cluster nodes
8. Run OSTF
9. Create environment snapshot deploy_env_with_public_api
Check that security rules are properly applied for DMZ network
Scenario:
1. Revert snapshot from previous test
2. Run instance
3. Try to access horizon from instance
4. Remove instance
Implements: blueprint test-separate-public-floating
Change-Id: I70474b5cab324aa4f4a042127d4e6961c95010bf
1. Move QuietLogger and logwrap to core
2. Fix QuietLogger (if log level was upper, than in param,
QuietLogger ebabled additional logging instead of pass)
3. Cover by unit-tests
4. Added missed license text
5. add *.log to gitignore
Change-Id: If842791000c76852fe1dec1e66edcc081c278b2c
Blueprint: fuel-qa-join-helpers
(cherry picked from commit b7ca0ff)
Rework checksum checker:
execution results may differ because of different commands
and it does not mean different md5
Change-Id: I25c4ef7ba919ff5e7e69b1e9f7f8f2cdcb713d81
Switch to SSHClient API usage in execute_on_remote: remote.check_call
check_call has been aligned to SSHClient
Change-Id: I6a6a0db5ccc1175c296a64d0c928d51558d51189
(cherry picked from commit 8e90a5b)
['stdout_str'] and ['stderr_str'] is accessible
on all SSHClient output (except async) only starting
from 2.9.22 and currently we using 2.9.21
Solution: roll-back part of changes from review 344612
Change-Id: I2ab955dd42a5b5db102236c7468f029bd89e3bc6
Replace deprecated methods by it's successors
Drop stdout_len and stderr_len as useless and unused
Change-Id: I558e864240c9d8bed7e9acd4dd1406c33d066800
Closes-bug: #1604688
- added waiters for node status
- removed redundant try/except/assert
Related blueprint: fuel-qa-failure-reason-grouping
Change-Id: I06ccac42856712d1f9afe64402d34aeba3c07af6
Scenario:
1. Check mcollective version on bootstrap
2. Create cluster
3. Add one node to cluster
4. Provision nodes
5. Check mcollective version on node
Change-Id: I92fe35d0c31f08bd0d69a8993c9f3a72e2bdb60d
Closes-Bug: #1460073
The problem is that after third reboot nodes are going
into maintenance mode and became unavailable for further
testing. We need disable UMM feature to prevent such behaviour.
Change-Id: I1cce936201872f47d13e3c482e23e1ba4cfc24b2
Closes-Bug: #1588877
1. PyCharm inspection: ignore no member for magic places
(six.moves, mixin for system_test, unicode<->string on python2)
2. Fix docstrings
3. Fix reraise of SkipTest
(use raise instead of raising again the same exception, but no args)
4. Bash simple variable usage
Closes-bug: #1578998
Change-Id: Ifac2dcb68b323ce48c6c80598abfd18ed9bf2caf
1. add FuelWebClient.assert_all_tasks_completed, which could check status
for specified cluster or wide
2. add NailgunClient.get_all_tasks_list for retrieving all tasks info from database
3. Call tasks status check after deployment success before short OSTF (
self.assert_ha_services_ready(cluster_id)
self.assert_os_services_ready(cluster_id)
)
4. add TestCliBase.assert_all_tasks_completed
5. call TestCliBase.assert_all_tasks_completed after deployment
Change-Id: I428fc17434d40951c6eb6cefe88dd007d1eb0761
Closes-bug: #1564943
- Add check on snapshot logs for master, controller, compute
- Add decorator with checking snapshot logs to
deploy_multirole_controller_cinder test
Change-Id: I5507908b73e8d464adbcd42220e93d8fc9f62e9a
Closes-Bug: #1541779
six library usage is enabled for non transparent compatible code
blueprint fuel-qa-python3-compatibility
Change-Id: I2a636c72454809e59545ec20c3cb52124fd9753a
Centos bootstrap was depricated in 8.0 and deleted in 9.0,
so we need to clen the code
Closes-Bug: #1560579
Change-Id: Ieeba0a1d08f3be8bc88f7abfb2fb109023c672ac
Make division transparent-compatible (from __future__ import division, // for strict int result)
Do not use round due to different types of result objects
blueprint fuel-qa-python3-compatibility
Related-bug: #1556791
Change-Id: I7bb173c6f97ac046af45c3f52cc32846a93a8981
fix: undefined-loop-variable - at some places it's fake fail,
at 2 places was a real problem
Related-bug: #1556791
Change-Id: I321d82cac0a3c031c43fd9e1bcbf9bfaab3b1164
Do not use filter(), map() or zip() for not iterator tasks
blueprint fuel-qa-python3-compatibility
Related-bug: #1556791
Change-Id: I6e031ed2ca18080a15eecd5d0c1db275f9ec9aa1
1. Implemented method: checkers.check_plugin_env
2. Used in very start of tests (example):
checkers.check_plugin_path_env(
var_name='EXAMPLE_PLUGIN_V3_PATH',
)
Closes-bug: #1550242
Change-Id: I3efcf84c22a4abe783b2b3f04825983f279aab4e
Remove ipaddr from fuelweb_test/requirements.txt and use netaddr
in test cases instead of ipaddr
Use string for creation of netaddr instances
Change-Id: Idc86dcaae6f10c13b04095fb11fa9351b130deb8
Closes-bug: #1544148
Settings should be enabled not only in
astute, but also in nailgun.
That is done via application of puppet
manifest of nailgun.
Change-Id: I2a1ba27ee6c73fd32d0b318181c3c6b2a10e2d58
Closes-bug: #1549447