Closed openshift-monitoring-bot[bot] closed 2 months ago
Hi @openshift-monitoring-bot[bot]. Thanks for your PR.
I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
/ok-to-test /lgtm /approve
/retitle MON-3982: [bot] Synchronize versions of the downstream components
@openshift-monitoring-bot[bot]: This pull request references MON-3982 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.18.0" version, but no target version was set.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: openshift-monitoring-bot[bot], simonpasquier
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/retest-required
Remaining retests: 0 against base HEAD ea4fce3568fd46e7e82fa17356e47c903584fee5 and 2 for PR HEAD d919a2321518645714c83e8101721fb349ad78f6 in total
@openshift-monitoring-bot[bot]: 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 |
---|---|---|---|---|
ci/prow/e2e-aws-ovn-single-node | d919a2321518645714c83e8101721fb349ad78f6 | link | false | /test e2e-aws-ovn-single-node |
Full PR test history. Your PR dashboard.
[ART PR BUILD NOTIFIER]
Distgit: cluster-monitoring-operator This PR has been included in build cluster-monitoring-operator-container-v4.18.0-202408201312.p0.g86aa090.assembly.stream.el9. All builds following this will include this PR.
Description
This pull request updates
jsonnet/versions.yaml
to match with the already in use downstream versions of the monitoring components.Based on that file, it regenerates the assets to update some metadata (mainly the
app.kubernetes.io/version
annotation) attached to some of the resources and update other placeholders.It is safe to merge this change (provided that the CI jobs pass).
If you wish to perform this manually, execute the following commands from cluster-monitoring-operator repository: