NO-JIRA: feat: add MCP Gateway and smoke test steps to openshift-mcp-server e2e#78314
NO-JIRA: feat: add MCP Gateway and smoke test steps to openshift-mcp-server e2e#78314matzew wants to merge 1 commit intoopenshift:mainfrom
Conversation
Add install-gateway, register-mcp-server, and smoke-test steps to the e2e-aws test for openshift-mcp-server release-0.3. The full step flow is now: install-operator, install-gateway, deploy-mcp-server, register-mcp-server, wait-ready, smoke-test. Signed-off-by: Matthias Wessendorf <mwessend@redhat.com>
|
@matzew: This pull request explicitly references no jira issue. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: matzew The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
WalkthroughThe e2e-aws workflow in the CI configuration is simplified by consolidating three separate installation and deployment steps (install-operator, deploy-mcp-server, wait-ready) into a single e2e-test step that invokes a Makefile command. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 11 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (11 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
ci-operator/config/openshift/openshift-mcp-server/openshift-openshift-mcp-server-release-0.3.yaml (1)
34-46:⚠️ Potential issue | 🔴 Critical
Makefile-ocp.mkdoes not contain thee2e-testtarget referenced in this step — the command will fail.The CI step at lines 34-46 executes
make -f Makefile-ocp.mk e2e-test, but verification ofMakefile-ocp.mkon therelease-0.3branch ofopenshift/openshift-mcp-servershows noe2e-testtarget exists. The Makefile contains only abuild-ocptarget. This will cause a "No rule to make target 'e2e-test'" error when the step runs.Additionally, the PR description claims this PR adds three new steps (
install-gateway,register-mcp-server,smoke-test) to create a 6-step flow, but the YAML file defines only a single consolidatede2e-teststep. Either the PR description is stale, or the intended changes were not committed. Before this can merge:
- Create the
e2e-testtarget inMakefile-ocp.mk(or fix the target name if it's defined elsewhere)- Clarify the PR intent and update the description to match the actual file changes
- Ensure the Makefile properly consumes the
MCP_SERVER_IMAGEenvironment variable🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@ci-operator/config/openshift/openshift-mcp-server/openshift-openshift-mcp-server-release-0.3.yaml` around lines 34 - 46, The CI step invokes "make -f Makefile-ocp.mk e2e-test" but Makefile-ocp.mk on release-0.3 has no e2e-test target (only build-ocp), causing a "No rule" failure; add an e2e-test target to Makefile-ocp.mk (or change the YAML to call the correct existing target) that sequences the intended steps (install-gateway, register-mcp-server, smoke-test) and consumes the MCP_SERVER_IMAGE env var (use MCP_SERVER_IMAGE in the commands/recipes) so the CI command succeeds; also update the PR description to reflect whether you added the three explicit targets or consolidated them under e2e-test.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In
`@ci-operator/config/openshift/openshift-mcp-server/openshift-openshift-mcp-server-release-0.3.yaml`:
- Around line 34-46: The CI step invokes "make -f Makefile-ocp.mk e2e-test" but
Makefile-ocp.mk on release-0.3 has no e2e-test target (only build-ocp), causing
a "No rule" failure; add an e2e-test target to Makefile-ocp.mk (or change the
YAML to call the correct existing target) that sequences the intended steps
(install-gateway, register-mcp-server, smoke-test) and consumes the
MCP_SERVER_IMAGE env var (use MCP_SERVER_IMAGE in the commands/recipes) so the
CI command succeeds; also update the PR description to reflect whether you added
the three explicit targets or consolidated them under e2e-test.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 7ae45c00-3622-4572-9a02-f020e477e12a
📒 Files selected for processing (1)
ci-operator/config/openshift/openshift-mcp-server/openshift-openshift-mcp-server-release-0.3.yaml
|
[REHEARSALNOTIFIER]
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals. Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/retest |
|
/pj-rehearse |
|
@matzew: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-openshift-openshift-mcp-server-release-0.3-e2e-aws |
|
@matzew: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@matzew: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
Add install-gateway, register-mcp-server, and smoke-test steps to the e2e-aws test for openshift-mcp-server release-0.3. The full step flow is now: install-operator, install-gateway, deploy-mcp-server, register-mcp-server, wait-ready, smoke-test.
Summary by CodeRabbit