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

hack in field selectors for 3.6 #16541

Merged

Conversation

deads2k
Copy link
Contributor

@deads2k deads2k commented Sep 25, 2017

This doesn't make any of the structural fixes to make field selectors more consistent and reliable across APIs, but it should enable compatible field selection in the 3.6 groupified APIs.

@bparees @gabemontero per request

@openshift-ci-robot openshift-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Sep 25, 2017
@openshift-merge-robot openshift-merge-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 25, 2017
@liggitt
Copy link
Contributor

liggitt commented Sep 25, 2017

looks good enough to me

@deads2k
Copy link
Contributor Author

deads2k commented Sep 25, 2017

looks good enough to me

"damning with faint praise" comes to mind... :)

@bparees
Copy link
Contributor

bparees commented Sep 25, 2017

/lgtm
but i think we need an ose equivalent backport for this to help anyone.

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 25, 2017
@openshift-merge-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bparees, deads2k

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

@deads2k
Copy link
Contributor Author

deads2k commented Sep 25, 2017

/retest

@deads2k deads2k added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 25, 2017
@deads2k
Copy link
Contributor Author

deads2k commented Sep 25, 2017

@stevekuznetsov @bparees extended-builds failed, but this ended up in queue

@stevekuznetsov
Copy link
Contributor

but this ended up in queue

What do you mean? Do you have some logs?

@stevekuznetsov
Copy link
Contributor

Oh

@stevekuznetsov
Copy link
Contributor

Builds are not blocking

@deads2k
Copy link
Contributor Author

deads2k commented Sep 26, 2017

@csrwng can you help me sort out whether this error is real? I wouldn't expect to have changed anything for a test that used to work in 3.6.

@csrwng
Copy link
Contributor

csrwng commented Sep 26, 2017

@deads2k this looks like a CI problem. In 3.6 not passing an arg would result in an error, but in 3.7 it only results in a warning. Looks like the builder image being used to run the test is a 3.7 one and not 3.6 (maybe latest?). But anyway not a real failure.

@bparees
Copy link
Contributor

bparees commented Sep 26, 2017

it was a docker change (how docker handled you not supplying an ARG that the dockerfile defined). It went from being an error to a warning.

We fixed the test in 3.7 when it broke (I guess when we updated docker at some point). We'll just need to backport the same fix to the 3.6 branch:

you should be able to just cherry pick this into your PR:
#16212

Docker changed the error for a non-existent --build-arg to a warning
and changed the text of the message slightly, breaking one of our tests.
Docker change: moby/moby@f150f42

Fixes: openshift#16197
@openshift-merge-robot openshift-merge-robot removed the lgtm Indicates that a PR is ready to be merged. label Sep 26, 2017
@deads2k deads2k added lgtm Indicates that a PR is ready to be merged. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Sep 26, 2017
@openshift-ci-robot
Copy link

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

Test name Commit Details Rerun command
ci/openshift-jenkins/extended_builds ea49279 link /test extended_builds

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.

@deads2k
Copy link
Contributor Author

deads2k commented Sep 26, 2017

@bparees @csrwng I picked the one you pointed out. I don't want to keep holding this on existing CI problems. Is this another CI issue?

@csrwng
Copy link
Contributor

csrwng commented Sep 26, 2017

@deads2k this one is actually a bug that we fixed post-3.6. But nothing related to this pull.

@bparees
Copy link
Contributor

bparees commented Sep 26, 2017

@deads2k we'll let you slide on that failure.

@deads2k deads2k removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 26, 2017
@openshift-merge-robot
Copy link
Contributor

Automatic merge from submit-queue

@openshift-merge-robot openshift-merge-robot merged commit 08fb8fd into openshift:release-3.6 Sep 26, 2017
@deads2k deads2k deleted the api-09-field-selector3.6 branch January 24, 2018 14:35
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. lgtm Indicates that a PR is ready to be merged. retest-not-required 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

8 participants