You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our workflow has us allocating jobs to a pool of queues (all maas servers with their own agent), with the ability to failover to the next device in the pool if one can't be provisioned. However, this doesn't work when the agent is in an offline state. We can't tell from the testflinger output if the agent is offline or just busy servicing an existing job. The outcome is that we end up waiting for hours before timing out.
In this case, it would be helpful to know the status of the agent (offline, waiting, etc), so that we can skip it when offline.
Our workflow has us allocating jobs to a pool of queues (all maas servers with their own agent), with the ability to failover to the next device in the pool if one can't be provisioned. However, this doesn't work when the agent is in an offline state. We can't tell from the testflinger output if the agent is offline or just busy servicing an existing job. The outcome is that we end up waiting for hours before timing out.
In this case, it would be helpful to know the status of the agent (offline, waiting, etc), so that we can skip it when offline.
For example:
The text was updated successfully, but these errors were encountered: