Uploaded image for project: 'Opencast'
  1. MH-9002

Capture devices in different timezones are reported to be "offline"

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed and reviewed
    • Affects versions: 1.4.0, 1.3.1, 1.3
    • Fix versions: 1.4.0
    • Labels:
      None
    • Severity:
      Incorrectly Functioning With Workaround
    • Steps to reproduce:
      Hide
      Steps to reproduce:
      1. Attach a capture agent to a 1.3.0 or 1.3.1 core
      2. Make sure both capture agent and core are in different time zones
      3. Go to the admin ui and select that capture agent when scheduling a recording

      The following message appear (see screenshot):

      The capture agent you previously selected is currently offline. You may want to select a different capture agent.
      The timezone for this capture agent is 1 hours earlier. Capture will occur according to the time local to the agent, though when you look at your list of Recordings it will be shown in your local time.
      The capture agent you previously selected is currently offline. You may want to select a different capture agent.

      This message is misleading, since the only problem is that the agent is in a different time zone. It is unclear why the admin ui thinks that the device would be offline. In the debugger, I could see it update its status every now and then, and the REST endpoints correcmark it as IDLE.
      Show
      Steps to reproduce: 1. Attach a capture agent to a 1.3.0 or 1.3.1 core 2. Make sure both capture agent and core are in different time zones 3. Go to the admin ui and select that capture agent when scheduling a recording The following message appear (see screenshot): The capture agent you previously selected is currently offline. You may want to select a different capture agent. The timezone for this capture agent is 1 hours earlier. Capture will occur according to the time local to the agent, though when you look at your list of Recordings it will be shown in your local time. The capture agent you previously selected is currently offline. You may want to select a different capture agent. This message is misleading, since the only problem is that the agent is in a different time zone. It is unclear why the admin ui thinks that the device would be offline. In the debugger, I could see it update its status every now and then, and the REST endpoints correcmark it as IDLE.
    • Tags (folksonomy):

      TestRail: Results

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                edu.alonso Eduardo Alonso
                Reporter:
                twunden Tobias Wunden
              • Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  TestRail: Cases