Hi @Terry Chan
As this problem is more related to SQL server, after I discussed it with my teammates, we would suggest you check from this official article to see whether there is some step wrong in the process of upgrade, which includes:
- Prerequisites
- Rolling upgrade basics for availability groups
- Rolling upgrade process
- AG with one remote secondary replica
- AG with failover cluster instance nodes
- Upgrade or update SQL Server instances with multiple AGs
- Rolling upgrade of a distributed availability group
- General steps to upgrade a distributed availability group
- Diagram example for a rolling upgrade of a distributed availability group
- Special steps for change data capture or replication
https://learn.microsoft.com/en-us/sql/database-engine/availability-groups/windows/upgrading-always-on-availability-group-replica-instances?view=sql-server-ver16
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.