Updating to OSG 26¶

This document provides instructions for upgrading to the OSG 26 series. Please read through the instructions before upgrading.

Updating the OSG Repositories¶

1. Because configuration updates may be necessary, be sure to turn off any OSG services before updating them. Consult the relevant section for the service you're upgrading before updating the OSG Yum repositories:

   • Compute Entrypoint
   • HTCondor hosts
   • OSDF Cache or Origin
   • GlideinWMS Frontend

2. Clean the yum cache:

   root@host # yum clean all --enablerepo=*
   

3. Remove the old series Yum repositories:

   root@host # yum erase osg-release
   

   This step ensures that any local modifications to *.repo files will not prevent installing the new series repositories. Any modified *.repo files should appear under /etc/yum.repos.d/ with the *.rpmsave extension. After installing the new OSG repositories (the next step) you may want to apply any changes made in the *.rpmsave files to the new *.repo files.

4. Update your Yum repositories to OSG 26

5. Update software:

       :::console
       root@host # yum update
   

   Warning

   • Please be aware that running yum update may also update other RPMs. You can exclude packages from being updated using the --exclude=[package-name or glob] option for the yum command.
   • Watch the yum update carefully for any messages about a .rpmnew file being created. That means that a configuration file had been edited, and a new default version was to be installed. In that case, RPM does not overwrite the edited configuration file but instead installs the new version with a .rpmnew extension. You will need to merge any edits that have made into the .rpmnew file and then move the merged version into place (that is, without the .rpmnew extension).

6. Continue on to any update instructions that match the role(s) that the host performs.

Updating Your OSG Compute Entrypoint¶

The OSG 26 release series contains HTCondor-CE 26.

To upgrade your CE to OSG 26, follow the sections below.

1. Ensure that you have the latest HTCondor installed (at least HTCondor 25.15.15 or HTCondor 25.0.15).

2. Run the condor_ce_upgrade_check script and address any issues found.

3. If you have an HTCondor batch system, also run the condor_upgrade_check script and address any issues found.

4. Also consult the upgrade documentation for more information.

You may proceed with the repository and RPM update process.

Updating Your HTCondor Hosts¶

If you are running an HTCondor pool, consult the following instructions to update to HTCondor from OSG 25.

1. Ensure that you have the latest HTCondor installed (at least HTCondor 25.15.15 or HTCondor 25.0.15).

2. Run the condor_upgrade_check script and address any issues found.

3. Also consult the HTCondor 26.0 upgrade instructions.

You may proceed with the repository and RPM update process.

Updating Your OSDF Cache or Origin¶

OSG 26 ships with the Pelican 26 series; note the following changes from 7.26 or earlier:

All

• If you use environment variables that start with OSDF_ or STASH_, replace the OSDF_ or STASH_ prefix with PELICAN_. You must do this for daemons and clients. Configuration via environment variables starting with OSDF_ and STASH_ is dropped.

• Back up your database before upgrading. The database schema has changed and, if you need to downgrade, you will need to restore the database from the backup.

  Run the following command to get the location of the database file:

  $ pelican-server config get server.dblocation
  

  (Note: the default location is /var/lib/pelican/pelican.sqlite)

  Then, use the following command to make a backup to a file named pelicanbackup.sqlite (replacing <DBLOCATION> with the path to the database file):

  $ sqlite3 <DBLOCATION> ".backup 'pelicanbackup.sqlite'"
  

  To restore the backup, shut down the pelican-cache service (for a cache) or the pelican-origin service (for an origin) and overwrite the database with the backup file using the following (replacing <DBLOCATION> with the path to the database file):

  $ systemctl stop pelican-cache
  $ mv -f pelicanbackup.sqlite <DBLOCATION>
  

  Or

  $ systemctl stop pelican-origin
  $ mv -f pelicanbackup.sqlite <DBLOCATION>
  

• If you use OIDC for web UI access, and use the Server.UIAdminUsers, Server.UserAdminUsers, or Server.CollectionAdminUsers options, you will need to change the listed usernames to Pelican usernames by running a migration script.

  Download the conversion helper script and run it before upgrading the RPMs.

  Note

  We recommend using admin groups instead of users (Server.AdminGroups) to simplify access management going forward.

• If you use API keys, you may need to re-create some of them. After upgrading, check the server logs for the name of the key and the string "Re-mint it." Then, recreate those API keys using the instructions for the pelican-server apikey command.

Origins

• If you set Origin.IssuerMode to oa4mp in your configuration, you must change it to embedded. Support for the OA4MP issuer has been removed and replaced with a token issuer built into the Pelican server.

For additional upgrade information, see both the release notes for 7.27 and the release notes for 26.0.

After making any necessary config changes and backups, you may proceed with the repository and RPM update process.

Updating Your GlideinWMS Frontend¶

Verify your frontend configuration and make the following change, if necessary, before upgrading:

• In the security section of your frontend configuration (frontend.xml), replace the ProxyAll plugin with CredentialsBasic.

You may proceed with the repository and RPM update process.

Getting Help¶

To get assistance, please use the this page.