Commit Graph

16 Commits

Author SHA1 Message Date
Dan Winship
71b02dd422 Fix up e2enode.GetReadySchedulableNodes, replace many uses of framework.GetReadySchedulableNodesOrDie
Remove the "OrDie" from the name (since it doesn't "or die") and add
an extra check that there is at least 1 node available, since many
callers already did that themselves, and many others should have.
2019-09-24 13:03:39 -04:00
carlory
3c70201d1b remove blank lines 2019-08-28 01:27:31 +08:00
carlory
2301a3b15b cleanup test code in lifecycle, servicecatalog and ui package 2019-08-27 09:51:23 +08:00
SataQiu
332be4b1e3 refactor: replace framework.Failf with e2elog.Failf 2019-06-19 17:52:35 +08:00
Jiatong Wang
b1c346c295 Move node related methods to framework/node package
- Add a package "node" under e2e/framework and alias e2enode;
- Rename some functions whose name have redundant string.

Signed-off-by: Jiatong Wang <wangjiatong@vmware.com>
2019-06-17 16:59:07 -07:00
Jorge Alarcon Ochoa
4969a05327 Refactored pod-related functions from framework/util.go
This a refactoring of framework/utils.go into framework/pod.

Signed-off-by: Jorge Alarcon Ochoa <alarcj137@gmail.com>
2019-05-30 09:30:26 -04:00
Akihito INOH
be4af8f83f Use framework.ExpectNoError() for e2e/lifecycle
The e2e test framework has ExpectNoError() for readable test code.
This replaces Expect(err).NotTo(HaveOccurred()) with it for e2e/lifecycle.
2019-05-10 10:45:32 +09:00
John Schnake
338bc3ce42 Move framework ssh code to new package
The framework/ssh.go code was heavily used throughout the framework
and could be useful elsewhere but reusing those methods requires
importing all of the framework.

Extracting these methods to their own package for reuse.

Only a few methods had to be copied into this package from the
rest of the framework to avoid an import cycle.
2019-05-08 11:00:36 -05:00
Jiatong Wang
b26b6f0d5c Modify e2e/lifecycle tests to import e2elog.Logf
Signed-off-by: Jiatong Wang <wangjiatong@vmware.com>
2019-05-07 00:23:13 -07:00
SataQiu
1d8615a0a2 fix golint failures of test/e2e/lifecycle 2019-04-25 23:40:22 +08:00
Daniel Watkins
c9a9ae07e6 e2e: Ensure that sysrq-trigger is enabled before use
On Ubuntu (and, presumably, other distros too), the default
configuration prohibits some sysrq operations.  Before performing sysrq
operations in the e2e testing, ensure that all operations are permitted.
2018-08-06 11:49:12 -04:00
wojtekt
4cb99318d2 Fix PodStore to wait for being initialized 2018-04-12 15:38:11 +02:00
Chris Glass
5a6de4d22a Do not use ifupdown commands
The ifupdown commands (ifup and ifdown) are not useful on many modern
distributions. Instead, the "ip link set" set of commands are standard
linux utilities and should be available everywhere (see
http://baturin.org/docs/iproute2/).

ipupdown utilities have the added quirk that they return 0 on failure,
which makes the changed line fail silently in case ifdown didn't bring
the network down.

After the interface was brought back up, renew DHCP requests to ensure
the network is actually useable.

Signed-off-by: Chris Glass <chris.glass@canonical.com>
2018-01-31 08:33:43 +01:00
Dr. Stefan Schimanski
012b085ac8 pkg/apis/core: mechanical import fixes in dependencies 2017-11-09 12:14:08 +01:00
Kevin
4c8539cece use core client with explicit version globally 2017-10-27 15:48:32 +08:00
Mike Danese
3c39173ee4 fixit: break sig-cluster-lifecycle tests into subpackage 2017-07-19 10:14:51 -07:00