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

[release-v0.4] fix: Fix owner references in created resources #119

Merged
merged 1 commit into from
Apr 8, 2024

Conversation

akrejcir
Copy link
Collaborator

@akrejcir akrejcir commented Apr 2, 2024

Manual cherry-pick of: #101

The manual change is in the test code, so that it compiles with older gomega and kubevirt.io/client-go.

Release note:

None

@kubevirt-bot kubevirt-bot added release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Apr 2, 2024
@0xFelix
Copy link
Member

0xFelix commented Apr 2, 2024

Same comment as on #120:

Can you put a list of conflicting files and a note explaining the required changes into the commit message? (e.g. what you wrote in the PR description)

Now the resources will be correctly cleaned up after the VM
is deleted.

This is a cherry-pick of e1edce9.

There were conflicts in the `tests/proxy_test.go` file, because
this branch uses older versions of `gomega` and `kubevirt.io/client-go`
modules.

Signed-off-by: Andrej Krejcir <akrejcir@redhat.com>
@akrejcir
Copy link
Collaborator Author

akrejcir commented Apr 4, 2024

Same comment as on #120:

Can you put a list of conflicting files and a note explaining the required changes into the commit message? (e.g. what you wrote in the PR description)

Done

Copy link
Member

@0xFelix 0xFelix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you very much!

/approve

@kubevirt-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 0xFelix

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 4, 2024
@akrejcir
Copy link
Collaborator Author

akrejcir commented Apr 8, 2024

/retest

@akrejcir
Copy link
Collaborator Author

akrejcir commented Apr 8, 2024

/cc @ksimon1 @jcanocan

@jcanocan
Copy link

jcanocan commented Apr 8, 2024

/lgtm

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Apr 8, 2024
@kubevirt-bot kubevirt-bot merged commit 5947f0f into kubevirt:release-v0.4 Apr 8, 2024
4 of 5 checks passed
@akrejcir akrejcir deleted the fix-cleanup-0.4 branch April 9, 2024 13:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants