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

Ingress Upgrade Testing #546

Merged
merged 3 commits into from
Nov 26, 2018
Merged

Conversation

agau4779
Copy link
Contributor

Continuation of #392 .

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 14, 2018
@k8s-ci-robot
Copy link
Contributor

Hi @agau4779. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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 added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Nov 14, 2018
@agau4779
Copy link
Contributor Author

/assign @rramkumar1

@agau4779
Copy link
Contributor Author

/assign bowei

pkg/e2e/status.go Show resolved Hide resolved
pkg/e2e/status.go Outdated Show resolved Hide resolved
pkg/e2e/status.go Outdated Show resolved Hide resolved
pkg/e2e/status.go Show resolved Hide resolved
pkg/e2e/status.go Outdated Show resolved Hide resolved
)

const (
configMapName = "status-cm"
Copy link
Member

Choose a reason for hiding this comment

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

should we create unique config maps for each run (per framework instance) to avoid potential clashes if we have a messed up run?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

hm, on the guitar test side we need to know the name of the configmap in order to check the conents. @rramkumar1 - thoughts? What does a messed-up run look like in this case?

Copy link
Contributor

Choose a reason for hiding this comment

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

@bowei What do you mean by messed up run?

Copy link
Member

Choose a reason for hiding this comment

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

ignore my comment, after discussion, I don't think it makes sense.

pkg/e2e/status.go Outdated Show resolved Hide resolved
pkg/e2e/status.go Show resolved Hide resolved
pkg/e2e/status.go Outdated Show resolved Hide resolved
pkg/e2e/status.go Outdated Show resolved Hide resolved
@bowei
Copy link
Member

bowei commented Nov 19, 2018

/ok-to-test

@k8s-ci-robot k8s-ci-robot removed the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Nov 19, 2018
pkg/e2e/status.go Outdated Show resolved Hide resolved
// Loop until we successfully update the config map
for {
var err error
sm.cm, err = sm.f.Clientset.Core().ConfigMaps("default").Update(sm.cm)
Copy link
Member

Choose a reason for hiding this comment

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

could it a race if we do update rather than patch?

options := &e2e.WaitForIngressOptions{
ExpectUnreachable: runs == 0,
}
ing, err := e2e.WaitForIngress(s, tc.ing, options)
Copy link
Member

Choose a reason for hiding this comment

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

I forget -- does this have some delay in the check to avoid excessively spamming when the LB is down?

needUpdate := true
// Framework.shutdown() kills this loop.
for {
if s.MasterUpgraded() && needUpdate {
Copy link
Member

Choose a reason for hiding this comment

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

do this in a follow on--

is it possible to separate out the wait for upgrade logic so it's easier to reuse?

@bowei
Copy link
Member

bowei commented Nov 26, 2018

/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 Nov 26, 2018
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agau4779, bowei

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 Nov 26, 2018
@k8s-ci-robot k8s-ci-robot merged commit 0557276 into kubernetes:master Nov 26, 2018
@agau4779 agau4779 deleted the upgrade-testing branch November 26, 2018 18:12
@agau4779 agau4779 restored the upgrade-testing branch November 27, 2018 19:28
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/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants