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

bump kubevirt-ipam-controller to v0.1.3-alpha #1830

Closed

Conversation

kubevirt-bot
Copy link
Collaborator

bump kubevirt-ipam-controller to v0.1.3-alpha
Executed by Bumper script

bump kubevirt-ipam-controller to v0.1.3-alpha

Signed-off-by: CNAO Bump Bot <noreply@github.com>
@kubevirt-bot kubevirt-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Jul 23, 2024
@kubevirt-bot
Copy link
Collaborator Author

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign qinqon for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found 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

Copy link

sonarcloud bot commented Jul 23, 2024

@oshoval
Copy link
Collaborator

oshoval commented Jul 23, 2024

/hold

we have this instead, that does the same + updating the bump script to add more
#1829
basically they shouldn't conflict, but we dont need both

for some reason this one is broken, maybe skopeo failed to fetch the hash
but when i ran manually it worked (i believe that running it again on the automation will work, but we dont need)
CNAO_VERSION=99.0.0 ./hack/components/bump-kubevirt-ipam-controller.sh
(maybe the tag was released before the images ? exactly when the bumper ran on CI)

this flow will happen just now because i extended the bump script
next time it will be automatic as it was before

validated manually that the changes i did to components.yaml are the same done here

@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 Jul 23, 2024
@kubevirt-bot
Copy link
Collaborator Author

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

Test name Commit Details Required Rerun command
pull-e2e-cnao-multus-dynamic-networks-functests fc8a5e0 link true /test pull-e2e-cnao-multus-dynamic-networks-functests
pull-e2e-cluster-network-addons-operator-multus-functests fc8a5e0 link true /test pull-e2e-cluster-network-addons-operator-multus-functests
pull-e2e-cnao-kube-secondary-dns-functests fc8a5e0 link true /test pull-e2e-cnao-kube-secondary-dns-functests
pull-e2e-cluster-network-addons-operator-kubemacpool-functests fc8a5e0 link true /test pull-e2e-cluster-network-addons-operator-kubemacpool-functests
pull-e2e-cluster-network-addons-operator-ovs-cni-functests fc8a5e0 link true /test pull-e2e-cluster-network-addons-operator-ovs-cni-functests
pull-e2e-cluster-network-addons-operator-br-marker-functests fc8a5e0 link true /test pull-e2e-cluster-network-addons-operator-br-marker-functests
pull-e2e-cluster-network-addons-operator-macvtap-cni-functests fc8a5e0 link true /test pull-e2e-cluster-network-addons-operator-macvtap-cni-functests
pull-e2e-cluster-network-addons-operator-workflow-k8s fc8a5e0 link true /test pull-e2e-cluster-network-addons-operator-workflow-k8s
pull-e2e-cluster-network-addons-operator-lifecycle-k8s fc8a5e0 link true /test pull-e2e-cluster-network-addons-operator-lifecycle-k8s

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.

@oshoval
Copy link
Collaborator

oshoval commented Jul 24, 2024

/close

@oshoval oshoval closed this Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants