Fix timestamp constraint violation in __wti_disagg_set_crypt_key

XMLWordPrintableJSON

      format-stress-test-disagg-switch-stepdown-async-2 on amazon2023-stress-nonstandalone

      Host: i-06696d6a0cfa57155
      Project: wiredtiger
      Commit: 865efbe6
      Please refer to BF(G) Playbook for instructions on handling BF and BFG tickets as well as Auto-Resolution Rules

      Task Logs:

      format-stress-test-disagg-switch-stepdown-async-2 task_log

      Logs:

      [1787073948:094405][30557:0xffff54dddbc0], t, connection-open-session: [WT_VERB_DEFAULT][ERROR]: __wti_disagg_set_crypt_key, 537: set_key timestamp 97146357 must be strictly greater than the stable timestamp 97147018: Invalid argument
      [1787074000:274068][30557:0xffff771fdbc0], t, connection-open-session: [WT_VERB_DEFAULT][ERROR]: __wti_disagg_set_crypt_key, 537: set_key timestamp 104531261 must be strictly greater than the stable timestamp 104531859: Invalid argument
      

      logs

      format-stress-test-disagg-switch-stepdown-async-2 task_log

      Logs:

      Command 'shell.exec' in function 'format test disagg' (step 4 of 4) stopped early: context canceled.
      

      logs

      format-stress-test-disagg-switch-stepdown-async-2 task_log

      Logs:

      Running task commands failed: running command: command stopped early: context canceled
      

      logs

      format-stress-test-disagg-switch-stepdown-async-2 task_log

      Logs:

      t: No such file or directory.
      

      logs

      Repro Artifacts:

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            xgen-buildbaron-user
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: