open-rmf / open-rmf/rmf

[Bug]: Cannot Launch rmf demos properly since at least 12 June 2024 via official docker image

Open
#477 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
439
Forks
90
PR merge metrics
No merged PRs in 30d

Description

Before proceeding, is there an existing issue or discussion for this?
OS and version

Ubuntu 22.04

Open-RMF installation type

Docker

Other Open-RMF installation methods

No response

Open-RMF version or commit hash

2.3.0

ROS distribution

Rolling

ROS installation type

Docker

Other ROS installation methods

No response

Package or library, if applicable

No response

Description of the bug

No demo scenario can be launched properly

More precisely, the fleet adapter cannot connect to the server

[fleet_adapter-15] [ERROR] [1718262000.911974934] [tinyRobot_fleet_adapter]: Connection lost
[fleet_adapter-15] > Reconnecting in 1s
[fleet_adapter-15] > Host: ws://localhost:8000/_internal
[fleet_adapter-15] [INFO] [1718262001.912357421] [tinyRobot_fleet_adapter]: Attempting to connect to ws://localhost:8000/_internal
[fleet_adapter-15] [ERROR] [1718262001.913277417] [tinyRobot_fleet_adapter]: Connection to ws://localhost:8000/_internal failed. Reason:
[fleet_adapter-15]  > URI: ws://localhost:8000/_internal
[fleet_adapter-15] > Status: Closed
[fleet_adapter-15] > Remote Server: None Specified
[fleet_adapter-15] > Error/close reason: Underlying Transport Error
[fleet_adapter-15] 

This causes the scenarios to not be usable as is.

Steps to reproduce the bug

Follow the instructions here

docker pull ghcr.io/open-rmf/rmf/rmf_demos:latest
docker tag ghcr.io/open-rmf/rmf/rmf_demos:latest rmf:latest
docker run -it --network host rmf:latest bash -c "export ROS_DOMAIN_ID=9; ros2 launch rmf_demos_gz office.launch.xml headless:=1"
Expected behavior

Launch with no problem nor tinkering needed

Actual behavior

Cannot use as is

Additional information or screenshots

This problem occurred since yesterday ( 12 June ) and maybe before when I tried to run some demos to try new things but failed, Today I tried launching from docker but failed too.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Docker container instructions and the ros2 launch rmf_demos_gz office.launch.xml headless:=1 command on Ubuntu 22.04. Reproduce the fleet adapter's failed connection to ws://localhost:8000/_internal; done means the official image launches the demo scenario without tinkering.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, ubuntu
Domain
infrastructure, robotics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.