Failure when upgrading RE1 to Ubuntu 20.04

Ask
1

Hello!

I am attempting to upgrade our Stretch RE1 to 20.04 using the instructions on Github
When running the stretch_new_robot_install.sh script, I receive the “FAILURE. INSTALLATION DID NOT COMPLETE.” message, but the log messages above show no error.

Looking through the log files, it seems to have failed when creating the Galactic ament workspace:

Could not checkout ref ‘ros2-beta’: fatal: invalid reference: ros2-beta

Any help to solve this issue would be greatly appreciated!

You can find the full log files here.

2

Hi @lstegner, a few days ago the ‘ros2-beta’ branch from the realsense-ros repo was renamed to ‘ros2-development’, which is why the new robot install failed looking for the old branch. It’s now fixed in Stretch Install and you don’t have to start a new robot install from scratch. You can pickup from where the script crashed by:

  1. Opening ~/.bashrc and commenting out the lines that source noetic/setup.bash and catkin_ws/devel/setup.bash.

  2. Running the following command:

    ~/stretch_install/factory/20.04/stretch_create_ament_workspace.sh

  3. Uncommenting out the lines from step 1.

Then continue with the post-install steps from the instructions on Github. Thank you for reporting this issue here!

Update Nov 4: Added steps 1 & 3 of the instructions above based on the error Laura saw below.

1 Like
3

Hi @bshah, thank you so much for the quick fix!

When I run the script you recommend to resume the install, I get the following:

###########################################
CREATING GALACTIC AMENT WORKSPACE at /home/hello-robot/ament_ws
###########################################
Ensuring correct version of ROS is sourced...
Cannot create workspace while a conflicting ROS version is sourced. Exiting.
hello-robot@stretch-re1-1042:~/stretch_install$

However, I was able to start the new robot install from scratch, and it succeeded.

1 Like
4

Glad to hear it @lstegner! That’s my mistake; the error is expected because I forgot to mention an additional step to “unsource” ROS1 while building the ROS2 workspace. I’ve fixed this in my reply above so it’s correct for anyone else who sees this thread.

1 Like