Skip to content

[release-4.20] OCPBUGS-76335: Remove the collect-profiles job#1223

Merged
openshift-merge-bot[bot] merged 3 commits intoopenshift:release-4.20from
tmshort:OCPBUGS-76335
Feb 11, 2026
Merged

[release-4.20] OCPBUGS-76335: Remove the collect-profiles job#1223
openshift-merge-bot[bot] merged 3 commits intoopenshift:release-4.20from
tmshort:OCPBUGS-76335

Conversation

@tmshort
Copy link
Copy Markdown
Contributor

@tmshort tmshort commented Feb 6, 2026

Delete the collect-profiles job from Microshift and mark for deleed in OCP. Includes all relevant resources.

This is an automated cherry-pick of #1220

Includes: operator-framework/operator-lifecycle-manager#3742, which was part of #1201

(cherry picked from commit e497da1)

Delete the collect-profiles job from Microshift and mark for deleed in OCP.
Includes all relevant resources.

Signed-off-by: Todd Short <todd.short@me.com>
(cherry picked from commit e497da1)
@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 Feb 6, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@tmshort: This pull request references Jira Issue OCPBUGS-76335, which is invalid:

  • expected dependent Jira Issue OCPBUGS-76266 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.

Details

In response to this:

Delete the collect-profiles job from Microshift and mark for deleed in OCP. Includes all relevant resources.

This is an automated cherry-pick of #1220

(cherry picked from commit e497da1)

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

openshift-ci Bot commented Feb 6, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tmshort

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 Feb 6, 2026
@tmshort
Copy link
Copy Markdown
Contributor Author

tmshort commented Feb 6, 2026

/retest-required

1 similar comment
@jianzhangbjz
Copy link
Copy Markdown
Contributor

/retest-required

@jianzhangbjz
Copy link
Copy Markdown
Contributor

/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 Feb 9, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@jianzhangbjz: This pull request references Jira Issue OCPBUGS-76335, 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.20.z) matches configured target version for branch (4.20.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-76266 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-76266 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), skipping review request.

Details

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.

@jianzhangbjz
Copy link
Copy Markdown
Contributor

jianzhangbjz commented Feb 9, 2026

Failed to build OCP cluster, https://prow.ci.openshift.org/view/gs/test-platform-results/logs/release-openshift-origin-installer-launch-aws-modern/2020730120880263168

launch 4.20,openshift/operator-framework-olm#1223 aws

Got the same error as e2e-gcp-olm

level=error msg=failed to initialize the cluster: Cluster operator operator-lifecycle-manager is not available: timed out waiting for the condition
Installer exit with code 6


: operator conditions operator-lifecycle-manager expand_less | 0s
-- | --
{Operator unavailable (null): operator is not reporting conditions  Operator unavailable (null): operator is not reporting conditions}

CVO:
1956:2026-02-09T04:14:53.394541683Z W0209 04:14:53.394369       1 helper.go:97] Secret "openshift-operator-lifecycle-manager/pprof-cert" not found. It either has already been removed or it has never been installed on this cluster.
Kubelet:
34899:Feb 09 04:57:52.839803 ci-op-q4giyhil-6082f-xhw5k-master-0 kubenswrapper[2619]: E0209 04:57:52.839720    2619 secret.go:189] Couldn't get secret openshift-operator-lifecycle-manager/pprof-cert: secret "pprof-cert" not found

Copy link
Copy Markdown
Contributor

@oceanc80 oceanc80 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/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 Feb 9, 2026
@oceanc80
Copy link
Copy Markdown
Contributor

oceanc80 commented Feb 9, 2026

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Feb 9, 2026
@jianzhangbjz
Copy link
Copy Markdown
Contributor

Hi @tmshort , I think the reason for #1223 (comment) is that the secretName: pprof-cert has been removed, which was introduced in #1129

jiazha-mac:~ jiazha$ omg get deploy catalog-operator -o yaml |grep -i secret
                f:secret:
                  f:secretName: {}
                f:secret:
                  f:secretName: {}
        secret:
          secretName: catalog-operator-serving-cert
        secret:
          secretName: pprof-cert

jiazha-mac:~ jiazha$ omg get secret
NAME                                         TYPE                     DATA  AGE
builder-dockercfg-98gg5                      kubernetes.io/dockercfg  1     46m
catalog-operator-serving-cert                kubernetes.io/tls        2     55m
default-dockercfg-4x5mz                      kubernetes.io/dockercfg  1     46m
deployer-dockercfg-hspxr                     kubernetes.io/dockercfg  1     46m
olm-operator-serviceaccount-dockercfg-5tc5l  kubernetes.io/dockercfg  1     46m
olm-operator-serving-cert                    kubernetes.io/tls        2     55m
package-server-manager-serving-cert          kubernetes.io/tls        2     55m

We need to remove it in the Deployment for this cherry-pick.

@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 9, 2026
@tmshort
Copy link
Copy Markdown
Contributor Author

tmshort commented Feb 9, 2026

/retest-required

@tmshort
Copy link
Copy Markdown
Contributor Author

tmshort commented Feb 9, 2026

/retest

@jianzhangbjz
Copy link
Copy Markdown
Contributor

Hi @tmshort , it failed as follows. I believe we also need to pull operator-framework/operator-lifecycle-manager#3742

jiazha-mac:must-gather-collect jiazha$ omg logs catalog-operator-56b7b769c7-tltr9
2026-02-09T23:02:50.238068714Z time="2026-02-09T23:02:50Z" level=info msg="log level info"
2026-02-09T23:02:50.238679894Z time="2026-02-09T23:02:50Z" level=info msg="TLS keys set, using https for metrics"
2026-02-09T23:02:50.238784894Z Error: error setting up health/metric/pprof service: certificate monitoring for client-ca failed: open : no such file or directory
2026-02-09T23:02:50.238784894Z error setting up health/metric/pprof service: certificate monitoring for client-ca failed: open : no such file or directory

jiazha-mac:must-gather-collect jiazha$ omg logs olm-operator-fbbcb9d86-w9q4x 
2026-02-09T23:02:09.240459288Z time="2026-02-09T23:02:09Z" level=info msg="log level info"
2026-02-09T23:02:09.240941188Z time="2026-02-09T23:02:09Z" level=info msg="TLS keys set, using https for metrics"
2026-02-09T23:02:09.241410537Z time="2026-02-09T23:02:09Z" level=fatal msg="Error setting up health/metric/pprof service: certificate monitoring for client-ca failed: open : no such file or directory"

@openshift-ci-robot
Copy link
Copy Markdown

@tmshort: This pull request references Jira Issue OCPBUGS-76335, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.z) matches configured target version for branch (4.20.z)
  • bug is in the state POST, 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-76266 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-76266 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), skipping review request.

Details

In response to this:

Delete the collect-profiles job from Microshift and mark for deleed in OCP. Includes all relevant resources.

This is an automated cherry-pick of #1220

Includes: operator-framework/operator-lifecycle-manager#3742, which was part of #1201

(cherry picked from commit e497da1)

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.

@tmshort
Copy link
Copy Markdown
Contributor Author

tmshort commented Feb 10, 2026

/test e2e-gcp-olm

@jianzhangbjz
Copy link
Copy Markdown
Contributor

/retest-required

@jianzhangbjz
Copy link
Copy Markdown
Contributor

Test passed.

1. Build an OCP cluster with this PR
launch 4.20,openshift/operator-framework-olm#1223 aws
jiazha-mac:~ jiazha$ oc get clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.20.0-0-2026-02-11-014600-test-ci-ln-ki6vxyb-latest   True        False         8m47s   Cluster version is 4.20.0-0-2026-02-11-014600-test-ci-ln-ki6vxyb-latest
jiazha-mac:~ jiazha$ 

2. Check if the collect-profiles job is removed. LGTM.
jiazha-mac:~ jiazha$ oc get cronjob
No resources found in openshift-operator-lifecycle-manager namespace.
jiazha-mac:~ jiazha$ oc get job
No resources found in openshift-operator-lifecycle-manager namespace.
jiazha-mac:~ jiazha$ 
jiazha-mac:~ jiazha$ oc get pods
NAME                                      READY   STATUS    RESTARTS   AGE
catalog-operator-7fcf58db8-zswhl          1/1     Running   0          36m
olm-operator-657cbb64f6-m45th             1/1     Running   0          36m
package-server-manager-76fc745999-sglpq   2/2     Running   0          36m
packageserver-745477f5bd-d7fbp            1/1     Running   0          33m
packageserver-745477f5bd-v2nqf            1/1     Running   0          33m
jiazha-mac:~ jiazha$ 

jiazha-mac:~ jiazha$ oc get networkpolicy
NAME                       POD-SELECTOR                 AGE
catalog-operator           app=catalog-operator         40m
default-deny-all-traffic   <none>                       40m
olm-operator               app=olm-operator             40m
package-server-manager     app=package-server-manager   40m
packageserver              app=packageserver            40m

@jianzhangbjz
Copy link
Copy Markdown
Contributor

/verified by @jianzhangbjz
/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Feb 11, 2026
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 11, 2026
@openshift-ci-robot
Copy link
Copy Markdown

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

Details

In response to this:

/verified by @jianzhangbjz
/lgtm

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

openshift-ci Bot commented Feb 11, 2026

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

@openshift-merge-bot openshift-merge-bot Bot merged commit a685cb3 into openshift:release-4.20 Feb 11, 2026
13 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

@tmshort: Jira Issue Verification Checks: Jira Issue OCPBUGS-76335
✔️ 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-76335 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:

Delete the collect-profiles job from Microshift and mark for deleed in OCP. Includes all relevant resources.

This is an automated cherry-pick of #1220

Includes: operator-framework/operator-lifecycle-manager#3742, which was part of #1201

(cherry picked from commit e497da1)

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.

@tmshort
Copy link
Copy Markdown
Contributor Author

tmshort commented Feb 11, 2026

/cherry-pick release-4.19

@tmshort tmshort deleted the OCPBUGS-76335 branch February 11, 2026 18:42
@openshift-cherrypick-robot
Copy link
Copy Markdown

@tmshort: #1223 failed to apply on top of branch "release-4.19":

Applying: Remove the collect-profiles job
Using index info to reconstruct a base tree...
M	manifests/0000_50_olm_07-collect-profiles.cronjob.yaml
A	manifests/0000_50_olm_07-collect-profiles.networkpolicy.yaml
M	microshift-manifests/0000_50_olm_07-collect-profiles.cronjob.yaml
A	microshift-manifests/0000_50_olm_07-collect-profiles.networkpolicy.yaml
M	scripts/generate_crds_manifests.sh
Falling back to patching base and 3-way merge...
Auto-merging scripts/generate_crds_manifests.sh
CONFLICT (content): Merge conflict in scripts/generate_crds_manifests.sh
CONFLICT (modify/delete): microshift-manifests/0000_50_olm_07-collect-profiles.cronjob.yaml deleted in Remove the collect-profiles job and modified in HEAD. Version HEAD of microshift-manifests/0000_50_olm_07-collect-profiles.cronjob.yaml left in tree.
Removing microshift-manifests/0000_50_olm_00-pprof-secret.yaml
Removing microshift-manifests/0000_50_olm_00-pprof-rbac.yaml
Removing microshift-manifests/0000_50_olm_00-pprof-config.yaml
CONFLICT (modify/delete): manifests/0000_50_olm_07-collect-profiles.networkpolicy.yaml deleted in HEAD and modified in Remove the collect-profiles job. Version Remove the collect-profiles job of manifests/0000_50_olm_07-collect-profiles.networkpolicy.yaml left in tree.
Auto-merging manifests/0000_50_olm_07-collect-profiles.cronjob.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 set advice.mergeConflict false"
Patch failed at 0001 Remove the collect-profiles job

Details

In response to this:

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

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

8 participants