Skip to content

Conversation

@chrischdi
Copy link
Contributor

@chrischdi chrischdi commented Sep 16, 2025

Disables the secure-serving port which is unused for all providers, except ibm and powervs where it is used as livenessprobe.

@chrischdi chrischdi changed the title OCPBUGS-51305 aws: disable unused secure-serving port and webhook OCPBUGS-51305: aws: disable unused secure-serving port and webhook Sep 16, 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 Sep 16, 2025
@openshift-ci-robot
Copy link

@chrischdi: This pull request references Jira Issue OCPBUGS-51305, which is invalid:

  • expected the bug to target the "4.21.0" version, but no target version was set

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:

Disables the secure-serving port which is unused.

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.

@chrischdi
Copy link
Contributor Author

/jira sync

@chrischdi
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 16, 2025
@openshift-ci-robot
Copy link

@chrischdi: This pull request references Jira Issue OCPBUGS-51305, 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.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sunzhaohua2

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 sunzhaohua2 September 16, 2025 13:24
@chrischdi chrischdi force-pushed the pr-aws-ccm-disable-webhook-port branch from 113f052 to 59e2736 Compare September 16, 2025 13:52
@openshift-ci-robot
Copy link

@chrischdi: This pull request references Jira Issue OCPBUGS-51305, which is valid.

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

Requesting review from QA contact:
/cc @sunzhaohua2

In response to this:

Disables the secure-serving port which is unused for all providers, except ibm and powervs where it is used as livenessprobe.

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.

@chrischdi chrischdi changed the title OCPBUGS-51305: aws: disable unused secure-serving port and webhook OCPBUGS-51305: ccm: disable unused secure-serving port and webhook Sep 16, 2025
@chrischdi chrischdi force-pushed the pr-aws-ccm-disable-webhook-port branch from 59e2736 to afd7814 Compare September 16, 2025 14:04
@chrischdi chrischdi force-pushed the pr-aws-ccm-disable-webhook-port branch from afd7814 to ca9e78f Compare September 17, 2025 06:36
@chrischdi
Copy link
Contributor Author

/retest

@chrischdi
Copy link
Contributor Author

/retest-required

@chrischdi
Copy link
Contributor Author

/retest

@chrischdi
Copy link
Contributor Author

/retest-required

@chrischdi
Copy link
Contributor Author

/retest

1 similar comment
@chrischdi
Copy link
Contributor Author

/retest

@chrischdi
Copy link
Contributor Author

/assign mdbooth
/assign theobarberbany

Kindly asking fro some review :-)

@chrischdi
Copy link
Contributor Author

/hold

Reverting the change for nutanix to see if that fixes CI

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 2, 2025
@chrischdi chrischdi force-pushed the pr-aws-ccm-disable-webhook-port branch from b18e5db to ca9e78f Compare October 2, 2025 14:19
@chrischdi
Copy link
Contributor Author

/retes

@chrischdi
Copy link
Contributor Author

/retest

1 similar comment
@chrischdi
Copy link
Contributor Author

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 13, 2025

@chrischdi: 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-openstack-ovn ca9e78f link false /test e2e-openstack-ovn
ci/prow/e2e-nutanix-ovn ca9e78f link false /test e2e-nutanix-ovn

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.

@chrischdi
Copy link
Contributor Author

/verified bypass

nutanix and openstack e2e permafailing. Verified manually that they don't have any active CCM webhooks:

❯ pwd
/Users/cschlott/go/src/github.com/openshift/cloud-provider-nutanix
❯ go run ./ --help | grep -e "--webhooks" -A 4
      --webhooks strings   A list of webhooks to enable. '*' enables all on-by-default webhooks, 'foo' enables the webhook named 'foo', '-foo' disables the webhook named 'foo'.
                           All webhooks:
                           Disabled-by-default webhooks:

Webhook serving flags:
❯ pwd
/Users/cschlott/go/src/github.com/openshift/cloud-provider-openstack
❯ go run ./cmd/openstack-cloud-controller-manager --help | grep -e "--webhooks" -A 4
      --webhooks strings   A list of webhooks to enable. '*' enables all on-by-default webhooks, 'foo' enables the webhook named 'foo', '-foo' disables the webhook named 'foo'.
                           All webhooks:
                           Disabled-by-default webhooks:

Webhook serving flags:

@openshift-ci-robot
Copy link

@chrischdi: The verified label has been added.

In response to this:

/verified bypass

nutanix and openstack e2e permafailing. Verified manually that they don't have any active CCM webhooks:

❯ pwd
/Users/cschlott/go/src/github.com/openshift/cloud-provider-nutanix
❯ go run ./ --help | grep -e "--webhooks" -A 4
     --webhooks strings   A list of webhooks to enable. '*' enables all on-by-default webhooks, 'foo' enables the webhook named 'foo', '-foo' disables the webhook named 'foo'.
                          All webhooks:
                          Disabled-by-default webhooks:

Webhook serving flags:
❯ pwd
/Users/cschlott/go/src/github.com/openshift/cloud-provider-openstack
❯ go run ./cmd/openstack-cloud-controller-manager --help | grep -e "--webhooks" -A 4
     --webhooks strings   A list of webhooks to enable. '*' enables all on-by-default webhooks, 'foo' enables the webhook named 'foo', '-foo' disables the webhook named 'foo'.
                          All webhooks:
                          Disabled-by-default webhooks:

Webhook serving flags:

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-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 14, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 9f2dcd3 into openshift:main Oct 14, 2025
20 of 22 checks passed
@openshift-ci-robot
Copy link

@chrischdi: Jira Issue OCPBUGS-51305 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state.

In response to this:

Disables the secure-serving port which is unused for all providers, except ibm and powervs where it is used as livenessprobe.

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.

@chrischdi
Copy link
Contributor Author

/jira backport release-4.20,release-4.19,release-4.18,release-4.17,release-4.16,release-4.15,release-4.14

@openshift-ci-robot
Copy link

@chrischdi: The following backport issues have been created:

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.20
/cherrypick release-4.19
/cherrypick release-4.18
/cherrypick release-4.17
/cherrypick release-4.16
/cherrypick release-4.15
/cherrypick release-4.14

In response to this:

/jira backport release-4.20,release-4.19,release-4.18,release-4.17,release-4.16,release-4.15,release-4.14

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-cherrypick-robot

@openshift-ci-robot: #415 failed to apply on top of branch "release-4.14":

Applying: ccm: disable unused secure-serving port and webhook
Using index info to reconstruct a base tree...
M	pkg/cloud/aws/assets/deployment.yaml
M	pkg/cloud/azure/assets/cloud-controller-manager-deployment.yaml
M	pkg/cloud/azurestack/assets/cloud-controller-manager-deployment.yaml
M	pkg/cloud/gcp/assets/cloud-controller-manager.yaml
M	pkg/cloud/nutanix/assets/cloud-controller-manager-deployment.yaml
M	pkg/cloud/openstack/assets/deployment.yaml
M	pkg/cloud/vsphere/assets/cloud-controller-manager-deployment.yaml
Falling back to patching base and 3-way merge...
Auto-merging pkg/cloud/vsphere/assets/cloud-controller-manager-deployment.yaml
CONFLICT (content): Merge conflict in pkg/cloud/vsphere/assets/cloud-controller-manager-deployment.yaml
Auto-merging pkg/cloud/openstack/assets/deployment.yaml
Auto-merging pkg/cloud/nutanix/assets/cloud-controller-manager-deployment.yaml
CONFLICT (content): Merge conflict in pkg/cloud/nutanix/assets/cloud-controller-manager-deployment.yaml
Auto-merging pkg/cloud/gcp/assets/cloud-controller-manager.yaml
CONFLICT (content): Merge conflict in pkg/cloud/gcp/assets/cloud-controller-manager.yaml
Auto-merging pkg/cloud/azurestack/assets/cloud-controller-manager-deployment.yaml
CONFLICT (content): Merge conflict in pkg/cloud/azurestack/assets/cloud-controller-manager-deployment.yaml
Auto-merging pkg/cloud/azure/assets/cloud-controller-manager-deployment.yaml
CONFLICT (content): Merge conflict in pkg/cloud/azure/assets/cloud-controller-manager-deployment.yaml
Auto-merging pkg/cloud/aws/assets/deployment.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 ccm: disable unused secure-serving port and webhook

In response to this:

@chrischdi: The following backport issues have been created:

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.20
/cherrypick release-4.19
/cherrypick release-4.18
/cherrypick release-4.17
/cherrypick release-4.16
/cherrypick release-4.15
/cherrypick release-4.14

In response to this:

/jira backport release-4.20,release-4.19,release-4.18,release-4.17,release-4.16,release-4.15,release-4.14

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.

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.

@chrischdi
Copy link
Contributor Author

/cherrypick release-4.20

@openshift-cherrypick-robot

@chrischdi: new pull request created: #419

In response to this:

/cherrypick release-4.20

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.

@chrischdi
Copy link
Contributor Author

/cherrypick release-4.19

@openshift-cherrypick-robot

@chrischdi: new pull request created: #420

In response to this:

/cherrypick release-4.19

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.

@chrischdi
Copy link
Contributor Author

/cherrypick release-4.18

@openshift-cherrypick-robot

@chrischdi: new pull request created: #421

In response to this:

/cherrypick release-4.18

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.

@chrischdi
Copy link
Contributor Author

/cherrypick release-4.17

/cherrypick release-4.16

@openshift-cherrypick-robot

@chrischdi: new pull request created: #422

In response to this:

/cherrypick release-4.17

/cherrypick release-4.16

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-cherrypick-robot

@chrischdi: new pull request created: #423

In response to this:

/cherrypick release-4.17

/cherrypick release-4.16

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.

@chrischdi
Copy link
Contributor Author

/cherrypick release-4.15

@openshift-cherrypick-robot

@chrischdi: #415 failed to apply on top of branch "release-4.15":

Applying: ccm: disable unused secure-serving port and webhook
Using index info to reconstruct a base tree...
M	pkg/cloud/aws/assets/deployment.yaml
M	pkg/cloud/azure/assets/cloud-controller-manager-deployment.yaml
M	pkg/cloud/azurestack/assets/cloud-controller-manager-deployment.yaml
M	pkg/cloud/gcp/assets/cloud-controller-manager.yaml
M	pkg/cloud/nutanix/assets/cloud-controller-manager-deployment.yaml
M	pkg/cloud/openstack/assets/deployment.yaml
M	pkg/cloud/vsphere/assets/cloud-controller-manager-deployment.yaml
Falling back to patching base and 3-way merge...
Auto-merging pkg/cloud/vsphere/assets/cloud-controller-manager-deployment.yaml
CONFLICT (content): Merge conflict in pkg/cloud/vsphere/assets/cloud-controller-manager-deployment.yaml
Auto-merging pkg/cloud/openstack/assets/deployment.yaml
Auto-merging pkg/cloud/nutanix/assets/cloud-controller-manager-deployment.yaml
CONFLICT (content): Merge conflict in pkg/cloud/nutanix/assets/cloud-controller-manager-deployment.yaml
Auto-merging pkg/cloud/gcp/assets/cloud-controller-manager.yaml
CONFLICT (content): Merge conflict in pkg/cloud/gcp/assets/cloud-controller-manager.yaml
Auto-merging pkg/cloud/azurestack/assets/cloud-controller-manager-deployment.yaml
CONFLICT (content): Merge conflict in pkg/cloud/azurestack/assets/cloud-controller-manager-deployment.yaml
Auto-merging pkg/cloud/azure/assets/cloud-controller-manager-deployment.yaml
CONFLICT (content): Merge conflict in pkg/cloud/azure/assets/cloud-controller-manager-deployment.yaml
Auto-merging pkg/cloud/aws/assets/deployment.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 ccm: disable unused secure-serving port and webhook

In response to this:

/cherrypick release-4.15

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.

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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants