- Introduce new method for getting devops node based
on nailgun node's id
- Add missing 'value' key to enabling sriov
Change-Id: I95b60c25eab97e8577a16481741a76db99207976
(cherry picked from commit 8d2ccd2d26)
Now devops3 does not contains all needed hardcode for adding baremetal
network and nodes with it; instead of this, we can prepare and use the
template
Change-Id: I74c4276908231a1651ee2768b3d618d4b3dfa824
Partial-bug:1669762
(cherry picked from commit 80b97af7ab)
VMware not supported since Fuel 10. So we should stop test it.
Change-Id: I5996520ded3419fd2ce2cb1e76056eed157bfffb
Implements: blueprint remove-vmware
We have few tests failed on call "warm_shutdown_nodes"
with 4x60 timeout. But there are few rassed tests with
10x60 timeout. So longer timeout should be used for
all tests.
Change-Id: I0c7e63b4e9156f35d6679a9dcdfb7b9249c6796a
Partial-Bug: 1652000
(cherry picked from commit 18e4d59570)
Wrong property used for the stdout analysis .
Also steps order fixed.
Change-Id: I56f465facdd3e3e4fd6b4e7aa61690214f3b254c
Partial-Bug: 1652030
(cherry picked from commit 0eb080905b)
We should check cluster status and deploy state after
deploy and redeploy. Current tests did not contain this
check and fails after deployment on OSTFs run.
Change-Id: I84adc8981b1486c163425fa0b9506e29650203cf
Closes-Bug: 1658071
Serialization for features mentioned in title was changed so
we have to use new fields
Change-Id: If362a37fdb16d6672a266567490e67a22ba16f3e
Partial-bug:1644588
(cherry picked from commit 11783da6ac)
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
1. Backport code from mater to make debug easier
2. Use wsrep_ready, wsrep_connected and wsrep_cluster_size
Closes-bug: #1628963
Change-Id: I1e2234e0568a2875c82cc2cb29ddfa7fac61ab92
When we manage the environment with a manually added node, the lack of this
check leads to a fail.
Change-Id: I782bb7e0f6676281207e0f4201ce6b9fd930e76e
The nailgun validator for openstack config raises an exception
when 'deployment' task is present for particular cluster
and has 'pending' or 'running' state, so, we should implement
equivalent check on fuel-qa side.
Change-Id: I720e8fcd21907c64b393bc933056aef61167b25f
Closes-Bug: #1618880
update_node_networks: fuelweb_admin network is set directly
Automatic substitution is not supported ant it was a reason
for tests failure on the fuel-devops 3
Change-Id: Ia7dcee574c3146a870cd317dd991566af7eaefbe
This change removes hardcoded unavailable releases and makes the
replace_default_repos function more flexible to support only needed
and available releases. The previous version didn't work with UCA
environments.
Change-Id: Iec53c695037b08ee26e8e6c07fbf1dfacfcadde8
Closes-Bug: #1624295
Related-Bug: #1615488
Signed-off-by: Maksim Malchuk <mmalchuk@mirantis.com>
Test scenario 1:
1. Revert snapshot "ready_with_3_slaves"
2. Create env with 3 controller nodes and 1 compute+cinder node
3. Provision nodes
4. Upload two simple graphs
5. Make snapshots for next tests and resume snapshot
6. Execute graphs
7. Check that graph tasks was executed and
finished without any errors
8. Check the created by graph tasks file
Test scenario 2:
1. Revert snapshot "extension_graph_prepare_env"
2. Execute graphs via API
3. Check that graph tasks was executed and
finished without any errors
4. Check the created by graph tasks file
Change-Id: I45849d680c1224771ac8db61827ac56950c903f4
Closes bug: 1619638
Blueprint: graph-concept-extension
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
Get ID of a last created cluster: sort clusters
Due to possible order change in list_clusters,
we have to sort clusters before select "last"
Change-Id: I701405e517708ce92568d98c6b6559dcc5c052d7
Start NailgunClient implementation for Mitaka and Newton in core
Implemented: OSTF part.
We expect, that at Occata release we could switch to python-fuelclient
Blueprint: fuel-qa-join-helpers
Change-Id: Idefd263cf1c8a4a4d366615f2408dd7c3f2e99a4
Use repr in logwrap
make unicode strings ha one controller tests
get_cluster_block_devices -> make unicode output
(method used 1 times in single test)
Change-Id: Ia72f57b6be13c66edfcb4512f99f01f11da20f13
Closes-bug: #1620330
(cherry picked from commit 5fb4f5d)
1. Initialize NailgunClient with session only - old way was deprecated > 1 month ago
2. get_releases_details -> get_release (was method duplicate)
This changes is required for the future refactoring (move to core)
Change-Id: Ia01a453f7f8233d4d39152bf56714157e3d74475
Blueprint: fuel-qa-join-helpers
(cherry picked from commit 132455b)
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)
Right now we have mitaka and mitaka+UCA releases which both uses
Ubuntu as operation system. We want to predict "which release will be
taken for next operations".
'octane upgrade-env' now requires release id so this patch is required
for further changes
https://review.openstack.org/#/c/358881/
Change-Id: Icc4c2f534a13e11995129bad62b4fc985633fb34
Andreas Jaeger