Skip to content

[release-4.18] OCPBUGS-76924: Remove the collect-profiles job#1231

Merged
openshift-merge-bot[bot] merged 3 commits intoopenshift:release-4.18from
openshift-cherrypick-robot:cherry-pick-1229-to-release-4.18
Feb 14, 2026
Merged

[release-4.18] OCPBUGS-76924: Remove the collect-profiles job#1231
openshift-merge-bot[bot] merged 3 commits intoopenshift:release-4.18from
openshift-cherrypick-robot:cherry-pick-1229-to-release-4.18

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

This is an automated cherry-pick of #1229

/assign tmshort

tmshort and others added 3 commits February 13, 2026 21:17
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)
(cherry picked from commit bd9e0cd)
@openshift-ci-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot: Jira Issue OCPBUGS-76587 has been cloned as Jira Issue OCPBUGS-76924. Will retitle bug to link to clone.
/retitle [release-4.18] OCPBUGS-76924: Remove the collect-profiles job

Details

In response to this:

This is an automated cherry-pick of #1229

/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 changed the title [release-4.18] OCPBUGS-76587: Remove the collect-profiles job [release-4.18] OCPBUGS-76924: Remove the collect-profiles job Feb 13, 2026
@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 13, 2026
@openshift-ci-robot
Copy link
Copy Markdown

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

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

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

Copy link
Copy Markdown
Member

@rashmigottipati rashmigottipati left a comment

Choose a reason for hiding this comment

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

/lgtm

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

tmshort commented Feb 13, 2026

/approve

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 13, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, rashmigottipati, 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 13, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

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

@jianzhangbjz
Copy link
Copy Markdown
Contributor

Test passed.

1. Build an OCP cluster with this PR
launch 4.18,openshift/operator-framework-olm#1231 aws
jiazha-mac:~ jiazha$ oc get clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.18.0-0-2026-02-14-020643-test-ci-ln-vx43bp2-latest   True        False         11m     Cluster version is 4.18.0-0-2026-02-14-020643-test-ci-ln-vx43bp2-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-vx43bp2-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$ oc get job
No resources found in openshift-operator-lifecycle-manager namespace.
jiazha-mac:~ jiazha$ oc get pods
NAME                                     READY   STATUS    RESTARTS      AGE
catalog-operator-6dcb4f8755-dhk9d        1/1     Running   0             42m
olm-operator-5f77896967-9tvgk            1/1     Running   0             42m
package-server-manager-8d55794d4-6fvjp   2/2     Running   1 (29m ago)   42m
packageserver-549bd99466-6qlkp           1/1     Running   0             36m
packageserver-549bd99466-hrgkk           1/1     Running   0             36m
jiazha-mac:~ jiazha$ oc get networkpolicy
No resources found in openshift-operator-lifecycle-manager namespace.
jiazha-mac:~ jiazha$ 

@jianzhangbjz
Copy link
Copy Markdown
Contributor

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

@jianzhangbjz: This pull request references Jira Issue OCPBUGS-76924, 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.18.z) matches configured target version for branch (4.18.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-76587 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-76587 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.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
/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.

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 14, 2026
@openshift-ci-robot
Copy link
Copy Markdown

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

Details

In response to this:

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

@openshift-merge-bot openshift-merge-bot Bot merged commit c2df9e7 into openshift:release-4.18 Feb 14, 2026
12 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-76924
✔️ 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-76924 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 #1229

/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

tmshort commented Feb 16, 2026

/cherry-pick release-4.17

@openshift-cherrypick-robot
Copy link
Copy Markdown
Author

@tmshort: new pull request created: #1232

Details

In response to this:

/cherry-pick release-4.17

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

Fix included in accepted release 4.18.0-0.nightly-2026-02-17-175651

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.

9 participants