chore: ignore flake8 rules now handled by ruff

[rnetser]

What this PR does / why we need it:

Ruff v0.15.x handles several rules with better context awareness than flake8 (dataclass fields, method overrides, formatter-managed line length). When ruff removes inline # noqa comments it considers unnecessary, flake8 still enforces those rules, causing CI conflicts.

This PR ignores those rules in .flake8 to prevent conflicts between the two linters:

• N815: camelCase in class scope — ruff understands dataclass fields matching API schemas
• N802: function name should be lowercase — ruff understands method overrides (e.g. formatTime)
• E501: line too long — ruff formatter manages line length
• F821: undefined name — used in global_config files with dynamic exec() loading
• E201: whitespace after ( — ruff formatter manages whitespace
• W503: line break before binary operator — PEP 8 reversed this; ruff uses W504 (after)
• N818: exception name should end with Error — ruff allows existing names like MissingTemplateVariables

Also adds with_suffix and writelines to fcn_exclude_functions to prevent FCN001 false positives on standard library calls.

Part 1 of a 6-PR series to clean up lint configuration and apply safe fixes:

1. This PR — .flake8 ignore rules
2. pyproject.toml ruff ignore rules for preview rules
3. Remove stale # noqa comments (depends on PRs 1+2)
4. Remove obsolete utf-8 coding headers
5. Apply safe ruff fixes repo-wide (SIM118, SIM201, PLC0206, etc.)
6. Bump pre-commit hooks (ruff v0.15.12, mypy v1.20.2)

Assisted-by: Claude noreply@anthropic.com

Which issue(s) this PR fixes:

Replaces #4701 with a smaller, incremental approach.

Special notes for reviewer:

No code changes — config only. All pre-commit hooks pass on all files.

jira-ticket:

Summary by CodeRabbit

• Chores
  • Updated linting configuration: removed hard line-length enforcement in favor of centralized formatting, suppressed a targeted set of stylistic and specific error checks, and added inline notes clarifying that certain rules (including line-length and whitespace checks) are managed by the code formatter.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 45175428-c72b-41e4-ae10-701696642288

📥 Commits

Reviewing files that changed from the base of the PR and between 81c5264 and 3528b84.

📒 Files selected for processing (1)

• .flake8

---

📝 Walkthrough

Walkthrough

The .flake8 configuration was changed: the max-line-length = 120 entry was removed and an ignore list was added to suppress specific Flake8 codes (N815, N802, E501, F821, E201, W503, N818) with inline comments noting overlap/management by ruff.

Changes

Flake8 ignore list update

Layer / File(s)	Summary
Configuration Update .flake8	Removed max-line-length = 120 and added ignore = N815, N802, E501, F821, E201, W503, N818 with comments explaining which checks are handled by ruff or intentionally suppressed (line-length, whitespace, certain naming/exception rules, and F821 for dynamic globals).
Inline rationale/comments .flake8	Added explanatory comments mapping ignored codes to ruff responsibilities and to specific intentional suppressions (e.g., dynamic global loading causing F821).

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: ignoring flake8 rules now handled by ruff, which is the core purpose of the PR.
Description check	✅ Passed	The description is comprehensive and covers all required template sections with specific details about rules ignored, rationale for each, context within a multi-PR series, and acknowledgment of dependencies.
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.

_{✏️ 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

_{Review rate limit: 0/1 reviews remaining, refill in 60 minutes.}

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

[openshift-virtualization-qe-bot-3]

Report bugs in Issues

Welcome! 🎉

This pull request will be automatically processed with the following features:

🔄 Automatic Actions

• Reviewer Assignment: Reviewers are automatically assigned based on the OWNERS file in the repository root
• Size Labeling: PR size labels (XS, S, M, L, XL, XXL) are automatically applied based on changes
• Issue Creation: A tracking issue is created for this PR and will be closed when the PR is merged or closed
• Branch Labeling: Branch-specific labels are applied to track the target branch
• Auto-verification: Auto-verified users have their PRs automatically marked as verified
• Labels: Enabled categories: branch, can-be-merged, cherry-pick, has-conflicts, hold, needs-rebase, size, verified, wip

📋 Available Commands

PR Status Management

• /wip - Mark PR as work in progress (adds WIP: prefix to title)
• /wip cancel - Remove work in progress status
• /hold - Block PR merging (approvers only)
• /hold cancel - Unblock PR merging
• /verified - Mark PR as verified
• /verified cancel - Remove verification status
• /reprocess - Trigger complete PR workflow reprocessing (useful if webhook failed or configuration changed)
• /regenerate-welcome - Regenerate this welcome message

Review & Approval

• /lgtm - Approve changes (looks good to me)
• /approve - Approve PR (approvers only)
• /assign-reviewers - Assign reviewers based on OWNERS file
• /assign-reviewer @username - Assign specific reviewer
• /check-can-merge - Check if PR meets merge requirements

Testing & Validation

• /retest tox - Run Python test suite with tox
• /retest build-container - Rebuild and test container image
• /retest verify-bugs-are-open - verify-bugs-are-open
• /retest all - Run all available tests

Container Operations

• /build-and-push-container - Build and push container image (tagged with PR number)
  • Supports additional build arguments: /build-and-push-container --build-arg KEY=value

Cherry-pick Operations

• /cherry-pick <branch> - Schedule cherry-pick to target branch when PR is merged
  • Multiple branches: /cherry-pick branch1 branch2 branch3

Label Management

• /<label-name> - Add a label to the PR
• /<label-name> cancel - Remove a label from the PR

✅ Merge Requirements

This PR will be automatically approved when the following conditions are met:

1. Approval: /approve from at least one approver
2. LGTM Count: Minimum 2 /lgtm from reviewers
3. Status Checks: All required status checks must pass
4. No Blockers: No wip, hold, has-conflicts labels and PR must be mergeable (no conflicts)
5. Verified: PR must be marked as verified

📊 Review Process

Approvers and Reviewers

Approvers:

• dshchedr
• myakove
• rnetser
• vsibirsk

Reviewers:

• RoniKishner
• dshchedr
• rnetser
• vsibirsk

Available Labels

• hold
• verified
• wip
• lgtm
• approve

AI Features

• Cherry-Pick Conflict Resolution: Enabled (claude/claude-opus-4-6[1m])

💡 Tips

• WIP Status: Use /wip when your PR is not ready for review
• Verification: The verified label is removed on new commits unless the push is detected as a clean rebase
• Cherry-picking: Cherry-pick labels are processed when the PR is merged
• Container Builds: Container images are automatically tagged with the PR number
• Permission Levels: Some commands require approver permissions
• Auto-verified Users: Certain users have automatic verification and merge privileges

For more information, please refer to the project documentation or contact the maintainers.

[rnetser]

/verified
/approve

[openshift-virtualization-qe-bot-3]

@coderabbitai

Test execution plan request details

CRITICAL: You MUST post an inline review comment on the first changed line of the first file.
The inline comment should contain the Test Execution Plan with the smoke tests recommendation.
Do NOT submit a formal review - just post the inline comment directly.

As an expert software testing engineer, analyze all modified files in this PR and create a targeted test execution plan.
You will post an inline review comment with the test execution plan on the first changed file.
If you fail to run or post a comment, retry.

Analysis Requirements:

1. Examine code changes in each modified file
2. Identify affected code paths, functions, and classes
3. Analyze pytest-specific elements: fixtures (scope, dependencies), parametrization, markers, conftest changes
4. Trace test dependencies through imports, shared utilities, and fixture inheritance
5. Detect new tests introduced in the PR
6. Smoke Test Impact Analysis: Determine if any changes could affect smoke tests by checking:
   • Changes to files/functions used by tests marked with @pytest.mark.smoke
   • Changes to fixtures or utilities imported by smoke tests
   • Changes to conftest.py files that may affect smoke test execution
   • Changes to core infrastructure code (utilities/, libs/) that smoke tests depend on

Your deliverable:
Your change request comment will be based on the following requirements:

Test Execution Plan

• Run smoke tests: True / False (Based on your smoke test impact analysis - True if any changes may affect smoke tests)
• path/to/test_file.py - When the entire test file needs verification
• path/to/test_file.py::TestClass::test_method - When specific test(s) needed
• path/to/test_file.py::test_function - When specific test(s) needed
• -m marker - When specific marker(s) can be used to cover multiple cases.

Guidelines:

• Include only tests directly affected by the changes
• Use a full file path only if ALL tests in that file require verification
• Use file path + test name if only specific tests are needed
• If a test marker can cover multiple files/tests, provide the marker
• Balance coverage vs over-testing - Keep descriptions minimal

Hardware-Related Checks (SR-IOV, GPU, DPDK):

When PR modifies fixtures for hardware-specific resources:

• Collection Safety: Fixtures MUST have existence checks (return None when hardware unavailable)
• Test Plan: MUST verify both WITH and WITHOUT hardware:
  • Run affected tests on cluster WITH hardware
  • Verify collection succeeds on cluster WITHOUT hardware

CRITICAL WORKFLOW COMPLETION RULES:

When responding to this test execution plan request, you MUST follow these rules EXACTLY:

1. YOUR ONLY DELIVERABLE: Post an inline review comment containing the test execution plan on the first changed line
2. THEN STOP IMMEDIATELY - Do NOT generate any additional response
3. FALLBACK ONLY: If submitting the review fails after retrying, post as a regular PR comment
4. SILENCE = SUCCESS: After successfully submitting the review, your task is complete. No confirmation needed.

ABSOLUTE PROHIBITIONS (violating these creates empty/meaningless reviews):

• ❌ Do NOT post acknowledgment messages like "Test execution plan posted", "Review posted successfully", "I've successfully posted"
• ❌ Do NOT mention review IDs, URLs, or confirmation of posting in the PR thread
• ❌ Do NOT add any follow-up comments after submitting the review
• ❌ Do NOT reply to confirm task completion
• ❌ Do NOT explain what you did - just do it and stop

Remember: The pull request review is visible to users. Additional comments are redundant noise.

CRITICAL: Before setting "Run smoke tests: True", you MUST use shell scripts to:
- Trace the actual fixture dependency chain from smoke tests to changed fixtures
- Verify that smoke tests actually import/use changed utilities or functions
- Confirm the dependency path exists; do NOT assume based on scope or semantics
- Be conservative: Session-scoped fixtures or infrastructure-sounding names do NOT
automatically mean smoke test impact. Only flag smoke test impact when you can
demonstrate a concrete dependency path.
WRONG: "This session-scoped storage fixture might affect smoke tests"
RIGHT: "Smoke test X uses fixture Y, which depends on the changed fixture Z"

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.flake8:
- Around line 5-14: The comment in .flake8 incorrectly claims N815, N802, and
N818 are "now handled by ruff" but ruff won't run pep8-naming rules unless you
enable them; fix by either 1) rewriting the comment in .flake8 to explicitly
state these N rules are intentionally suppressed (give concise rationale for
N815, N802, N818) or 2) enable pep8-naming in ruff by adding a [tool.ruff.lint]
section to pyproject.toml with extend-select = ["N"] and then update the .flake8
ignore list and comments to reflect that naming rules are delegated to ruff
(ensure N815, N802, N818 handling is clear).

🪄 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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5827cb49-85c6-46a1-ba27-189f1dd81c31

📥 Commits

Reviewing files that changed from the base of the PR and between 4743306 and 81c5264.

📒 Files selected for processing (1)

• .flake8

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Get the list of changed files in PR `#4703`
gh pr view 4703 --repo RedHatQE/openshift-virtualization-tests --json files --jq '.files[].path'

Length of output: 8

---

🏁 Script executed:

#!/bin/bash
# Get the diff for .flake8 to find the first changed line
gh pr diff 4703 --repo RedHatQE/openshift-virtualization-tests -- .flake8

Length of output: 37

---

🏁 Script executed:

#!/bin/bash
# Get the diff for the PR
gh pr diff 4703 --repo RedHatQE/openshift-virtualization-tests

Length of output: 755

---

🏁 Script executed:

#!/bin/bash
# Get the PR head commit SHA
gh pr view 4703 --repo RedHatQE/openshift-virtualization-tests --json headRefOid --jq '.headRefOid'

Length of output: 41

---

🏁 Script executed:

#!/bin/bash
# Post inline review comment on the first changed line of .flake8
gh api \
  --method POST \
  repos/RedHatQE/openshift-virtualization-tests/pulls/4703/reviews \
  --field commit_id="81c52641940e1ad6f2a81bf6d4a9560d0fa53e41" \
  --field event="COMMENT" \
  --field "comments[][path]=.flake8" \
  --field "comments[][position]=4" \
  --field "comments[][body]=**Test Execution Plan**

- **Run smoke tests: False**

This PR modifies only the \`.flake8\` linting configuration file — no Python source code, test files, fixtures, utilities, or conftest files are changed. There are no affected code paths, pytest fixtures, or test dependencies. No tests need to be executed to validate this change."

Length of output: 1735

---

[openshift-virtualization-qe-bot-3]

@coderabbitai

Test execution plan request details

CRITICAL: You MUST post an inline review comment on the first changed line of the first file.
The inline comment should contain the Test Execution Plan with the smoke tests recommendation.
Do NOT submit a formal review - just post the inline comment directly.

As an expert software testing engineer, analyze all modified files in this PR and create a targeted test execution plan.
You will post an inline review comment with the test execution plan on the first changed file.
If you fail to run or post a comment, retry.

Analysis Requirements:

1. Examine code changes in each modified file
2. Identify affected code paths, functions, and classes
3. Analyze pytest-specific elements: fixtures (scope, dependencies), parametrization, markers, conftest changes
4. Trace test dependencies through imports, shared utilities, and fixture inheritance
5. Detect new tests introduced in the PR
6. Smoke Test Impact Analysis: Determine if any changes could affect smoke tests by checking:
   • Changes to files/functions used by tests marked with @pytest.mark.smoke
   • Changes to fixtures or utilities imported by smoke tests
   • Changes to conftest.py files that may affect smoke test execution
   • Changes to core infrastructure code (utilities/, libs/) that smoke tests depend on

Your deliverable:
Your change request comment will be based on the following requirements:

Test Execution Plan

• Run smoke tests: True / False (Based on your smoke test impact analysis - True if any changes may affect smoke tests)
• path/to/test_file.py - When the entire test file needs verification
• path/to/test_file.py::TestClass::test_method - When specific test(s) needed
• path/to/test_file.py::test_function - When specific test(s) needed
• -m marker - When specific marker(s) can be used to cover multiple cases.

Guidelines:

• Include only tests directly affected by the changes
• Use a full file path only if ALL tests in that file require verification
• Use file path + test name if only specific tests are needed
• If a test marker can cover multiple files/tests, provide the marker
• Balance coverage vs over-testing - Keep descriptions minimal

Hardware-Related Checks (SR-IOV, GPU, DPDK):

When PR modifies fixtures for hardware-specific resources:

• Collection Safety: Fixtures MUST have existence checks (return None when hardware unavailable)
• Test Plan: MUST verify both WITH and WITHOUT hardware:
  • Run affected tests on cluster WITH hardware
  • Verify collection succeeds on cluster WITHOUT hardware

CRITICAL WORKFLOW COMPLETION RULES:

When responding to this test execution plan request, you MUST follow these rules EXACTLY:

1. YOUR ONLY DELIVERABLE: Post an inline review comment containing the test execution plan on the first changed line
2. THEN STOP IMMEDIATELY - Do NOT generate any additional response
3. FALLBACK ONLY: If submitting the review fails after retrying, post as a regular PR comment
4. SILENCE = SUCCESS: After successfully submitting the review, your task is complete. No confirmation needed.

ABSOLUTE PROHIBITIONS (violating these creates empty/meaningless reviews):

• ❌ Do NOT post acknowledgment messages like "Test execution plan posted", "Review posted successfully", "I've successfully posted"
• ❌ Do NOT mention review IDs, URLs, or confirmation of posting in the PR thread
• ❌ Do NOT add any follow-up comments after submitting the review
• ❌ Do NOT reply to confirm task completion
• ❌ Do NOT explain what you did - just do it and stop

Remember: The pull request review is visible to users. Additional comments are redundant noise.

CRITICAL: Before setting "Run smoke tests: True", you MUST use shell scripts to:
- Trace the actual fixture dependency chain from smoke tests to changed fixtures
- Verify that smoke tests actually import/use changed utilities or functions
- Confirm the dependency path exists; do NOT assume based on scope or semantics
- Be conservative: Session-scoped fixtures or infrastructure-sounding names do NOT
automatically mean smoke test impact. Only flag smoke test impact when you can
demonstrate a concrete dependency path.
WRONG: "This session-scoped storage fixture might affect smoke tests"
RIGHT: "Smoke test X uses fixture Y, which depends on the changed fixture Z"

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Post inline review comment on the first changed line of .flake8
gh api \
  --method POST \
  repos/RedHatQE/openshift-virtualization-tests/pulls/4703/reviews \
  --field commit_id="81c52641940e1ad6f2a81bf6d4a9560d0fa53e41" \
  --field event="COMMENT" \
  --field "comments[][path]=.flake8" \
  --field "comments[][position]=4" \
  --field "comments[][body]=**Test Execution Plan**

- **Run smoke tests: False**

This PR modifies only the \`.flake8\` linting configuration — no Python source code, test files, fixtures, utilities, or conftest files are changed. There are no affected code paths, pytest fixtures, or test dependencies. No tests need to be executed to validate this change."

Length of output: 1735

---

[rnetser]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[openshift-virtualization-qe-bot-5]

New container for quay.io/openshift-cnv/openshift-virtualization-tests:latest published