search

openshift / cluster-kube-apiserver-operator

The kube-apiserver operator installs and maintains the kube-apiserver on a cluster
Apache License 2.0
74 stars 159 forks source link

OCPBUGS-24005: when skipping a webhook check because of missing CA log the name of the webhook #1632

Closed p0lyn0mial closed 10 months ago

p0lyn0mial commented 10 months ago

for easier troubleshooting when a check is skipped because service-ca hasn't provided a CA for the webook we should also log the name of the webhook.

openshift-ci-robot commented 10 months ago

@p0lyn0mial: This pull request explicitly references no jira issue.

In response to [this](https://github.com/openshift/cluster-kube-apiserver-operator/pull/1632): >for easier troubleshooting when a check is skipped because `service-ca` hasn't provided a CA for the webook we should also log the name of the webhook. Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-kube-apiserver-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 10 months ago

@p0lyn0mial: This pull request references Jira Issue OCPBUGS-24005, 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-kube-apiserver-operator/pull/1632): >for easier troubleshooting when a check is skipped because `service-ca` hasn't provided a CA for the webook we should also log the name of the webhook. Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-kube-apiserver-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.
p0lyn0mial commented 10 months ago

/assign @sanchezl

p0lyn0mial commented 10 months ago

/jira refresh

openshift-ci-robot commented 10 months ago

@p0lyn0mial: This pull request references Jira Issue OCPBUGS-24005, which is valid.

3 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)

Requesting review from QA contact: /cc @gangwgr

In response to [this](https://github.com/openshift/cluster-kube-apiserver-operator/pull/1632#issuecomment-1908152723): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-kube-apiserver-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[bot] commented 10 months ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: p0lyn0mial, sanchezl

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-kube-apiserver-operator/blob/master/OWNERS)~~ [p0lyn0mial,sanchezl] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
openshift-ci[bot] commented 10 months ago

@p0lyn0mial: The following tests 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-gcp-operator-single-node aa098be1041d572418387122aee4015d01c4ac2c link false /test e2e-gcp-operator-single-node
ci/prow/e2e-aws-operator-disruptive-single-node aa098be1041d572418387122aee4015d01c4ac2c link false /test e2e-aws-operator-disruptive-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/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
openshift-ci-robot commented 10 months ago

@p0lyn0mial: Jira Issue OCPBUGS-24005: All pull requests linked via external trackers have merged:

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

In response to [this](https://github.com/openshift/cluster-kube-apiserver-operator/pull/1632): >for easier troubleshooting when a check is skipped because `service-ca` hasn't provided a CA for the webook we should also log the name of the webhook. Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-kube-apiserver-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 10 months ago

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-kube-apiserver-operator-container-v4.16.0-202401242108.p0.g1c6d106.assembly.stream for distgit ose-cluster-kube-apiserver-operator. All builds following this will include this PR.

p0lyn0mial commented 9 months ago

/cherry-pick release-4.15

openshift-cherrypick-robot commented 9 months ago

@p0lyn0mial: new pull request created: #1647

In response to [this](https://github.com/openshift/cluster-kube-apiserver-operator/pull/1632#issuecomment-1956547198): >/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/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.