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

LimitRange e2e test improved. #55065

Merged
merged 1 commit into from
Nov 23, 2017
Merged

Conversation

kmrov
Copy link

@kmrov kmrov commented Nov 3, 2017

What this PR does / why we need it: Improves the e2e test for LimitRange API by testing Update, Delete and Watch features.

Release note:

NONE

@k8s-ci-robot k8s-ci-robot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 3, 2017
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Nov 3, 2017
@luxas
Copy link
Member

luxas commented Nov 5, 2017

/ok-to-test

Also marks it as a Conformance test.

needs @kubernetes/sig-architecture-feature-requests (cc @timothysc) approval in a SIG meeting as well

@k8s-ci-robot k8s-ci-robot added sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. kind/feature Categorizes issue or PR as related to a new feature. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 5, 2017
@kmrov
Copy link
Author

kmrov commented Nov 6, 2017

/retest

Copy link
Member

@timothysc timothysc left a comment

Choose a reason for hiding this comment

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

/lgtm but we need @kubernetes/sig-architecture-pr-reviews to approve any conformance changes

@kmrov please add a release note though to callout any conformance additions.

options := metav1.ListOptions{LabelSelector: selector.String()}
limitRanges, err := f.ClientSet.CoreV1().LimitRanges(f.Namespace.Name).List(options)
Expect(err).NotTo(HaveOccurred(), "failed to query for limitRanges")
Expect(len(limitRanges.Items)).To(Equal(0))
Copy link
Member

Choose a reason for hiding this comment

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

I would warn here b/c we've seen a number of test conditions fail on loaded clusters due to waiting on cleanup conditions. I realize that it shouldn't occur, but we've seen patterns of odd cleanup when running (N) overlapping test cases with namespaces names that are not completely unique.

Copy link
Author

Choose a reason for hiding this comment

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

What can you suggest to do to avoid the problems here?

Expect(err).NotTo(HaveOccurred(), "failed to set up watch")

By("Submitting a LimitRange")
limitRange, err = f.ClientSet.CoreV1().LimitRanges(f.Namespace.Name).Create(limitRange)
Copy link
Member

Choose a reason for hiding this comment

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

Update vs. Create based on previous value of list.

Copy link
Author

Choose a reason for hiding this comment

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

Should Update at line 140 use a new LimitRange structure, not the old with changed limit value?

@timothysc timothysc added this to the v1.9 milestone Nov 6, 2017
@timothysc timothysc added the sig/testing Categorizes an issue or PR as relevant to SIG Testing. label Nov 6, 2017
@luxas
Copy link
Member

luxas commented Nov 6, 2017

We definitely need an associated issue here. Is there any tracking issue / doc for changes to the Conformance suite over time?

@bgrant0607
Copy link
Member

@kmrov @timothysc
Please do not mark this as conformance now. I'll put it on the SIG Arch. agenda.

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed release-note-none Denotes a PR that doesn't merit a release note. labels Nov 13, 2017
@bgrant0607 bgrant0607 added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 15, 2017
@dims
Copy link
Member

dims commented Nov 16, 2017

Looks like the hold is for conformance annotation on the tests

@kmrov kmrov force-pushed the master branch 2 times, most recently from 8f4f43d to 41c20f4 Compare November 16, 2017 13:20
@kmrov kmrov changed the title LimitRange e2e test improved and marked as Conformance. LimitRange e2e test improved. Nov 16, 2017
@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. and removed release-note Denotes a PR that will be considered when it comes time to generate release notes. labels Nov 16, 2017
@bgrant0607 bgrant0607 removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 16, 2017
@bgrant0607
Copy link
Member

Yes, the hold was due to the conformance tag. Since that was removed, I removed the hold.

Thanks for the test improvements.

@kmrov
Copy link
Author

kmrov commented Nov 17, 2017

/priority important-longterm

@k8s-ci-robot k8s-ci-robot added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Nov 17, 2017
@luxas
Copy link
Member

luxas commented Nov 17, 2017

/retest

@luxas
Copy link
Member

luxas commented Nov 17, 2017

@timothysc LGTM this for real as the Conformance tag was removed?

Copy link
Member

@timothysc timothysc left a comment

Choose a reason for hiding this comment

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

/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 22, 2017
@xiangpengzhao
Copy link
Contributor

@timothysc a comment /approve no-issue is needed here :)
or
@kmrov you can create an issue for this PR and update the PR body accordingly to associate the PR with the issue (e.g., add Fixes: #issue-number to PR body), then the PR can get the approved label automatically (as @timothysc already commented /approve)

@timothysc
Copy link
Member

/approve no-issue

@k8s-github-robot k8s-github-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 22, 2017
@k8s-github-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kmrov, timothysc

Associated issue requirement bypassed by: timothysc

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

Needs approval from an approver in each of these OWNERS Files:

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@spiffxp
Copy link
Member

spiffxp commented Nov 22, 2017

/status in-progress
though honestly at this point it doesn't really matter, since it's approved+lgtm+passing

@jberkus
Copy link

jberkus commented Nov 22, 2017

/priority critical-urgent

/remove-priority important-longterm

adjusting priorities for code freeze

@k8s-ci-robot k8s-ci-robot added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. and removed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Nov 22, 2017
@k8s-github-robot
Copy link

[MILESTONENOTIFIER] Milestone Pull Request Current

@k82cn @kmrov @timothysc

Note: This pull request is marked as priority/critical-urgent, and must be updated every 1 day during code freeze.

Example update:

ACK.  In progress
ETA: DD/MM/YYYY
Risks: Complicated fix required
Pull Request Labels
  • sig/architecture sig/testing: Pull Request will be escalated to these SIGs if needed.
  • priority/critical-urgent: Never automatically move pull request out of a release milestone; continually escalate to contributor and SIG through all available channels.
  • kind/feature: New functionality.
Help

@k8s-github-robot
Copy link

Automatic merge from submit-queue (batch tested with PRs 52767, 55065, 55148, 56228, 56221). If you want to cherry-pick this change to another branch, please follow the instructions here.

@k8s-github-robot k8s-github-robot merged commit 47611b3 into kubernetes:master Nov 23, 2017
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. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. release-note-none Denotes a PR that doesn't merit a release note. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/testing Categorizes an issue or PR as relevant to SIG Testing. 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.

None yet