fix: dependency in prom-rules-verify make target

[nestoracunablanco]

This target needs that the necessary tooling is available beforehand.

What this PR does / why we need it: makefile minor fixes

Special notes for your reviewer:

Release note:

[kubevirt-bot]

Hi @nestoracunablanco. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

[nestoracunablanco]

@RamLavi @phoracek What are your thoughts on this change? Do you require any additional modifications or clarifications?

[RamLavi]

/ok-to-test

[nestoracunablanco]

/test all

[kubevirt-bot]

@nestoracunablanco: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test all

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.

[nestoracunablanco]

Hi @RamLavi, It seems that I'm unable to trigger the tests. Could someone else please trigger them?

[RamLavi]

/ok-to-test

[RamLavi]

/lgtm

[nestoracunablanco]

/test all

[kubevirt-bot]

@nestoracunablanco: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test all

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.

[RamLavi]

/ok-to-test

@nestoracunablanco can you rebase? it would probably solve the IPAM lane issue

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[RamLavi]

/lgtm

[nestoracunablanco]

/retest

[kubevirt-bot]

@nestoracunablanco: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[RamLavi]

@nestoracunablanco looks like a metrics-relevant test failed on the kubemacpool tier1 lane.

E2E Test Suite: [It] [rfe_id:3503][crit:medium][vendor:[email protected]][level:component]Virtual Machines Check the client When all the VMs are serviced by default (opt-out mode) and creating two VMs with same mac, one on unmanaged (opted out) namespace should detect duplicate macs gauge after restarting kubemacpool, and then mitigating that

Can you take a look to see if it's related?

[nestoracunablanco]

@RamLavi, I ran the kubemacpool functional tests on my workstation, and they were successful.

Since the change pertains only to the verification of the Prometheus rules and is related to the build process (with no code modifications that could impact runtime), I do not see a connection between this change and the error.

[nestoracunablanco]

@RamLavi, based on the information I provided, do you have any issues with rerunning the pull-e2e-cluster-network-addons-operator-kubemacpool-functests?

[RamLavi]

/test pull-e2e-cluster-network-addons-operator-kubemacpool-functests

[nestoracunablanco]

@RamLavi, all tests are successful now. Is there anything else needed for approval?

[RamLavi]

/approve

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RamLavi

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:

• OWNERS [RamLavi]

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

[RamLavi]

/retest
seems unrelated. will open an issue separately