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

CM Stackdriver Adapter e2e test is failing all the time #53800

Closed
piosz opened this Issue Oct 12, 2017 · 17 comments

Comments

Projects
None yet
7 participants
@piosz

This comment has been minimized.

Show comment
Hide comment
@piosz
Member

piosz commented Oct 12, 2017

@cmluciano

This comment has been minimized.

Show comment
Hide comment
Member

cmluciano commented Oct 31, 2017

@crassirostris

This comment has been minimized.

Show comment
Hide comment
@crassirostris

crassirostris Oct 31, 2017

Member

That's a different issue, google cloud project is misconfigured

/cc @fejta @krzyzacy

Member

crassirostris commented Oct 31, 2017

That's a different issue, google cloud project is misconfigured

/cc @fejta @krzyzacy

@krzyzacy

This comment has been minimized.

Show comment
Hide comment
@krzyzacy

krzyzacy Oct 31, 2017

Member

@cmluciano why a sig-network test need to run stackdriver test?

Member

krzyzacy commented Oct 31, 2017

@cmluciano why a sig-network test need to run stackdriver test?

@crassirostris

This comment has been minimized.

Show comment
Hide comment
@crassirostris

crassirostris Oct 31, 2017

Member

@krzyzacy These are basic tests which guarantee that no feature breaks logging on GCE/GKE, so it's OK

Member

crassirostris commented Oct 31, 2017

@krzyzacy These are basic tests which guarantee that no feature breaks logging on GCE/GKE, so it's OK

@cmluciano

This comment has been minimized.

Show comment
Hide comment
@cmluciano
Member

cmluciano commented Oct 31, 2017

@krzyzacy

This comment has been minimized.

Show comment
Hide comment
@krzyzacy

krzyzacy Oct 31, 2017

Member

ah, it's running under it's own peoject k8s-jenkins-gce-gci-ip-aliases rather than fetching from the pool, I'll find owner of the project as I don't have permission to configure it

Member

krzyzacy commented Oct 31, 2017

ah, it's running under it's own peoject k8s-jenkins-gce-gci-ip-aliases rather than fetching from the pool, I'll find owner of the project as I don't have permission to configure it

@cmluciano

This comment has been minimized.

Show comment
Hide comment
@cmluciano

cmluciano Oct 31, 2017

Member

@cmluciano why a sig-network test need to run stackdriver test?

Good question, I'm not 100% sure so I'll defer to @crassirostris 's answer.

I'm just trying to deflake sig-net's dashboard :P

Member

cmluciano commented Oct 31, 2017

@cmluciano why a sig-network test need to run stackdriver test?

Good question, I'm not 100% sure so I'll defer to @crassirostris 's answer.

I'm just trying to deflake sig-net's dashboard :P

@krzyzacy

This comment has been minimized.

Show comment
Hide comment
@krzyzacy

krzyzacy Oct 31, 2017

Member

/assign

Member

krzyzacy commented Oct 31, 2017

/assign

@krzyzacy

This comment has been minimized.

Show comment
Hide comment
@krzyzacy

krzyzacy Oct 31, 2017

Member

@crassirostris btw I'm not sure why it fails in the gke job

Member

krzyzacy commented Oct 31, 2017

@crassirostris btw I'm not sure why it fails in the gke job

@krzyzacy

This comment has been minimized.

Show comment
Hide comment
@krzyzacy

krzyzacy Oct 31, 2017

Member

Added the required roles, waiting for result from next run

Member

krzyzacy commented Oct 31, 2017

Added the required roles, waiting for result from next run

@crassirostris

This comment has been minimized.

Show comment
Hide comment
@crassirostris

crassirostris Oct 31, 2017

Member

@krzyzacy As I've mentioned, the original issue is unrelated

Member

crassirostris commented Oct 31, 2017

@krzyzacy As I've mentioned, the original issue is unrelated

@crassirostris

This comment has been minimized.

Show comment
Hide comment
@crassirostris
Member

crassirostris commented Oct 31, 2017

@krzyzacy Thanks!

@krzyzacy

This comment has been minimized.

Show comment
Hide comment
@krzyzacy

krzyzacy Nov 2, 2017

Member

/unassign
https://k8s-testgrid.appspot.com/google-gce#gci-gce-ip-alias
the test is green now for ip-alias job

Member

krzyzacy commented Nov 2, 2017

/unassign
https://k8s-testgrid.appspot.com/google-gce#gci-gce-ip-alias
the test is green now for ip-alias job

@fejta-bot

This comment has been minimized.

Show comment
Hide comment
@fejta-bot

fejta-bot Feb 7, 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot commented Feb 7, 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@fejta-bot

This comment has been minimized.

Show comment
Hide comment
@fejta-bot

fejta-bot Mar 9, 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

fejta-bot commented Mar 9, 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

@fejta-bot

This comment has been minimized.

Show comment
Hide comment
@fejta-bot

fejta-bot Apr 8, 2018

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot commented Apr 8, 2018

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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