Skip to content

[release-4.16] OCPBUGS-55697: Add validation to avoid conflicts between KubeAPIServer and NamedCertificates SANs #6114

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

Open
wants to merge 1 commit into
base: release-4.16
Choose a base branch
from

Conversation

jparrill
Copy link
Contributor

@jparrill jparrill commented May 5, 2025

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

openshift-ci-robot commented May 5, 2025

@jparrill: This pull request references Jira Issue OCPBUGS-55697, which is invalid:

  • expected dependent Jira Issue OCPBUGS-55500 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

This pull request references RHOCPPRIO-433 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.z" version, but no target version was set.

In response to this:

What this PR does / why we need it

Which issue(s) this PR fixes

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 review from enxebre and isco-rodriguez May 5, 2025 10:10
@openshift-ci openshift-ci bot added area/control-plane-operator Indicates the PR includes changes for the control plane operator - in an OCP release area/hypershift-operator Indicates the PR includes changes for the hypershift operator and API - outside an OCP release labels May 5, 2025
Copy link
Contributor

openshift-ci bot commented May 5, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jparrill

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 area/testing Indicates the PR includes changes for e2e testing approved Indicates a PR has been approved by an approver from all required OWNERS files. and removed do-not-merge/needs-area labels May 5, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 5, 2025

@jparrill: This pull request references Jira Issue OCPBUGS-55697, which is invalid:

  • expected dependent Jira Issue OCPBUGS-55500 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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.

This pull request references RHOCPPRIO-433 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.z" version, but no target version was set.

In response to this:

What this PR does / why we need it

Which issue(s) this PR fixes

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.

@jparrill
Copy link
Contributor Author

jparrill commented May 5, 2025

Looking at the log error:

GO111MODULE=on GOFLAGS=-mod=vendor go test -race -count=25 -timeout=30m ./... -coverprofile cover.out
go: go.mod requires go >= 1.22.1 (running go 1.21.13; GOTOOLCHAIN=local)
make: *** [Makefile:171: test] Error 1
{"component":"entrypoint","error":"wrapped process failed: exit status 2","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:84","func":"sigs.k8s.io/prow/pkg/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2025-05-05T10:18:25Z"} 

We need to move the Golang version (of 4.16, 4.15 and 4.14) to >= 1.22.1 in order to continue with this backport to all way long to release-4.14.

@sjenning WDYT?

…r and NamedCertificates SANs

This PR adds validation to ensure there are no conflicts between the SAN's of the user's APIServer NamedCertificates and the KubeAPIServer CPO certificates. This prevents potential issues with certificate SANs conflicts that could break the TLS trust chain between the nodes and the KAS

Signed-off-by: Juan Manuel Parrilla Madrid <[email protected]>
@jparrill jparrill force-pushed the OCPBUGS-54483-4-16 branch from 4c3d13f to 7cd7560 Compare May 6, 2025 07:45
@jparrill
Copy link
Contributor Author

jparrill commented May 6, 2025

Looking at the log error:

GO111MODULE=on GOFLAGS=-mod=vendor go test -race -count=25 -timeout=30m ./... -coverprofile cover.out
go: go.mod requires go >= 1.22.1 (running go 1.21.13; GOTOOLCHAIN=local)
make: *** [Makefile:171: test] Error 1
{"component":"entrypoint","error":"wrapped process failed: exit status 2","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:84","func":"sigs.k8s.io/prow/pkg/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2025-05-05T10:18:25Z"} 

We need to move the Golang version (of 4.16, 4.15 and 4.14) to >= 1.22.1 in order to continue with this backport to all way long to release-4.14.

@sjenning WDYT?

nvm, looks like there was an issue in my local with cache. All ok now

@openshift-ci-robot
Copy link

@jparrill: An error was encountered updating to the POST state for bug OCPBUGS-55697 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/16873217/transitions": POST https://issues.redhat.com/rest/api/2/issue/16873217/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:

What this PR does / why we need it

Which issue(s) this PR fixes

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.

@enxebre
Copy link
Member

enxebre commented May 6, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 6, 2025
@jparrill
Copy link
Contributor Author

jparrill commented May 6, 2025

/retest

1 similar comment
@jparrill
Copy link
Contributor Author

jparrill commented May 6, 2025

/retest

@jparrill
Copy link
Contributor Author

jparrill commented May 6, 2025

/test e2e-aws

@jparrill
Copy link
Contributor Author

jparrill commented May 7, 2025

/retest

@celebdor
Copy link
Collaborator

celebdor commented May 7, 2025

/retitle [release-4.16] OCPBUGS-55697: Add validation to avoid conflicts between KubeAPIServer and NamedCertificates SANs

@openshift-ci openshift-ci bot changed the title [release-4.16] OCPBUGS-55697, RHOCPPRIO-433: Add validation to avoid conflicts between KubeAPIServer and NamedCertificates SANs [release-4.16] OCPBUGS-55697: Add validation to avoid conflicts between KubeAPIServer and NamedCertificates SANs May 7, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label May 7, 2025
@openshift-ci-robot
Copy link

@jparrill: This pull request references Jira Issue OCPBUGS-55697, 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.z) matches configured target version for branch (4.16.z)
  • 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-55500 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-55500 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.z
  • bug has dependents

Requesting review from QA contact:
/cc @wewang58

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

In response to this:

What this PR does / why we need it

Which issue(s) this PR fixes

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.

@jparrill
Copy link
Contributor Author

jparrill commented May 8, 2025

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ba952e1 and 2 for PR HEAD 7cd7560 in total

3 similar comments
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ba952e1 and 2 for PR HEAD 7cd7560 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ba952e1 and 2 for PR HEAD 7cd7560 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ba952e1 and 2 for PR HEAD 7cd7560 in total

@jparrill
Copy link
Contributor Author

/retest

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ba952e1 and 2 for PR HEAD 7cd7560 in total

@jparrill
Copy link
Contributor Author

/retest

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ba952e1 and 2 for PR HEAD 7cd7560 in total

1 similar comment
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ba952e1 and 2 for PR HEAD 7cd7560 in total

@jparrill
Copy link
Contributor Author

/retest

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ba952e1 and 2 for PR HEAD 7cd7560 in total

2 similar comments
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ba952e1 and 2 for PR HEAD 7cd7560 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ba952e1 and 2 for PR HEAD 7cd7560 in total

@jparrill
Copy link
Contributor Author

/retest

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ba952e1 and 2 for PR HEAD 7cd7560 in total

1 similar comment
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ba952e1 and 2 for PR HEAD 7cd7560 in total

@jparrill
Copy link
Contributor Author

/retest

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ba952e1 and 2 for PR HEAD 7cd7560 in total

6 similar comments
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ba952e1 and 2 for PR HEAD 7cd7560 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ba952e1 and 2 for PR HEAD 7cd7560 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ba952e1 and 2 for PR HEAD 7cd7560 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ba952e1 and 2 for PR HEAD 7cd7560 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ba952e1 and 2 for PR HEAD 7cd7560 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ba952e1 and 2 for PR HEAD 7cd7560 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 9a16d65 and 1 for PR HEAD 7cd7560 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 9a16d65 and 2 for PR HEAD 7cd7560 in total

1 similar comment
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 9a16d65 and 2 for PR HEAD 7cd7560 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 5f7e4aa and 1 for PR HEAD 7cd7560 in total

Copy link
Contributor

openshift-ci bot commented May 22, 2025

@jparrill: 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-kubevirt-aws-ovn-reduced 7cd7560 link true /test e2e-kubevirt-aws-ovn-reduced
ci/prow/e2e-aws 7cd7560 link true /test e2e-aws

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.

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. area/control-plane-operator Indicates the PR includes changes for the control plane operator - in an OCP release area/hypershift-operator Indicates the PR includes changes for the hypershift operator and API - outside an OCP release area/testing Indicates the PR includes changes for e2e testing backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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