BUG #17177: Secondary fails to start after upgrade from 13.3

The following bug has been logged on the website:

Bug reference:      17177
Logged by:          Andriy Bartash
Email address:      abartash@xmatters.com
PostgreSQL version: 13.4
Operating system:   CentOS7
Description:

Physical replication, primary and secondary are on 13.3, upgrading secondary
first and getting
2021-09-02 17:47:03.024 UTC [18068] (user=) (db=) (rhost=) (app=) [vxid:
txid:0] [] LOG:  unexpected timeline ID 2 in log segment
00000002000053E8000000E7, offset 4956160
2021-09-02 17:47:03.136 UTC [18068] (user=) (db=) (rhost=) (app=) [vxid:
txid:0] [] LOG:  unexpected timeline ID 2 in log segment
00000002000053E8000000E7, offset 5890048
2021-09-02 17:47:03.137 UTC [18171] (user=) (db=) (rhost=) (app=) [vxid:
txid:0] [] FATAL:  terminating walreceiver process due to administrator
command
Cluster is not starting.
Tried to replace 00000002000053E8000000E7 from primary manually but it
didn't help.
Once downgraded postgres to 13.3, cluster started successfully in standby
mode.
-----------------------------------------------------
pg_controldata output:
-----------------------------------------------------
pg_controldata -D /pgsql/cluster/data/
pg_control version number:            1300
Catalog version number:               202007201
Database system identifier:           6942522466342357095
Database cluster state:               in archive recovery
pg_control last modified:             Fri 03 Sep 2021 12:28:17 AM UTC
Latest checkpoint location:           53FC/37E028B8
Latest checkpoint's REDO location:    53FB/FAB28A40
Latest checkpoint's REDO WAL file:    00000002000053FB000000FA
Latest checkpoint's TimeLineID:       2
Latest checkpoint's PrevTimeLineID:   2

Please let me know if I need to provide anything else
Thank you in advance, Andriy