Skip to content

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

Merged

Conversation

chiragkyal
Copy link
Member

@chiragkyal chiragkyal commented Apr 22, 2025

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

Signed-off-by: chiragkyal <ckyal@redhat.com>
@openshift-ci openshift-ci bot requested review from Miciah and Thealisyed April 22, 2025 11:17
@swghosh
Copy link
Member

swghosh commented Apr 22, 2025

/retitle: OCPBUGS-55214: Fix default cert issuer name for HyperShift in RouteExternalCertificate test case

@openshift-ci openshift-ci bot changed the title Fix default certificate common name for HyperShift : OCPBUGS-55214: Fix default cert issuer name for HyperShift in RouteExternalCertificate test case Apr 22, 2025
@openshift-ci-robot
Copy link

@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 /jira refresh.

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.

@swghosh
Copy link
Member

swghosh commented Apr 22, 2025

@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.

@swghosh
Copy link
Member

swghosh commented Apr 22, 2025

/retitle OCPBUGS-55214: Fix default cert issuer name for HyperShift in RouteExternalCertificate test case

@openshift-ci openshift-ci bot changed the title : OCPBUGS-55214: Fix default cert issuer name for HyperShift in RouteExternalCertificate test case OCPBUGS-55214: Fix default cert issuer name for HyperShift in RouteExternalCertificate test case Apr 22, 2025
@swghosh
Copy link
Member

swghosh commented Apr 22, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Apr 22, 2025
@openshift-ci-robot
Copy link

@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
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @lihongan

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

In response to this:

/jira refresh

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 openshift-ci bot requested a review from lihongan April 22, 2025 13:00
@openshift-ci-robot
Copy link

@chiragkyal: This pull request references Jira Issue OCPBUGS-55214, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @lihongan

In response to this:

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

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
Copy link
Contributor

Miciah commented Apr 22, 2025

/approve
/lgtm

@chiragkyal
Copy link
Member Author

/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

Copy link
Contributor

openshift-ci bot commented Apr 22, 2025

@chiragkyal: trigger 9 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • 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

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/f733f350-1f7f-11f0-8023-fb8fdb4c4020-0

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 22, 2025
@chiragkyal
Copy link
Member Author

/test e2e-gcp-ovn-techpreview

Copy link
Contributor

openshift-ci bot commented Apr 22, 2025

[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 /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 Apr 22, 2025
@chiragkyal
Copy link
Member Author

/test e2e-gcp-ovn-techpreview

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 118fc94 and 2 for PR HEAD ec3d027 in total

@chiragkyal
Copy link
Member Author

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 118fc94 and 2 for PR HEAD ec3d027 in total

Copy link

openshift-trt bot commented Apr 23, 2025

Job Failure Risk Analysis for sha: ec3d027

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-gcp-ovn-techpreview IncompleteTests
Tests for this run (18) are below the historical average (2583): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-ipv6 IncompleteTests
Tests for this run (103) are below the historical average (1490): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD aa19c60 and 1 for PR HEAD ec3d027 in total

@swghosh
Copy link
Member

swghosh commented Apr 23, 2025

/skip

@Miciah
Copy link
Contributor

Miciah commented Apr 23, 2025

/override ci/prow/e2e-metal-ipi-ovn-ipv6

Copy link
Contributor

openshift-ci bot commented Apr 23, 2025

@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:

/override ci/prow/e2e-metal-ipi-ovn-ipv6

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.

@stbenjam
Copy link
Member

/override ci/prow/e2e-metal-ipi-ovn-ipv6

Copy link
Contributor

openshift-ci bot commented Apr 23, 2025

@stbenjam: Overrode contexts on behalf of stbenjam: ci/prow/e2e-metal-ipi-ovn-ipv6

In response to this:

/override ci/prow/e2e-metal-ipi-ovn-ipv6

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.

@stbenjam
Copy link
Member

/override ci/prow/e2e-aws-ovn-serial

Copy link
Contributor

openshift-ci bot commented Apr 23, 2025

@stbenjam: Overrode contexts on behalf of stbenjam: ci/prow/e2e-aws-ovn-serial

In response to this:

/override ci/prow/e2e-aws-ovn-serial

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.

@openshift-merge-bot openshift-merge-bot bot merged commit df9b542 into openshift:main Apr 23, 2025
56 checks passed
@openshift-ci-robot
Copy link

@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:

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

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.

Copy link
Contributor

openshift-ci bot commented Apr 23, 2025

@chiragkyal: 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/4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback ec3d027 link false /test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback
ci/prow/e2e-aws-disruptive ec3d027 link false /test e2e-aws-disruptive
ci/prow/e2e-aws-csi ec3d027 link false /test e2e-aws-csi
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout ec3d027 link false /test e2e-metal-ipi-ovn-kube-apiserver-rollout
ci/prow/okd-scos-e2e-aws-ovn ec3d027 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-etcd-scaling ec3d027 link false /test e2e-aws-ovn-etcd-scaling
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 ec3d027 link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-metal-ipi-serial ec3d027 link false /test e2e-metal-ipi-serial
ci/prow/e2e-metal-ipi-virtualmedia ec3d027 link false /test e2e-metal-ipi-virtualmedia
ci/prow/e2e-aws-ovn-cgroupsv2 ec3d027 link false /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-metal-ipi-ovn-dualstack ec3d027 link false /test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-azure-ovn-etcd-scaling ec3d027 link false /test e2e-azure-ovn-etcd-scaling
ci/prow/e2e-openstack-serial ec3d027 link false /test e2e-openstack-serial
ci/prow/e2e-gcp-disruptive ec3d027 link false /test e2e-gcp-disruptive
ci/prow/e2e-metal-ipi-serial-ovn-ipv6 ec3d027 link false /test e2e-metal-ipi-serial-ovn-ipv6
ci/prow/e2e-aws-ovn-single-node-serial ec3d027 link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-azure-ovn-upgrade ec3d027 link false /test e2e-azure-ovn-upgrade
ci/prow/okd-e2e-gcp ec3d027 link false /test okd-e2e-gcp
ci/prow/e2e-metal-ipi-ovn ec3d027 link false /test e2e-metal-ipi-ovn
ci/prow/e2e-aws-ovn-kube-apiserver-rollout ec3d027 link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-gcp-ovn-etcd-scaling ec3d027 link false /test e2e-gcp-ovn-etcd-scaling
ci/prow/e2e-aws-ovn-single-node-upgrade ec3d027 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws ec3d027 link false /test e2e-aws
ci/prow/e2e-vsphere-ovn-etcd-scaling ec3d027 link false /test e2e-vsphere-ovn-etcd-scaling
ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway ec3d027 link false /test e2e-metal-ipi-ovn-dualstack-local-gateway
ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-techpreview ec3d027 link false /test e2e-metal-ipi-ovn-dualstack-bgp-techpreview
ci/prow/e2e-gcp-fips-serial ec3d027 link false /test e2e-gcp-fips-serial
ci/prow/e2e-gcp-ovn-techpreview ec3d027 link false /test e2e-gcp-ovn-techpreview

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.

@chiragkyal chiragkyal deleted the hypershift-default-cert branch April 23, 2025 14:01
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-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants