| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Change-Id: I1055b232711c95fdbf89ba9fe8b9d61a561fbcd5
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix consists of 2 parts:
- Calculate correctly left time for waiting in
'scale_dcs_pod_amount_and_wait' function. Before, it had bug,
where we were waiting less time than requested. And it led to the
unexpected timeout errors.
Example: it could fail waiting only 180sec having 600sec as real
timeout.
- Reset 'attempts' on the instantiated 'waiter's to avoid
redundant waiting reusing the single waiter instance.
Example. On deletion of 20 PVCs we save about 1,5 minutes.
In whole test suite we create much more PVCs than 20.
Change-Id: I5d06a63dd0c2c5bd67fdb09fef87948d65e6bf22
|
| |
|
|
|
|
|
|
|
|
|
| |
New TC insures that app pod is restarted properly when one of the
target node is down.
This patch includes libs of vmware api
These libraries can perform VM operations like power on and off via
vmware client api's.
Change-Id: I11ad4dc3318cb0583de5882d8067ed7e30ea9962
|
|
|
Separate node reboot functionality from single test case to re-use
it at other places. Update test case accordingly.
Change-Id: Ib9a7f15d29237e4f21aafc408c074e799e706740
Signed-off-by: Sri Vignesh <sselvan@redhat.com>
Signed-off-by: vamahaja <vamahaja@redhat.com>
|
