azurenoops / azurenoops/spin_agent

[BUG] [Portfolio] - Portfolio dashboard entirely dominated by QA test debris — all 21 visible systems are QA orphans, real systems invisible

Open
#635 0 comments 0 reactions 1 assignee Claimed by @jrspinella View on GitHub
agent:oracle area:rmf bug priority:critical
Dominant language
C#
Stars
3
Forks
1
Avg merge
18h 9m
Merged PRs (30d)
43

Description

## Bug Description

The Portfolio Risk Profile dashboard (org-scoped view) is entirely populated by QA test debris systems. As of the 2026-07-11 sweep, all 21 systems displayed in the PEO-790 org portfolio are named "QA Test System [TIMESTAMP]" with the QTS acronym. No legitimate production systems (including Coastal Watch) are visible. Every chart, compliance bar, ATO status tile, and risk table in the dashboard is showing test noise.

This is a critical visibility escalation of issue #615 (no system delete capability). Because systems cannot be deleted, the QA test orphans have accumulated until they dominate the entire org-scoped portfolio view, rendering it effectively non-functional for any demonstration, review, or real use.

## Steps to Reproduce

1. Navigate to `https://ca-ato-copilot-dashboard-v2.blackwater-9393aa1a.centralus.azurecontainerapps.io/`
2. Observe the Portfolio Risk Profile page (PEO-790 org context)
3. Scroll through "Compliance by System" bar chart — all 21 entries show "QTS 0%"
4. Scroll to "ATO Status" — all entries show "QTS None"
5. Scroll to "System Risk Summary" table — all rows are QA Test System [TIMESTAMP] entries
6. Note: No real systems (Coastal Watch or others) are visible

## Expected Behavior

Portfolio dashboard shows legitimate systems with real compliance data. Test systems should not persist beyond their test sweep or should be filterable/deletable.

## Actual Behavior

- 21 of 21 visible systems in the portfolio are QA test orphans (QTS acronym)
- All compliance bars show "QTS 0%"
- All ATO tiles show "QTS None"
- The portfolio view is completely unusable for any legitimate purpose
- MCP backend reports 71 total systems; the accumulation is accelerating (was 63 in prior sweeps)

## Root Cause

Directly caused by #615 (no system delete capability). With no way to clean up test systems, they accumulate in the active org and contaminate all portfolio views. The system count grew from 58 (#615 filed) → 63 → 71 across sweeps.

## Console Errors

- Recurring SignalR race condition: `Failed to start HttpConnection before stop() was called` (#544)

## Browser/Environment

Azure Container Apps Dashboard
Browser: Chromium (Playwright/Hermes browser)
Date: 2026-07-11T13:02:00Z
Sweep: Automated 4-hour QA sweep

## Playwright Test Code

```typescript
test('[Portfolio] portfolio dashboard contaminated by QA test debris', async ({ page }) => {
await page.goto('/');
// Verify no QTS-named systems appear in compliance chart
const qtsLinks = page.locator('text=QTS');
await expect(qtsLinks).toHaveCount(0);
});
```

## Related Issues
- #615: No delete capability for systems (root cause)
- #619: Total Systems KPI mismatch
- #621: Chat blocked by SYSTEM_REQUIRED due to orphan accumulation

*Filed by Oracle — Automated 4-hour QA Sweep 2026-07-11T13:02:00Z*

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.