Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Travis CI to use most current k8s server version #665

Merged
merged 1 commit into from
Oct 31, 2018

Conversation

micw523
Copy link
Contributor

@micw523 micw523 commented Oct 27, 2018

This PR corrects behavior reported in #660 that causes e2e tests which uses API introduced after 1.7.0 to fail.

Changes:

/assign @roycaihw

@k8s-ci-robot k8s-ci-robot added the ¯\_(ツ)_/¯ ¯\\\_(ツ)_/¯ label Oct 27, 2018
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Oct 27, 2018
@micw523
Copy link
Contributor Author

micw523 commented Oct 27, 2018

/cc @roycaihw
/unshrug

@k8s-ci-robot
Copy link
Contributor

@micw523: ¯\_(ツ)_/¯

In response to this:

/cc @roycaihw
/unshrug

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.

@k8s-ci-robot k8s-ci-robot removed the ¯\_(ツ)_/¯ ¯\\\_(ツ)_/¯ label Oct 27, 2018
sudo minikube start --vm-driver=$MINIKUBE_DRIVER --bootstrapper=kubeadm --kubernetes-version=$K8S_VERSION --logtostderr

# Make sure minikube information is not outdated
sudo minikube update-context
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need to run minikube update-context? I assume it modifies the kubeconfig file to point to the minikube cluster and I'd expect minikube start does that for us already

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

# Make sure minikube information is not outdated
sudo minikube update-context

export MINIKUBE_OK="false"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's not export this variable and make it local

@@ -30,6 +30,11 @@ trap "clean_exit" EXIT
# Switch off SE-Linux
setenforce 0

# Mount root to fix dns issues
# Define $HOME since somehow this is not defined
export HOME=/home/travis
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is unexpected. The travis doc mentioned that default the environment variables are available and HOME=/home/travis (do not depend on this value).

If the environment variable is truly missed, I'm wondering if ~ like the previous implementation works for you?

Copy link
Contributor Author

@micw523 micw523 Oct 29, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think $HOME works in 14.04, but somehow it’s not there in the 16.04 env. I was super surprised as well. ~ doesn’t work since we have to define MINIKUBE_HOME and it does not like itself to be defined ~

# Mount root to fix dns issues
# Define $HOME since somehow this is not defined
export HOME=/home/travis
sudo mount --make-rshared /
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which dns issue does this solve?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Frankly I am not sure. I’ve seen others using it and we had disable dns in our previous script. I think kubedns sometimes does not like the CI environments.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@roycaihw
Copy link
Member

cc @dims
as you previously implemented the kube-init script

@roycaihw
Copy link
Member

LGTM. Please squash the commits before merging

@roycaihw
Copy link
Member

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 31, 2018
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: micw523, roycaihw

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:

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 31, 2018
@k8s-ci-robot k8s-ci-robot merged commit bfb89c6 into kubernetes-client:master Oct 31, 2018
@micw523 micw523 deleted the k8s-version-upgrade branch November 1, 2018 01:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants