# Pitfall Log

Project: ansible/ansible

Summary: Found 29 structured pitfall item(s), including 4 high/blocking item(s). Top priority: Installation risk - Installation risk requires verification.

## 1. Installation risk - Installation risk requires verification

- Severity: high
- Evidence strength: source_linked
- Finding: Project evidence flags a installation risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/ansible/ansible/issues/87228

## 2. Configuration risk - Configuration risk requires verification

- Severity: high
- Evidence strength: source_linked
- Finding: Project evidence flags a configuration risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/ansible/ansible/issues/79725

## 3. Configuration risk - Configuration risk requires verification

- Severity: high
- Evidence strength: source_linked
- Finding: Project evidence flags a configuration risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/ansible/ansible/issues/85568

## 4. Security or permission risk - Security or permission risk requires verification

- Severity: high
- Evidence strength: source_linked
- Finding: Project evidence flags a security or permission risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/ansible/ansible/issues/87217

## 5. Installation risk - Installation risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Developers should check this installation risk before relying on the project: btrfs scrub status doesn't update via ansible
- User impact: Developers may fail before the first successful local run: btrfs scrub status doesn't update via ansible
- Evidence: failure_mode_cluster:github_issue | https://github.com/ansible/ansible/issues/87213

## 6. Installation risk - Installation risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Project evidence flags a installation risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/ansible/ansible/issues/87213

## 7. Configuration risk - Configuration risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Developers should check this configuration risk before relying on the project: Action plugin: how to execute module with check mode unset?
- User impact: Developers may misconfigure credentials, environment, or host setup: Action plugin: how to execute module with check mode unset?
- Evidence: failure_mode_cluster:github_issue | https://github.com/ansible/ansible/issues/87071

## 8. Configuration risk - Configuration risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Developers should check this configuration risk before relying on the project: [regression] PowerShell v5 support broke with ansible-core 2.21
- User impact: Developers may misconfigure credentials, environment, or host setup: [regression] PowerShell v5 support broke with ansible-core 2.21
- Evidence: failure_mode_cluster:github_issue | https://github.com/ansible/ansible/issues/87147

## 9. Configuration risk - Configuration risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Developers should check this configuration risk before relying on the project: argument_specs with list of str accept integer in it
- User impact: Developers may misconfigure credentials, environment, or host setup: argument_specs with list of str accept integer in it
- Evidence: failure_mode_cluster:github_issue | https://github.com/ansible/ansible/issues/87217

## 10. Configuration risk - Configuration risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Developers should check this configuration risk before relying on the project: getent returns misleading error when service override fails due to platform limitations on Alpine
- User impact: Developers may misconfigure credentials, environment, or host setup: getent returns misleading error when service override fails due to platform limitations on Alpine
- Evidence: failure_mode_cluster:github_issue | https://github.com/ansible/ansible/issues/85568

## 11. Configuration risk - Configuration risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Project evidence flags a configuration risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/ansible/ansible/issues/87147

## 12. Capability evidence risk - Capability evidence risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: README/documentation is current enough for a first validation pass.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: capability.assumptions | https://github.com/ansible/ansible

## 13. Runtime risk - Runtime risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Project evidence flags a runtime risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: packet_text.keyword_scan | https://github.com/ansible/ansible

## 14. Maintenance risk - Maintenance risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Project evidence flags a maintenance risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/ansible/ansible

## 15. Security or permission risk - Security or permission risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: no_demo
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: downstream_validation.risk_items | https://github.com/ansible/ansible

## 16. Security or permission risk - Security or permission risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: no_demo
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: risks.scoring_risks | https://github.com/ansible/ansible

## 17. Security or permission risk - Security or permission risk requires verification

- Severity: medium
- Evidence strength: source_linked
- Finding: Project evidence flags a security or permission risk. Review the linked source before relying on this workflow.
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: community_evidence:github | https://github.com/ansible/ansible/issues/87125

## 18. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: issue_or_pr_quality=unknown。
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/ansible/ansible

## 19. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: release_recency=unknown。
- User impact: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://github.com/ansible/ansible

## 20. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: v2.16.19
- User impact: Upgrade or migration may change expected behavior: v2.16.19
- Evidence: failure_mode_cluster:github_release | https://github.com/ansible/ansible/releases/tag/v2.16.19

## 21. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: v2.16.19rc1
- User impact: Upgrade or migration may change expected behavior: v2.16.19rc1
- Evidence: failure_mode_cluster:github_release | https://github.com/ansible/ansible/releases/tag/v2.16.19rc1

## 22. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: v2.18.18
- User impact: Upgrade or migration may change expected behavior: v2.18.18
- Evidence: failure_mode_cluster:github_release | https://github.com/ansible/ansible/releases/tag/v2.18.18

## 23. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: v2.18.18rc1
- User impact: Upgrade or migration may change expected behavior: v2.18.18rc1
- Evidence: failure_mode_cluster:github_release | https://github.com/ansible/ansible/releases/tag/v2.18.18rc1

## 24. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: v2.19.11
- User impact: Upgrade or migration may change expected behavior: v2.19.11
- Evidence: failure_mode_cluster:github_release | https://github.com/ansible/ansible/releases/tag/v2.19.11

## 25. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: v2.19.11rc1
- User impact: Upgrade or migration may change expected behavior: v2.19.11rc1
- Evidence: failure_mode_cluster:github_release | https://github.com/ansible/ansible/releases/tag/v2.19.11rc1

## 26. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: v2.20.7
- User impact: Upgrade or migration may change expected behavior: v2.20.7
- Evidence: failure_mode_cluster:github_release | https://github.com/ansible/ansible/releases/tag/v2.20.7

## 27. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: v2.20.7rc1
- User impact: Upgrade or migration may change expected behavior: v2.20.7rc1
- Evidence: failure_mode_cluster:github_release | https://github.com/ansible/ansible/releases/tag/v2.20.7rc1

## 28. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: v2.21.1
- User impact: Upgrade or migration may change expected behavior: v2.21.1
- Evidence: failure_mode_cluster:github_release | https://github.com/ansible/ansible/releases/tag/v2.21.1

## 29. Maintenance risk - Maintenance risk requires verification

- Severity: low
- Evidence strength: source_linked
- Finding: Developers should check this maintenance risk before relying on the project: v2.21.1rc1
- User impact: Upgrade or migration may change expected behavior: v2.21.1rc1
- Evidence: failure_mode_cluster:github_release | https://github.com/ansible/ansible/releases/tag/v2.21.1rc1