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.

Sign up for GitHub

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

Jump to bottom

AWS kube-down: Issue warning if VPC not found #27518

Merged
merged 1 commit into from
Jun 20, 2016
Merged

AWS kube-down: Issue warning if VPC not found #27518

merged 1 commit into from
Jun 20, 2016

Conversation

justinsb
Copy link
Member

To address issue #17219

@justinsb justinsb added this to the v1.3 milestone Jun 16, 2016
@justinsb justinsb added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Jun 16, 2016
@k8s-github-robot k8s-github-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. release-note-label-needed labels Jun 16, 2016
@justinsb justinsb mentioned this pull request Jun 16, 2016
Closed
@davidopp davidopp added release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed release-note-label-needed labels Jun 16, 2016
@davidopp davidopp self-assigned this Jun 16, 2016
@davidopp
Copy link
Member

LGTM

Thanks, Justin!!

@davidopp davidopp added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 16, 2016
@roberthbailey
Copy link
Contributor

/cc @activars

@davidopp
Copy link
Member

This is failing due to "Kubectl apply should apply a new configuration to an existing RC" failure which appears in several roll-up test failures ("broken test run") but not any individual issues. I'll file an issue and restart the test.

@davidopp
Copy link
Member

@k8s-bot test this issue: #27521

@wojtek-t
Copy link
Member

@k8s-bot e2e test this please, issue: #27449

@j1n6
Copy link
Contributor

j1n6 commented Jun 17, 2016

👍

@goltermann
Copy link
Contributor

In E2E on GCE cluster failed to create on nodes failing to validate, but wholly unrelated to the code change.

@k8s-bot e2e test this issue: #IGNORE

@davidopp
Copy link
Member

Looks like an infrastructure problem; master failed to come up

Waiting for 7 ready nodes. 6 ready nodes, 6 registered. Retrying.
Waiting for 7 ready nodes. 6 ready nodes, 6 registered. Retrying.
Detected 6 ready nodes, found 6 nodes out of expected 7. Your cluster may not be fully functional.
NAME                                      STATUS                     AGE
e2e-gce-agent-pr-34-0-master              Ready,SchedulingDisabled   26m
e2e-gce-agent-pr-34-0-minion-group-05j0   Ready                      25m
e2e-gce-agent-pr-34-0-minion-group-0twx   Ready                      25m
e2e-gce-agent-pr-34-0-minion-group-oo31   Ready                      25m
e2e-gce-agent-pr-34-0-minion-group-tijt   Ready                      25m
e2e-gce-agent-pr-34-0-minion-group-yfym   Ready                      25m
2016/06/18 11:40:34 e2e.go:218: Error running up: exit status 1
2016/06/18 11:40:34 e2e.go:214: Step 'up' finished in 28m26.67816745s
2016/06/18 11:40:34 e2e.go:114: Error starting e2e cluster. Aborting.

@davidopp
Copy link
Member

@k8s-bot e2e test this issue: #IGNORE

@davidopp
Copy link
Member

Another infrastructure failure:

FATAL: Could not checkout bee5acd42028b0130c8c1b56c60fbd284f123edb
hudson.plugins.git.GitException: Could not checkout bee5acd42028b0130c8c1b56c60fbd284f123edb
    at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:1992)
    at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
    at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
    at hudson.remoting.UserRequest.perform(UserRequest.java:120)
    at hudson.remoting.UserRequest.perform(UserRequest.java:48)
    at hudson.remoting.Request$2.run(Request.java:332)
    at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:745)
    at ......remote call to agent-pr-8(Native Method)
    at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
    at hudson.remoting.UserResponse.retrieve(UserRequest.java:220)
    at hudson.remoting.Channel.call(Channel.java:781)
    at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
    at sun.reflect.GeneratedMethodAccessor243.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
    at com.sun.proxy.$Proxy64.execute(Unknown Source)
    at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1135)
    at hudson.scm.SCM.checkout(SCM.java:485)
    at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)
    at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)
    at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
    at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
    at hudson.model.Run.execute(Run.java:1738)
    at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
    at hudson.model.ResourceController.execute(ResourceController.java:98)
    at hudson.model.Executor.run(Executor.java:410)
Caused by: hudson.plugins.git.GitException: Command "/usr/bin/git checkout -f bee5acd42028b0130c8c1b56c60fbd284f123edb" returned status code 128:
stdout: 
stderr: fatal: reference is not a tree: bee5acd42028b0130c8c1b56c60fbd284f123edb

    at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1719)
    at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:63)
    at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:1984)
    at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
    at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
    at hudson.remoting.UserRequest.perform(UserRequest.java:120)
    at hudson.remoting.UserRequest.perform(UserRequest.java:48)
    at hudson.remoting.Request$2.run(Request.java:332)
    at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:745)
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing JUnit
[xUnit] [INFO] - [JUnit] - No test report file(s) were found with the pattern '_artifacts/**.xml' relative to '/var/lib/jenkins/workspace/kubernetes-pull-build-test-e2e-gce' for the testing framework 'JUnit'.  Did you enter a pattern relative to the correct directory?  Did you generate the result report(s) for 'JUnit'?
[xUnit] [ERROR] - No test reports found for the metric 'JUnit' with the resolved pattern '_artifacts/**.xml'. Configuration error?.
[xUnit] [INFO] - Failing BUILD.
[xUnit] [INFO] - There are errors when processing test results.
[xUnit] [INFO] - Skipping tests recording.
[xUnit] [INFO] - Stop build.
[PostBuildScript] - Execution post build scripts.
[kubernetes-pull-build-test-e2e-gce] $ /bin/bash -xe /tmp/hudson1864197756255474751.sh
+ mkdir -p _tmp
+ curl -fsS --retry 3 https://raw.githubusercontent.com/kubernetes/kubernetes/master/hack/jenkins/upload-to-gcs.sh
+ chmod +x ./_tmp/upload-to-gcs.sh
+ [[ ! -e /var/lib/jenkins/workspace/kubernetes-pull-build-test-e2e-gce/build-log.txt ]]
+ curl -fsS --retry 3 http://pull-jenkins-master:8080/job/kubernetes-pull-build-test-e2e-gce/45661/consoleText

@davidopp
Copy link
Member

@k8s-bot e2e test this issue: #IGNORE

@justinsb
Copy link
Member Author

Any objection if I just mark "retest-not-required"? e2e doesn't hit this...

@justinsb
Copy link
Member Author

It's that missing bee5acd42028b0130c8c1b56c60fbd284f123edb again though.

Not sure exactly what's going on here. bee5.. isn't in the main k8s repo. I'm guessing bee5.. is the merge is what we pulled using +refs/pull/27518/merge:refs/remotes/origin/pr/27518/merge, except that is 4d4bdf... (at least now). I wonder if maybe an intermediate commit changes the sha?

@justinsb
Copy link
Member Author

@k8s-bot e2e test this issue: #IGNORE

@goltermann
Copy link
Contributor

@k8s-bot verify this issue: #IGNORE

@goltermann
Copy link
Contributor

@k8s-bot e2e test this issue: #IGNORE

@goltermann
Copy link
Contributor

@k8s-bot node e2e test this issue: #IGNORE

@k8s-bot
Copy link

k8s-bot commented Jun 20, 2016

GCE e2e build/test passed for commit e58a16e.

@k8s-github-robot
Copy link

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

@k8s-bot
Copy link

k8s-bot commented Jun 20, 2016

GCE e2e build/test passed for commit e58a16e.

@k8s-github-robot
Copy link

Automatic merge from submit-queue

@k8s-github-robot k8s-github-robot merged commit 2274359 into kubernetes:master Jun 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@roberthbailey roberthbailey

@davidopp davidopp

Labels
lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/backlog Higher priority than priority/awaiting-more-evidence. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Milestone
v1.3
Development

Successfully merging this pull request may close these issues.
9 participants
@justinsb @davidopp @roberthbailey @wojtek-t @j1n6 @goltermann @k8s-bot @k8s-github-robot @googlebot