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

Using fork of openshift/library-go #1097

Closed
mhenriks opened this issue Feb 5, 2020 · 12 comments · Fixed by #3336
Closed

Using fork of openshift/library-go #1097

mhenriks opened this issue Feb 5, 2020 · 12 comments · Fixed by #3336
Labels
kind/bug lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@mhenriks
Copy link
Member

mhenriks commented Feb 5, 2020

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind enhancement

What happened:

#1091 references a fork of openshift/library-go

Once the following PR is merged, CDI should go back the mainline:

openshift/library-go#540

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • CDI version (use kubectl get deployments cdi-deployment -o yaml):
  • Kubernetes version (use kubectl version):
  • Cloud provider or hardware configuration:
  • Install tools:
  • Others:
@kubevirt-bot
Copy link
Contributor

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.

/lifecycle stale

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 5, 2020
@kubevirt-bot
Copy link
Contributor

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.

/lifecycle rotten

@kubevirt-bot kubevirt-bot 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 Jun 4, 2020
@awels
Copy link
Member

awels commented Jun 4, 2020

/lifecycle frozen

@kubevirt-bot kubevirt-bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Jun 4, 2020
@awels
Copy link
Member

awels commented Jun 4, 2020

This still applies right @mhenriks

@aglitke
Copy link
Member

aglitke commented Feb 13, 2023

@mhenriks please take a look and see if we can make the needed methods public in openshift/library-go#540

@mhenriks
Copy link
Member Author

created openshift/library-go#1486

@alromeros
Copy link
Collaborator

created openshift/library-go#1486

Just lgtmed, hope we can merge it soon.

@alromeros
Copy link
Collaborator

alromeros commented Jan 29, 2024

Closing this since it's been addressed by openshift/library-go@434fa21. Feel free to reopen if necessary.

@akalenyu
Copy link
Collaborator

akalenyu commented May 2, 2024

/reopen
so we remember to get rid of the fork

@kubevirt-bot
Copy link
Contributor

@akalenyu: Reopened this issue.

In response to this:

/reopen
so we remember to get rid of the fork

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.

@kubevirt-bot kubevirt-bot reopened this May 2, 2024
@mhenriks
Copy link
Member Author

mhenriks commented May 3, 2024

thanks for the reminder @akalenyu

@mhenriks
Copy link
Member Author

mhenriks commented May 3, 2024

Unfortunately have to wait until we move to k8s 1.29 (release-4.16+ branch in library-go) to do this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
6 participants