Configuring OS versions

Configuring OS versions

Before you begin

Before you start upgrading your Ubuntu version in Cloud Next environment (glossary term, activate to view definition), review the following specifications:

• Acquia recommends that you do not make any other changes to your site during the upgrade process.
• In Ubuntu 20.04:
  • Python2, rssh, Drush 9, and Drush 10 binaries are unavailable. If you depend on global Drush 9 or Drush 10, you must start using vendored Drush.
  • The ack-grep command is unavailable. You must update scripts to use the ack command instead.
  • The .svg file extension cannot be used with the ImageMagick module.
• In Ubuntu 22.04:
  • The preceding limitations for Ubuntu 20.04 apply to Ubuntu 22.04 as well.
  • The SimpleSAML compatibility shim is removed. Therefore, applications that did not make the SimpleSAML changes during the Cloud Next upgrade must make these changes.
  • OpenSSL 3.x disables a lot of legacy algorithms by default. For example, certificates using SHA1 or MD5 as hash algorithms are invalid. In addition, TLS protocols earlier than 1.2 are disabled.
  • The default Ubuntu version for newly provisioned Cloud Next environments, is Ubuntu 22.04.

• The drush8 and drush-launcher commands are unavailable on Ubuntu 24.04 (Noble). Update workflows to use a vendored Drush command.

• Ruby is not installed on Ubuntu 24.04 (Noble). Update scripts that require Ruby to use PHP or shell instead.

• CDE environments are hosted on Acquia Cloud Classic. CDE environments will remain on Ubuntu 16.04 until the CDE feature is available in Cloud Next.

• If you use LDAP, ensure that you add the custom variable, LDAPTLS_CACERT. For more information, visit Configuring LDAPS.

Upgrading the operating system in your Cloud Next environment

To upgrade your non-production and production Cloud Next environments to an available operating system:

1. Sign in to the Cloud Platform user interface.
   1. Access your organization (glossary term, activate to view definition), application (glossary term, activate to view definition), and environment.
2. Click Configuration > Operating System.
   The system displays the currently installed operating system.

3. In Available versions, click Upgrade now.

   Note

   If you try to upgrade your production environment without upgrading your non-production environment first, the system displays a warning message.

4. Type CONFIRM and click Submit.
   After some time, the system completes the upgrade process and displays a confirmation message.
5. Click Done.
   This completes the upgrade process. You can start testing your environment.

Testing your environments after the upgrade

Acquia recommends that you test your non-production environments immediately after you upgrade the operating system in such environments. By testing your environments, you can:

• Investigate and resolve any technical issues with the help of Acquia Support.
• Reduce the risk of delays or undesired behavior with your production environment upgrade.

When testing your environments through automated tests or manual inspection, review the application behavior that depends on the following:

• Custom logic in .htaccess files
• Image software such as ffmpeg, ImageMagick, or webp
• System libraries
• Connection to external network APIs/services from Drupal, PHP, or tools such as curl or wget, particularly those using older SSL/TLS versions
• Scheduled tasks or cron jobs
• Cloud hooks
• Custom shell scripts or commands that run on the SSH pod (glossary term, activate to view definition)

In addition, you must monitor application performance in New Relic after the upgrade and compare that with prior performance.

Reverting your operating system to another available version

While upgrading your container (glossary term, activate to view definition) operating system to new versions, you might run into some issues. While you troubleshoot such issues, you can revert your upgrade to ensure that your site remains unaffected.

To revert your operating system:

1. Sign in to the Cloud Platform user interface.
2. Access your organization, application, and environment.
3. Click Configuration > Operating System.
   The system displays the currently installed operating system.

4. In Available versions, click Revert.

   Note

   After a version of the operating system becomes end-of-life, you cannot revert your operating system to that version through the Cloud Platform user interface. In such cases, you can create a Support ticket.

5. Type CONFIRM and click Submit.
   After some time, the system completes the revert process and displays a confirmation message. If the revert process fails, click File support case to create a Support ticket.
6. Click Done.
   This completes the revert process. After you fix all issues, you can start your upgrade process again.

• Released in October, 2024 for non-FedRAMP customers. 

• Released in January, 2026 for FedRAMP customers.

Before you begin

Before you start upgrading your Ubuntu version in Cloud Next environment (glossary term, activate to view definition), review the following specifications:

• Acquia recommends that you do not make any other changes to your site during the upgrade process.
• In Ubuntu 20.04:
  • Python2, rssh, Drush 9, and Drush 10 binaries are unavailable. If you depend on global Drush 9 or Drush 10, you must start using vendored Drush.
  • The ack-grep command is unavailable. You must update scripts to use the ack command instead.
  • The .svg file extension cannot be used with the ImageMagick module.
• In Ubuntu 22.04:
  • The preceding limitations for Ubuntu 20.04 apply to Ubuntu 22.04 as well.
  • The SimpleSAML compatibility shim is removed. Therefore, applications that did not make the SimpleSAML changes during the Cloud Next upgrade must make these changes.
  • OpenSSL 3.x disables a lot of legacy algorithms by default. For example, certificates using SHA1 or MD5 as hash algorithms are invalid. In addition, TLS protocols earlier than 1.2 are disabled.
  • The default Ubuntu version for newly provisioned Cloud Next environments, is Ubuntu 22.04.

• The drush8 and drush-launcher commands are unavailable on Ubuntu 24.04 (Noble). Update workflows to use a vendored Drush command.

• Ruby is not installed on Ubuntu 24.04 (Noble). Update scripts that require Ruby to use PHP or shell instead.

• CDE environments are hosted on Acquia Cloud Classic. CDE environments will remain on Ubuntu 16.04 until the CDE feature is available in Cloud Next.

• If you use LDAP, ensure that you add the custom variable, LDAPTLS_CACERT. For more information, visit Configuring LDAPS.

Upgrading the operating system in your Cloud Next environment

To upgrade your non-production and production Cloud Next environments to an available operating system:

1. Sign in to the Cloud Platform user interface.
   1. Access your organization (glossary term, activate to view definition), application (glossary term, activate to view definition), and environment.
2. Click Configuration > Operating System.
   The system displays the currently installed operating system.

3. In Available versions, click Upgrade now.

   Note

   If you try to upgrade your production environment without upgrading your non-production environment first, the system displays a warning message.

4. Type CONFIRM and click Submit.
   After some time, the system completes the upgrade process and displays a confirmation message.
5. Click Done.
   This completes the upgrade process. You can start testing your environment.

Testing your environments after the upgrade

Acquia recommends that you test your non-production environments immediately after you upgrade the operating system in such environments. By testing your environments, you can:

• Investigate and resolve any technical issues with the help of Acquia Support.
• Reduce the risk of delays or undesired behavior with your production environment upgrade.

When testing your environments through automated tests or manual inspection, review the application behavior that depends on the following:

• Custom logic in .htaccess files
• Image software such as ffmpeg, ImageMagick, or webp
• System libraries
• Connection to external network APIs/services from Drupal, PHP, or tools such as curl or wget, particularly those using older SSL/TLS versions
• Scheduled tasks or cron jobs
• Cloud hooks
• Custom shell scripts or commands that run on the SSH pod (glossary term, activate to view definition)

In addition, you must monitor application performance in New Relic after the upgrade and compare that with prior performance.

Reverting your operating system to another available version

While upgrading your container (glossary term, activate to view definition) operating system to new versions, you might run into some issues. While you troubleshoot such issues, you can revert your upgrade to ensure that your site remains unaffected.

To revert your operating system:

1. Sign in to the Cloud Platform user interface.
2. Access your organization, application, and environment.
3. Click Configuration > Operating System.
   The system displays the currently installed operating system.

4. In Available versions, click Revert.

   Note

   After a version of the operating system becomes end-of-life, you cannot revert your operating system to that version through the Cloud Platform user interface. In such cases, you can create a Support ticket.

5. Type CONFIRM and click Submit.
   After some time, the system completes the revert process and displays a confirmation message. If the revert process fails, click File support case to create a Support ticket.
6. Click Done.
   This completes the revert process. After you fix all issues, you can start your upgrade process again.