Skip to content

Rename x86_64 to amd64 for architecture consistency#3789

Merged
vsibirsk merged 2 commits intoRedHatQE:mainfrom
vsibirsk:vk-rename-x86-64
Feb 16, 2026
Merged

Rename x86_64 to amd64 for architecture consistency#3789
vsibirsk merged 2 commits intoRedHatQE:mainfrom
vsibirsk:vk-rename-x86-64

Conversation

@vsibirsk
Copy link
Copy Markdown
Collaborator

@vsibirsk vsibirsk commented Feb 9, 2026

Short description:

Align architecture naming with Kubernetes/KubeVirt conventions

Assisted by: Cursor

More details:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for reviewer:
jira-ticket:

Summary by CodeRabbit

  • Tests

    • Updated test configurations and markers to use "amd64" architecture designation instead of "x86_64".
    • Removed tests validating the deprecated "x86_64" architecture nomenclature.
  • Chores

    • Standardized architecture naming convention across the system to use "amd64" instead of "x86_64".
    • Simplified architecture validation to recognize AMD_64, ARM_64, and S390X architectures.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Feb 9, 2026

📝 Walkthrough

Walkthrough

This pull request systematically renames the x86_64 architecture constant to amd64/AMD_64 across configuration files, core utilities, and tests. The changes propagate from constant definitions through configuration markers, environment variables, and unit test expectations.

Changes

Cohort / File(s) Summary
Test Configuration & Markers
conftest.py, pytest.ini, scripts/tests_analyzer/pytest_marker_analyzer.py, tox.ini
Updates pytest markers and environment variables from x86_64 to amd64. Conftest.py imports AMD_64 constant instead of X86_64 and applies it to test markers.
Architecture Constants & Utilities
utilities/constants.py, utilities/architecture.py, utilities/cpu.py
Renames ArchImages.X86_64 to ArchImages.AMD64 in constants; removes X86_64 normalization logic from architecture.py; updates docstring example from x86_64 to amd64 in cpu.py.
Unit Tests & Fixtures
utilities/unittests/conftest.py, utilities/unittests/test_architecture.py, utilities/unittests/test_constants.py, utilities/unittests/test_cpu.py
Updates test fixtures to use amd64 environment variable; removes x86_64-specific test case in test_cpu.py; renames and updates assertions in test_architecture.py; updates constant validation in test_constants.py to expect AMD64.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~18 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Description check ❓ Inconclusive The description lacks critical details required by the template; only the short description is provided without explanations, issue references, or implementation notes. Add comprehensive details under 'More details', 'What this PR does / why we need it', and 'Which issue(s) this PR fixes' sections; provide JIRA ticket if available.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically summarizes the main change: renaming x86_64 to amd64 for architecture consistency across the codebase.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

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

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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

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

@openshift-virtualization-qe-bot-3
Copy link
Copy Markdown
Contributor

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, conflict labels
  5. Verified: PR must be marked as verified (if verification is enabled)

📊 Review Process

Approvers and Reviewers

Approvers:

  • dshchedr
  • myakove
  • rnetser
  • vsibirsk

Reviewers:

  • RoniKishner
  • dshchedr
  • geetikakay
  • rnetser
  • vsibirsk
Available Labels
  • hold
  • verified
  • wip
  • lgtm
  • approve

💡 Tips

  • WIP Status: Use /wip when your PR is not ready for review
  • Verification: The verified label is automatically removed on each new commit
  • 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.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Feb 9, 2026

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

 _______________________________________
< Nullus Bugus Maximus. No bug too big. >
 ---------------------------------------
  \
   \   (\__/)
       (•ㅅ•)
       /   づ

✏️ Tip: You can disable in-progress messages and the fortune message in your review settings.

Tip

CodeRabbit can generate a title for your PR based on the changes.

Add @coderabbitai placeholder anywhere in the title of your PR and CodeRabbit will replace it with a title based on the changes in the PR. You can change the placeholder by changing the reviews.auto_title_placeholder setting.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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

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

1 similar comment
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Feb 9, 2026

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

 _______________________________________
< Nullus Bugus Maximus. No bug too big. >
 ---------------------------------------
  \
   \   (\__/)
       (•ㅅ•)
       /   づ

✏️ Tip: You can disable in-progress messages and the fortune message in your review settings.

Tip

CodeRabbit can generate a title for your PR based on the changes.

Add @coderabbitai placeholder anywhere in the title of your PR and CodeRabbit will replace it with a title based on the changes in the PR. You can change the placeholder by changing the reviews.auto_title_placeholder setting.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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

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

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Feb 9, 2026

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

 _______________________________________
< Nullus Bugus Maximus. No bug too big. >
 ---------------------------------------
  \
   \   (\__/)
       (•ㅅ•)
       /   づ

✏️ Tip: You can disable in-progress messages and the fortune message in your review settings.

Tip

CodeRabbit can generate a title for your PR based on the changes.

Add @coderabbitai placeholder anywhere in the title of your PR and CodeRabbit will replace it with a title based on the changes in the PR. You can change the placeholder by changing the reviews.auto_title_placeholder setting.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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

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

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Feb 9, 2026

📝 Walkthrough

Walkthrough

This pull request systematically replaces the X86_64 architecture constant with AMD_64 across configuration files, utility modules, and test suites. Changes include updating pytest markers, environment variables, class names in the constants module, and adjusting test expectations accordingly.

Changes

Cohort / File(s) Summary
Configuration & Pytest Setup
conftest.py, pytest.ini, scripts/tests_analyzer/pytest_marker_analyzer.py, tox.ini
Updated architecture constant from X86_64 to AMD_64 in pytest marker collection, pytest configuration markers, and test environment variables (OPENSHIFT_VIRTUALIZATION_TEST_IMAGES_ARCH).
Utility Constants & Architecture
utilities/constants.py, utilities/architecture.py, utilities/cpu.py
Renamed ArchImages inner class from X86_64 to AMD64; removed X86_64 normalization logic and tightened allowed architectures to AMD_64, ARM_64, and S390X; updated docstring example from x86_64 to amd64.
Test Suite
utilities/unittests/conftest.py, utilities/unittests/test_architecture.py, utilities/unittests/test_constants.py, utilities/unittests/test_cpu.py
Updated test environment architecture labels and mocked node resources to amd64; renamed test cases and adjusted expectations to match AMD_64; removed x86_64-specific test validations.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description check ⚠️ Warning The description is largely incomplete, providing only a short description and assistant attribution while leaving critical sections (rationale, issues fixed, special notes, JIRA ticket) empty or unfilled. Complete the 'More details', 'What this PR does / why we need it', 'Which issue(s) this PR fixes', 'Special notes for reviewer', and 'jira-ticket' sections with substantive information explaining the change's purpose and impact.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: renaming x86_64 to amd64 for architecture consistency, which is exactly what the changeset accomplishes.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

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

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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

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

3 similar comments
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Feb 9, 2026

📝 Walkthrough

Walkthrough

This pull request systematically replaces the X86_64 architecture constant with AMD_64 across configuration files, utility modules, and test suites. Changes include updating pytest markers, environment variables, class names in the constants module, and adjusting test expectations accordingly.

Changes

Cohort / File(s) Summary
Configuration & Pytest Setup
conftest.py, pytest.ini, scripts/tests_analyzer/pytest_marker_analyzer.py, tox.ini
Updated architecture constant from X86_64 to AMD_64 in pytest marker collection, pytest configuration markers, and test environment variables (OPENSHIFT_VIRTUALIZATION_TEST_IMAGES_ARCH).
Utility Constants & Architecture
utilities/constants.py, utilities/architecture.py, utilities/cpu.py
Renamed ArchImages inner class from X86_64 to AMD64; removed X86_64 normalization logic and tightened allowed architectures to AMD_64, ARM_64, and S390X; updated docstring example from x86_64 to amd64.
Test Suite
utilities/unittests/conftest.py, utilities/unittests/test_architecture.py, utilities/unittests/test_constants.py, utilities/unittests/test_cpu.py
Updated test environment architecture labels and mocked node resources to amd64; renamed test cases and adjusted expectations to match AMD_64; removed x86_64-specific test validations.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description check ⚠️ Warning The description is largely incomplete, providing only a short description and assistant attribution while leaving critical sections (rationale, issues fixed, special notes, JIRA ticket) empty or unfilled. Complete the 'More details', 'What this PR does / why we need it', 'Which issue(s) this PR fixes', 'Special notes for reviewer', and 'jira-ticket' sections with substantive information explaining the change's purpose and impact.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: renaming x86_64 to amd64 for architecture consistency, which is exactly what the changeset accomplishes.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

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

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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

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

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Feb 9, 2026

📝 Walkthrough

Walkthrough

This pull request systematically replaces the X86_64 architecture constant with AMD_64 across configuration files, utility modules, and test suites. Changes include updating pytest markers, environment variables, class names in the constants module, and adjusting test expectations accordingly.

Changes

Cohort / File(s) Summary
Configuration & Pytest Setup
conftest.py, pytest.ini, scripts/tests_analyzer/pytest_marker_analyzer.py, tox.ini
Updated architecture constant from X86_64 to AMD_64 in pytest marker collection, pytest configuration markers, and test environment variables (OPENSHIFT_VIRTUALIZATION_TEST_IMAGES_ARCH).
Utility Constants & Architecture
utilities/constants.py, utilities/architecture.py, utilities/cpu.py
Renamed ArchImages inner class from X86_64 to AMD64; removed X86_64 normalization logic and tightened allowed architectures to AMD_64, ARM_64, and S390X; updated docstring example from x86_64 to amd64.
Test Suite
utilities/unittests/conftest.py, utilities/unittests/test_architecture.py, utilities/unittests/test_constants.py, utilities/unittests/test_cpu.py
Updated test environment architecture labels and mocked node resources to amd64; renamed test cases and adjusted expectations to match AMD_64; removed x86_64-specific test validations.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description check ⚠️ Warning The description is largely incomplete, providing only a short description and assistant attribution while leaving critical sections (rationale, issues fixed, special notes, JIRA ticket) empty or unfilled. Complete the 'More details', 'What this PR does / why we need it', 'Which issue(s) this PR fixes', 'Special notes for reviewer', and 'jira-ticket' sections with substantive information explaining the change's purpose and impact.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: renaming x86_64 to amd64 for architecture consistency, which is exactly what the changeset accomplishes.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

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

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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

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

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Feb 9, 2026

📝 Walkthrough

Walkthrough

This pull request systematically replaces the X86_64 architecture constant with AMD_64 across configuration files, utility modules, and test suites. Changes include updating pytest markers, environment variables, class names in the constants module, and adjusting test expectations accordingly.

Changes

Cohort / File(s) Summary
Configuration & Pytest Setup
conftest.py, pytest.ini, scripts/tests_analyzer/pytest_marker_analyzer.py, tox.ini
Updated architecture constant from X86_64 to AMD_64 in pytest marker collection, pytest configuration markers, and test environment variables (OPENSHIFT_VIRTUALIZATION_TEST_IMAGES_ARCH).
Utility Constants & Architecture
utilities/constants.py, utilities/architecture.py, utilities/cpu.py
Renamed ArchImages inner class from X86_64 to AMD64; removed X86_64 normalization logic and tightened allowed architectures to AMD_64, ARM_64, and S390X; updated docstring example from x86_64 to amd64.
Test Suite
utilities/unittests/conftest.py, utilities/unittests/test_architecture.py, utilities/unittests/test_constants.py, utilities/unittests/test_cpu.py
Updated test environment architecture labels and mocked node resources to amd64; renamed test cases and adjusted expectations to match AMD_64; removed x86_64-specific test validations.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description check ⚠️ Warning The description is largely incomplete, providing only a short description and assistant attribution while leaving critical sections (rationale, issues fixed, special notes, JIRA ticket) empty or unfilled. Complete the 'More details', 'What this PR does / why we need it', 'Which issue(s) this PR fixes', 'Special notes for reviewer', and 'jira-ticket' sections with substantive information explaining the change's purpose and impact.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: renaming x86_64 to amd64 for architecture consistency, which is exactly what the changeset accomplishes.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

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

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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

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

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (3)
tox.ini (1)

8-16: 🧹 Nitpick | 🔵 Trivial

Consider renaming the testenv to match the new terminology.

The environment is still named pytest-check-x86 (line 8) while the arch value is now amd64 (line 16). This mismatch could confuse contributors. Consider renaming to pytest-check-amd64 for consistency, and updating the envlist on line 2 accordingly.

utilities/architecture.py (1)

20-33: ⚠️ Potential issue | 🟡 Minor

Breaking change: x86_64 is no longer accepted as a valid architecture — fix the error message grammar.

The core behavioral change is confirmed: x86_64 has been removed from the allowed set; only amd64, arm64, and s390x are now accepted. Since get_cluster_architecture() reads from both the OPENSHIFT_VIRTUALIZATION_TEST_IMAGES_ARCH env var and kubernetes.io/arch node labels:

  • Node labels: Kubernetes already reports amd64 for x86-64 nodes, so no issue there.
  • Env var: Any CI pipeline, developer setup, or external caller still passing x86_64 will now get a ValueError.

However, fix the grammar error in the error message on line 33: change "architecture in not supported" to "architecture is not supported". The test on line 94 of test_architecture.py expects the current incorrect grammar, so update that test assertion as well.

Note: The X86_64 constant is still defined in utilities/constants.py and used in utilities/infra.py for converting platform.machine() results to Kubernetes arch constants, so this constant need not be removed.

utilities/unittests/test_architecture.py (1)

88-97: ⚠️ Potential issue | 🟠 Major

HIGH: Missing test for x86_64 as now-unsupported architecture.

The existing unsupported test only checks a generic "unsupported" string. Since this PR explicitly removes x86_64 from the valid architectures in get_cluster_architecture(), you should add a test confirming that "x86_64" is now rejected with a ValueError. This is a meaningful behavioral change — anyone who previously had OPENSHIFT_VIRTUALIZATION_TEST_IMAGES_ARCH=x86_64 in their environment will hit this error, and the test suite should document and verify that.

Suggested addition after line 97
    def test_get_cluster_architecture_x86_64_unsupported(self):
        """Test that x86_64 is no longer a supported architecture value"""
        with (
            patch.dict(os.environ, {"OPENSHIFT_VIRTUALIZATION_TEST_IMAGES_ARCH": "x86_64"}),
            pytest.raises(
                ValueError,
                match="x86_64 architecture in not supported",
            ),
        ):
            get_cluster_architecture()
🤖 Fix all issues with AI agents
In `@conftest.py`:
- Around line 593-594: Update the trailing comment that currently reads
"verified on x86_64 platforms" to match the marker being applied by
item.add_marker(marker=AMD_64); change it to "verified on amd64 platforms" (or
"verified on x86_64/amd64 platforms") so the comment and the AMD_64 marker stay
consistent and avoid confusion.

In `@pytest.ini`:
- Line 45: Update the pytest marker description that currently reads "amd64:
Tests that can run on x86_64-based cluster" to use the standardized term; change
the description to something like "amd64: Tests that can run on amd64-based
cluster" so the marker name and description consistently reference amd64 (locate
the marker entry in pytest.ini where the "amd64:" description is defined).

Comment thread conftest.py Outdated
Comment thread pytest.ini Outdated
rnetser
rnetser previously requested changes Feb 9, 2026
Comment thread docs/ARCHITECTURE_SUPPORT.md Outdated
Comment thread scripts/tests_analyzer/pytest_marker_analyzer.py
Comment thread conftest.py Outdated
Comment thread pytest.ini Outdated
Comment thread utilities/unittests/conftest.py
@rnetser
Copy link
Copy Markdown
Collaborator

rnetser commented Feb 11, 2026

/approve
/lgtm

@dshchedr
Copy link
Copy Markdown
Collaborator

/approve
/lgtm

@openshift-virtualization-qe-bot-3
Copy link
Copy Markdown
Contributor

/retest all

Auto-triggered: Files in this PR were modified by merged PR #3592.

Overlapping files

utilities/constants.py

@hmeir
Copy link
Copy Markdown
Contributor

hmeir commented Feb 16, 2026

/lgtm

@openshift-virtualization-qe-bot-5
Copy link
Copy Markdown

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants