Summary

What is the problem or use case, what are we trying to achieve?

Astrolabe is reporting setup failures across the suite:
https://spruce.mongodb.com/version/65a75ed161837d655953aafd/tasks?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC

Running post-task commands failed: running command: command failed: missing file '/data/mci/xxx/astrolabe-src/logs.tar.gz': opening file '/data/mci/xxx/astrolabe-src/logs.tar.gz': open /data/mci/xxx/astrolabe-src/logs.tar.gz: no such file or directory

Post task completed - FAILURE. Overall task status changed to FAILED.

This post-task is failing changing the status to failure.

Motivation

Who is the affected end user?

Who are the stakeholders?

All astrolabe build variants except for dotnet

How does this affect the end user?

Are they blocked? Are they annoyed? Are they confused?

Astrolabe tests seem to still be passing, but this setup issue hides that.

How likely is it that this problem or use case will occur?

Main path? Edge case?

The main path, seems to recur every task.

If the problem does occur, what are the consequences and how severe are they?

Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?

Each astrolabe task's logs must be inspected to determine if a driver change actually broke compatibility.

Is this issue urgent?

Does this ticket have a required timeline? What is it?

TBD

Is this ticket required by a downstream team?

Needed by e.g. Atlas, Shell, Compass?

Any driver with an astrolabe task

Is this ticket only for tests?

Does this ticket have any functional impact, or is it just test improvements?

Yes, improves shared astrolabe testing

Acceptance Criteria

What specific requirements must be met to consider the design phase complete?

• Correct file missing issue causing setup failure