bug: Example JSON config for hardware simulator doesn't work

[binfordn]

Overview

This config file doesn't work as-is if you use it with a hardware simulator: https://github.com/Opentrons/opentrons/blob/edge/robot-server/simulators/test.json

The issue that I can spot is an invalid pipette type: p10_single_v1 doesn't exist. An example that works is p20_single_v2.0. I think there are more errors in the module config that I can't spot, because it still doesn't work if I just change that.

Steps to reproduce

Follow these instructions: https://github.com/Opentrons/opentrons-integration-tools/tree/main/raspberry-pi

"Part 2" is where the invalid file comes in.

Current behavior

Opentrons Robot HTTP Server is unable to start.

# systemctl restart opentrons-robot-server.service
(...times out)

# systemctl status opentrons-robot-server.service
● opentrons-robot-server.service - Opentrons Robot HTTP Server
     Loaded: loaded (/etc/systemd/system/opentrons-robot-server.service; enabled; pre
     Active: activating (start) since Thu 2024-04-04 01:25:37 UTC; 18s ago
   Main PID: 1331 (uvicorn)
     CGroup: /system.slice/opentrons-robot-server.service
● opentrons-robot-server.service - Opentrons Robot HTTP Server
     Loaded: loaded (/etc/systemd/system/opentrons-robot-server.service; enabled; pre
     Active: activating (start) since Thu 2024-04-04 01:25:37 UTC; 23s ago
   Main PID: 1331 (uvicorn)
     CGroup: /system.slice/opentrons-robot-server.service
● opentrons-robot-server.service - Opentrons Robot HTTP Server
     Loaded: loaded (/etc/systemd/system/opentrons-robot-server.service; enabled; pre
     Active: activating (start) since Thu 2024-04-04 01:25:37 UTC; 39s ago
● opentrons-robot-server.service - Opentrons Robot HTTP Server
░░
░░ Unit opentrons-status-leds.service has begun starting up.
Apr 03 23:26:04 opentrons ot-commit-machine-id[155]: machine-id "bf0246ac87fc407f9c19
Apr 03 23:26:04 opentrons systemd[1]: Starting Rerun udev for block devices...
● opentrons-robot-server.service - Opentrons Robot HTTP Server
     Loaded: loaded (/etc/systemd/system/opentrons-robot-server.service; enabled; pre
     Active: activating (start) since Thu 2024-04-04 01:25:37 UTC; 1min 37s ago
   Main PID: 1331 (uvicorn)
     CGroup: /system.slice/opentrons-robot-server.service
             └─1331 /usr/bin/python /usr/bin/uvicorn robot_server.app:app --uds /

Apr 04 01:27:13 bf0246 uvicorn[1331]: Error response: 503 - LegacyError -
Apr 04 01:27:13 bf0246 uvicorn[1331]:  - "GET /instruments HTTP/1.1" 503
Apr 04 01:27:13 bf0246 uvicorn[1331]: Error response: 503 - LegacyError -
Apr 04 01:27:13 bf0246 uvicorn[1331]:  - "GET /robot/lights HTTP/1.1" 503
Apr 04 01:27:13 bf0246 uvicorn[1331]: Error response: 503 - LegacyError -
Apr 04 01:27:13 bf0246 uvicorn[1331]:  - "GET /pipettes HTTP/1.1" 503
Apr 04 01:27:13 bf0246 uvicorn[1331]: Error response: 503 - LegacyError -
Apr 04 01:27:13 bf0246 uvicorn[1331]:  - "GET /modules HTTP/1.1" 503
Apr 04 01:27:14 bf0246 uvicorn[1331]: Error response: 503 - LegacyError -
Apr 04 01:27:14 bf0246 uvicorn[1331]:  - "GET /health HTTP/1.1" 503

Expected behavior

The Robot HTTP Server starts successfully with a valid config file. Example:

{
  "attached_instruments": {
    "right": {
      "model": "p300_single_v2.0",
      "id": "321"
    },
    "left": {
      "model": "p20_single_v2.0",
      "id": "123"
    }
  },
  "attached_modules": {}
}

Operating system

Windows

System and robot setup or anything else?

• Image version 7.1.0 (latest image on Opentrons website: https://support.opentrons.com/s/article/List-of-software-releases-for-Opentrons)
• App version Opentrons-v7.2.1-win-b40806
• Connected to Raspberry Pi 3B+ via Ethernet