NM briefly changes its state from ASLEEP to CONNECTED_GLOBAL when resuming from suspend
When going to suspend without closing the established connection first, it appears to me that nm-1.2 (from Fedora 29) quickly changes its state from ASLEEP to CONNECTED_GLOBAL, before coming back to CONNECTED_LOCAL state, which is the expected state in this case (only virbr0 is still up upon resume).
I think that, this is caused by the final call to nm_manager_update_state() in do_sleep_wake(). When resuming, priv->connectivity_state still has the NM_CONNECTIVITY_FULL it had before suspend, and this value makes the elevation of new_state from NM_STATE_CONNECTED_LOCAL to NM_STATE_CONNECTED_GLOBAL.
The connectivity update happens later.
In the this log file nm.log, the connected devices before suspend are cdc-wdm0, and tap0. The log has been obained with NetworkManager --no-daemon --log-level=TRACE --log-domains=SUSPEND,CORE,DBUS_PROPS,CONCHECK,DEVICE --debug