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

remove e2e run before cluster upgrade #9988

Merged
merged 1 commit into from
Jun 18, 2015

Conversation

mikedanese
Copy link
Member

part of #8081

@k8s-bot
Copy link

k8s-bot commented Jun 17, 2015

GCE e2e build/test passed for commit b4a26997192aba469cfd064d184a7b5419d118b7.

echo "Tests on initial version succeeded. Running the checked master upgrade."
go run "$(dirname $0)/e2e.go" -v --test --test_args='--ginkgo.focus=Skipped.*Cluster\supgrade.*gce-upgrade' -check_version_skew=false
echo "Master upgrade complete. Running e2e on the upgraded cluster."
go run "$(dirname $0)/e2e.go" -v -build -up -version="" -test -check_version_skew=false
Copy link
Contributor

Choose a reason for hiding this comment

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

So I think you want to run e2e tests of the old version?

In this scenario, you've upgraded the master, but the nodes are still at the old version. If the e2e tests at the new version test a new feature that doesn't exist in the old version, they'll fail.

Copy link
Member Author

Choose a reason for hiding this comment

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

For this test, the old version is the new version. Currently (and since it was added), it deploys a locally built version and upgrades with the locally built version.

@k8s-bot
Copy link

k8s-bot commented Jun 18, 2015

GCE e2e build/test passed for commit dbb47fe.

@mbforbes
Copy link
Contributor

So this is just meant to be run locally, right? As a shortcut for building, running master upgrade (to itself), then running e2es? I guess I'm wondering what part of #8081 this solves?

@mikedanese
Copy link
Member Author

Yes this is to update the local upgrade-test helper script to match what jenkins does.

@mikedanese
Copy link
Member Author

This was in parity with jenkins before the recent discussion in #8081 but not after removing the first e2e run. I would say local helper scripts are part of the master upgrade harness.

@mbforbes
Copy link
Contributor

Ack, thanks for the explanation.

@mbforbes mbforbes added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 18, 2015
echo "Tests on initial version succeeded. Running the checked master upgrade."
go run "$(dirname $0)/e2e.go" -v --test --test_args='--ginkgo.focus=Skipped.*Cluster\supgrade.*gce-upgrade' -check_version_skew=false
echo "Master upgrade complete. Running e2e on the upgraded cluster."
go run "$(dirname $0)/e2e.go" -v -version="" -test -check_version_skew=false
Copy link
Contributor

Choose a reason for hiding this comment

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

do you need -version="" here?

Copy link
Contributor

Choose a reason for hiding this comment

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

do you want to specify the string of only the tests that aren't flaky?

satnam6502 added a commit that referenced this pull request Jun 18, 2015
remove e2e run before cluster upgrade
@satnam6502 satnam6502 merged commit 4bf6058 into kubernetes:master Jun 18, 2015
@mikedanese mikedanese deleted the upgrade-pre-e2e branch June 18, 2015 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm "Looks good to me", indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants