Skip to content

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #1936

/assign sanchezl

It should be <namespace>-<name>, not the other way around
Instead of re-creating configmap from scratch every time this function
should attempt to use existing configmap and replace the contents only.
This would prevent extra configmap updates when metadata changes
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Detected clone of Jira Issue OCPBUGS-55217 with correct target version. Will retitle the PR to link to the clone.
/retitle [release-4.19] OCPBUGS-60682: CombineCABundleConfigMaps: use optimistic create/update

In response to this:

This is an automated cherry-pick of #1936

/assign sanchezl

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 changed the title [release-4.19] OCPBUGS-55217: CombineCABundleConfigMaps: use optimistic create/update [release-4.19] OCPBUGS-60682: CombineCABundleConfigMaps: use optimistic create/update Sep 12, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 12, 2025
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-60682, which is invalid:

  • expected dependent Jira Issue OCPBUGS-60473 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is Closed (Duplicate) 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.

In response to this:

This is an automated cherry-pick of #1936

/assign sanchezl

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.

@wangke19
Copy link
Contributor

/retest

@wangke19
Copy link
Contributor

/test unit

Copy link
Contributor

openshift-ci bot commented Sep 16, 2025

@openshift-cherrypick-robot: all tests passed!

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.

@wangke19
Copy link
Contributor

/lgtm

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

openshift-ci bot commented Sep 16, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, wangke19
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@wangke19
Copy link
Contributor

/cc @p0lyn0mial

@openshift-ci openshift-ci bot requested a review from p0lyn0mial September 16, 2025 12:02
@vrutkovs
Copy link
Member

This is probably not required - we'll need this only if 4.19 cert metadata is being updated

/close

@openshift-ci openshift-ci bot closed this Sep 18, 2025
Copy link
Contributor

openshift-ci bot commented Sep 18, 2025

@vrutkovs: Closed this PR.

In response to this:

This is probably not required - we'll need this only if 4.19 cert metadata is being updated

/close

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
jira/invalid-bug Indicates that a referenced Jira bug is invalid 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