Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #1294

/assign damdo

/cherrypick release-4.20

Since 4.20, some Cluster-API ConfigMap manifests have wanted to set
this:

  $ oc adm release extract --to manifests quay.io/openshift-release-dev/ocp-release:4.20.10-x86_64
  $ grep -r binaryData manifests
  manifests/0000_30_cluster-api_04_cm.infrastructure-aws.yaml:binaryData:

so we need to compare the in-cluster ConfigMap with this property as
well, when deciding if the resource needs updating.
@coderabbitai
Copy link

coderabbitai bot commented Jan 17, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-73929 has been cloned as Jira Issue OCPBUGS-74009. Will retitle bug to link to clone.
/retitle [release-4.21] OCPBUGS-74009: lib/resourcemerge/core: Reconcile ConfigMap binaryData too

Details

In response to this:

This is an automated cherry-pick of #1294

/assign damdo

/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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot changed the title [release-4.21] OCPBUGS-73929: lib/resourcemerge/core: Reconcile ConfigMap binaryData too [release-4.21] OCPBUGS-74009: lib/resourcemerge/core: Reconcile ConfigMap binaryData too Jan 17, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. 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 Jan 17, 2026
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-74009, 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.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-73929 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-73929 targets the "4.22.0" version, which is one of the valid target versions: 4.22.0
  • bug has dependents

Requesting review from QA contact:
/cc @jiajliu

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

Details

In response to this:

This is an automated cherry-pick of #1294

/assign damdo

/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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested a review from jiajliu January 17, 2026 09:12
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 17, 2026

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@damdo
Copy link
Member

damdo commented Jan 19, 2026

/assign @wking @hongkailiu

@theobarberbany
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 19, 2026
@hongkailiu
Copy link
Member

/appove

@hongkailiu
Copy link
Member

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 20, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hongkailiu, openshift-cherrypick-robot, theobarberbany

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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 Jan 20, 2026
@hongkailiu
Copy link
Member

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jan 20, 2026
@damdo
Copy link
Member

damdo commented Jan 20, 2026

@hongkailiu @wking

Are you able to also verify it? Or should I ask QE? TY

@wking
Copy link
Member

wking commented Jan 20, 2026

Repeating my 4.22/dev verification steps, this time with a launch 4.21,openshift/cluster-version-operator#1295 aws,techpreview ClusterBot cluster (logs):

$ oc -n openshift-cluster-api get -o jsonpath-as-json='{.binaryData.components\-zstd}' configmap aws | cut -b -80
[
    "KLUv/QRolCYC2g+iWDOgaoxqDt6xwE7Zvyk57mwiafsazqcoDN8KhhZ3P5BbAujrQ8ApDwHPgX1
]
$ oc -n openshift-cluster-api patch configmap aws --type json -p '[{"op": "add", "path": "/binaryData/components-zstd", "value": "dGVzdGluZwo="}]'
configmap/aws patched
$ oc -n openshift-cluster-version logs -l k8s-app=cluster-version-operator --tail -1 | grep -i 'openshift-cluster-api/aws\|Result of work' | tail -n3
I0120 18:18:58.576914       1 task_graph.go:564] Result of work: errs=[]
I0120 18:21:52.031544       1 task_graph.go:564] Result of work: errs=[]
I0120 18:24:45.535156       1 task_graph.go:564] Result of work: errs=[]
$ oc -n openshift-cluster-api get -o jsonpath-as-json='{.binaryData.components\-zstd}' configmap aws | cut -b -80
[
    "dGVzdGluZwo="
]
$ oc -n openshift-cluster-version logs -l k8s-app=cluster-version-operator --tail -1 | grep -i 'openshift-cluster-api/aws\|Result of work' | tail -n3
I0120 18:24:45.535156       1 task_graph.go:564] Result of work: errs=[]
I0120 18:27:37.754228       1 core.go:138] Updating ConfigMap openshift-cluster-api/aws due to diff:   &v1.ConfigMap{
I0120 18:27:39.036554       1 task_graph.go:564] Result of work: errs=[]
$ oc -n openshift-cluster-api get -o jsonpath-as-json='{.binaryData.components\-zstd}' configmap aws | cut -b -80
[
    "KLUv/QRolCYC2g+iWDOgaoxqDt6xwE7Zvyk57mwiafsazqcoDN8KhhZ3P5BbAujrQ8ApDwHPgX1
]

So this one looks good to me too :)

/verified by @wking

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 20, 2026
@openshift-ci-robot
Copy link
Contributor

@wking: This PR has been marked as verified by @wking.

Details

In response to this:

Repeating my 4.22/dev verification steps, this time with a launch 4.21,openshift/cluster-version-operator#1295 aws,techpreview ClusterBot cluster (logs):

$ oc -n openshift-cluster-api get -o jsonpath-as-json='{.binaryData.components\-zstd}' configmap aws | cut -b -80
[
   "KLUv/QRolCYC2g+iWDOgaoxqDt6xwE7Zvyk57mwiafsazqcoDN8KhhZ3P5BbAujrQ8ApDwHPgX1
]
$ oc -n openshift-cluster-api patch configmap aws --type json -p '[{"op": "add", "path": "/binaryData/components-zstd", "value": "dGVzdGluZwo="}]'
configmap/aws patched
$ oc -n openshift-cluster-version logs -l k8s-app=cluster-version-operator --tail -1 | grep -i 'openshift-cluster-api/aws\|Result of work' | tail -n3
I0120 18:18:58.576914       1 task_graph.go:564] Result of work: errs=[]
I0120 18:21:52.031544       1 task_graph.go:564] Result of work: errs=[]
I0120 18:24:45.535156       1 task_graph.go:564] Result of work: errs=[]
$ oc -n openshift-cluster-api get -o jsonpath-as-json='{.binaryData.components\-zstd}' configmap aws | cut -b -80
[
   "dGVzdGluZwo="
]
$ oc -n openshift-cluster-version logs -l k8s-app=cluster-version-operator --tail -1 | grep -i 'openshift-cluster-api/aws\|Result of work' | tail -n3
I0120 18:24:45.535156       1 task_graph.go:564] Result of work: errs=[]
I0120 18:27:37.754228       1 core.go:138] Updating ConfigMap openshift-cluster-api/aws due to diff:   &v1.ConfigMap{
I0120 18:27:39.036554       1 task_graph.go:564] Result of work: errs=[]
$ oc -n openshift-cluster-api get -o jsonpath-as-json='{.binaryData.components\-zstd}' configmap aws | cut -b -80
[
   "KLUv/QRolCYC2g+iWDOgaoxqDt6xwE7Zvyk57mwiafsazqcoDN8KhhZ3P5BbAujrQ8ApDwHPgX1
]

So this one looks good to me too :)

/verified by @wking

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-merge-bot openshift-merge-bot bot merged commit 6fb3e84 into openshift:release-4.21 Jan 20, 2026
16 checks passed
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-74009
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-74009 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

This is an automated cherry-pick of #1294

/assign damdo

/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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-cherrypick-robot
Copy link
Author

@openshift-cherrypick-robot: new pull request created: #1303

Details

In response to this:

This is an automated cherry-pick of #1294

/assign damdo

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

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. 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