Skip to content

[release-4.21] OCPBUGS-76266: Remove the collect-profiles job#1220

Merged
openshift-merge-bot[bot] merged 3 commits intoopenshift:release-4.21from
tmshort:PR-1219
Feb 6, 2026
Merged

[release-4.21] OCPBUGS-76266: Remove the collect-profiles job#1220
openshift-merge-bot[bot] merged 3 commits intoopenshift:release-4.21from
tmshort:PR-1219

Conversation

@tmshort
Copy link
Copy Markdown
Contributor

@tmshort tmshort commented Feb 5, 2026

This is an automated cherry-pick of #1215
Also pulls in #1216 and #1218
Alternative to #1219

/assign tmshort

tmshort and others added 3 commits February 5, 2026 14:16
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>
@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 5, 2026
@openshift-ci-robot
Copy link
Copy Markdown

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

  • expected dependent Jira Issue OCPBUGS-31547 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:

This is an automated cherry-pick of #1215
Alternative to #1219

/assign tmshort

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 added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 5, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Feb 5, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 5, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, 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
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 5, 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.

@jianzhangbjz
Copy link
Copy Markdown
Contributor

Test passed.

1. Build an OCP cluster with this PR
launch 4.21,openshift/operator-framework-olm#1220 aws
jiazha-mac:~ jiazha$ oc get clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.21.0-0-2026-02-06-014327-test-ci-ln-iy2tjmt-latest   True        False         6m7s    Cluster version is 4.21.0-0-2026-02-06-014327-test-ci-ln-iy2tjmt-latest
jiazha-mac:~ jiazha$ 

2. Check if the collect-profiles job is removed. LGTM.
jiazha-mac:~ jiazha$ oc project openshift-operator-lifecycle-manager 
Now using project "openshift-operator-lifecycle-manager" on server "https://api.ci-ln-iy2tjmt-76ef8.aws-2.ci.openshift.org:6443".
jiazha-mac:~ jiazha$ oc get cronjob
No resources found in openshift-operator-lifecycle-manager namespace.
jiazha-mac:~ jiazha$ 
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-5d855c47cd-k48sz        1/1     Running   0          35m
olm-operator-88c48d5bb-ntk4m             1/1     Running   0          35m
package-server-manager-6496fc467-mbxv4   2/2     Running   0          36m
packageserver-86886fc696-bbwsb           1/1     Running   0          33m
packageserver-86886fc696-kxdst           1/1     Running   0          33m
jiazha-mac:~ jiazha$ 
jiazha-mac:~ jiazha$ oc get networkpolicy
NAME                       POD-SELECTOR                 AGE
catalog-operator           app=catalog-operator         39m
default-deny-all-traffic   <none>                       39m
olm-operator               app=olm-operator             39m
package-server-manager     app=package-server-manager   38m
packageserver              app=packageserver            39m

@jianzhangbjz
Copy link
Copy Markdown
Contributor

/verified by @jianzhangbjz
/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 6, 2026
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 6, 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
/label backport-risk-assessed

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

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

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

@openshift-merge-bot openshift-merge-bot Bot merged commit 54812af into openshift:release-4.21 Feb 6, 2026
15 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

@tmshort: Jira Issue Verification Checks: Jira Issue OCPBUGS-76266
✔️ 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-76266 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 #1215
Also pulls in #1216 and #1218
Alternative to #1219

/assign tmshort

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 6, 2026

/cherry-pick release-4.20

@openshift-cherrypick-robot
Copy link
Copy Markdown

@tmshort: #1220 failed to apply on top of branch "release-4.20":

Applying: Remove the collect-profiles job
Applying: change to check collect-profile networkpolicy dynamically
Using index info to reconstruct a base tree...
A	tests-extension/test/qe/specs/olmv0_networkpolicy.go
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): tests-extension/test/qe/specs/olmv0_networkpolicy.go deleted in HEAD and modified in change to check collect-profile networkpolicy dynamically. Version change to check collect-profile networkpolicy dynamically of tests-extension/test/qe/specs/olmv0_networkpolicy.go left in tree.
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 0002 change to check collect-profile networkpolicy dynamically

Details

In response to this:

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