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

chore: Cleanup old manifests #1356

Merged
merged 10 commits into from
Jan 29, 2025

Conversation

brianmcarey
Copy link
Member

@brianmcarey brianmcarey commented Jan 22, 2025

What this PR does / why we need it:

These manifests have been copied to gocli and they are now applied from there. These manifests were a leftover and should be cleaned up.

I have included links in the commits to the new location for each of these manifests.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

Release note:


@kubevirt-bot
Copy link
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@kubevirt-bot kubevirt-bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Jan 22, 2025
@brianmcarey
Copy link
Member Author

/test check-provision-k8s-1.31

@brianmcarey
Copy link
Member Author

/test check-provision-k8s-1.31

1 similar comment
@brianmcarey
Copy link
Member Author

/test check-provision-k8s-1.31

@kubevirt-bot kubevirt-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 25, 2025
@dhiller
Copy link
Contributor

dhiller commented Jan 27, 2025

/cc

@kubevirt-bot kubevirt-bot requested a review from dhiller January 27, 2025 10:50
@brianmcarey brianmcarey force-pushed the cleanup-old-manifests branch from d84be2f to 6713bbb Compare January 28, 2025 08:25
@kubevirt-bot kubevirt-bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 28, 2025
@brianmcarey brianmcarey marked this pull request as ready for review January 28, 2025 14:37
@kubevirt-bot kubevirt-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 28, 2025
@dosubot dosubot bot added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Jan 28, 2025
@kubevirt-bot kubevirt-bot requested a review from ormergi January 28, 2025 14:37
@brianmcarey
Copy link
Member Author

@dhiller rebased and should be ready for review.

@kubevirt-bot kubevirt-bot requested a review from qinqon January 28, 2025 14:37
@kubevirt-bot
Copy link
Contributor

kubevirt-bot commented Jan 28, 2025

@brianmcarey: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
check-provision-k8s-1.31-s390x 6713bbb link false /test check-provision-k8s-1.31-s390x

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-sigs/prow repository. I understand the commands that are listed here.

cp -rf /tmp/cdi*.yaml /opt/

# copy aaq manifests
cp -rf /tmp/aaq/ /opt/
Copy link
Contributor

Choose a reason for hiding this comment

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

In the check-provision I don't see the aaq deployed, at least the flag is set to false. Is that tested somewhere else?

Copy link
Contributor

Choose a reason for hiding this comment

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

@Barakmor1 do you know? Maybe we can check that part by just enabling the flag on the provision-check or is there something that speaks against this?

Copy link
Contributor

@dhiller dhiller left a comment

Choose a reason for hiding this comment

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

/approve

@Barakmor1 if it's worth it we should make sure we test the aaq deployment somehow

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Jan 29, 2025
@kubevirt-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhiller

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 Jan 29, 2025
@kubevirt-bot kubevirt-bot merged commit 02ffdf4 into kubevirt:main Jan 29, 2025
10 of 11 checks passed
@Barakmor1
Copy link
Member

/hold

@kubevirt-bot kubevirt-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 29, 2025
@Barakmor1
Copy link
Member

@brianmcarey @dhiller Please give me a chance to have a look

@Barakmor1
Copy link
Member

Honestly, I think this was merged too fast. I didn't have enough time to review, but the AAQ deployment was useful for manual testing.

kubevirt-bot added a commit to kubevirt-bot/kubevirt that referenced this pull request Jan 29, 2025
[02ffdf4 chore: Cleanup old manifests](kubevirt/kubevirtci#1356)
[a1574f9 nfs-csi: Increase timeout for pvc to reach bound state](kubevirt/kubevirtci#1359)
[3da6ba3 provision: Clean up old images from extra-pre-pull-images](kubevirt/kubevirtci#1357)

```release-note
NONE
```

Signed-off-by: kubevirt-bot <[email protected]>
kubevirt-bot added a commit to kubevirt-bot/kubevirt that referenced this pull request Jan 30, 2025
[02ffdf4 chore: Cleanup old manifests](kubevirt/kubevirtci#1356)
[a1574f9 nfs-csi: Increase timeout for pvc to reach bound state](kubevirt/kubevirtci#1359)
[3da6ba3 provision: Clean up old images from extra-pre-pull-images](kubevirt/kubevirtci#1357)

```release-note
NONE
```

Signed-off-by: kubevirt-bot <[email protected]>
kubevirt-bot added a commit to kubevirt-bot/kubevirt that referenced this pull request Jan 30, 2025
[36f1f62 Automatic bump of CentOS Stream to latest](kubevirt/kubevirtci#1360)
[02ffdf4 chore: Cleanup old manifests](kubevirt/kubevirtci#1356)
[a1574f9 nfs-csi: Increase timeout for pvc to reach bound state](kubevirt/kubevirtci#1359)
[3da6ba3 provision: Clean up old images from extra-pre-pull-images](kubevirt/kubevirtci#1357)

```release-note
NONE
```

Signed-off-by: kubevirt-bot <[email protected]>
nirdothan pushed a commit to nirdothan/kubevirt that referenced this pull request Feb 1, 2025
[36f1f62 Automatic bump of CentOS Stream to latest](kubevirt/kubevirtci#1360)
[02ffdf4 chore: Cleanup old manifests](kubevirt/kubevirtci#1356)
[a1574f9 nfs-csi: Increase timeout for pvc to reach bound state](kubevirt/kubevirtci#1359)
[3da6ba3 provision: Clean up old images from extra-pre-pull-images](kubevirt/kubevirtci#1357)

```release-note
NONE
```

Signed-off-by: kubevirt-bot <[email protected]>
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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. size/XXL
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants