vendor: Glide update, droppping tectonic-node-controller and trimming cluster-api

[wking]

Generated with:

$ glide update --strip-vendor
$ glide-vc --use-lock-file --no-tests --only-code
$ bazel run //:gazelle

using:

$ glide --version
(cd $GOPATH/src/github.com/Masterminds/glide && git describe)
v0.13.1-7-g3e13fd1
$ (cd $GOPATH/src/github.com/sgotti/glide-vc && git describe)
v0.1.0-2-g6ddf6ee
$ bazel version
Build label: 0.16.1- (@non-git)
Build target: bazel-out/k8-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Mon Aug 13 16:42:29 2018 (1534178549)
Build timestamp: 1534178549
Build timestamp as int: 1534178549

The tectonic-node-controller removal catches us up with 596591b (#232).

The cluster-api trim adjusts the content from b00e40e (#119). Because cluster-api wasn't in glide.lock, I suspect neither glide nor glide-vc were run before that commit.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wking

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [wking]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[wking]

The smoke tests timed out waiting for the router:

Waiting for router to be created ...
NAME                          STATUS    ROLES       AGE       VERSION
ip-10-0-14-141.ec2.internal   Ready     bootstrap   4m        v1.11.0+d4cacc0
ip-10-0-16-85.ec2.internal    Ready     master      4m        v1.11.0+d4cacc0
ip-10-0-32-255.ec2.internal   Ready     master      4m        v1.11.0+d4cacc0
ip-10-0-5-115.ec2.internal    Ready     master      4m        v1.11.0+d4cacc0
NAME      DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
router    1         1         1            0           7s
error: timed out waiting for the condition
Installation failed

/retest

[abhinavdahiya]

@wking https://github.com/openshift/installer/pull/287/commits was already doing that. ??
cc @crawford

[wking]

https://github.com/openshift/installer/pull/287/commits was already doing that.

Somehow I missed #287 being filed. I'm fine with this getting in however, either this way or through #287.

[openshift-ci-robot]

@wking: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
ci/prow/e2e-aws-smoke	cbbe745	link	/test e2e-aws-smoke

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[crawford]

Fixed in #287. I see the competition for "Most Lines Deleted" is heating up! 😛

/close

[openshift-ci-robot]

@crawford: Closing this PR.

In response to this:

Fixed in #287. I see the competition for "Most Lines Deleted" is heating up! 😛

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.