handle_adws_recovery
Resolve Active Directory Web Services (ADWS) errors that cause deployment stalls by checking logs, waiting for service initialization, and optionally retrying failed tasks.
Instructions
Handle Active Directory Web Services (ADWS) recovery for stuck deployments.
ADWS errors are common during Active Directory deployments. This tool:
Checks if deployment is stuck on ADWS errors
Waits for ADWS to start (default: 10 minutes)
Optionally retries the failed tasks automatically
When to use:
Deployment failed with "Unable to find a default server with Active Directory Web Services running"
Deployment is stuck on OU configuration tasks
DC VM is deployed but AD services haven't fully started
What this does:
Checks deployment logs for ADWS errors
Waits for ADWS to initialize (5-15 minutes typical)
Retries failed Ansible tasks (if auto_retry=True)
Provides status updates during wait
Args: wait_minutes: Minutes to wait for ADWS to start (default: 10, max: 30) auto_retry: Automatically retry failed tasks after wait (default: True) user_id: Optional user ID (admin only)
Returns: Recovery result with status and next steps
Example: # Handle ADWS recovery with auto-retry result = await handle_adws_recovery(wait_minutes=10, auto_retry=True)
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| wait_minutes | No | ||
| auto_retry | No | ||
| user_id | No |