3650 trunk port err-disabled after upgrade to 16.3.8

After upgrading a standalone Catalyst 3650-48PD-E IP Base switch that has a single fiber cable trunk connected to the main 3650 access switch stack for its path outbound to the Internet, we had the switchport for the trunk go err-disabled on the standalone switch after it came up from the reboot after the upgrade process. We upgraded from 3.6.6E to 16.3.8. I had performed the same upgrade without issues on other offices that are configured in this way.

We don't prune vlans on this trunk, pvst is running on both, BPDUguard is not on this port, and both switches have the same vlan configuration and are running VTP.

I didn't see a message about the port being err-disabled in the syslog, just a message about it being blocked by spanning tree and some link flaps. I looked it up, and the STP syslog message below suggests native vlan was set to different vlans on either side of the trunk, but both switches don't specify a native vlan so it should default to vlan 1, and currently both are trunking native vlan 1.

I was able to recover from this problem by doing a shut / no shut on the impacted interface gi1/1/1, and we didn't get spanning tree messages after that, the port came up without issue. I'd like to better understand what happened so I can control for it when I upgrade other offices with similar setups. Does it look like the err-disable status is from link flap, and is the STP syslog message unrelated to the err-disable status? STP should only block, not errdisable, as there is not BPDUguard on this port. Errdisable flap-value for link flap is the default of 5 flaps in 10 seconds, but we saw 3 flaps in 10 seconds. Would errdisable recovery cause link-flap help in this case? Is this a known bug?

Syslog from the standalone switch after rebooting from the upgrade below. This shows what happened before the port went errdisabled, but there wasn't an entry in syslog for the port going errdisabled.

000259: *Jul 30 20:44:24: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/1, changed state to down 000266: *Jul 30 20:51:16: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/1, changed state to up 000271: *Jul 30 20:51:18: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 3 on GigabitEthernet1/1/1 VLAN1. 000272: *Jul 30 20:51:18: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking GigabitEthernet1/1/1 on VLAN0001. Inconsistent local vlan. 000273: *Jul 30 20:51:18: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/1, changed state to up 000276: *Jul 30 20:51:23: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/1, changed state to down 000277: *Jul 30 20:51:26: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/1/1, changed state to up