-
Notifications
You must be signed in to change notification settings - Fork 4.7k
OCPBUGS-55214: Fix default cert issuer name for HyperShift in RouteExternalCertificate
test case
#29698
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
OCPBUGS-55214: Fix default cert issuer name for HyperShift in RouteExternalCertificate
test case
#29698
Conversation
Signed-off-by: chiragkyal <ckyal@redhat.com>
/retitle: OCPBUGS-55214: Fix default cert issuer name for HyperShift in |
RouteExternalCertificate
test case
@chiragkyal: An error was encountered updating to the POST state for bug OCPBUGS-55214 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details. Full error message.
No response returned: Post "https://issues.redhat.com/rest/api/2/issue/16842597/transitions": POST https://issues.redhat.com/rest/api/2/issue/16842597/transitions giving up after 5 attempt(s)
Please contact an administrator to resolve this issue, then request a bug refresh with In response to this: 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. |
@Miciah the failed test job on HyperShift was observed in openshift/hypershift#6064 > https://github.com/openshift/hypershift/pull/6064/checks?check_run_id=40924952557 test run. |
/retitle OCPBUGS-55214: Fix default cert issuer name for HyperShift in |
RouteExternalCertificate
test caseRouteExternalCertificate
test case
/jira refresh |
@swghosh: This pull request references Jira Issue OCPBUGS-55214, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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. |
@chiragkyal: This pull request references Jira Issue OCPBUGS-55214, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
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. |
/approve |
/payload-job periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-techpreview periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-dualstack-techpreview periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-ipv6-techpreview periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview periodic-ci-openshift-release-master-ci-4.19-e2e-gcp-ovn-techpreview periodic-ci-openshift-release-master-ci-4.19-e2e-gcp-ovn-techpreview-serial periodic-ci-openshift-multiarch-master-nightly-4.19-ocp-e2e-aws-ovn-techpreview-multi-a-a periodic-ci-openshift-release-master-nightly-4.19-e2e-vsphere-ipi-ovn-runc-techpreview |
@chiragkyal: trigger 9 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/f733f350-1f7f-11f0-8023-fb8fdb4c4020-0 |
/test e2e-gcp-ovn-techpreview |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chiragkyal, Miciah 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 |
/test e2e-gcp-ovn-techpreview |
/retest-required |
Job Failure Risk Analysis for sha: ec3d027
|
/skip |
/override ci/prow/e2e-metal-ipi-ovn-ipv6 |
@Miciah: Miciah unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers. In response to this:
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-sigs/prow repository. |
/override ci/prow/e2e-metal-ipi-ovn-ipv6 |
@stbenjam: Overrode contexts on behalf of stbenjam: ci/prow/e2e-metal-ipi-ovn-ipv6 In response to this:
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-sigs/prow repository. |
/override ci/prow/e2e-aws-ovn-serial |
@stbenjam: Overrode contexts on behalf of stbenjam: ci/prow/e2e-aws-ovn-serial In response to this:
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-sigs/prow repository. |
@chiragkyal: Jira Issue OCPBUGS-55214: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-55214 has been moved to the MODIFIED state. In response to this:
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. |
@chiragkyal: The following tests failed, say
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-sigs/prow repository. I understand the commands that are listed here. |
This PR will decide the default cert issuer name. If the tests are running on HyperShift, the default cert issuer name would be
"root-ca"
, otherwise"ingress-operator"
https://issues.redhat.com//browse/OCPBUGS-55214