Chain comparison is failing when nodes have the same block

[4miners]

Expected behavior

Chain comparison should pass when nodes have the same block.

Actual behavior

Chain comparison is failing even when nodes have the same block. Last block is 15910358440661876618 - every node in the netwok have this block.

11:41:58.790Z DEBUG lisk-framework: Perform chain recovery due to poor consensus
11:41:58.791Z  WARN lisk-framework: Chain comparison failed, starting recovery
11:41:58.791Z  WARN lisk-framework:
    Deleting last block { id: '15910358440661876618',
      version: 1,
      timestamp: 97979220,
      height: 19,
      previousBlock: '12630086668773113114',
      numberOfTransactions: 0,
      totalAmount: 0,
      totalFee: 0,
      reward: 0,
      payloadLength: 0,
      payloadHash:
       'e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855',
      generatorPublicKey:
       '5f6cc5a8aac752d37c676b0d46a798f7625e37dfa1e96091983274e04ab7ffe2',
      generatorId: '2037513790649430470L',
      blockSignature:
       '64fe8a9ffd3375e580804a1de7283857ae6964518cdbefe6bbc9e28ffe0f74cf65fc1ee1c43543e59e86419392718e5c11c5e226f4e621f46b125908f1094c07',
      confirmations: 0,
      totalForged: '0',
      transactions: [] }
11:41:58.816Z DEBUG lisk-framework: Performing backward tick
11:41:58.827Z DEBUG lisk-framework:
    Application state { os: 'linux4.15.0-54-generic',
      version: '2.0.0-rc.0',
      wsPort: 5000,
      httpPort: 4000,
      minVersion: '1.1.0-rc.0',
      protocolVersion: '1.1',
      height: 18,
      nethash:
       '198f2b61a8eb95fbeed58b8216780b68f697f26b849acf00c8c93bb9b24f783d',
      broadhash:
       '2ca25a3d7e2eef75e3b7286e5ce69b462a50a88acbe7f2133aae75f3862413b0',
      nonce: 'D5HpiAdnmVqLJCbS' }
11:41:58.862Z  INFO lisk-framework: Recovery complete, new last block 12630086668773113114
11:41:58.869Z ERROR lisk-framework: Failed chain recovery after failing to load blocks while network consensus was low. null
11:41:58.872Z DEBUG lisk-framework:
    Application state { os: 'linux4.15.0-54-generic',
      version: '2.0.0-rc.0',
      wsPort: 5000,
      httpPort: 4000,
      minVersion: '1.1.0-rc.0',
      protocolVersion: '1.1',
      height: 18,
      nethash:
       '198f2b61a8eb95fbeed58b8216780b68f697f26b849acf00c8c93bb9b24f783d',
      broadhash:
       '2ca25a3d7e2eef75e3b7286e5ce69b462a50a88acbe7f2133aae75f3862413b0',
      nonce: 'D5HpiAdnmVqLJCbS' }
11:41:58.901Z DEBUG lisk-framework: Establishing broadhash consensus after sync: 0 %
11:41:58.902Z  INFO lisk-framework: Finished sync

Also this message is weird because chain recovery was succesfull:

11:41:58.869Z ERROR lisk-framework: Failed chain recovery after failing to load blocks while network consensus was low. null

Steps to reproduce

Sync with alphanet (jenkinsnet-19).

Which version(s) does this affect? (Environment, OS, etc...)

release/2.0.0

[shuse2]

Chain comparison is failing even when nodes have the same block is caused by the #3612
When it syncs to the node, it fails by #3612, which leads to this error.