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

Kettle google-cloud-sdk should not need force pinning. #19414

Closed
MushuEE opened this issue Sep 30, 2020 · 14 comments
Closed

Kettle google-cloud-sdk should not need force pinning. #19414

MushuEE opened this issue Sep 30, 2020 · 14 comments
Assignees
@MushuEE
Labels
area/kettle kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Milestone
v1.21

Comments

@MushuEE
Copy link
Contributor

MushuEE commented Sep 30, 2020

What should be cleaned up or changed:
#19369 was added to deal with #19365

BigQuery error in load operation: Could not connect with BigQuery server due to:
RedirectMissingLocation('Redirected but the response is missing a Location:
header.',)

The pinning of the version should be a short term fix.

Provide any links for context:
@MushuEE MushuEE added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Sep 30, 2020
@MushuEE
Copy link
Contributor Author

MushuEE commented Sep 30, 2020

/assign
/area kettle

@MushuEE MushuEE mentioned this issue Sep 30, 2020
Merged
@MushuEE
Copy link
Contributor Author

MushuEE commented Sep 30, 2020

Revert #19415 on close

@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 30, 2020
@BenTheElder
Copy link
Member

🛸 scanning for signs of life 🛸

@MushuEE
Copy link
Contributor Author

MushuEE commented Jan 6, 2021

This will take a little digging, but I will circle back. I found this issue even internal.
/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 6, 2021
@MushuEE MushuEE mentioned this issue Mar 2, 2021
Merged
@fejta-bot
Copy link

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-contributor-experience at kubernetes/community.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 6, 2021
@fejta-bot
Copy link

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-contributor-experience at kubernetes/community.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 6, 2021
@fejta-bot
Copy link

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-contributor-experience at kubernetes/community.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

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-contributor-experience at kubernetes/community.
/close

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.

@BenTheElder
Copy link
Member

#21120 actually fixed here I think?

@BenTheElder BenTheElder added sig/testing Categorizes an issue or PR as relevant to SIG Testing. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Jun 18, 2021
@MushuEE
Copy link
Contributor Author

MushuEE commented Jun 22, 2021

@BenTheElder Correct I believe it no longer needs to be back pinned as the issue was fixed.

@spiffxp
Copy link
Member

spiffxp commented Jul 13, 2021

/milestone v1.21

@k8s-ci-robot
Copy link
Contributor

@spiffxp: The provided milestone is not valid for this repository. Milestones in this repository: [someday, v1.22, v1.23]

Use /milestone clear to clear the milestone.

In response to this:

/milestone v1.21

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.

@spiffxp
Copy link
Member

spiffxp commented Jul 13, 2021

/milestone v1.21

@k8s-ci-robot k8s-ci-robot added this to the v1.21 milestone Jul 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@MushuEE MushuEE

Labels
area/kettle kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Projects
None yet
Milestone
v1.21
Development

No branches or pull requests
5 participants
@spiffxp @BenTheElder @MushuEE @k8s-ci-robot @fejta-bot