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

Do not merge: Making a no op change to test @k8s-bot federation gce e2e test this #30458

Closed
wants to merge 2 commits into from
Closed

Do not merge: Making a no op change to test @k8s-bot federation gce e2e test this #30458

wants to merge 2 commits into from

Conversation

nikhiljindal
Copy link
Contributor

@nikhiljindal nikhiljindal commented Aug 11, 2016 •
edited by k8s-oncall
Loading

Testing kubernetes/test-infra#335

This change is Reviewable

@nikhiljindal nikhiljindal self-assigned this Aug 11, 2016
@nikhiljindal
Copy link
Contributor Author

@k8s-bot federation gce e2e test this

@k8s-github-robot k8s-github-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. release-note-label-needed labels Aug 11, 2016
@nikhiljindal
Copy link
Contributor Author

Trying again after kubernetes/test-infra#379

@k8s-bot federation gce e2e test this

This was referenced Aug 15, 2016
Merged
Merged
Merged
@k8s-github-robot
Copy link

@nikhiljindal
You must link to the test flake issue which caused you to request this manual re-test.
Re-test requests should be in the form of: k8s-bot test this issue: #<number>
Here is the list of open test flakes.

@k8s-bot
Copy link

k8s-bot commented Aug 30, 2016

Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test".
(Note: "add to whitelist" is no longer supported. Please update configurations in kubernetes/test-infra/jenkins/job-configs/kubernetes-jenkins-pull instead.)

This message will repeat several times in short succession due to jenkinsci/ghprb-plugin#292. Sorry.

@nikhiljindal
Copy link
Contributor Author

Trying again after kubernetes/test-infra#465

@k8s-bot federation gce e2e test this

@k8s-github-robot k8s-github-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 30, 2016
@k8s-bot
Copy link

k8s-bot commented Sep 1, 2016

Can one of the admins verify that this patch is reasonable to test? If so, please reply "ok to test".
(Note: "add to whitelist" is no longer supported. Please update configurations in kubernetes/test-infra/jenkins/job-configs/kubernetes-jenkins-pull instead.)

This message will repeat several times in short succession due to jenkinsci/ghprb-plugin#292. Sorry.

@nikhiljindal
Copy link
Contributor Author

nikhiljindal commented Sep 2, 2016 •
edited
Loading

@k8s-bot federation gce e2e test this

Retrying after kubernetes/test-infra#470 (comment)

@nikhiljindal
Copy link
Contributor Author

@k8s-bot federation gce e2e test this

Retrying after kubernetes/test-infra#470 (comment)

@ixdy
Copy link
Member

ixdy commented Sep 6, 2016

@k8s-bot federation gce e2e test this

(this is probably gonna fail due to rebase, though.)

@ixdy
Copy link
Member

ixdy commented Sep 6, 2016

@nikhiljindal can you rebase, and also update federation/cluster/common.sh to add a gcloud auth list right after GCR repository detected. Using gcloud?

@nikhiljindal nikhiljindal removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 6, 2016
@nikhiljindal
Copy link
Contributor Author

Rebased and added gcloud auth list.

Rerunning federation e2e.

@k8s-bot federation gce e2e test this

@nikhiljindal
Copy link
Contributor Author

@k8s-bot federation gce e2e test this

Retrying after #32162

@nikhiljindal
Copy link
Contributor Author

@k8s-bot federation gce e2e test this

Retrying after increasing network quota (kubernetes/test-infra#470 (comment))

@nikhiljindal
Copy link
Contributor Author

@k8s-bot federation gce e2e test this

Retrying after enabling Cloud DNS API

@nikhiljindal
Copy link
Contributor Author

@k8s-bot federation gce e2e test this

Retrying after kubernetes/test-infra#529

@nikhiljindal
Copy link
Contributor Author

@k8s-bot federation gce e2e test this

Retrying after rebasing on #32545 and #32613

@nikhiljindal nikhiljindal added the do-not-merge DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed. label Sep 14, 2016
@k8s-bot
Copy link

k8s-bot commented Sep 14, 2016

GCE e2e build/test failed for commit 895e62a.

Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake.

@nikhiljindal
Copy link
Contributor Author

Jenkins Federation GCE e2e is still running.
Jenkins GCI Federation GCE e2e failed with:

Updating project ssh metadata...failed.
ERROR: (gcloud.compute.config-ssh) Could not add SSH key to project metadata:
 - Project k8s-jkns-pr-gci-bld-e2e-gce-fd cannot accept requests to setMetadata while in an inactive billing state.  Billing state may take several minutes to update.

Error response from daemon: no such id: kubernetes-pull-build-test-gci-federation-e2e-gce-1
Error: failed to stop containers: [kubernetes-pull-build-test-gci-federation-e2e-gce-1]

@vishh I assume you set up the project k8s-jkns-pr-gci-bld-e2e-gce-fd Looks like there is some issue with its billing state. Can you please take a look?

@vishh
Copy link
Contributor

vishh commented Sep 14, 2016

@mtaufen had set up the projects.

@mtaufen
Copy link
Contributor

mtaufen commented Sep 14, 2016

I'll take a look. I think I was added to the proper billing group for this, but I'll double check.

@mtaufen
Copy link
Contributor

mtaufen commented Sep 14, 2016

It looks like it needed me to manually set the correct billing account. I've no idea why it needed me to do this, as I created the project with a script which IIRC is supposed to set this up correctly. And other projects I created with that script yesterday did select the correct billing account.

@nikhiljindal
Copy link
Contributor Author

For "Jenkins Federation GCE e2e", all tests expect the following 2 tests passed:

[k8s.io] Federated ingresses [Feature:Federation] Federated Ingresses Ingress connectivity and DNS 
  should be able to connect to a federated ingress via its load balancer

[k8s.io] Federated ingresses [Feature:Federation] Federated Ingresses 
  should create and update matching ingresses in underlying clusters

@quinton-hoole Can you please take a look. They should be broken on HEAD as well.

@nikhiljindal nikhiljindal mentioned this pull request Sep 14, 2016
Merged
@nikhiljindal
Copy link
Contributor Author

@k8s-bot federation gce e2e test this

Retrying with increased timeout and also billing account fixes for GCI project.

@ghost
Copy link

ghost commented Sep 14, 2016

@nikhiljindal Sure, I'm on it.

@k8s-github-robot k8s-github-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 13, 2016
@k8s-github-robot
Copy link

@nikhiljindal PR needs rebase

@mtaufen
Copy link
Contributor

mtaufen commented Oct 20, 2016

@nikhiljindal Let's close this.

@k8s-github-robot
Copy link

This PR hasn't been active in 30 days. It will be closed in 59 days (Jan 18, 2017).

cc @nikhiljindal

You can add 'keep-open' label to prevent this from happening, or add a comment to keep it open another 90 days

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@nikhiljindal nikhiljindal

Labels
do-not-merge DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
7 participants
@nikhiljindal @k8s-github-robot @k8s-bot @ixdy @vishh @mtaufen @googlebot