Update automation guide defaults so cmc-migrateops-compute-migration includes --set_static_ip_dest by default unless explicitly overridden. Clarify vmware-specific default as vm_platforms selection, and record the behavior change in run learnings for future runs.
Update ATVM run workflow rules to remove the default pre-run approval gate for automation requests while keeping safety checks around live running-state and spec verification. Set watcher-backed execution as the default unless explicitly overridden and require post-execution reporting of the exact template and runner commands used. Record the workflow shift in automation run learnings with a dated entry for future consistency.
Handle dict-shaped reporter events when deriving watcher host failures.
- parse reporter JSON events with type/message/severity fields
- preserve existing support for list-shaped event records
- record the false-PASS failure mode in ATVM automation run learnings
Execute the template step before starting watcher-backed ATVM runs.
- run --template-command synchronously in start-atvm-run.sh
- write template output to /tmp/<build>.launch.log
- stop before watcher/runner startup if template generation fails
- document the corrected wrapper behavior in watcher-service docs
- record the stale specPattern failure mode in automation run learnings
Update the ATVM git instructions so controller-repo git drafting and the SSH-prefixed push example only apply when the operator explicitly asks for the e2e cypress repo or a close variation.
Align AGENTS.md with git-guide.md so generic ATVM git requests no longer assume the controller repo by default.
Add an AGENTS.md rule for vCenter VM snapshot requests so snapshot names default to the format using the local America/New_York timezone unless the operator requests a different name.
Update the ATVM git guide so push examples do not hardcode origin/main.
Prefer the operator-specified remote and branch when provided, and otherwise draft a generic SSH-prefixed git push command or use the remote/branch already established in context.
Add a dedicated ESX VM guide for read-first hardware change workflows,
including disk creation, datastore VMDK attachment, and PCI passthrough
assignment.
Update the existing lookup/assignment runbook and top-level docs to
reference the new guide and require explicit reporting of VM name
mismatches and missing datastore directories before any change.
Prefer failing and terminal host results when merging supplemental
subrun artifacts so a later partial artifact cannot overwrite a more
authoritative outcome.
Also point ATVM agent guidance at the ATVM-specific git guide and add
that guide to document draft-only commit handling and the default SSH
command pattern.
require categorized PASS results to be confirmed from the child run log or Cloud Run Finished summary
forbid treating watcher host_results, grouped XML, or check-xml-files.ts alone as proof of PASS
record the 2026-04-24 false-PASS incident as a run learning
Handle Currents "Cloud Run Finished" table rows where the trailing
"s" in long duration values wraps onto its own continuation line.
Instead of appending that standalone continuation to the end of the
host row, drop the wrapped row and rely on the existing duration
parser to accept values without the trailing "s". This preserves all
host rows in parent summary parsing for completed non-categorized runs.
Also record the failure mode and recovery guidance in the ATVM run
learnings doc.
Add a small monitoring helper script for logging CPU and memory usage
for mtdi-daemon and galaxy-migrate.
Also update the cdssync workspace instructions to document how to use
the monitoring helper.
Add bulk data generation controls for folder count, files per folder,
file size range, and bulk dataset size limits.
Also update the cdssync docs to describe the new options and how
update mode applies to generated bulk files.
Add support for running content updates against an existing migration
test dataset without recreating the filesystem structure.
Also make ACL/xattr updates non-fatal on filesystems that do not
support those operations.
Add optional interval-based random content updates to the cdssync
migration test dataset generator and document the new behavior.
This allows the dataset to be created once and then updated either
continuously or every N seconds while preserving the intended
special-case file structure.
Add the cdssync migration test dataset manifest, generator script,
workspace instructions, and gitignore.
This sets the default workflow to:
- generate the dataset locally
- copy it to the test machine with metadata preserved
- verify the copied data before migration testing
Teach generated-spec TEST FLOW parsing to honor test-install-only runtime gates, including single-quoted Cypress.env checks, and suppress plugin branches when install-only mode disables them.
Document the 2026-04-16 install-only flow mismatch so future watcher updates keep Mattermost TEST FLOW aligned with the actual generated spec path.
Tighten `Cloud Run Finished` parsing so categorized watcher recovery only starts on real summary headers, stops at the grouped run's `Recorded Run` URL, and parses only actual summary-table host rows.
Also merge grouped per-host reporter artifacts into categorized recovery so completed grouped batches keep the correct host membership and Mattermost posts remain stable for both categorized and non-categorized runs.
Add the working vCenter placement-check pattern to the ATVM automation guide so explicit VM-list planning uses the correct lowercase govc JSON keys, resolves datastore refs to names, and ignores helper datastores such as install ISO attachments when deciding between gold and gold-2.
Adjust parent-run summary parsing so the watcher does not stop at the "Recorded Run" detection log line and miss later host rows in Mattermost status output.
Document the 2026-04-15 failure mode in ATVM run learnings so future watcher/reporting work preserves the broader Cloud Run Finished block parsing rule.
- skip report artifacts that disappear during watcher post-processing
- use safe mtime handling for XML and mochawesome discovery
- prevent watcher crashes from transient FileNotFoundError races
- map AutomatedTest-VMBootImg-Gold to gold and Gold-2 to gold-2
- require live vCenter placement checks for explicit VM lists
- stop mixed gold/gold-2 requests before planning ATVM runs
- return hostname-only datastore inventories by default
- tell the operator about the vCenter placement check before showing run commands
- clarify that repo inventory files are not the source of truth for current datastore membership
Remove the old issue-handling defaults and approval rules that referred
to the galaxy-complete workspace.
Keep the remaining commit approval and repository safety guidance.
