Repository navigation
Complete deferred bundle validation and reliability work #5124
Description
Complete the validation and reliability work outside the changes selected for main in #5119.
PR arrangement
Keep the ten existing implementation PRs as drafts. The selected changes in #5119 are now merged through #5252, #5253, #5254 and #5255.
When this work resumes, rebase the drafts onto main, recheck their dependencies and versions, and review each bundle topic separately.
The drafts retain unfinished implementation. Their existing reviews and tests do not establish readiness against the updated base.
Reuse the existing issues and their evidence. Keep deferred implementation PRs as drafts until work resumes.
| Area | Parent or issue | Remaining work |
|---|---|---|
| Bundle and functional coverage | Individual bundle issues below | Unfinished bundle cases, broader functional checks, service inventories, actions and upgrades. The selected Linux lifecycle has passed. Its broader checks remain open. |
| Backups | #5135 | Registration failures, cleanup, restore and retention, including #5054. |
| SQL operation polling | #5202 | Investigate the earlier HTTP 500. Passing later SQL tests did not establish its cause. |
| Pipeline recovery | #5236 | Dispatch, message redelivery, session-lock loss and overlapping worker updates. |
| Previous-version upgrades | #5128 | Implement and run the legacy Porter regression case. |
| Airlock submitted-file integrity | #5264 | Compare file contents through submission, review and approval. Check that old draft-SAS operations cannot alter the accepted copy. |
| Airlock migration | #5129 | Implement and validate data-preserving legacy-to-v2 migration after upgrade checks. |
| Deployment automation | Follow-up planning | Align AzureTRE-Deployment CI after the selected repository work and deferred coverage are complete. No upstream implementation PR is selected here. |
Deferred implementation PRs: PR #5195, PR #5210, PR #5212, PR #5214, PR #5216, PR #5217, PR #5219, PR #5220, PR #5222, PR #5223.
Completion steps
- Preserve the existing failure records, PR links and test evidence when moving issues.
- Resume individual bundle work with explicit prerequisites, functional checks and terminal cleanup.
- Keep backup registration, cleanup, restore and retention results separate.
- Complete previous-version upgrades before legacy Airlock migration.
- Close each child issue only when its own acceptance criteria are met.
The merged fixes associated with #5119 support this work. Their passing tests do not prove the remaining cases.
Completed Linux validation
Linux lifecycle validation passed at test revision fed265a, using deployed runtime 1cec703. The Linux case and all 23 smoke tests passed.
TRE API checks confirmed deletion of the VM and its test-created prerequisites. No separate Azure Resource Manager inventory or interactive access check was captured.
#5145 remains open for interactive access, other supported actions, VM sizes and previous-version upgrades.
Deferred bundle records
| Category | Issues |
|---|---|
| Workspace services | #5137, #5140, #5141, #5147, #5148, #5149, #5150 |
| User resources | #5138, #5143, #5145 |
| Shared services | #5159, #5160 |
Additional behaviour from selected bundles
The 13 source issues below are closed for their selected validation scope and retain that evidence. The additional tasks in this table remain unfinished and are tracked here.
| Source issue | Deferred task |
|---|---|
| #5139 | Add cross-subscription and previous-version upgrade evidence if those paths enter the accepted scope. |
| #5142 | Validate any independent Guacamole lifecycle claims with an explicit selection. |
| #5142 | Add interactive session, access-control and previous-version upgrade evidence. |
| #5144 | Add interactive desktop access, start/stop, password reset, denied/rejected flows and previous-version upgrade evidence separately. |
| #5146 | Run dedicated action and interactive-access checks where required. |
| #5146 | Verify optional tool installation and previous-version upgrades separately. |
| #5151 | Add independent workspace isolation, custom-action and previous-version upgrade evidence where required. |
| #5152 | Add network isolation, storage access, custom actions and older-version upgrades separately. Backups remain in #5135. |
| #5153 | Add functional network, access-control and previous-version upgrade checks separately. |
| #5156 | Add interactive administration, access-control and previous-version upgrade evidence separately. |
| #5157 | Add end-to-end mail delivery and previous-version upgrade evidence. |
| #5158 | Verify expiring-certificate renewal and previous-version upgrades separately. |
| #5161 | Add functional allowed/denied traffic and previous-version upgrade evidence where required. |
| #5162 | Add repository operations, access-control and previous-version upgrade checks. |
| #5163 | Add package upload/download, proxy behaviour, access-control and older-version upgrade evidence. |
Coverage requirements carried forward
- Complete failed and unrun service cases with functional assertions in each bundle issue. Prerequisite deployment alone does not establish service coverage.
- Run deferred user-resource cases with the required identity, prerequisites and resource ownership.
- Record API deletion and physical resource removal separately. Recovery cleanup does not prove that automatic deletion passed.
- Complete application use and older-version upgrade checks for deferred shared services.
- Keep broader AAD role, denial and tenant-boundary checks separate from the selected AAD case.
Common selection, inventory, consent, timeout and cleanup fixes remain in #5119. Post-merge command routing is tracked there.
Superseded tracking records
#5126, #5127, #5154. Their evidence and discussions remain available.
Sub-issues: #5128, #5129, #5135, #5137, #5138, #5140, #5141, #5143, #5145, #5147, #5148, #5149, #5150, #5159, #5160, #5202, #5236, #5264.
Activity
17 remaining items