Skip to content

e2e: add daily devnet QA test for device provisioning#2832

Open
martinsander00 wants to merge 2 commits intomainfrom
ms/2755
Open

e2e: add daily devnet QA test for device provisioning#2832
martinsander00 wants to merge 2 commits intomainfrom
ms/2755

Conversation

@martinsander00
Copy link
Contributor

@martinsander00 martinsander00 commented Feb 5, 2026

Resolves: #2755

Summary

  • Add QA test that exercises the full device provisioning lifecycle as defined in RFC12
  • Test deletes and recreates a device and its links, triggering new pubkey assignment via PDA
  • Runs Ansible playbooks to restart both doublezero-agent and doublezero-telemetry daemons
  • Next day's run validates provisioning succeeded by checking device health/status
  • Command-line flags (-device, -bm-host) allow future use on testnet and mainnet-beta

Testing Verification

  • Manual testing will be done when GitHub workflow is added to infra repo
  • Test is designed to be run daily; each run validates previous day's provisioning

@martinsander00 martinsander00 force-pushed the ms/2755 branch 3 times, most recently from aefd876 to e24b64b Compare February 6, 2026 02:41
Add a QA test that exercises the full device provisioning lifecycle as
defined in RFC12. The test:

1. Verifies device is healthy (validates previous day's provisioning)
2. Deletes device and links from the ledger
3. Recreates device and links (gets new pubkey via PDA)
4. Creates required interfaces (Loopback255, Loopback256)
5. Runs Ansible to restart doublezero-agent and doublezero-telemetry
6. Verifies device was recreated with new pubkey

The next day's run validates provisioning succeeded by checking
health=ready-for-users and status=activated.

Command-line flags (-device, -bm-host) allow future use on testnet
and mainnet-beta environments.

Resolves: #2755
Add a QA test that exercises the full device provisioning lifecycle as
defined in RFC12. The test:

1. Verifies device is healthy (validates previous day's provisioning)
2. Deletes device and links from the ledger
3. Recreates device and links (gets new pubkey via PDA)
4. Creates required interfaces (Loopback255, Loopback256)
5. Runs Ansible to restart doublezero-agent and doublezero-telemetry
6. Verifies device was recreated with new pubkey

The next day's run validates provisioning succeeded by checking
health=ready-for-users and status=activated.

Command-line flags (-device, -bm-host) allow future use on testnet
and mainnet-beta environments.

Resolves: #2755
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

e2e: add a daily devnet QA test that exercises the provisioning process

2 participants