Uploaded image for project: 'Indy Node'
  1. Indy Node
  2. INDY-382

[POOL_UPGRADE] Node is upgraded not on schedule when the upgrade is scheduled twice

    XMLWordPrintable

Details

    • Bug
    • Status: Complete
    • High
    • Resolution: Done
    • None
    • None
    • None

    • Build Info:
        sovrin-client version: 0.4.9
        sovrin-node version: 0.4.9
      OS/Platform: Ubuntu 16.04.2 LTS
      Setup: 4 nodes, 1 client

    • 14, INDY 17.21, INDY 17.22

    Description

      Overview:
      Node is upgraded not on schedule when the upgrade is scheduled twice.

      Case 1:
      Steps to Reproduce:
      1. Send POOL_UPGRADE to one or several nodes.
      Node1 upgrade is scheduled to 2017-07-25 14:00:

      send POOL_UPGRADE name=upgrade-1 version=0.4.9 sha256=f6f2ea8f45d8a057c9566a33f99474da2e5c6a6604d736121650e2730c6fb0a3 action=start schedule={'Gw6pDLhcBcoQesN72qfotTgFa7cbuqZpkX3Xo6pLhPhv': '2017-07-25T14:00:00.000000+00:00'} timeout=10 force=True

      Node2 upgrade is scheduled to 2017-07-10 14:10:

      send POOL_UPGRADE name=upgrade-2 version=0.4.9 sha256=f6f2ea8f45d8a057c9566a33f99474da2e5c6a6604d736121650e2730c6fb0a3 action=start schedule={'8ECVSk179mjsjKRLWiQtssMLgp6EPhWXtaYyStWPSGAb': '2017-07-10T14:10:00.000000+00:00'} timeout=10 force=True

      2. Send POOL_UPGRADE to all nodes.
      All nodes upgrade is scheduled to 2017-07-15:

      send POOL_UPGRADE name=upgrade-3 version=0.4.9 sha256=f6f2ea8f45d8a057c9566a33f99474da2e5c6a6604d736121650e2730c6fb0a3 action=start schedule={'Gw6pDLhcBcoQesN72qfotTgFa7cbuqZpkX3Xo6pLhPhv': '2017-07-15T12:20:00.000000+00:00', '8ECVSk179mjsjKRLWiQtssMLgp6EPhWXtaYyStWPSGAb': '2017-7-15T10:25:00.000000+00:00', 'DKVxG2fXXTU8yT5N7hGEbXB3dfdAnYv1JczDUHpmDxya': '2017-07-15T10:30:00.000000+00:00', '4PS3EDQ3dW1tci1Bp6543CfuuebjFrg36kLAUcskGfaA': '2017-07-15T10:35:00.000000+00:00'} timeout=10 force=False

      Actual Results:
      Node 1 and Node 2 were upgraded 2017-07-05 (in date of sending the last POOL_UPGRADE) at 14:00 and 14:10 accordingly.

      Expected Results:
      Nodes should be upgraded in accordance with the schedule.

      Attachments

        1. 2017-07-06 16_29_23-.png
          2017-07-06 16_29_23-.png
          697 kB
        2. cli.log
          149 kB
        3. new_logs.tar.gz
          537 kB
        4. Node1.log
          228 kB
        5. Node2.log
          250 kB
        6. Node3.log
          250 kB
        7. Node4.log
          251 kB
        8. upgrade_log_node1
          0.2 kB
        9. upgrade_log_node2
          0.3 kB
        10. upgrade_log_node3
          0.2 kB
        11. upgrade_log_node4
          0.2 kB

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. INDY-701 [POOL_UPGRADE] More earlier pool_upgrade was not happened when there were scheduled upgrade to future date.

          • Low - Minor problem or easily worked around.
          • Complete

          Bug - A problem which impairs or prevents the functions of the product. INDY-231 [POOL_UPGRADE] Upgrade scheduled to future date happened in current date on part of nodes

          • High - Serious problem that could block progress.
          • Complete

          Task - A task that needs to be done. INDY-280 Upgrade: submit pool upgrade when one node is scheduled to upgrade in a huge period of time, like a week

          • Medium - Has the potential to affect progress.
          • Complete

          Activity

            People

              nage Nathan George
              ozheregelya Olga Zheregelya
              Nikita Spivachuk, Olga Zheregelya, Vladimir Shishkin
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: