Skip to content

bug(nvca): refresh running queues after registration #835

Description

@kristinapathak

Describe the bug

A running NVCA agent can keep using its previous queue credentials after a successful registration returns a replacement queue set. Work for the newly registered queue is not processed until a later credential refresh or agent restart.

Steps or code to reproduce bug

  1. Start an NVCA agent with a queue manager.
  2. Trigger a registration update that returns queue credentials for a different GPU queue.
  3. Inspect the running queue manager.

Expected behavior

The running queue manager immediately uses the queue credentials returned by the successful registration.

Additional context

The fix refreshes the in-memory queue manager after the registration response is persisted. A regression test covers switching from the original queue to a replacement GPU queue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-triageIssue or PR awaiting maintainer triage

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions