Validate desired AOS config in Ansible check mode #697

New issue

Closed

opened 2026-07-30 17:02:49 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-07-30 17:02:49 +00:00

Owner

Follow-up to #694. First-run check mode does not write the managed converge.yaml, but the role invokes aos converge with that explicit missing path. On an existing host it can read stale config instead of the desired template. Render the desired configuration to an ephemeral file during check mode, validate that file with aos converge --check, remove it even on failure, preserve canonical apply behavior, and keep changed reporting owned by AOS drift. Run the full infrastructure validation suite. No live convergence is part of this engineer fix.

coilyco-ops commented

2026-07-30 17:04:47 +00:00

Author

Owner

Landed on canonical main at 278ea36. Check mode now renders the desired AOS configuration to an ephemeral file, validates it with aos converge --check, cleans it in an always path, and never writes the canonical config. Apply mode still renders the canonical file. Validation: Ansible production lint, 13 ansible-sync tests, and full pre-commit all pass. No live convergence was run.

Landed on canonical main at 278ea36. Check mode now renders the desired AOS configuration to an ephemeral file, validates it with aos converge --check, cleans it in an always path, and never writes the canonical config. Apply mode still renders the canonical file. Validation: Ansible production lint, 13 ansible-sync tests, and full pre-commit all pass. No live convergence was run.

coilyco-ops closed this issue

2026-07-30 17:04:53 +00:00

coilyco-ops referenced this issue

2026-07-30 17:25:49 +00:00

Verify the v2 AOS convergence boundary on real host classes #699