Skip to content

Revert "tide: use org-level query for openstack-k8s-operators" - #82821

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
Prucek:revert-82798-fix-openstack-tide-query
Aug 3, 2026
Merged

Revert "tide: use org-level query for openstack-k8s-operators"#82821
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
Prucek:revert-82798-fix-openstack-tide-query

Conversation

@Prucek

@Prucek Prucek commented Aug 3, 2026

Copy link
Copy Markdown
Member

Reverts #82798

Summary by CodeRabbit

This PR reverts the organization-level Tide query for openstack-k8s-operators.

It restores repository-specific Prow configuration for the affected component repositories. These configurations define repository-specific Tide requirements, including approved and lgtm labels and blocking labels.

It also restores repository-level plugins such as approve, assign, hold, lgtm, lifecycle, verify-owners, wip, and needs-rebase.

@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Walkthrough

The PR moves Prow settings from the organization level to repository-level configurations. Most repositories receive approval, LGTM, needs-rebase, standard plugin, and Tide settings. The organization-level configuration retains only repo-brancher-controller. The tcib Tide query is scoped to its repository.

Changes

Repository Prow policy configuration

Layer / File(s) Summary
Organization plugin configuration
core-services/prow/02_config/openstack-k8s-operators/_pluginconfig.yaml
The organization-level plugin configuration now contains only repo-brancher-controller for push events.
Repository plugin and review policies
core-services/prow/02_config/openstack-k8s-operators/*/_pluginconfig.yaml
Repository configurations add approval rules, disable self-approval where configured, enable review-based LGTM, register needs-rebase, and add standard Prow plugins.
Repository Tide merge queries
core-services/prow/02_config/openstack-k8s-operators/*/_prowconfig.yaml
Repository Tide queries require approved and lgtm labels and exclude repository-specific blocking labels. The tcib query is scoped to openstack-k8s-operators/tcib.

Estimated code review effort: 3 (Moderate) | ~25 minutes

Possibly related PRs

  • openshift/release#82745: Adds similar repository-specific Prow plugin, approval, LGTM, external-plugin, and Tide configurations.
  • openshift/release#82798: Modifies the same OpenStack Kubernetes Operators Prow configuration area with complementary organization-level changes.

Suggested reviewers: hector-vido, joeavaikath

🚥 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 clearly identifies the reversal of the organization-level Tide query change, which matches the pull request objective.
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 The HEAD diff changes 73 YAML files only; searches of added lines and all changed files found no Ginkgo test declarations or dynamic test titles.
Test Structure And Quality ✅ Passed The pull request changes 73 YAML configuration files only; no Ginkgo test code or cluster-test operations are present, so these test-quality requirements do not apply.
Microshift Test Compatibility ✅ Passed The pull request changes 73 YAML configuration files only; it adds no Ginkgo tests or test declarations that require MicroShift compatibility review.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The commit changes only Prow YAML configuration files; it adds no Ginkgo e2e tests or It/Describe/Context/When declarations, so SNO test compatibility is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed The 73 changed files are Prow plugin and Tide YAML only; no deployment manifests, operator code, controllers, or topology-sensitive scheduling constraints were modified.
Ote Binary Stdout Contract ✅ Passed All 73 changed files are YAML Prow configurations; no executable source or process-level stdout writes were added, so the OTE binary contract is unaffected.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The diff changes only 73 YAML Prow configuration files; it adds no Ginkgo test constructs or test source, so this compatibility check is not applicable.
No-Weak-Crypto ✅ Passed The commit changes only Prow YAML configuration. Exact scans of all 1,193 added lines found no MD5, SHA1, DES, RC4, Blowfish, ECB, crypto, or secret-comparison usage.
Container-Privileges ✅ Passed All 73 changed files are Prow _pluginconfig/_prowconfig YAML files; scans of 1,193 added lines found no privileged, host*, SYS_ADMIN, root, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs ✅ Passed The PR changes only Prow YAML configuration; searches of all added and changed content found no logging statements or password, token, credential, or PII fields.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 3, 2026
@openshift-ci
openshift-ci Bot requested review from Akrog and abays August 3, 2026 15:25
@openshift-ci

openshift-ci Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

@Prucek: 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 added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Aug 3, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@Prucek: 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.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@core-services/prow/02_config/openstack-k8s-operators/glance-operator/_prowconfig.yaml`:
- Around line 1-14: Replace the per-repository tide.queries entries in all
listed _prowconfig.yaml files with the organization-level query using orgs:
[openstack-k8s-operators], preserving the required organization-level plugin
configuration and avoiding individual repos qualifiers in each query.

In
`@core-services/prow/02_config/openstack-k8s-operators/lightspeed-mcps/_pluginconfig.yaml`:
- Around line 45-47: Add review_acts_as_lgtm: true under the lgtm configuration
in
core-services/prow/02_config/openstack-k8s-operators/lightspeed-mcps/_pluginconfig.yaml
lines 45-47, lightspeed-operator/_pluginconfig.yaml lines 45-47, and
lightspeed-rag-content/_pluginconfig.yaml lines 45-47, preserving the existing
repository entries.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 1842f07b-526e-47ab-8272-4a28ebd6a732

📥 Commits

Reviewing files that changed from the base of the PR and between 200e3d8 and eec99f1.

📒 Files selected for processing (73)
  • core-services/prow/02_config/openstack-k8s-operators/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/architecture/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/barbican-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/barbican-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/ci-framework/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/ci-framework/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/ci-playground/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/cinder-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/cinder-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/data-plane-adoption/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/data-plane-adoption/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/designate-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/designate-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/edpm-ansible/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/edpm-ansible/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/edpm-image-builder/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/edpm-image-builder/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/glance-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/glance-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/heat-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/heat-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/horizon-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/horizon-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/infra-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/infra-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/install_yamls/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/install_yamls/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/ironic-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/ironic-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/keystone-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/keystone-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/lightspeed-mcps/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/lightspeed-mcps/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/lightspeed-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/lightspeed-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/lightspeed-rag-content/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/lightspeed-rag-content/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/manila-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/manila-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/mariadb-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/mariadb-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/neutron-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/neutron-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/nova-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/nova-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/octavia-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/octavia-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/openstack-baremetal-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/openstack-baremetal-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/openstack-k8s-operators-ci/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/openstack-k8s-operators-ci/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/openstack-must-gather/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/openstack-must-gather/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/openstack-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/openstack-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/osp-director-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/osp-director-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/ovn-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/ovn-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/repo-setup/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/repo-setup/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/sg-core/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/sg-core/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/swift-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/swift-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/tcib/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/tcib/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/telemetry-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/telemetry-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/test-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/test-operator/_prowconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/watcher-operator/_pluginconfig.yaml
  • core-services/prow/02_config/openstack-k8s-operators/watcher-operator/_prowconfig.yaml
💤 Files with no reviewable changes (1)
  • core-services/prow/02_config/openstack-k8s-operators/_pluginconfig.yaml

Comment on lines +1 to +14
tide:
queries:
- labels:
- approved
- lgtm
missingLabels:
- backports/unvalidated-commits
- do-not-merge/hold
- do-not-merge/invalid-owners-file
- do-not-merge/work-in-progress
- jira/invalid-bug
- needs-rebase
repos:
- openstack-k8s-operators/glance-operator

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🩺 Stability & Availability | 🟠 Major | 🏗️ Heavy lift

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -e
printf '%s\n' '--- target files ---'
for f in \
  core-services/prow/02_config/openstack-k8s-operators/glance-operator/_prowconfig.yaml \
  core-services/prow/02_config/openstack-k8s-operators/heat-operator/_prowconfig.yaml \
  core-services/prow/02_config/openstack-k8s-operators/horizon-operator/_prowconfig.yaml \
  core-services/prow/02_config/openstack-k8s-operators/infra-operator/_prowconfig.yaml \
  core-services/prow/02_config/openstack-k8s-operators/install_yamls/_prowconfig.yaml \
  core-services/prow/02_config/openstack-k8s-operators/ironic-operator/_prowconfig.yaml \
  core-services/prow/02_config/openstack-k8s-operators/keystone-operator/_prowconfig.yaml
do
  printf '\n### %s\n' "$f"
  cat -n "$f"
done

printf '%s\n' '--- related Tide configuration ---'
rg -n -C 3 'openstack-k8s-operators|backports/unvalidated-commits|tide:|queries:' core-services/prow | head -n 500

printf '%s\n' '--- repository-wide matching prow configs ---'
git ls-files 'core-services/prow/**/_prowconfig.yaml' | wc -l
git ls-files 'core-services/prow/**/_prowconfig.yaml' | rg 'openstack-k8s-operators|prowconfig' | head -n 200

Repository: openshift/release

Length of output: 50373


🌐 Web query:

openshift/release pull request 82798 Tide resource limit 35 repo qualifiers

💡 Result:

There is no public record of a pull request numbered 82798 in the openshift/release repository. Search results indicate that pull request numbers in the openshift/release repository have recently reached the 81xxx range (e.g., #81370 [1], #81744 [2]). It is possible that the PR number mentioned is either incorrect, from a different repository, or refers to a future or private pull request. Regarding the technical context of the query, Tide is a Prow component used in OpenShift CI to manage pull request merges [3][4]. Tide uses GitHub search queries to identify mergeable pull requests based on criteria such as labels, authors, and repository qualifications [5][3]. Configuration for Tide is managed in _prowconfig.yaml files [4]. While there are various configuration limits in Prow and Tide (such as API rate limits [3][6] and query management [6]), there is no widely documented "35 repo qualifiers" resource limit associated with Tide in public OpenShift or Kubernetes documentation. It is likely that the query refers to a specific configuration adjustment or troubleshooting effort within an internal OpenShift release engineering context that is not publicly accessible.

Citations:


🏁 Script executed:

#!/bin/bash
set -e

printf '%s\n' '--- OpenStack K8s Operators configuration files ---'
git ls-files 'core-services/prow/02_config/openstack-k8s-operators/**' | sed -n '1,200p'

printf '%s\n' '--- organization-scoped Tide queries ---'
rg -n -C 5 'openstack-k8s-operators:' core-services/prow/02_config core-services/prow/01_config 2>/dev/null | head -n 200

printf '%s\n' '--- Tide query merge and generation documentation/code references ---'
rg -n -i -C 3 'prowconfig|tide.*quer|queries.*tide|github.*search|repo qualifier|resource limit' \
  README.md docs core-services prow 2>/dev/null | head -n 400

printf '%s\n' '--- recent history for the affected directory ---'
git log --oneline -20 -- core-services/prow/02_config/openstack-k8s-operators

printf '%s\n' '--- repository state and candidate comparison refs ---'
git status --short
git branch --all --no-color | head -n 50

Repository: openshift/release

Length of output: 30043


🌐 Web query:

site:github.com/openshift/release "openstack-k8s-operators" "tide" "queries"

💡 Result:

In the context of the openstack-k8s-operators project and the OpenShift release engineering infrastructure, Tide is a Prow component responsible for managing automated PR merges [1][2]. Tide uses a configuration that defines which pull requests are eligible to be automatically merged based on specific criteria, such as passing CI status, required labels, and review approvals [1][3]. There is no single public query explicitly titled "openstack-k8s-operators tide queries." Instead, Tide configuration is managed globally within the openshift/release repository [1][2]. Individual repositories, such as those under the openstack-k8s-operators organization, are subject to these centralized rules, which are defined in Prow configuration files (often located under core-services/prow/02_config/) [1][4][5][6]. Key points regarding how these queries and configurations are managed: 1. Centralized Management: Tide configurations for various repositories, including those for the OpenStack operators, are defined within the openshift/release repository [1][2]. Changes to these configurations, such as removing or updating merge rules for a specific repository, are performed via pull requests to the openshift/release repo [1]. 2. Functionality: Tide queries effectively function by selecting sets of PRs that meet specific criteria (e.g., matching certain labels) and verifying their status against required presubmit jobs [1][3]. These jobs are defined in the ci-operator configuration for each operator [7][6]. 3. Repository Interaction: The openstack-k8s-operators repositories (e.g., nova-operator, cinder-operator) maintain their own CI definitions and OWNERS files, which are frequently synchronized with the central release engineering configuration [4][5][6]. If you are looking to troubleshoot why a PR is not merging via Tide, you should check the Prow configuration files in the openshift/release repository for the specific repository path or verify the status of the required CI jobs for that repository [1][7].

Citations:


🏁 Script executed:

#!/bin/bash
set -e

printf '%s\n' '--- commit metadata ---'
git show --no-patch --format=fuller 745c993cef
git show --no-patch --format=fuller eec99f1f31

printf '%s\n' '--- changed paths in PR `#82798` ---'
git diff --name-status 745c993cef^ 745c993cef
printf 'changed path count: '
git diff --name-only 745c993cef^ 745c993cef | wc -l

printf '%s\n' '--- changed paths in the revert ---'
git diff --name-status eec99f1f31^ eec99f1f31
printf 'reverted path count: '
git diff --name-only eec99f1f31^ eec99f1f31 | wc -l

printf '%s\n' '--- exact Tide configuration change for affected files ---'
git diff --find-renames --unified=4 745c993cef^ 745c993cef -- \
  'core-services/prow/02_config/openstack-k8s-operators/**/_prowconfig.yaml' \
  | sed -n '1,500p'

printf '%s\n' '--- current and pre-PR organization-level configuration ---'
for ref in 745c993cef^ 745c993cef eec99f1f31; do
  printf '\n### %s\n' "$ref"
  git ls-tree -r --name-only "$ref" core-services/prow/02_config/openstack-k8s-operators \
    | while read -r f; do
        git show "$ref:$f" 2>/dev/null | grep -q '^tide:' && {
          echo "--- $f"
          git show "$ref:$f"
        }
      done
done

Repository: openshift/release

Length of output: 50373


🏁 Script executed:

#!/bin/bash
set -e

printf '%s\n' '--- configuration fragment merge rules ---'
cat -n core-services/prow/02_config/README.md | sed -n '1,120p'

printf '%s\n' '--- Tide query configuration documentation references ---'
rg -n -i -C 4 'merge.*query|query.*merge|tide|github search|repos:' \
  core-services/prow/02_config/README.md core-services/prow/02_config/_config.yaml \
  core-services/prow/02_config 2>/dev/null \
  | rg -i 'merge|tide|query|github|openstack-k8s-operators' \
  | head -n 300

Repository: openshift/release

Length of output: 34008


🏁 Script executed:

#!/bin/bash
set -e

python3 - <<'PY'
from pathlib import Path
import re

root = Path("core-services/prow/02_config/openstack-k8s-operators")
pattern = re.compile(
    r"^tide:\n"
    r"  queries:\n"
    r"  - labels:\n"
    r"(?:    - .*\n)+"
    r"    missingLabels:\n"
    r"(?:    - .*\n)+"
    r"    repos:\n"
    r"    - ([^\n]+)\n",
    re.MULTILINE,
)

matches = []
for path in sorted(root.glob("*/_prowconfig.yaml")):
    text = path.read_text()
    match = pattern.search(text)
    if match:
        matches.append((path, match.group(1), match.group(0)))

print("matching per-repository Tide blocks:", len(matches))
print("unique repositories:", len({repo for _, repo, _ in matches}))
print("unique query bodies:", len({block for _, _, block in matches}))
print("generated repo qualifier length:",
      sum(len(f'repo:{repo} ') for _, repo, _ in matches))

for path, repo, _ in matches:
    print(f"{repo}\t{path}")
PY

printf '%s\n' '--- organization-level replacement from PR `#82798` ---'
git show 745c993cef:core-services/prow/02_config/openstack-k8s-operators/_prowconfig.yaml

printf '%s\n' '--- current restored organization-level path ---'
git ls-tree -r --name-only HEAD core-services/prow/02_config/openstack-k8s-operators \
  | grep '/_prowconfig.yaml$' \
  | grep -E '/openstack-k8s-operators/_prowconfig.yaml$|/tcib/_prowconfig.yaml$' || true

Repository: openshift/release

Length of output: 4848


Do not restore the per-repository Tide queries.

These files restore 35 identical per-repository queries. Prow combines them into one GitHub search with 35 repo: qualifiers. PR #82798 records that this exceeds GitHub’s resource limit and causes Tide sync to fail. Restore the organization-level query with orgs: [openstack-k8s-operators] and preserve the required organization-level plugin configuration.

📍 Affects 7 files
  • core-services/prow/02_config/openstack-k8s-operators/glance-operator/_prowconfig.yaml#L1-L14 (this comment)
  • core-services/prow/02_config/openstack-k8s-operators/heat-operator/_prowconfig.yaml#L1-L14
  • core-services/prow/02_config/openstack-k8s-operators/horizon-operator/_prowconfig.yaml#L1-L14
  • core-services/prow/02_config/openstack-k8s-operators/infra-operator/_prowconfig.yaml#L1-L14
  • core-services/prow/02_config/openstack-k8s-operators/install_yamls/_prowconfig.yaml#L1-L14
  • core-services/prow/02_config/openstack-k8s-operators/ironic-operator/_prowconfig.yaml#L1-L14
  • core-services/prow/02_config/openstack-k8s-operators/keystone-operator/_prowconfig.yaml#L1-L14
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@core-services/prow/02_config/openstack-k8s-operators/glance-operator/_prowconfig.yaml`
around lines 1 - 14, Replace the per-repository tide.queries entries in all
listed _prowconfig.yaml files with the organization-level query using orgs:
[openstack-k8s-operators], preserving the required organization-level plugin
configuration and avoiding individual repos qualifiers in each query.

Source: Path instructions

Comment on lines +45 to +47
lgtm:
- repos:
- openstack-k8s-operators/lightspeed-mcps

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

rg -n -C 2 'review_acts_as_lgtm|openstack-k8s-operators/lightspeed-(mcps|operator|rag-content)' \
  core-services/prow/02_config/openstack-k8s-operators

Repository: openshift/release

Length of output: 29212


🏁 Script executed:

#!/bin/bash
set -euo pipefail

for f in \
  core-services/prow/02_config/openstack-k8s-operators/lightspeed-mcps/_pluginconfig.yaml \
  core-services/prow/02_config/openstack-k8s-operators/lightspeed-operator/_pluginconfig.yaml \
  core-services/prow/02_config/openstack-k8s-operators/lightspeed-rag-content/_pluginconfig.yaml \
  core-services/prow/02_config/openstack-k8s-operators/ironic-operator/_pluginconfig.yaml \
  core-services/prow/02_config/openstack-k8s-operators/keystone-operator/_pluginconfig.yaml
do
  echo "===== $f ====="
  cat -n "$f" | sed -n '1,55p'
done

echo "===== all review_acts_as_lgtm entries in Prow configuration ====="
rg -n -B 3 -A 2 '^  review_acts_as_lgtm:' core-services/prow

Repository: openshift/release

Length of output: 50374


🏁 Script executed:

#!/bin/bash
set -euo pipefail

files=(
  core-services/prow/02_config/openstack-k8s-operators/lightspeed-mcps/_pluginconfig.yaml
  core-services/prow/02_config/openstack-k8s-operators/lightspeed-operator/_pluginconfig.yaml
  core-services/prow/02_config/openstack-k8s-operators/lightspeed-rag-content/_pluginconfig.yaml
  core-services/prow/02_config/openstack-k8s-operators/ironic-operator/_pluginconfig.yaml
  core-services/prow/02_config/openstack-k8s-operators/keystone-operator/_pluginconfig.yaml
)

for f in "${files[@]}"; do
  echo "===== $f ====="
  awk '
    /^lgtm:/ { in_lgtm=1; print NR ":" $0; next }
    in_lgtm && /^  [^ -][^:]*:/ { in_lgtm=0 }
    in_lgtm && (/- repos:/ || /review_acts_as_lgtm:/ || /- openstack-k8s-operators\/lightspeed/ || /- openstack-k8s-operators\/ironic/ || /- openstack-k8s-operators\/keystone/) {
      print NR ":" $0
    }
  ' "$f"
done

echo "===== Prow references to review_acts_as_lgtm ====="
rg -l 'review_acts_as_lgtm' --glob '*.go' --glob '*.md' --glob '*.yaml' --glob '*.yml' . \
  | head -n 80

Repository: openshift/release

Length of output: 7827


🏁 Script executed:

#!/bin/bash
set -euo pipefail

files=(
  core-services/prow/02_config/openstack-k8s-operators/lightspeed-mcps/_pluginconfig.yaml
  core-services/prow/02_config/openstack-k8s-operators/lightspeed-operator/_pluginconfig.yaml
  core-services/prow/02_config/openstack-k8s-operators/lightspeed-rag-content/_pluginconfig.yaml
  core-services/prow/02_config/openstack-k8s-operators/ironic-operator/_pluginconfig.yaml
  core-services/prow/02_config/openstack-k8s-operators/keystone-operator/_pluginconfig.yaml
)

for f in "${files[@]}"; do
  echo "===== $f ====="
  sed -n '30,45p' "$f"
done

echo "===== exact lightspeed configuration occurrences ====="
rg -n -B 8 -A 3 'review_acts_as_lgtm|^lgtm:' \
  core-services/prow/02_config/openstack-k8s-operators/lightspeed-mcps/_pluginconfig.yaml \
  core-services/prow/02_config/openstack-k8s-operators/lightspeed-operator/_pluginconfig.yaml \
  core-services/prow/02_config/openstack-k8s-operators/lightspeed-rag-content/_pluginconfig.yaml \
  core-services/prow/02_config/openstack-k8s-operators/ironic-operator/_pluginconfig.yaml \
  core-services/prow/02_config/openstack-k8s-operators/keystone-operator/_pluginconfig.yaml

Repository: openshift/release

Length of output: 10253


Restore automatic LGTM handling.

Add review_acts_as_lgtm: true under lgtm in all three files:

  • lightspeed-mcps/_pluginconfig.yaml
  • lightspeed-operator/_pluginconfig.yaml
  • lightspeed-rag-content/_pluginconfig.yaml

Without this setting, approving reviews do not satisfy the lgtm label requirement.

📍 Affects 3 files
  • core-services/prow/02_config/openstack-k8s-operators/lightspeed-mcps/_pluginconfig.yaml#L45-L47 (this comment)
  • core-services/prow/02_config/openstack-k8s-operators/lightspeed-operator/_pluginconfig.yaml#L45-L47
  • core-services/prow/02_config/openstack-k8s-operators/lightspeed-rag-content/_pluginconfig.yaml#L45-L47
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@core-services/prow/02_config/openstack-k8s-operators/lightspeed-mcps/_pluginconfig.yaml`
around lines 45 - 47, Add review_acts_as_lgtm: true under the lgtm configuration
in
core-services/prow/02_config/openstack-k8s-operators/lightspeed-mcps/_pluginconfig.yaml
lines 45-47, lightspeed-operator/_pluginconfig.yaml lines 45-47, and
lightspeed-rag-content/_pluginconfig.yaml lines 45-47, preserving the existing
repository entries.

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 3, 2026
@openshift-ci

openshift-ci Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deepsm007, Prucek

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 6a3d71f into openshift:main Aug 3, 2026
12 checks passed
@openshift-ci

openshift-ci Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

@Prucek: 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-barbican-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/barbican-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-ci-framework-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/ci-framework/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-cinder-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/cinder-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-data-plane-adoption-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/data-plane-adoption/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-designate-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/designate-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-edpm-ansible-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/edpm-ansible/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-edpm-image-builder-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/edpm-image-builder/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-glance-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/glance-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-heat-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/heat-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-horizon-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/horizon-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-infra-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/infra-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-install_yamls-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/install_yamls/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-ironic-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/ironic-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-keystone-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/keystone-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-lightspeed-mcps-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/lightspeed-mcps/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-lightspeed-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/lightspeed-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-lightspeed-rag-content-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/lightspeed-rag-content/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-manila-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/manila-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-mariadb-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/mariadb-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-neutron-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/neutron-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-nova-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/nova-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-octavia-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/octavia-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-openstack-baremetal-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/openstack-baremetal-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-openstack-k8s-operators-ci-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/openstack-k8s-operators-ci/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-openstack-must-gather-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/openstack-must-gather/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-openstack-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/openstack-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-osp-director-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/osp-director-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-ovn-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/ovn-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-repo-setup-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/repo-setup/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-sg-core-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/sg-core/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-swift-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/swift-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-_prowconfig.yaml using file ``
    • key core-services-prow-02_config-openstack-k8s-operators-tcib-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/tcib/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-telemetry-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/telemetry-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-test-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/test-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-watcher-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/watcher-operator/_prowconfig.yaml
  • config configmap in namespace ci at cluster core-ci using the following files:
    • key core-services-prow-02_config-openstack-k8s-operators-barbican-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/barbican-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-ci-framework-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/ci-framework/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-cinder-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/cinder-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-data-plane-adoption-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/data-plane-adoption/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-designate-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/designate-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-edpm-ansible-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/edpm-ansible/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-edpm-image-builder-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/edpm-image-builder/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-glance-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/glance-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-heat-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/heat-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-horizon-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/horizon-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-infra-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/infra-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-install_yamls-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/install_yamls/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-ironic-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/ironic-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-keystone-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/keystone-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-lightspeed-mcps-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/lightspeed-mcps/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-lightspeed-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/lightspeed-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-lightspeed-rag-content-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/lightspeed-rag-content/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-manila-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/manila-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-mariadb-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/mariadb-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-neutron-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/neutron-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-nova-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/nova-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-octavia-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/octavia-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-openstack-baremetal-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/openstack-baremetal-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-openstack-k8s-operators-ci-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/openstack-k8s-operators-ci/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-openstack-must-gather-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/openstack-must-gather/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-openstack-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/openstack-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-osp-director-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/osp-director-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-ovn-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/ovn-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-repo-setup-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/repo-setup/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-sg-core-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/sg-core/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-swift-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/swift-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-_prowconfig.yaml using file ``
    • key core-services-prow-02_config-openstack-k8s-operators-tcib-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/tcib/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-telemetry-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/telemetry-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-test-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/test-operator/_prowconfig.yaml
    • key core-services-prow-02_config-openstack-k8s-operators-watcher-operator-_prowconfig.yaml using file core-services/prow/02_config/openstack-k8s-operators/watcher-operator/_prowconfig.yaml
Details

In response to this:

Reverts #82798

Summary by CodeRabbit

This PR reverts the organization-level Tide query for openstack-k8s-operators.

It restores repository-specific Prow configuration for the affected component repositories. These configurations define repository-specific Tide requirements, including approved and lgtm labels and blocking labels.

It also restores repository-level plugins such as approve, assign, hold, lgtm, lifecycle, verify-owners, wip, and needs-rebase.

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. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants