search

openshift / cluster-monitoring-operator

Manage the OpenShift monitoring stack
Apache License 2.0
247 stars 360 forks source link

[release-4.16] OCPBUGS-34530: inject trusted CA bundle into UWM Alertmanager #2373

Closed simonpasquier closed 2 months ago

simonpasquier commented 3 months ago

Manual cherry-pick of #2349

simonpasquier commented 3 months ago

/jira cherrypick OCPBUGS-33686

openshift-ci-robot commented 3 months ago

@simonpasquier: Jira Issue OCPBUGS-33686 has been cloned as Jira Issue OCPBUGS-34529. Will retitle bug to link to clone. /retitle OCPBUGS-34529: OCPBUGS-xxx: inject trusted CA bundle into UWM Alertmanager

In response to [this](https://github.com/openshift/cluster-monitoring-operator/pull/2373#issuecomment-2134688539): >/jira cherrypick OCPBUGS-33686 Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-monitoring-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
openshift-ci-robot commented 3 months ago

@simonpasquier: This pull request references Jira Issue OCPBUGS-34529, which is invalid:

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to [this](https://github.com/openshift/cluster-monitoring-operator/pull/2373): >Manual cherry-pick of #2349 Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-monitoring-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
simonpasquier commented 3 months ago

/jira cherrypick OCPBUGS-33645

openshift-ci-robot commented 3 months ago

@simonpasquier: Jira Issue OCPBUGS-33645 has been cloned as Jira Issue OCPBUGS-34530. Will retitle bug to link to clone. /retitle OCPBUGS-34530: [release-4.16] OCPBUGS-34529: inject trusted CA bundle into UWM Alertmanager

In response to [this](https://github.com/openshift/cluster-monitoring-operator/pull/2373#issuecomment-2134692941): >/jira cherrypick OCPBUGS-33645 Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-monitoring-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
openshift-ci-robot commented 3 months ago

@simonpasquier: This pull request references Jira Issue OCPBUGS-34530, which is invalid:

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to [this](https://github.com/openshift/cluster-monitoring-operator/pull/2373): >Manual cherry-pick of #2349 Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-monitoring-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
simonpasquier commented 3 months ago

/jira refresh

openshift-ci-robot commented 3 months ago

@simonpasquier: This pull request references Jira Issue OCPBUGS-34530, which is invalid:

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to [this](https://github.com/openshift/cluster-monitoring-operator/pull/2373#issuecomment-2134696358): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-monitoring-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
simonpasquier commented 3 months ago

/jira refresh

openshift-ci-robot commented 3 months ago

@simonpasquier: This pull request references Jira Issue OCPBUGS-34530, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug * bug is open, matching expected state (open) * bug target version (4.16.0) matches configured target version for branch (4.16.0) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST) * release note text is set and does not match the template * dependent bug [Jira Issue OCPBUGS-33645](https://issues.redhat.com//browse/OCPBUGS-33645) is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED) * dependent [Jira Issue OCPBUGS-33645](https://issues.redhat.com//browse/OCPBUGS-33645) targets the "4.17.0" version, which is one of the valid target versions: 4.17.0 * bug has dependents

Requesting review from QA contact: /cc @juzhao

In response to [this](https://github.com/openshift/cluster-monitoring-operator/pull/2373#issuecomment-2134711345): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-monitoring-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
simonpasquier commented 3 months ago

/hold

this can wait after 4.16 GA.

juzhao commented 3 months ago

/jira refresh

openshift-ci-robot commented 3 months ago

@juzhao: This pull request references Jira Issue OCPBUGS-34530, which is valid.

7 validation(s) were run on this bug * bug is open, matching expected state (open) * bug target version (4.16.0) matches configured target version for branch (4.16.0) * bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST) * release note text is set and does not match the template * dependent bug [Jira Issue OCPBUGS-33645](https://issues.redhat.com//browse/OCPBUGS-33645) is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED) * dependent [Jira Issue OCPBUGS-33645](https://issues.redhat.com//browse/OCPBUGS-33645) targets the "4.17.0" version, which is one of the valid target versions: 4.17.0 * bug has dependents

Requesting review from QA contact: /cc @juzhao

In response to [this](https://github.com/openshift/cluster-monitoring-operator/pull/2373#issuecomment-2134857543): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-monitoring-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
simonpasquier commented 3 months ago

/label backport-risk-assessed

simonpasquier commented 2 months ago

/jira refresh

openshift-ci-robot commented 2 months ago

@simonpasquier: This pull request references Jira Issue OCPBUGS-34530, which is valid.

7 validation(s) were run on this bug * bug is open, matching expected state (open) * bug target version (4.16.0) matches configured target version for branch (4.16.0) * bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST) * release note text is set and does not match the template * dependent bug [Jira Issue OCPBUGS-33645](https://issues.redhat.com//browse/OCPBUGS-33645) is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED) * dependent [Jira Issue OCPBUGS-33645](https://issues.redhat.com//browse/OCPBUGS-33645) targets the "4.17.0" version, which is one of the valid target versions: 4.17.0 * bug has dependents

Requesting review from QA contact: /cc @juzhao

In response to [this](https://github.com/openshift/cluster-monitoring-operator/pull/2373#issuecomment-2194099772): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-monitoring-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
simonpasquier commented 2 months ago

/hold cancel

marioferh commented 2 months ago

/retest-required

openshift-ci[bot] commented 2 months ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: marioferh, 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: - ~~[OWNERS](https://github.com/openshift/cluster-monitoring-operator/blob/release-4.16/OWNERS)~~ [marioferh,simonpasquier] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
juzhao commented 2 months ago

/label cherry-pick-approved /label qe-approved

openshift-ci[bot] commented 2 months ago

@simonpasquier: 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 e6ec598411a8b1487efed06c7167afed7218b862 link false /test e2e-aws-ovn-single-node

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
openshift-ci-robot commented 2 months ago

/retest-required

Remaining retests: 0 against base HEAD 5b1d12e7ad23eaafd8fce3e23d0a9d814313259e and 2 for PR HEAD e6ec598411a8b1487efed06c7167afed7218b862 in total

openshift-ci-robot commented 2 months ago

@simonpasquier: Jira Issue OCPBUGS-34530: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-34530 has been moved to the MODIFIED state.

In response to [this](https://github.com/openshift/cluster-monitoring-operator/pull/2373): >Manual cherry-pick of #2349 Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-monitoring-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
openshift-bot commented 2 months ago

[ART PR BUILD NOTIFIER]

This PR has been included in build cluster-monitoring-operator-container-v4.16.0-202406280629.p0.gbe8e0da.assembly.stream.el9 for distgit cluster-monitoring-operator. All builds following this will include this PR.

simonpasquier commented 2 months ago

/cherry-pick release-4.15

simonpasquier commented 2 months ago

/cherrypick release-4.15

openshift-cherrypick-robot commented 2 months ago

@simonpasquier: new pull request created: #2399

In response to [this](https://github.com/openshift/cluster-monitoring-operator/pull/2373#issuecomment-2196484490): >/cherry-pick release-4.15 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
openshift-cherrypick-robot commented 2 months ago

@simonpasquier: new pull request could not be created: failed to create pull request against openshift/cluster-monitoring-operator#release-4.15 from head openshift-cherrypick-robot:cherry-pick-2373-to-release-4.15: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-2373-to-release-4.15."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

In response to [this](https://github.com/openshift/cluster-monitoring-operator/pull/2373#issuecomment-2196485394): >/cherrypick release-4.15 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.