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

[bot] Update jsonnet dependencies #1805

Conversation

openshift-monitoring-bot[bot]
Copy link

Description

This pull request updates all jsonnet dependencies listed in jsonnet/jsonnetfile.json to their latest versions and regenerates all assets.

If you wish to perform this manually, execute the following commands from the cluster-monitoring-operator repository:

make update
make generate

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 24, 2022

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.

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/test-infra repository.

@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Oct 24, 2022
@jan--f
Copy link
Contributor

jan--f commented Oct 24, 2022

/ok-to-test
/lgtm
/label docs-approved
/label px-approved
/label qe-approved
Adding labels for a simple version bump.

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. docs-approved Signifies that Docs has signed off on this PR px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 24, 2022
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 24, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 24, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jan--f, openshift-monitoring-bot[bot]

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 24, 2022
Copy link
Contributor

@simonpasquier simonpasquier left a comment

Choose a reason for hiding this comment

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

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 24, 2022
@@ -31,7 +31,7 @@ spec:
expr: |
sum by (namespace, pod, cluster) (
max by(namespace, pod, cluster) (
kube_pod_status_phase{namespace=~"(openshift-.*|kube-.*|default)",job="kube-state-metrics", phase=~"Pending|Unknown"}
kube_pod_status_phase{namespace=~"(openshift-.*|kube-.*|default)",job="kube-state-metrics", phase=~"Pending|Unknown|Failed"}
Copy link
Contributor

Choose a reason for hiding this comment

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

we don't want to merge this change because of https://issues.redhat.com/browse/TRT-589

@monitoring-commit-bot monitoring-commit-bot bot force-pushed the automated-updates-master-update-generate branch from 6ac3103 to 4161469 Compare October 31, 2022 00:43
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 31, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 31, 2022

New changes are detected. LGTM label has been removed.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 19, 2022
@monitoring-commit-bot monitoring-commit-bot bot force-pushed the automated-updates-master-update-generate branch from 4161469 to d4ac8e6 Compare November 21, 2022 00:36
@openshift-merge-robot openshift-merge-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Nov 21, 2022
@raptorsun
Copy link
Contributor

we can close this one when #1818 has been merged.

@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 28, 2022
@monitoring-commit-bot monitoring-commit-bot bot force-pushed the automated-updates-master-update-generate branch from 17b109a to bb7794f Compare December 5, 2022 00:30
@monitoring-commit-bot monitoring-commit-bot bot force-pushed the automated-updates-master-update-generate branch from bb7794f to f5a0dd7 Compare December 19, 2022 00:28
@monitoring-commit-bot monitoring-commit-bot bot force-pushed the automated-updates-master-update-generate branch from f5a0dd7 to 0a2cb31 Compare December 26, 2022 00:30
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@monitoring-commit-bot monitoring-commit-bot bot force-pushed the automated-updates-master-update-generate branch from 0a2cb31 to e0cdf5a Compare January 2, 2023 00:30
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 2, 2023

@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/versions e0cdf5a link false /test versions

Full PR test history. Your PR dashboard.

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

@jan--f
Copy link
Contributor

jan--f commented Jan 2, 2023

@raptorsun #1818 was merged, should this PR be closed now?

@raptorsun
Copy link
Contributor

@raptorsun #1818 was merged, should this PR be closed now?

Yes, Let's
/close
this PR :)

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 3, 2023

@raptorsun: Closed this PR.

In response to this:

@raptorsun #1818 was merged, should this PR be closed now?

Yes, Let's
/close
this PR :)

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/test-infra repository.

@openshift-ci openshift-ci bot closed this Jan 3, 2023
@simonpasquier simonpasquier deleted the automated-updates-master-update-generate branch January 3, 2023 13:11
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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. docs-approved Signifies that Docs has signed off on this PR ok-to-test Indicates a non-member PR verified by an org member that is safe to test. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants