Remove prow jobs from placement-operator repo

[amartyasinha]

placement-operator repo is no longer maintained, thus removing prow jobs and configs for the same

Summary by CodeRabbit

This pull request removes all CI/CD automation configuration for the openstack-k8s-operators/placement-operator repository from the OpenShift CI infrastructure, reflecting that the placement-operator is no longer actively maintained.

Impact:

• CI Operator Configuration: Deletion of build and test pipeline definitions for the placement-operator, including configurations for the main branch and 18.0-fr5 variant. These files defined base images, build stages (including opm-builder), resource limits, and test workflows (functional tests, pre-commit checks, and KUTTL-based deployment tests).

• Prow Job Management: Removal of Prow job configurations and plugin settings for the repository, including approval workflows, external plugin integrations (cherrypick, backport-verifier, JIRA lifecycle, payload testing), merge strategies (rebase merge method), and merge eligibility rules.

• Automated Job Sanitization: Removal of prow job entries from the sanitization configuration, eliminating automated cleanup rules specific to the placement-operator.

The changes effectively decommission the repository from the OpenShift CI infrastructure, stopping automated builds, tests, and merge workflows for the placement-operator.

[openshift-merge-bot]

@amartyasinha, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

couldn't prepare candidate: couldn't rebase candidate onto 7cdb3d69ddbbe2a36d261cd9e4aed1f4cd519be8 due to conflicts

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: b4e06e8b-b7da-43d8-9533-6e01be2b0dab

📥 Commits

Reviewing files that changed from the base of the PR and between 7cdb3d6 and 815aec7.

⛔ Files ignored due to path filters (3)

• ci-operator/jobs/openstack-k8s-operators/placement-operator/OWNERS is excluded by !ci-operator/jobs/**
• ci-operator/jobs/openstack-k8s-operators/placement-operator/openstack-k8s-operators-placement-operator-18.0-fr5-presubmits.yaml is excluded by !ci-operator/jobs/**
• ci-operator/jobs/openstack-k8s-operators/placement-operator/openstack-k8s-operators-placement-operator-main-presubmits.yaml is excluded by !ci-operator/jobs/**

📒 Files selected for processing (7)

• ci-operator/config/openstack-k8s-operators/placement-operator/OWNERS
• ci-operator/config/openstack-k8s-operators/placement-operator/openstack-k8s-operators-placement-operator-18.0-fr5.yaml
• ci-operator/config/openstack-k8s-operators/placement-operator/openstack-k8s-operators-placement-operator-main.yaml
• core-services/prow/02_config/openstack-k8s-operators/placement-operator/OWNERS
• core-services/prow/02_config/openstack-k8s-operators/placement-operator/_pluginconfig.yaml
• core-services/prow/02_config/openstack-k8s-operators/placement-operator/_prowconfig.yaml
• core-services/sanitize-prow-jobs/_config.yaml

💤 Files with no reviewable changes (7)

• core-services/prow/02_config/openstack-k8s-operators/placement-operator/OWNERS
• core-services/prow/02_config/openstack-k8s-operators/placement-operator/_prowconfig.yaml
• ci-operator/config/openstack-k8s-operators/placement-operator/OWNERS
• core-services/prow/02_config/openstack-k8s-operators/placement-operator/_pluginconfig.yaml
• ci-operator/config/openstack-k8s-operators/placement-operator/openstack-k8s-operators-placement-operator-18.0-fr5.yaml
• ci-operator/config/openstack-k8s-operators/placement-operator/openstack-k8s-operators-placement-operator-main.yaml
• core-services/sanitize-prow-jobs/_config.yaml

---

Walkthrough

This pull request removes placement-operator from the OpenShift release CI infrastructure. The changes delete Prow plugin automation configuration and presubmit job pipeline references across multiple configuration files within the release repository.

Changes

Placement-operator CI Infrastructure Removal

Layer / File(s)	Summary
Prow plugin and workflow automation removal core-services/prow/02_config/openstack-k8s-operators/placement-operator/_pluginconfig.yaml	Complete deletion of Prow plugin configuration including approve, LGTM, external plugin endpoints, and trigger settings that controlled automation for placement-operator.
Presubmit job pipeline references removal core-services/sanitize-prow-jobs/_config.yaml	Removal of both openstack-k8s-operators-placement-operator-18.0-fr5 and main branch presubmit job entries from the CI pipeline configuration.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

lgtm, approved

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Remove prow jobs from placement-operator repo' directly and clearly describes the main change—deletion of Prow jobs and configurations for the placement-operator, matching the PR objectives.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	This PR only deletes prow/ci-operator YAML and OWNERS; there are no Ginkgo tests (no ginkgo imports or It/Describe titles) in the affected repo paths.
Test Structure And Quality	✅ Passed	PR deletes only OWNERS and prow/ci YAML files (no Ginkgo *_test.go touched), so there’s no Ginkgo test code quality to assess. citeturn0view0
Microshift Test Compatibility	✅ Passed	PR #80460 deletes only CI/prow YAML + OWNERS files (21 deletions) and adds no Go/Ginkgo e2e tests, so MicroShift test compatibility is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR only deletes placement-operator OWNERS and Prow/CI YAML configs; no new Go/Ginkgo e2e tests were added (diff shows 0 Go files, only YAML/OWNERS deletions).
Topology-Aware Scheduling Compatibility	✅ Passed	PR only deletes placement-operator Prow/CI config and OWNERS files; no deployment manifests/operator code/controllers are added or modified, so no new topology-dependent scheduling constraints are...
Ote Binary Stdout Contract	✅ Passed	PR #80460 only deletes placement-operator CI/prow config files (OWNERS/YAML); it does not change OTE binary Go code or any main/init/TestMain stdout logic.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR only deletes Prow/CI YAML and OWNERS; repo scan found no placement-operator Ginkgo e2e tests or _test.go files with ginkgo constructs to flag.
No-Weak-Crypto	✅ Passed	Checked all files deleted by PR #80460 (placement-operator CI/Prow YAML + OWNERS + sanitize config) for MD5/SHA1/DES/RC4/3DES/Blowfish/ECB and constant-time/crypto tokens; none found.
Container-Privileges	✅ Passed	PR removes placement-operator CI/prow config files; in this checkout those paths don’t exist, and the only related _config.yaml contains no privileged/hostPID/hostNetwork/hostIPC/SYS_ADMIN/allowPri...
No-Sensitive-Data-In-Logs	✅ Passed	PR #80460 deletes 21 files with 0 additions. Spot-checked deleted YAMLs/OWNERS: no password/token/Authorization strings found.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@amartyasinha: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[gibizer]

Yepp. We moved the placement-operator logic into the nova-operator and therefore the placement-operator repo is not maintained any more so we don't need CI runs on it any more.

[abays]

/lgtm

[stuggi]

/lgtm

[abays]

/pj-rehearse ack

[openshift-merge-bot]

@abays: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[hector-vido]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abays, amartyasinha, gibizer, hector-vido, stuggi

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:

• ci-operator/config/openstack-k8s-operators/placement-operator/OWNERS [abays,gibizer,hector-vido,stuggi]
• ci-operator/jobs/openstack-k8s-operators/placement-operator/OWNERS [abays,gibizer,hector-vido,stuggi]
• core-services/prow/02_config/openstack-k8s-operators/placement-operator/OWNERS [abays,gibizer,hector-vido,stuggi]
• core-services/sanitize-prow-jobs/OWNERS [hector-vido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@amartyasinha: 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-ci]

@amartyasinha: Updated the following 2 configmaps:

• config configmap in namespace ci at cluster app.ci using the following files:
  • key core-services-prow-02_config-openstack-k8s-operators-placement-operator-_prowconfig.yaml using file ``
• config configmap in namespace ci at cluster core-ci using the following files:
  • key core-services-prow-02_config-openstack-k8s-operators-placement-operator-_prowconfig.yaml using file ``

Details

In response to this:

placement-operator repo is no longer maintained, thus removing prow jobs and configs for the same

Summary by CodeRabbit

This pull request removes all CI/CD automation configuration for the openstack-k8s-operators/placement-operator repository from the OpenShift CI infrastructure, reflecting that the placement-operator is no longer actively maintained.

Impact:

• CI Operator Configuration: Deletion of build and test pipeline definitions for the placement-operator, including configurations for the main branch and 18.0-fr5 variant. These files defined base images, build stages (including opm-builder), resource limits, and test workflows (functional tests, pre-commit checks, and KUTTL-based deployment tests).

• Prow Job Management: Removal of Prow job configurations and plugin settings for the repository, including approval workflows, external plugin integrations (cherrypick, backport-verifier, JIRA lifecycle, payload testing), merge strategies (rebase merge method), and merge eligibility rules.

• Automated Job Sanitization: Removal of prow job entries from the sanitization configuration, eliminating automated cleanup rules specific to the placement-operator.

The changes effectively decommission the repository from the OpenShift CI infrastructure, stopping automated builds, tests, and merge workflows for the placement-operator.

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.