50d49d9c51
Enables memcg notification in cluster/node e2e tests
2017-06-26 11:40:22 -07:00
29b2db5af3
Logs node e2e perf data to standalone json files
2017-06-12 14:27:56 -07:00
de1150385d
fix typo
2017-05-15 12:07:36 +08:00
abb5c3fd5a
Fix flag formatting errors in the node tests
...
There were three problems:
- Lack of a trailing space after prepending flags.
- Passing multiple flags in a string to --kubelet-flags seems to confuse
the flag parser; it stops parsing ALL flags as soon as it sees the
second kubelet flag. Fortunately, all instances of --kubelet-flags are
combined together, so we can just pass two of those.
- --feature-gates should be passed to the test framework, which then
forwards it to the kubelet, instead of using --kubelet-flags.
This hopefully fixes the dynamic config test failures on COS, which
started after #45602 .
2017-05-11 11:28:49 -07:00
0b1e45c5ff
enable memcg on all testing
2017-05-10 11:38:26 -07:00
8ab63dd9ea
Merge pull request #42740 from mtaufen/tarball-cleanup
...
Automatic merge from submit-queue (batch tested with PRs 42740, 44980, 45039, 41627, 45044)
Cleanup some of the tarball producing code for e2e node tests
This is some e2e node cleanup work I found sitting in a local branch while deleting old local git branches. It looks like it's still useful.
2017-04-27 13:27:00 -07:00
4f50a8d7cd
Merge pull request #44457 from dnardo/e2e_node_cni
...
Automatic merge from submit-queue (batch tested with PRs 43000, 44500, 44457, 44553, 44267)
Updates e2e_node test to allow both kubenet and cni to be specified f…
…or the network plugin.
This adds a simple CNI configuration which is added to the node during test setup.
This also modifies the default flags in services/kubelet.go to specify the "cni-bin-dir"
and the "cni-conf-dir" and removes the "network-plugin-dir" flag. This leaves the default
network plugin to kubenet.
**What this PR does / why we need it**:
**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #
**Special notes for your reviewer**:
**Release note**:
```release-note
```
2017-04-18 13:19:08 -07:00
a05c3c0efd
autogenerated
2017-04-14 10:40:57 -07:00
29b2708046
Add comment to setupCNI.
2017-04-13 15:11:24 -07:00
4e458ce001
Updates e2e_node test to allow both kubenet and cni to be specified for the network plugin.
...
This adds a simple CNI configuration which is added to the node during test setup.
This also modifies the default flags in services/kubelet.go to specify the "cni-bin-dir"
and the "cni-conf-dir" and removes the "network-plugin-dir" flag. This leaves the default
network plugin to kubenet.
2017-04-13 09:57:46 -07:00
e6321c7440
Cleanup some of the tarball producing code
2017-04-10 07:09:31 -07:00
08fefc9d9a
Merge pull request #42769 from timchenxiaoyu/acrosstypo
...
Automatic merge from submit-queue
fix across typo
fix across typo
NONE
2017-04-05 14:28:26 -07:00
f4d9bbc7d8
Bump CNI consumers to latest version
...
- vendored CNI plugins properly handle `DEL` on missing resources
- [based on v0.5.1](https://github.com/kubernetes/kubernetes/issues/43488#issuecomment-288525151 )
2017-03-22 16:03:13 -07:00
767719ea9c
fix across typo
2017-03-09 09:07:21 +08:00
e5d647988e
Merge pull request #39049 from ixdy/node-e2e-ssh-key
...
Automatic merge from submit-queue
Add flag to node e2e test specifying location of ssh privkey
**What this PR does / why we need it**: in CI, the ssh private key is not always located at `$HOME/.ssh`, so it's helpful to be able to override it.
@krzyzacy here's my resurrected change. I'm not sure why I neglected to follow-through on it originally.
**Release note**:
```release-note
NONE
```
2017-01-31 13:40:26 -08:00
924ec4711b
Prep node_e2e for GCI to COS name change
2017-01-23 15:00:39 -08:00
6a4d5cd7cc
start the apimachinery repo
2017-01-11 09:09:48 -05:00
20d221f75c
Enable auto-generating sources rules
2017-01-05 14:14:13 -08:00
a719a7d7e7
Do not use sudo when untar node e2e tar ball.
2016-12-21 16:28:33 -08:00
30a5efa33b
Add flag to node e2e test specifying location of ssh privkey
2016-12-21 11:52:41 -08:00
1955ed614f
Merge pull request #39074 from Random-Liu/node-e2e-set-user
...
Automatic merge from submit-queue
Node E2E: Set user with `--ssh-user` flag when running remote node e2e.
This PR unblocks https://github.com/kubernetes/test-infra/issues/1348 .
In our test environment, we must login test instance as user `jenkins` because of the service account. Node e2e is always using the default user on the host, which works fine till now, because it is always run as `jenkins` in our test environment.
However, now we moved the test runner into a docker container, inside the container user is `root` by default, which will cause error:
```
Permission denied (publickey)
```
This PR added a flag `--ssh-user` to explicitly specify the user used to ssh into test instance. The dockerized test runner can set user to `jenkins` with this flag.
@krzyzacy @ixdy
2016-12-21 11:21:09 -08:00
10f72be5af
Support set user with `--ssh-user` flag when running remote node e2e.
2016-12-21 01:54:02 -08:00
c57f2ec064
Fix report prefix for node conformance test.
2016-12-15 15:27:14 -08:00
06507e9378
Fix node conformance test.
2016-12-14 14:21:10 -08:00
02e96df55c
Update log level.
2016-12-13 19:08:55 -08:00
54c874f2c6
Update bazel.
2016-12-13 19:08:55 -08:00
4cdd1b788a
Add node conformance ci test.
2016-12-13 19:08:55 -08:00
bca5aea5ba
Refactor RunRemote to support TestSuite interface.
2016-12-13 19:08:55 -08:00
99dc80ccc2
Add TestSuite interface and update the CreateTestArchive function.
2016-12-13 19:08:55 -08:00
c87de85347
autoupdate BUILD files
2016-12-12 13:30:07 -08:00
486ddae35a
`make test-e2e-node` runs the same test with pr builder by default.
2016-12-09 16:06:18 -08:00
6f92572209
Move ssh related functions into ssh.go.
2016-12-05 23:59:58 -08:00
7c2b1f4752
Remove setup-node, which is not needed after we run the whole test as
...
root.
2016-12-05 16:16:08 -08:00
ba62dafe39
Merge pull request #37663 from Random-Liu/fix-node-e2e-firewall-configure
...
Automatic merge from submit-queue (batch tested with PRs 37094, 37663, 37442, 37808, 37826)
Node E2E: Fix node e2e firewall configure.
Get rid of the misleading error message:
```
W1129 12:57:16.967] E1129 12:57:16.967130 29815 remote.go:204] Failed to configured firewall: command [ssh -i /home/jenkins/.ssh/google_compute_engine -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o CheckHostIP=no -o StrictHostKeyChecking=no -o ServerAliveInterval=30 -o LogLevel=ERROR 104.154.201.208 -- sudo sh -c 'iptables -L INPUT | grep "Chain INPUT (policy DROP)"&&(iptables -C INPUT -w -p TCP -j ACCEPT || iptables -A INPUT -w -p TCP -j ACCEPT)&&(iptables -C INPUT -w -p UDP -j ACCEPT || iptables -A INPUT -w -p UDP -j ACCEPT)&&(iptables -C INPUT -w -p ICMP -j ACCEPT || iptables -A INPUT -w -p ICMP -j ACCEPT)'] failed with error: exit status 1 output:
W1129 12:57:17.271] E1129 12:57:17.271169 29815 remote.go:213] Failed to configured firewall: command [ssh -i /home/jenkins/.ssh/google_compute_engine -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o CheckHostIP=no -o StrictHostKeyChecking=no -o ServerAliveInterval=30 -o LogLevel=ERROR 104.154.201.208 -- sudo sh -c 'iptables -L FORWARD | grep "Chain FORWARD (policy DROP)" > /dev/null&&(iptables -C FORWARD -w -p TCP -j ACCEPT || iptables -A FORWARD -w -p TCP -j ACCEPT)&&(iptables -C FORWARD -w -p UDP -j ACCEPT || iptables -A FORWARD -w -p UDP -j ACCEPT)&&(iptables -C FORWARD -w -p ICMP -j ACCEPT || iptables -A FORWARD -w -p ICMP -j ACCEPT)'] failed with error: exit status 1 output:
W1129 12:57:17.557] E1129 12:57:17.556683 29815 remote.go:204] Failed to configured firewall: command [ssh -i /home/jenkins/.ssh/google_compute_engine -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o CheckHostIP=no -o StrictHostKeyChecking=no -o ServerAliveInterval=30 -o LogLevel=ERROR 104.154.128.178 -- sudo sh -c 'iptables -L INPUT | grep "Chain INPUT (policy DROP)"&&(iptables -C INPUT -w -p TCP -j ACCEPT || iptables -A INPUT -w -p TCP -j ACCEPT)&&(iptables -C INPUT -w -p UDP -j ACCEPT || iptables -A INPUT -w -p UDP -j ACCEPT)&&(iptables -C INPUT -w -p ICMP -j ACCEPT || iptables -A INPUT -w -p ICMP -j ACCEPT)'] failed with error: exit status 1 output:
W1129 12:57:17.771] I1129 12:57:17.771236 29815 remote.go:231] Killing any existing node processes on tmp-node-e2e-a1212c32-gci-dev-56-8977-0-0
W1129 12:57:17.877] E1129 12:57:17.877123 29815 remote.go:213] Failed to configured firewall: command [ssh -i /home/jenkins/.ssh/google_compute_engine -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o CheckHostIP=no -o StrictHostKeyChecking=no -o ServerAliveInterval=30 -o LogLevel=ERROR 104.154.128.178 -- sudo sh -c 'iptables -L FORWARD | grep "Chain FORWARD (policy DROP)" > /dev/null&&(iptables -C FORWARD -w -p TCP -j ACCEPT || iptables -A FORWARD -w -p TCP -j ACCEPT)&&(iptables -C FORWARD -w -p UDP -j ACCEPT || iptables -A FORWARD -w -p UDP -j ACCEPT)&&(iptables -C FORWARD -w -p ICMP -j ACCEPT || iptables -A FORWARD -w -p ICMP -j ACCEPT)'] failed with error: exit status 1 output:
W1129 12:57:17.898] I1129 12:57:17.898711 29815 remote.go:239] Extracting tar on tmp-node-e2e-a1212c32-gci-dev-56-8977-0-0
W1129 12:57:17.941] E1129 12:57:17.941566 29815 remote.go:204] Failed to configured firewall: command [ssh -i /home/jenkins/.ssh/google_compute_engine -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o CheckHostIP=no -o StrictHostKeyChecking=no -o ServerAliveInterval=30 -o LogLevel=ERROR 104.154.154.237 -- sudo sh -c 'iptables -L INPUT | grep "Chain INPUT (policy DROP)"&&(iptables -C INPUT -w -p TCP -j ACCEPT || iptables -A INPUT -w -p TCP -j ACCEPT)&&(iptables -C INPUT -w -p UDP -j ACCEPT || iptables -A INPUT -w -p UDP -j ACCEPT)&&(iptables -C INPUT -w -p ICMP -j ACCEPT || iptables -A INPUT -w -p ICMP -j ACCEPT)'] failed with error: exit status 1 output:
W1129 12:57:18.020] I1129 12:57:18.019802 29815 remote.go:231] Killing any existing node processes on tmp-node-e2e-a1212c32-coreos-alpha-1122-0-0-v20160727
W1129 12:57:18.024] E1129 12:57:18.024044 29815 remote.go:213] Failed to configured firewall: command [ssh -i /home/jenkins/.ssh/google_compute_engine -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o CheckHostIP=no -o StrictHostKeyChecking=no -o ServerAliveInterval=30 -o LogLevel=ERROR 104.154.154.237 -- sudo sh -c 'iptables -L FORWARD | grep "Chain FORWARD (policy DROP)" > /dev/null&&(iptables -C FORWARD -w -p TCP -j ACCEPT || iptables -A FORWARD -w -p TCP -j ACCEPT)&&(iptables -C FORWARD -w -p UDP -j ACCEPT || iptables -A FORWARD -w -p UDP -j ACCEPT)&&(iptables -C FORWARD -w -p ICMP -j ACCEPT || iptables -A FORWARD -w -p ICMP -j ACCEPT)'] failed with error: exit status 1 output:
```
The problem is that the command 'iptables -L FORWARD | grep "Chain FORWARD (policy DROP)" returns an error when the rule is not found, which is not expected behaviour.
@freehan
2016-12-03 04:27:48 -08:00
6d4e457f1f
Collect serial output when test fails in node e2e.
2016-12-01 10:41:24 -08:00
85afed5dd0
Fix node e2e firewall configure.
2016-11-29 15:40:31 -08:00
e000ff0872
Fix remote log fetching.
2016-11-22 18:40:40 -08:00
edf7608c51
Remove kubelet related flags from node e2e. Add a single flag `kubelet-flags` to pass kubelet flags all together.
2016-11-17 10:17:32 -08:00
09bc5e23a6
Avoid printing test result twice.
2016-11-15 18:10:27 -08:00
467a1cd23b
Merge pull request #35868 from Random-Liu/cleanup-node-e2e-output-dir
...
Automatic merge from submit-queue
Node E2E: Reorganize node e2e output directories.
Fixes https://github.com/kubernetes/kubernetes/issues/35074 .
This PR cleans up the result directory and workspace directory of node e2e test.
Local result directory:
```
/tmp/_artifacts/
|----- build-log.txt (build log)
|----- *.xml (junit xml file)
|----- local/ (local run *.log)
|----- hostname1/ (remote run *.log)
|----- hostname2/
```
Workspace directory on test node:
```
/tmp/node-e2e-yyyy-mm-ddThh-mm-ss/
|----- cluster/ (gci mounter)
|----- cni/ (cni binary)
|----- e2e_node.test (test binary)
|----- e2e_node_test.tar.gz (test tar)
|----- etcd060429031/ (etcd data directory)
|----- ginkgo (ginkgo binary)
|----- kubelet (kubelet binary)
|----- pod-manifest365096781/ (mirror pod directory)
|----- results/ (test result directory)
```
@mtaufen
/cc @kubernetes/sig-node
2016-11-10 01:58:58 -08:00
0562386385
re-enable node e2e for GCI mounter
...
Signed-off-by: Vishnu kannan <vishnuk@google.com>
2016-11-08 11:09:13 -08:00
dd8ec911f3
Revert "Revert "Merge pull request #35821 from vishh/gci-mounter-scope""
...
This reverts commit 402116aed4
2016-11-08 11:09:10 -08:00
d9ddd64c9c
Reorganize node e2e output directories.
2016-11-08 00:12:14 -08:00
919935beec
Remove sudo in test suite and run test with sudo.
2016-11-07 15:27:53 -08:00
c76c9c5330
Temporarily disable GCI mounter in e2e node tests
2016-11-04 12:42:47 -07:00
402116aed4
Revert "Merge pull request #35821 from vishh/gci-mounter-scope"
...
This reverts commit 973fa6b33441b5fe86b6
2016-11-03 20:23:25 -07:00
32bc46a202
Merge pull request #36181 from yujuhong/get_logs
...
Automatic merge from submit-queue
Node e2e: collect logs if the test fails unexpectedly
2016-11-03 14:40:52 -07:00
97a348063c
Node e2e: collect logs if the test fails unexpectedly
...
This only works for nodes with journald.
2016-11-03 11:54:02 -07:00
414e4ae549
Revert "Adding a root filesystem override for kubelet mounter"
...
This reverts commit e861a5761d
2016-11-02 15:18:09 -07:00
19c19c2e0f
Updating GCI mounter to be containerized
...
Signed-off-by: Vishnu kannan <vishnuk@google.com>
2016-10-27 09:37:08 -07:00
Yang Guo