Cross site state transfer - incorrect status of push operation

Status of push operation remains at value "CANCELLED" after the push operation was cancelled and reinvoked (even if state transfer is currently in progress) - "SENDING" value is expected. Otherwise works as expected (after the state transfer completes, status is switched to "OK").

• Sites LON (lonCache) - main, BRN (brnCache) - backup

Consider the following scenario:

[standalone@localhost:9999 distributed-cache=lonCache] site --push BRN
ok
[standalone@localhost:9999 distributed-cache=lonCache] site --cancelpush BRN
ok
[standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus
BRN=CANCELED
[standalone@localhost:9999 distributed-cache=lonCache] site --push BRN
ok
[standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus
BRN=CANCELED
[standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus
BRN=OK

Expected behavior:

[standalone@localhost:9999 distributed-cache=lonCache] site --push BRN
ok
[standalone@localhost:9999 distributed-cache=lonCache] site --cancelpush BRN
ok
[standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus
BRN=CANCELED
[standalone@localhost:9999 distributed-cache=lonCache] site --push BRN
ok
[standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus
BRN=SENDING
[standalone@localhost:9999 distributed-cache=lonCache] site --pushstatus
BRN=OK