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

[POOL_UPGRADE] Upgrade scheduled to future date happened in current date on part of nodes

    XMLWordPrintable

Details

    • Bug
    • Status: Complete
    • High
    • Resolution: Done
    • None
    • None
    • None
    • Build Info:
      sovrin-client version: 0.3.130
      sovrin-node version: 0.3.132

      OS/Platform: Ubuntu 16.04.2 LTS

    • Indy-1, 14, INDY 17.21, INDY 17.22

    Description

      Overview:
      There were several not successful attempts of POOL_UPGRADE (with invalid intervals between upgrades, without timeout, send transaction without connection to test environment, send transaction not as trustee) on following pool: https://docs.google.com/spreadsheets/d/1fkFQlkGFIs6b_tyiL-Wwu-E81SSJLanfdgYzJEhzmNM/edit#gid=359577200
      In each POOL_UPGRADE command date of upgrade was not today. After that valid transaction was send and part of nodes were upgraded.

      Steps to Reproduce:
      1. Open CLI in the client.
      2. send POOL_UPGRADE transaction (full history of commands is in cli.log).

      send POOL_UPGRADE name=upgrade-oz version=0.3.138 sha256=aad1242 action=start schedule={'Gw6pDLhcBcoQesN72qfotTgFa7cbuqZpkX3Xo6pLhPhv': '2017-06-25T12:30:00.000000+00:00', '8ECVSk179mjsjKRLWiQtssMLgp6EPhWXtaYyStWPSGAb': '2017-06-25T12:35:00.000000+00:00', 'DKVxG2fXXTU8yT5N7hGEbXB3dfdAnYv1JczDUHpmDxya': '2017-06-25T12:40:00.000000+00:00', '4PS3EDQ3dW1tci1Bp6543CfuuebjFrg36kLAUcskGfaA': '2017-06-25T12:45:00.000000+00:00', '4SWokCJWJc69Tn74VvLS6t2G2ucvXqM9FDMsWJjmsUxe': '2017-06-25T12:50:00.000000+00:00', 'Cv1Ehj43DDM5ttNBmC6VPpEfwXWwfGktHwjDJsTV5Fz8': '2017-06-25T12:55:00.000000+00:00', 'BM8dTooz5uykCbYSAAFwKNkYfT4koomBHsSWHTDtkjhW': '2017-06-25T13:00:00.000000+00:00'} timeout=5

      3. Look at nodes.

      Actual Results:
      Nodes 1, 2, 3, 4, and 7 were upgraded at specified time but the date was 2017-06-14, nodes 5 and 6 were not upgraded.

      Expected Results:
      Upgrade should be scheduled to 2017-06-25, nodes should not be upgraded.

      Additional Information:
      Logs of not upgraded node: Node5logs1.tar.gz Node5logs.tar.gz

      Logs of upgraded node: Node7logs.tar.gz

      upgrade_log of not upgraded node:

      2017-06-14 13:00:29.988500 scheduled 2017-06-25 12:50:00+00:00 0.3.138

      upgrade_log of upgraded node:

      2017-06-14 12:26:17.608040 scheduled 2017-06-25 13:00:00+00:00 0.3.138
      2017-06-14 12:59:59.612719 scheduled 2017-06-25 13:00:00+00:00 0.3.138
      2017-06-14 13:00:17.123279 succeeded 2017-06-25 13:00:00+00:00 0.3.138

      Attachments

        1. Node7logs.tar.gz
          8.41 MB
        2. Node5logs1.tar.gz
          9.50 MB
        3. Node5logs.tar.gz
          6.46 MB
        4. cli.log
          34 kB

        Issue Links

          Activity

            People

              Unassigned Unassigned
              ozheregelya Olga Zheregelya
              Andrey Kononykhin, Kelly Wilson, Mike Bailey, Nikita Spivachuk, Olga Zheregelya
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: