BUG: async-agent-manager is unreliable for 'missing-test-levels' worker #6848

Open
opened 2026-04-10 03:22:32 +00:00 by HAL9000 · 1 comment
Owner

Metadata

  • Branch: bugfix/async-agent-manager-missing-test-levels
  • Commit Message: fix(automation): resolve invalid_agent_name error for missing-test-levels worker dispatch
  • Milestone: (none — backlog)
  • Parent Epic: #6833

Background and Context

The async-agent-manager is consistently failing to dispatch the missing-test-levels worker with an invalid_agent_name error. This is happening even though other workers with the exact same agent name (test-infra-improver) are being dispatched successfully, indicating the issue is specific to this worker's configuration or tag rather than the agent name itself.

This was discovered during the Infrastructure Analysis Pool (Cycle 1) operation tracked in #6833, where the pool supervisor attempted to dispatch all 8 analysis workers. Seven workers dispatched successfully; only the missing-test-levels worker failed.

Current Behavior

When the pool supervisor attempts to dispatch a worker with the following parameters:

  • agent_name: test-infra-improver
  • tag: AUTO-INF-missing-test-levels
  • display_name: worker-testinfra-missing-test-levels

The async-agent-manager returns an invalid_agent_name error and refuses to dispatch the worker.

Other workers using the same agent_name (test-infra-improver) with different tags and display names dispatch successfully, ruling out a general agent name resolution issue.

Expected Behavior

The async-agent-manager should dispatch the missing-test-levels worker successfully using the same agent_name as the other successfully dispatched workers. The dispatch result should be a valid worker handle, not an error.

Acceptance Criteria

  • Root cause of invalid_agent_name error for missing-test-levels worker is identified
  • async-agent-manager successfully dispatches a worker with agent_name=test-infra-improver, tag=AUTO-INF-missing-test-levels, display_name=worker-testinfra-missing-test-levels
  • No regression: other workers with agent_name=test-infra-improver continue to dispatch successfully
  • If the bug is in tag/display_name validation, validation logic is corrected and documented
  • If the bug is in agent name resolution under specific conditions, the resolution logic is hardened

Supporting Information

  • Discovered during: Infrastructure Analysis Pool (Cycle 1) — #6833
  • Failing worker tag: AUTO-INF-missing-test-levels
  • Failing worker display_name: worker-testinfra-missing-test-levels
  • Succeeding workers: all other 7 workers in the same pool cycle with identical agent_name
  • Error returned: invalid_agent_name
  • Workaround: Pool supervisor retries dispatch; analysis gap persists until resolved

Backlog note: This issue was discovered during autonomous operation
on milestone v3.5.0. It does not block milestone completion and has been
placed in the backlog for human review and future milestone assignment.

Subtasks

  • Reproduce the invalid_agent_name error in isolation with the exact parameters above
  • Inspect async-agent-manager dispatch logic for tag/display_name-dependent agent name resolution
  • Identify whether the issue is in tag parsing, display_name parsing, or agent name lookup
  • Implement fix in async-agent-manager dispatch path
  • Tests (Behave): Add scenario for dispatching worker with missing-test-levels-style tag
  • Tests (Robot): Add integration test verifying dispatch succeeds for all pool worker configurations
  • Verify coverage ≥97% via nox -s coverage_report
  • Run nox (all default sessions), fix any errors

Definition of Done

This issue is complete when:

  • All subtasks above are completed and checked off.
  • A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation.
  • The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
  • The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.
  • All nox stages pass.
  • Coverage ≥ 97%.

Automated by CleverAgents Bot
Supervisor: Test Infrastructure Analysis | Agent: new-issue-creator

## Metadata - **Branch**: `bugfix/async-agent-manager-missing-test-levels` - **Commit Message**: `fix(automation): resolve invalid_agent_name error for missing-test-levels worker dispatch` - **Milestone**: *(none — backlog)* - **Parent Epic**: #6833 ## Background and Context The `async-agent-manager` is consistently failing to dispatch the `missing-test-levels` worker with an `invalid_agent_name` error. This is happening even though other workers with the exact same agent name (`test-infra-improver`) are being dispatched successfully, indicating the issue is specific to this worker's configuration or tag rather than the agent name itself. This was discovered during the Infrastructure Analysis Pool (Cycle 1) operation tracked in #6833, where the pool supervisor attempted to dispatch all 8 analysis workers. Seven workers dispatched successfully; only the `missing-test-levels` worker failed. ## Current Behavior When the pool supervisor attempts to dispatch a worker with the following parameters: - `agent_name`: `test-infra-improver` - `tag`: `AUTO-INF-missing-test-levels` - `display_name`: `worker-testinfra-missing-test-levels` The `async-agent-manager` returns an `invalid_agent_name` error and refuses to dispatch the worker. Other workers using the same `agent_name` (`test-infra-improver`) with different tags and display names dispatch successfully, ruling out a general agent name resolution issue. ## Expected Behavior The `async-agent-manager` should dispatch the `missing-test-levels` worker successfully using the same `agent_name` as the other successfully dispatched workers. The dispatch result should be a valid worker handle, not an error. ## Acceptance Criteria - [ ] Root cause of `invalid_agent_name` error for `missing-test-levels` worker is identified - [ ] `async-agent-manager` successfully dispatches a worker with `agent_name=test-infra-improver`, `tag=AUTO-INF-missing-test-levels`, `display_name=worker-testinfra-missing-test-levels` - [ ] No regression: other workers with `agent_name=test-infra-improver` continue to dispatch successfully - [ ] If the bug is in tag/display_name validation, validation logic is corrected and documented - [ ] If the bug is in agent name resolution under specific conditions, the resolution logic is hardened ## Supporting Information - Discovered during: Infrastructure Analysis Pool (Cycle 1) — #6833 - Failing worker tag: `AUTO-INF-missing-test-levels` - Failing worker display_name: `worker-testinfra-missing-test-levels` - Succeeding workers: all other 7 workers in the same pool cycle with identical `agent_name` - Error returned: `invalid_agent_name` - Workaround: Pool supervisor retries dispatch; analysis gap persists until resolved > **Backlog note:** This issue was discovered during autonomous operation > on milestone v3.5.0. It does not block milestone completion and has been > placed in the backlog for human review and future milestone assignment. ## Subtasks - [ ] Reproduce the `invalid_agent_name` error in isolation with the exact parameters above - [ ] Inspect `async-agent-manager` dispatch logic for tag/display_name-dependent agent name resolution - [ ] Identify whether the issue is in tag parsing, display_name parsing, or agent name lookup - [ ] Implement fix in `async-agent-manager` dispatch path - [ ] Tests (Behave): Add scenario for dispatching worker with `missing-test-levels`-style tag - [ ] Tests (Robot): Add integration test verifying dispatch succeeds for all pool worker configurations - [ ] Verify coverage ≥97% via `nox -s coverage_report` - [ ] Run `nox` (all default sessions), fix any errors ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done. - All nox stages pass. - Coverage ≥ 97%. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure Analysis | Agent: new-issue-creator
HAL9000 added this to the v3.7.0 milestone 2026-04-10 05:08:02 +00:00
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: Backlog — This is an automation infrastructure bug affecting the async-agent-manager worker dispatch. While it's a bug, it's in the automation tooling layer (not the core product), so Backlog priority is appropriate.
  • Milestone: v3.7.0 — Automation infrastructure improvements belong in M8
  • MoSCoW: Must Have — Per policy, all Type/Bug issues are Must Have.
  • Parent Epic: #6833 (as noted in the issue body)

The root cause is an invalid_agent_name error specific to the missing-test-levels worker config. Other workers with the same agent name dispatch successfully, suggesting a config-specific issue.


Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner

Issue triaged by project owner: - **State**: Verified - **Priority**: Backlog — This is an automation infrastructure bug affecting the `async-agent-manager` worker dispatch. While it's a bug, it's in the automation tooling layer (not the core product), so Backlog priority is appropriate. - **Milestone**: v3.7.0 — Automation infrastructure improvements belong in M8 - **MoSCoW**: Must Have — Per policy, all Type/Bug issues are Must Have. - **Parent Epic**: #6833 (as noted in the issue body) The root cause is an `invalid_agent_name` error specific to the `missing-test-levels` worker config. Other workers with the same agent name dispatch successfully, suggesting a config-specific issue. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner
HAL9000 self-assigned this 2026-04-10 06:07:52 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#6848
No description provided.