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

Do not check builds/details in build by strategy admission control #6678

Merged
merged 1 commit into from
Jan 16, 2016

Conversation

csrwng
Copy link
Contributor

@csrwng csrwng commented Jan 15, 2016

Fixes BZ 1298861

This was a regression introduced by #6576.

@openshift-bot
Copy link
Contributor

Evaluated for origin testonlyextended up to 1e9cd7f

@@ -49,6 +49,11 @@ func (a *buildByStrategy) Admit(attr admission.Attributes) error {
if resource := attr.GetResource(); resource != buildsResource && resource != buildConfigsResource {
return nil
}
// Explicitly exclude the builds/details subresource because it's only
// updating commit info and cannot change build type.
if attr.GetResource() == "builds" && attr.GetSubresource() == "details" {
Copy link
Contributor

Choose a reason for hiding this comment

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

s/"builds"/buildsResource/

@bparees
Copy link
Contributor

bparees commented Jan 15, 2016

one nit and lgtm. over to @smarterclayton

@bparees
Copy link
Contributor

bparees commented Jan 15, 2016

also fyi test+testonlyextended doesn't make much sense :)

@csrwng
Copy link
Contributor Author

csrwng commented Jan 15, 2016

updated.

Should the tag be "testextended" ?

@smarterclayton
Copy link
Contributor

Approved, merge when ready

@bparees
Copy link
Contributor

bparees commented Jan 15, 2016

"[test][extended:core(builds)]" is what you wanted (but it's also what you got as a result of what you did.. just saying the onlyextended does not actually limit it to only extended tests if you also put a test tag on it)

@csrwng
Copy link
Contributor Author

csrwng commented Jan 15, 2016

[test]

@liggitt liggitt added this to the 1.1.1 milestone Jan 15, 2016
@liggitt
Copy link
Contributor

liggitt commented Jan 15, 2016

@smarterclayton for approval to prevent regression in builders updating build details

@liggitt
Copy link
Contributor

liggitt commented Jan 15, 2016

nm, saw comment

@liggitt liggitt added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 15, 2016
@bparees
Copy link
Contributor

bparees commented Jan 15, 2016

@csrwng those extended test failures look scary, can you take a look?

@bparees
Copy link
Contributor

bparees commented Jan 15, 2016

@csrwng this one: https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/8636/consoleFull

going to run it again in the meantime after cleaning up the test tags.

[test]

@csrwng
Copy link
Contributor Author

csrwng commented Jan 15, 2016

@bparees after the failure below every test fails. It looks like the server stopped responding after that point. I didn't see this when I ran extended tests earlier today, so I think something must have gone wrong with the vm.


  Expected error:
      <*url.Error | 0xc2087a6180>: {
          Op: "Get",
          URL: "https://172.18.2.235:8443/api/v1/namespaces/extended-test-build-image-source-dx2lb/endpoints?timeout=30s",
          Err: {
              Op: "dial",
              Net: "tcp",
              Addr: {
                  IP: "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\xff\xff\xac\x12\x02\xeb",
                  Port: 8443,
                  Zone: "",
              },
              Err: 0x6f,
          },
      }
      Get https://172.18.2.235:8443/api/v1/namespaces/extended-test-build-image-source-dx2lb/endpoints?timeout=30s: dial tcp 172.18.2.235:8443: connection refused
  not to have occurred

@bparees
Copy link
Contributor

bparees commented Jan 15, 2016

ok we'll see what the current run yields.

@smarterclayton
Copy link
Contributor

[test]

On Fri, Jan 15, 2016 at 6:35 PM, OpenShift Bot notifications@github.com
wrote:

continuous-integration/openshift-jenkins/test FAILURE (
https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/44/) (Extended
Tests: core(builds))


Reply to this email directly or view it on GitHub
#6678 (comment).

@csrwng
Copy link
Contributor Author

csrwng commented Jan 15, 2016

@smarterclayton extended passed in one of the tests:
https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/8650/consoleFull

and failed with the same exact error above in the other test:

  Expected error:
      <*url.Error | 0xc2087a6180>: {
          Op: "Get",
          URL: "https://172.18.2.235:8443/api/v1/namespaces/extended-test-build-image-source-dx2lb/endpoints?timeout=30s",
          Err: {
              Op: "dial",
              Net: "tcp",
              Addr: {
                  IP: "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\xff\xff\xac\x12\x02\xeb",
                  Port: 8443,
                  Zone: "",
              },
              Err: 0x6f,
          },
      }
      Get https://172.18.2.235:8443/api/v1/namespaces/extended-test-build-image-source-dx2lb/endpoints?timeout=30s: dial tcp 172.18.2.235:8443: connection refused
  not to have occurred

@csrwng
Copy link
Contributor Author

csrwng commented Jan 15, 2016

I don't think that error is related to this pull

@csrwng
Copy link
Contributor Author

csrwng commented Jan 16, 2016

[test]

@openshift-bot
Copy link
Contributor

Evaluated for origin test up to 378876c

@csrwng
Copy link
Contributor Author

csrwng commented Jan 16, 2016

I wanted to kick off regular tests without the extended tests and then extended tests separately, but it doesn't look like it's letting me do that. It kicked off both again.

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test ABORTED (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/53/) (Extended Tests: core(builds))

@csrwng
Copy link
Contributor Author

csrwng commented Jan 16, 2016

@bparees
Copy link
Contributor

bparees commented Jan 16, 2016

It aggregates all the tags. If you want extended separate you can add the
testonlyextended tag again (Dan educated me this evening) and you'll get a
separate run for that.

Ben Parees | OpenShift
On Jan 15, 2016 10:42 PM, "Cesar Wong" notifications@github.com wrote:

I wanted to kick off regular tests without the extended tests and then
extended tests separately, but it doesn't look like it's letting me do
that. It kicked off both again.


Reply to this email directly or view it on GitHub
#6678 (comment).

@bparees
Copy link
Contributor

bparees commented Jan 16, 2016

1 for 2 on the test job, 2 for 2 on extended. test failure looks unrelated.
[merge]

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_origin/4647/) (Image: devenv-rhel7_3166)

@openshift-bot
Copy link
Contributor

Evaluated for origin merge up to 378876c

openshift-bot pushed a commit that referenced this pull request Jan 16, 2016
@openshift-bot openshift-bot merged commit d95ec08 into openshift:master Jan 16, 2016
@csrwng csrwng deleted the fix_build_details branch January 27, 2016 14:43
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants