ROS Resources: Documentation | Support | Discussion Forum | Service Status | Q&A answers.ros.org

Planned downtime for ros_bootstrap repository


#1

2018-09-11 at around 5AM pacific time the ros_bootstrap repository will be offline for 48 hours as we prepare to migrate the underlying host.


2018-09-13 update: We are about to perform the DNS changeover to migrate to the new bootstrap repository. The new repository is keeping everything at the same paths so there should be no interruption when your local DNS starts resolving to the new location.

Changes to repos.ros.org

  • User facing:

    • InRelease files are not currently being generated. We are investigating the issue but as it does not prevent use of the repository we are proceeding with the migration as the existing host has a retirement deadline.

    • Packages with Architecture: all now appear in all binary architectures. The underlying repository software now includes packages with Architecture: all in… all architectures regardless of which ones were specified manually. This has resulted in a few auxiliary packages being included in architectures they were not previously listed in but should not affect the operations otherwise.

    • Empty repositories for hardy, jaunty, and karmic have been dropped completely.

  • Behind the scenes

    • The new repository is generated by aptly rather than reprepro and hosted via AWS S3.

This thread may also be used later in the week for additional migration related downtime. In which case both this top post will be edited and a follow up message will be sent.

During this time the import_upstream job on ros_buildfarm instances will be unable to reach the default bootstrap repository host causing a temporary failure to import packages. import_upstream jobs targeting other repositories such as the primary ROS repositories will not be affected.

I’ll send an update when things are back up.


#2

The bootstrap repository is back online. Thanks everyone.

We are hoping that the migration itself will be seamless and take place within the next 24-48 hours. I’m doing my best to keep everything in the same place from an apt perspective so that no configuration changes are needed.


#3

We are about to perform the DNS changeover to migrate to the new bootstrap repository. The new repository is keeping everything at the same paths so there should be no interruption when your local DNS starts resolving to the new location.

Changes to repos.ros.org

  • User facing:

    • InRelease files are not currently being generated. We are investigating the issue but as it does not prevent use of the repository we are proceeding with the migration as the existing host has a retirement deadline.

    • Empty repositories for hardy, jaunty, and karmic have been dropped completely.

  • Behind the scenes

    • The new repository is generated by aptly rather than reprepro and hosted via AWS S3.