perfSONAR Announcements

[Mark Feit <>]

A quick post-mortem on the failed 5.2.1 upgrade, then I’ll stop filling your mailboxes:

 

What Happened:  Code added as part of the resolution of issue #1486 (https://github.com/perfsonar/pscheduler/issues/1486) didn’t properly take the upgrade case into account and resulted in a failure that left the system in an unusable state.  As mentioned yesterday, mea culpa.

 

Affected Systems:  Anything running EL9 (Alma, Rocky) or Oracle Linux 8 that did an upgrade while 5.2.1 was present on our distribution site or its mirrors.  Thanks to a delay in building and releasing packages, Debian and Ubuntu systems will not have been affected.

 

Mitigation:

• Recovery from failed upgrades can be done by taking the steps outlined in the email sent yesterday (https://lists.internet2.edu/sympa/arc/perfsonar-announce/2025-07/msg00001.html).
• The 5.2.1 release is no longer marked as the latest in the RPM repository.  Any system attempting an upgrade will see 5.2.0 as being current.  This took immediate effect yesterday on the main distribution site and the mirrors should be caught up in the next couple of hours.
• A fix for the bad code has been developed and we’re looking at some avenues for handling failed upgrades more gracefully.  The nature of RPM and Debian packaging don’t allow for a system to be fully rolled back to its pre-upgrade state, but we’ll do what we can.

 

What’s Next:

• Release of the fix will be delayed until after next week.
• After that, we’ll enable 5.2.1 in the repositories.  This will be done in such a way that systems in the recovered-from-failure state are properly upgraded to the latest.
• We’ll send the 5.2.1 release announcement that should have gone out yesterday.

 

We’re sorry for the disruption and appreciate your patience with this.  As always, please drop us a line if you have questions or problems.