"previous: Upgrading to 2.7.1":#v2_7_1
-h3. Debian 10, Ubuntu 18.04, and CentOS 7 are no longer supported
+h3. Debian 10, Ubuntu 18.04, and CentOS are no longer supported
-Arvados 3.0 no longer supports some of the older distributions supported by Arvados 2.7: Debian 10 "buster," Ubuntu 18.04 "bionic," and CentOS 7. If you are running Arvados on any of these distributions, you must first upgrade to the next major release of your distribution before you upgrade to Arvados 3.0.
+Arvados 3.0 no longer supports some of the older distributions supported by Arvados 2.7: Debian 10 "buster," Ubuntu 18.04 "bionic," and CentOS 7 and 8. If you are running Arvados on any of these distributions, you must first upgrade to a supported distribution before you upgrade to Arvados 3.0.
-Arvados 2.7 supports Debian 11 "bullseye," Ubuntu 20.04 "focal," and CentOS 8. You can upgrade to one of those releases, then proceed to upgrade Arvados to 3.0.
+Arvados 2.7 supports Debian 11 "bullseye" and Ubuntu 20.04 "focal." If you are running Debian or Ubuntu, You can upgrade to one of those releases, then proceed to upgrade Arvados to 3.0.
+
+If you are running CentOS, Arvados 2.7 supports Red Hat Enterprise Linux 8, AlmaLinux 8, and Rocky Linux 8. Please plan a migration to one of these related distributions. Then you can upgrade to Arvados 3.0.
h3. RVM is no longer supported
If you have a custom install that requires a different version of Ruby than the one included with your distribution, you must configure your system to ensure package scripts find that version of @ruby@ before any others. For example, you might do this on Debian-based distributions by customizing apt's @DPkg::Path@ setting.
+h3. Slow migration on upgrade
+
+This upgrade includes a database schema update to rebuild full text search indexes to remove UUID and portable data hash column data. This will provide better search results to users and take less space on the databaes, but plan for the @arvados-api-server@ package upgrade to take longer than usual.
+
h3. S3 volume IAMRole configuration entry has been removed
The @Volumes.*.DriverParameters.IAMRole@ configuration entry for S3 volumes has been removed. You should remove it from your @/etc/arvados/config.yml@ file to avoid warnings when services start up. As before, if @AccessKeyID@ and @SecretAccessKey@ are blank, keepstore will retrieve IAM role credentials from instance metadata. Previously, documentation indicated that keepstore would refuse to use the IAM credentials if @IAMRole@ was specified and did not match the instance metadata, but that check has not been working for some time.
projects / arvados.git / blobdiff