Add ERROR state for capture agent

Description

A capture agent should be able to indicate that it is in an ERROR state, i.e. unable to capture any recordings, for example because of a configuration error or capture hardware or stream being unavailable (e.g. an IP stream from a device that is down).

At present the CA can only show idle, unknown, or exit completely.

Currently supported states are:

/** The collection of all known states. TODO: Remove this when the states are replaced with enums */
List<String> KNOWN_STATES = Arrays.asList(new String[] { IDLE, SHUTTING_DOWN, CAPTURING, UPLOADING, UNKNOWN });

Activity

Show:
Stephen Marquard
July 26, 2016, 12:27 AM

In my view yes, because you may be scheduling for some time in the future when it'll be back online.

I think the "blacklisting" mechanism in the 2.x UI is intended to cater for cases where a CA should not be schedulable because it's known to be unavailable. Other than that, one should regard error, unknown, offline etc as transient states.

Greg Logan
July 26, 2016, 2:36 AM

Well that makes life easy then

Lars Kiesow
December 10, 2016, 2:37 AM

This is resolved, right?

Greg Logan
December 10, 2016, 7:16 AM

Not that I'm aware of... Neither r/2.3.x nor develop have an ERROR state, and I can't find a merged PR with this ticket.

Lars Kiesow
December 11, 2016, 1:07 AM

You are right. I confused that with the offline state you have added. I'll reopen it and set it to 2.4

Fixed and reviewed

Assignee

Greg Logan

Reporter

Stephen Marquard

Criticality

None

Tags (folksonomy)

None

Components

Fix versions

Affects versions