[6.19.z] Fix parametrization order for MCP server test

[Satellite-QE]

Cherrypick of PR: #20883

Problem Statement

Incorrect parametrization order for MCP server test:

• running downstream parameter tests Stage
• running stage parameter tests Prod

Solution

Fix parametrization order

Related Issues

SAT-42137

Summary by Sourcery

Bug Fixes:

• Fix mismatched parametrization IDs so 'stage' and 'downstream' MCP server parameters are tested against the correct environments.

[Satellite-QE]

trigger: test-robottelo
pytest: -v tests/foreman/sys/test_mcp.py::test_positive_call_mcp_server

[Satellite-QE]

PRT Result

Build Number: 14489
Build Status: SUCCESS
PRT Comment: pytest -v tests/foreman/sys/test_mcp.py::test_positive_call_mcp_server --external-logging
Test Result : ================= 3 passed, 63 warnings in 1405.68s (0:23:25) ==================

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adjusts the parametrization IDs for the MCP server pytest to align each environment-specific test with the correct MCP target fixture ordering, ensuring 'stage' and 'downstream' tests run against the intended environments.

File-Level Changes

Change	Details	Files
Correct mapping between MCP target fixtures and their parametrization IDs in the MCP server test.	Updated the order of parametrization IDs to match the order of MCP target fixtures so that 'stage' and 'downstream' map to the correct environments Ensured that upstream, stage, and downstream MCP server tests now execute against their intended targets during parametrized test runs	tests/foreman/sys/test_mcp.py

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}