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

MON-3689: Bump openshift/prometheus-operator to v0.71.2 #274

Merged
merged 5 commits into from Jan 26, 2024

Conversation

openshift-monitoring-bot[bot]
Copy link

Description

This is an automated version bump from CI.
The logs for this run can be found in the syncbot repo actions.
If you wish to perform this manually, execute the following commands from openshift/prometheus-operator repo:

git fetch https://github.com/prometheus-operator/prometheus-operator --tags
if ! git merge refs/tags/v0.71.2 --no-edit; then
  git checkout --theirs CHANGELOG.md Documentation VERSION bundle.yaml example go.mod go.sum pkg
  git checkout --ours 
  git add CHANGELOG.md Documentation VERSION bundle.yaml example go.mod go.sum pkg 
  git merge --continue
fi
go mod tidy
go mod vendor

if [ -f scripts/rh-manifest.sh ]; then
  bash scripts/rh-manifest.sh
  git add rh-manifest.txt
  git diff --cached --exit-code || git commit -s -m "[bot] update rh-manifest.txt"
fi

micborens and others added 5 commits January 25, 2024 14:39
* fix: typo on AuthenticationMethod check
Signed-off-by: Simon Pasquier <spasquie@redhat.com>
v0.71.2

# -----BEGIN PGP SIGNATURE-----
#
# iQIzBAABCAAdFiEE/jCAc0MNZY5toBt1AZCmbAoQ/E8FAmWydr0ACgkQAZCmbAoQ
# /E+zSw/9EWKp+DM/aFE+zFkxNh6pqUOvRqIOIC4PlX+uw9zoWhYVB05NXFtEQZDF
# ym1h1qeZkRcdg5wU9DURfMRYcU64op3zqepw3nrTE/J4V5q+LYYoTq8g5mMvb4Oj
# tpMuPzSaxv7uj2gsTEzkDSah+4LfwBVll8G+x/q3Mc3NXqqc7Ta+0vYKGoF6dOsL
# 5az4ERQHAVXVnGLlt95IKvGKDqcps9bGCF0WERXcmlSOhyhbqBloc+vwvrXqqnrA
# 1ELqJYwzm6bDsnr4+eBbnZI69Zl4EOA35ris9H+t8KiaabD0eWXNyy9A8j7ed8d5
# 721cN1OP5jD8yEhnIWb0RpDdXWYLMYe6xh8N24SKXZ+L7iuHFuLmBkOIXIoxUBhn
# wdfLOVokIbJFQBXBVYUlVI/eJtS7tSOQkwSPiqObzJqCT3vfcHzg8LqCS5x7p7Pe
# mblAZza+z1b8SY6xEHz7Y6LMkKdHqG+aVH3lP8l0UENGm8xLFPLSVnAY1QqkRlbQ
# pc+GBmQTBvwpD5NycMijREI47U+/qNzRJiyD5qPrpmWEpTudu3bfGHnk+XBqawcZ
# yatrLa8kVPAKcHCfBkTt4K5M4K3WvCUMx0huVfftVFTapT1zXTSFP1YpFVE7Mnin
# 2fQdXIWiLbgi/nnu3Ifrwl1D9JMlcyhilrPHRGFhBbfOHYgg1HI=
# =Z8lh
# -----END PGP SIGNATURE-----
# gpg: directory '/home/runner/.gnupg' created
# gpg: keybox '/home/runner/.gnupg/pubring.kbx' created
# gpg: Signature made Thu Jan 25 14:57:01 2024 UTC
# gpg:                using RSA key FE308073430D658E6DA01B750190A66C0A10FC4F
# gpg: Can't check signature: No public key
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@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 Jan 25, 2024
Copy link

openshift-ci bot commented Jan 25, 2024

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.

@simonpasquier
Copy link

/ok-to-test
/lgtm
/approve

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jan 26, 2024
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 26, 2024
Copy link

openshift-ci bot commented Jan 26, 2024

[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

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

@simonpasquier
Copy link

simonpasquier commented Jan 26, 2024

/retitle MON-3689: Bump openshift/prometheus-operator to v0.71.2

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 26, 2024
@openshift-ci openshift-ci bot changed the title [bot] Bump openshift/prometheus-operator to v0.71.2 MON-3689: Bump openshift/prometheus-operator to v0.71.2 Jan 26, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 26, 2024

@openshift-monitoring-bot[bot]: This pull request references MON-3689 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.16.0" version, but no target version was set.

In response to this:

Description

This is an automated version bump from CI.
The logs for this run can be found in the syncbot repo actions.
If you wish to perform this manually, execute the following commands from openshift/prometheus-operator repo:

git fetch https://github.com/prometheus-operator/prometheus-operator --tags
if ! git merge refs/tags/v0.71.2 --no-edit; then
 git checkout --theirs CHANGELOG.md Documentation VERSION bundle.yaml example go.mod go.sum pkg
 git checkout --ours 
 git add CHANGELOG.md Documentation VERSION bundle.yaml example go.mod go.sum pkg 
 git merge --continue
fi
go mod tidy
go mod vendor

if [ -f scripts/rh-manifest.sh ]; then
 bash scripts/rh-manifest.sh
 git add rh-manifest.txt
 git diff --cached --exit-code || git commit -s -m "[bot] update rh-manifest.txt"
fi

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 26, 2024
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD a1e0fcf and 2 for PR HEAD d9d8f7e in total

@simonpasquier
Copy link

/test e2e-agnostic-cmo

Copy link

openshift-ci bot commented Jan 26, 2024

@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/security d9d8f7e link false /test security

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 39566f5 into openshift:master Jan 26, 2024
7 of 8 checks passed
@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

This PR has been included in build prometheus-operator-admission-webhook-container-v4.16.0-202401272017.p0.g39566f5.assembly.stream for distgit prometheus-operator-admission-webhook.
All builds following this will include this PR.

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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants