Skip to content

[release-4.19] OCPBUGS-76587: Remove the collect-profiles job#1229

Merged
openshift-merge-bot[bot] merged 3 commits intoopenshift:release-4.19from
tmshort:OCPBUGS-76587
Feb 13, 2026
Merged

[release-4.19] OCPBUGS-76587: Remove the collect-profiles job#1229
openshift-merge-bot[bot] merged 3 commits intoopenshift:release-4.19from
tmshort:OCPBUGS-76587

Conversation

@tmshort
Copy link
Copy Markdown
Contributor

@tmshort tmshort commented Feb 11, 2026

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

This is an automated cherry-pick of #1223

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

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

  • expected dependent Jira Issue OCPBUGS-76335 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 deleted in OCP. Includes all relevant resources.

This is an automated cherry-pick of #1223

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 11, 2026
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 11, 2026
@jianzhangbjz
Copy link
Copy Markdown
Contributor

/jira refresh

@jianzhangbjz
Copy link
Copy Markdown
Contributor

/retest-required

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

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

@tmshort
Copy link
Copy Markdown
Contributor Author

tmshort commented Feb 12, 2026

/test okd-scos-images

@rashmigottipati
Copy link
Copy Markdown
Member

/retest-required

@jianzhangbjz
Copy link
Copy Markdown
Contributor

Test passed.

1. Build an OCP cluster with this PR
launch 4.19,openshift/operator-framework-olm#1229 aws
jiazha-mac:~ jiazha$ oc get clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.19.0-0-2026-02-12-013318-test-ci-ln-w0dp5pk-latest   True        False         12m     Cluster version is 4.19.0-0-2026-02-12-013318-test-ci-ln-w0dp5pk-latest

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-w0dp5pk-76ef8.aws-4.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-6ffbf9f699-l2qc4         1/1     Running   0          40m
olm-operator-78676fc46-9b9rt              1/1     Running   0          40m
package-server-manager-648d967dd7-j6jtz   2/2     Running   0          40m
packageserver-6c974dd4bc-58f5c            1/1     Running   0          36m
packageserver-6c974dd4bc-n8mcx            1/1     Running   0          36m

jiazha-mac:~ jiazha$ oc get networkpolicy
No resources found in openshift-operator-lifecycle-manager namespace.

@jianzhangbjz
Copy link
Copy Markdown
Contributor

Raised this issue to the DPTP team on Slack: https://redhat-internal.slack.com/archives/CBN38N3MW/p1770863997066949?thread_ts=1765791339.549229&cid=CBN38N3MW

error: failed to push image registry.build08.ci.openshift.org/ci-op-jnsbx1xn/release:latest: unable to upload new layer (0): Patch "https://registry.build08.ci.openshift.org/v2/ci-op-jnsbx1xn/release/blobs/uploads/67990363-a9b1-49ae-b1a1-1f890fd5ce6e?_state=wZQ9-UlbVg9Yoh-fLzJeSpfo0HPK0RWW8I3YPEPt3L97Ik5hbWUiOiJjaS1vcC1qbnNieDF4bi9yZWxlYXNlIiwiVVVJRCI6IjY3OTkwMzYzLWE5YjEtNDlhZS1iMWExLTFmODkwZmQ1Y2U2ZSIsIk9mZnNldCI6MCwiU3RhcnRlZEF0IjoiMjAyNi0wMi0xMlQwMTo1NToyNy41OTkxODYxMzdaIn0%3D": unknown version reference "machine-os"

@jianzhangbjz
Copy link
Copy Markdown
Contributor

/verified by @jianzhangbjz

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 12, 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

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

/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 12, 2026
@rashmigottipati
Copy link
Copy Markdown
Member

/test okd-scos-images

2 similar comments
@tmshort
Copy link
Copy Markdown
Contributor Author

tmshort commented Feb 12, 2026

/test okd-scos-images

@rashmigottipati
Copy link
Copy Markdown
Member

/test okd-scos-images

@tmshort
Copy link
Copy Markdown
Contributor Author

tmshort commented Feb 13, 2026

/override okd-scos-images
Per openshift/release#74547 OKD images are no longer need to be built for 4.20 or earlier.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 13, 2026

@tmshort: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • okd-scos-images

Only the following failed contexts/checkruns were expected:

  • ci/prow/e2e-gcp-console-olm
  • ci/prow/e2e-gcp-olm
  • ci/prow/e2e-gcp-ovn
  • ci/prow/e2e-upgrade
  • ci/prow/images
  • ci/prow/okd-scos-images
  • ci/prow/unit-api
  • ci/prow/unit-olm
  • ci/prow/unit-psm
  • ci/prow/unit-registry
  • ci/prow/verify
  • ci/prow/verify-deps
  • pull-ci-openshift-operator-framework-olm-main-e2e-gcp-console-olm
  • pull-ci-openshift-operator-framework-olm-main-e2e-gcp-olm
  • pull-ci-openshift-operator-framework-olm-main-e2e-gcp-ovn
  • pull-ci-openshift-operator-framework-olm-main-e2e-upgrade
  • pull-ci-openshift-operator-framework-olm-main-images
  • pull-ci-openshift-operator-framework-olm-main-okd-scos-images
  • pull-ci-openshift-operator-framework-olm-main-unit-api
  • pull-ci-openshift-operator-framework-olm-main-unit-olm
  • pull-ci-openshift-operator-framework-olm-main-unit-psm
  • pull-ci-openshift-operator-framework-olm-main-unit-registry
  • pull-ci-openshift-operator-framework-olm-main-verify
  • pull-ci-openshift-operator-framework-olm-main-verify-deps
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

/override okd-scos-images
Per openshift/release#74547 OKD images are no longer need to be built for 4.20 or earlier.

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.

@tmshort
Copy link
Copy Markdown
Contributor Author

tmshort commented Feb 13, 2026

/override ci/prow/okd-scos-images
Per openshift/release#74547 OKD images are no longer need to be built for 4.20 or earlier.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Feb 13, 2026

@tmshort: Overrode contexts on behalf of tmshort: ci/prow/okd-scos-images

Details

In response to this:

/override ci/prow/okd-scos-images
Per openshift/release#74547 OKD images are no longer need to be built for 4.20 or earlier.

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

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

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
/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: 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-merge-bot openshift-merge-bot Bot merged commit 05a5a75 into openshift:release-4.19 Feb 13, 2026
13 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

@tmshort: Jira Issue Verification Checks: Jira Issue OCPBUGS-76587
✔️ 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-76587 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 deleted in OCP. Includes all relevant resources.

This is an automated cherry-pick of #1223

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 tmshort deleted the OCPBUGS-76587 branch February 13, 2026 21:16
@tmshort
Copy link
Copy Markdown
Contributor Author

tmshort commented Feb 13, 2026

/cherry-pick release-4.18

@openshift-cherrypick-robot
Copy link
Copy Markdown

@tmshort: new pull request created: #1231

Details

In response to this:

/cherry-pick release-4.18

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