We have 2 Globus Data Transfer nodes, one for external to UAB transfers (dtn1) and one for internal (dtn2). We started the upgrade Friday evening with dtn2. We experienced an issue that caused the node to be down until this morning.
The problem was an old Gridmap entry in /etc/grid-security/grid-mapfile, /C=US/O=Globus Consortium/OU=Globus Connect User/CN=ajwarne: ['jelaiw'].
After much back and forth with Globus support, we deleted the entry and were able to proceed with the upgrade this morning.
dtn2 is on v5.4 and transfers are working as expected. The next step from here is to upgrade dtn1.
I upgraded dtn1 (off-campus) on Aug 4th. We ran into an issue with guest collections not being accessible to the owners. The cause was a bug on Globus' end that was resolved on Aug 9th.