PERFSCALE-4192: Jira mcp integration #55

abraham2512 · 2025-11-10T20:38:03Z

This PR integrates jira mcp client and prompt updates to fetch relevant jira issues.

Sample output

Implications to understand (AI generated)
Affected Component: Containerized applications, potentially involving Gitea and SSH connections.
Probable Root Cause: The file /tmp/secret/gitea-ssh-uri.txt is missing, likely due to a failure during its creation, an oversight during build time, or a misconfiguration. This prevents the container test from executing correctly. The "wrapped process failed" errors suggest a systemic issue related to unmet dependencies.
Verification Steps:
Identify which pods or components expect the file /tmp/secret/gitea-ssh-uri.txt.
Trace when and how this file is normally created (e.g., init container, ConfigMap, Secret).
Inspect logs from affected pods, focusing on startup sequences and dependency loading. Use oc logs <pod-name>.
Check cluster-wide health using oc adm cluster-health.
Review recent changes to deployments, SCCs, or PodPolicies.
Suggested Resolution:
Immediate Fix: If the file is expected to be mounted as a Secret, verify the Secret's existence and correct mounting path using oc describe pod/<pod_name> | grep Secrets.
Longer-Term Fixes:
Adjust default mounts/policies to ensure the directory receives appropriate permissions at runtime via SCCs/PodPolicies.
Review build-time scripts that generate the file to ensure they execute before container startup.
Implement liveness probes to check for the existence of critical resources before the main application logic executes.
Related JIRA Issues:
OCPBUGS-57111 - Upgrade from 4.15 to 4.16 fails because of kubelet reporting "Failed to register CRI auth plugins" error
OCPBUGS-9184 - [e2e-crc] Unable to determine an OpenShift release version.
OCPBUGS-66249 - OCP 4.19.19: GPU workloads with readOnlyRootFilesystem=true fail to run, show NVIDIA hook errors

vishnuchalla

This implementation is introducing tight integration with custom JIRA MCP server which is not the intended purpose.

Please consider BugZooka to be a tool that provides “Bring your own MCP” flexibility with minimal code changes and update these changes.

README.md

bugzooka/integrations/jira_client.py

kustomize/base/configmap-prompts.yaml

abraham2512 · 2025-12-02T03:37:29Z

Hi @vishnuchalla thank you for the review and sorry it took a while to circle back to this!
I've made the requested changes and hosted the jira client separately in quay.
Please let me know if any more changes are needed 🙂

vishnuchalla · 2025-12-03T13:54:01Z

Hey @abraham2512 thanks for the changes. Can you rebase please, so that I can take a look ASAP?

abraham2512 · 2025-12-04T04:19:09Z

@vishnuchalla rebased, ptal when you can 😄

vishnuchalla · 2025-12-04T20:23:24Z

kustomize/base/deployment-jira-mcp.yaml

@@ -0,0 +1,42 @@
+apiVersion: apps/v1


This deployment should be in its own namespace, idea being it can be commonly reused by others also to avoid tight coupling with BugZooka.

vishnuchalla · 2025-12-04T20:24:02Z

kustomize/base/kustomization.yaml

  - configmap-prompts.yaml
  - configmap-mcp-config.yaml
  - deployment.yaml
+  - deployment-jira-mcp.yaml


Shoudn't be part of this kustomize. Please see how we recently deployed Orion MCP for understanding.

vishnuchalla · 2025-12-04T20:24:57Z

README.md

 export QUAY_CRED='<base64 encoded pull secret>'
 export BUGZOOKA_IMAGE='<bugzooka image tag>'
 export BUGZOOKA_NAMESPACE='<your namespace>'
+export JIRA_MCP_IMAGE='<jira mcp server image>'


Same as other comments about JIRA MCP isolation.

vishnuchalla · 2025-12-04T20:26:16Z

bugzooka/integrations/gemini_client.py

    INFERENCE_MAX_TOOL_ITERATIONS,
 )
 from bugzooka.integrations.inference import InferenceAPIUnavailableError
+from bugzooka.analysis.prompts import JIRA_TOOL_PROMPT


Most of the changes here are related to formatting, can we avoid them in this PR please and only keep the real code changes? Those optimizations can be taken care in other follow ups if requried.

vishnuchalla · 2025-12-04T20:27:03Z

kustomize/base/configmap-prompts.yaml

-        "user": "Here is the log summary from an OpenShift environment:\n\n{summary}\n\nBased on this summary, provide a structured breakdown of:\n- The OpenShift component likely affected (e.g., etcd, kube-apiserver, ingress, SDN, Machine API)\n- The probable root cause\n- Steps to verify the issue further\n- Suggested resolution, including OpenShift-specific commands or configurations.",
-        "assistant": "**Affected Component:** <Identified component>\n\n**Probable Root Cause:** <Describe why this issue might be occurring>\n\n**Verification Steps:**\n- <Step 1>\n- <Step 2>\n- <Step 3>\n\n**Suggested Resolution:**\n- <OpenShift CLI commands>\n- <Relevant OpenShift configurations>"
-      },
+        "OPENSHIFT_PROMPT": {


Strange, do you have an inbuilt linter in our IDE? Almost all the changes are being formatted.

abraham2512 force-pushed the jira-mcp branch 10 times, most recently from 58b9813 to 85ec230 Compare November 11, 2025 11:39

vishnuchalla requested changes Nov 17, 2025

View reviewed changes

README.md Outdated Show resolved Hide resolved

bugzooka/integrations/jira_client.py Outdated Show resolved Hide resolved

bugzooka/integrations/jira_client.py Outdated Show resolved Hide resolved

kustomize/base/configmap-prompts.yaml Outdated Show resolved Hide resolved

abraham2512 requested a review from vishnuchalla December 2, 2025 03:35

abraham2512 force-pushed the jira-mcp branch from f02c446 to 55131ea Compare December 2, 2025 03:56

abraham2512 force-pushed the jira-mcp branch 2 times, most recently from 57a1d1e to 7db9c39 Compare December 3, 2025 20:24

mcp: jira client

52c557b

abraham2512 force-pushed the jira-mcp branch from f8a1638 to 52c557b Compare December 4, 2025 04:18

vishnuchalla reviewed Dec 4, 2025

View reviewed changes

vishnuchalla requested a review from avasilevskii December 4, 2025 20:29

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

PERFSCALE-4192: Jira mcp integration #55

PERFSCALE-4192: Jira mcp integration #55

Uh oh!

abraham2512 commented Nov 10, 2025 •

edited

Loading

Uh oh!

vishnuchalla left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

abraham2512 commented Dec 2, 2025

Uh oh!

vishnuchalla commented Dec 3, 2025

Uh oh!

abraham2512 commented Dec 4, 2025 •

edited

Loading

Uh oh!

vishnuchalla Dec 4, 2025

Uh oh!

vishnuchalla Dec 4, 2025

Uh oh!

vishnuchalla Dec 4, 2025

Uh oh!

vishnuchalla Dec 4, 2025

Uh oh!

vishnuchalla Dec 4, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

PERFSCALE-4192: Jira mcp integration #55

Are you sure you want to change the base?

PERFSCALE-4192: Jira mcp integration #55

Uh oh!

Conversation

abraham2512 commented Nov 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

vishnuchalla left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

abraham2512 commented Dec 2, 2025

Uh oh!

vishnuchalla commented Dec 3, 2025

Uh oh!

abraham2512 commented Dec 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

vishnuchalla Dec 4, 2025

Choose a reason for hiding this comment

Uh oh!

vishnuchalla Dec 4, 2025

Choose a reason for hiding this comment

Uh oh!

vishnuchalla Dec 4, 2025

Choose a reason for hiding this comment

Uh oh!

vishnuchalla Dec 4, 2025

Choose a reason for hiding this comment

Uh oh!

vishnuchalla Dec 4, 2025

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

abraham2512 commented Nov 10, 2025 •

edited

Loading

abraham2512 commented Dec 4, 2025 •

edited

Loading