# Pitfall Log / 踩坑日志

项目：ansible/ansible

摘要：发现 29 个潜在踩坑项，其中 4 个为 high/blocking；最高优先级：安装坑 - 来源证据：powershell exec_wrapper fails when multiple powershell.exe entries are found in PATH。

## 1. 安装坑 · 来源证据：powershell exec_wrapper fails when multiple powershell.exe entries are found in PATH

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：powershell exec_wrapper fails when multiple powershell.exe entries are found in PATH
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/ansible/ansible/issues/87228 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 2. 配置坑 · 来源证据：ansible.builtin.copy module - updates pre-existing files' ownership of dest directory if remote_src: true

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：ansible.builtin.copy module - updates pre-existing files' ownership of dest directory if remote_src: true
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/ansible/ansible/issues/79725 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 3. 配置坑 · 来源证据：getent returns misleading error when service override fails due to platform limitations on Alpine

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：getent returns misleading error when service override fails due to platform limitations on Alpine
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/ansible/ansible/issues/85568 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 4. 安全/权限坑 · 来源证据：argument_specs with list of str accept integer in it

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：argument_specs with list of str accept integer in it
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/ansible/ansible/issues/87217 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 5. 安装坑 · 失败模式：installation: btrfs scrub status doesn't update via ansible

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: btrfs scrub status doesn't update via ansible
- 对用户的影响：Developers may fail before the first successful local run: btrfs scrub status doesn't update via ansible
- 证据：failure_mode_cluster:github_issue | https://github.com/ansible/ansible/issues/87213 | btrfs scrub status doesn't update via ansible

## 6. 安装坑 · 来源证据：btrfs scrub status doesn't update via ansible

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：btrfs scrub status doesn't update via ansible
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/ansible/ansible/issues/87213 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 7. 配置坑 · 失败模式：configuration: Action plugin: how to execute module with check mode unset?

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: Action plugin: how to execute module with check mode unset?
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: Action plugin: how to execute module with check mode unset?
- 证据：failure_mode_cluster:github_issue | https://github.com/ansible/ansible/issues/87071 | Action plugin: how to execute module with check mode unset?

## 8. 配置坑 · 失败模式：configuration: [regression] PowerShell v5 support broke with ansible-core 2.21

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: [regression] PowerShell v5 support broke with ansible-core 2.21
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: [regression] PowerShell v5 support broke with ansible-core 2.21
- 证据：failure_mode_cluster:github_issue | https://github.com/ansible/ansible/issues/87147 | [regression] PowerShell v5 support broke with ansible-core 2.21

## 9. 配置坑 · 失败模式：configuration: argument_specs with list of str accept integer in it

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: argument_specs with list of str accept integer in it
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: argument_specs with list of str accept integer in it
- 证据：failure_mode_cluster:github_issue | https://github.com/ansible/ansible/issues/87217 | argument_specs with list of str accept integer in it

## 10. 配置坑 · 失败模式：configuration: getent returns misleading error when service override fails due to platform limitations on Al...

- 严重度：medium
- 证据强度：source_linked
- 发现：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
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: getent returns misleading error when service override fails due to platform limitations on Alpine
- 证据：failure_mode_cluster:github_issue | https://github.com/ansible/ansible/issues/85568 | getent returns misleading error when service override fails due to platform limitations on Alpine

## 11. 配置坑 · 来源证据：[regression] PowerShell v5 support broke with ansible-core 2.21

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：[regression] PowerShell v5 support broke with ansible-core 2.21
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/ansible/ansible/issues/87147 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 12. 能力坑 · 能力判断依赖假设

- 严重度：medium
- 证据强度：source_linked
- 发现：README/documentation is current enough for a first validation pass.
- 对用户的影响：假设不成立时，用户拿不到承诺的能力。
- 证据：capability.assumptions | https://github.com/ansible/ansible | README/documentation is current enough for a first validation pass.

## 13. 运行坑 · 运行可能依赖外部服务

- 严重度：medium
- 证据强度：source_linked
- 发现：项目说明出现 external service/cloud/webhook/database 等运行依赖关键词。
- 对用户的影响：本地安装成功不等于能力可用，外部服务不可用会阻断体验。
- 证据：packet_text.keyword_scan | https://github.com/ansible/ansible | matched external service / cloud / webhook / database keyword

## 14. 维护坑 · 维护活跃度未知

- 严重度：medium
- 证据强度：source_linked
- 发现：未记录 last_activity_observed。
- 对用户的影响：新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。
- 证据：evidence.maintainer_signals | https://github.com/ansible/ansible | last_activity_observed missing

- 严重度：medium
- 证据强度：source_linked
- 发现：no_demo
- 证据：downstream_validation.risk_items | https://github.com/ansible/ansible | no_demo; severity=medium

## 16. 安全/权限坑 · 存在评分风险

- 严重度：medium
- 证据强度：source_linked
- 发现：no_demo
- 对用户的影响：风险会影响是否适合普通用户安装。
- 证据：risks.scoring_risks | https://github.com/ansible/ansible | no_demo; severity=medium

## 17. 安全/权限坑 · 来源证据：Workers crash with SIGABRT on macOS 26+ when AWS / boto3-using plugins are in use

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Workers crash with SIGABRT on macOS 26+ when AWS / boto3-using plugins are in use
- 对用户的影响：可能阻塞安装或首次运行。
- 证据：community_evidence:github | https://github.com/ansible/ansible/issues/87125 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 18. 维护坑 · issue/PR 响应质量未知

- 严重度：low
- 证据强度：source_linked
- 发现：issue_or_pr_quality=unknown。
- 对用户的影响：用户无法判断遇到问题后是否有人维护。
- 证据：evidence.maintainer_signals | https://github.com/ansible/ansible | issue_or_pr_quality=unknown

## 19. 维护坑 · 发布节奏不明确

- 严重度：low
- 证据强度：source_linked
- 发现：release_recency=unknown。
- 对用户的影响：安装命令和文档可能落后于代码，用户踩坑概率升高。
- 证据：evidence.maintainer_signals | https://github.com/ansible/ansible | release_recency=unknown

## 20. 维护坑 · 失败模式：maintenance: v2.16.19

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v2.16.19
- 对用户的影响：Upgrade or migration may change expected behavior: v2.16.19
- 证据：failure_mode_cluster:github_release | https://github.com/ansible/ansible/releases/tag/v2.16.19 | v2.16.19

## 21. 维护坑 · 失败模式：maintenance: v2.16.19rc1

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v2.16.19rc1
- 对用户的影响：Upgrade or migration may change expected behavior: v2.16.19rc1
- 证据：failure_mode_cluster:github_release | https://github.com/ansible/ansible/releases/tag/v2.16.19rc1 | v2.16.19rc1

## 22. 维护坑 · 失败模式：maintenance: v2.18.18

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v2.18.18
- 对用户的影响：Upgrade or migration may change expected behavior: v2.18.18
- 证据：failure_mode_cluster:github_release | https://github.com/ansible/ansible/releases/tag/v2.18.18 | v2.18.18

## 23. 维护坑 · 失败模式：maintenance: v2.18.18rc1

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v2.18.18rc1
- 对用户的影响：Upgrade or migration may change expected behavior: v2.18.18rc1
- 证据：failure_mode_cluster:github_release | https://github.com/ansible/ansible/releases/tag/v2.18.18rc1 | v2.18.18rc1

## 24. 维护坑 · 失败模式：maintenance: v2.19.11

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v2.19.11
- 对用户的影响：Upgrade or migration may change expected behavior: v2.19.11
- 证据：failure_mode_cluster:github_release | https://github.com/ansible/ansible/releases/tag/v2.19.11 | v2.19.11

## 25. 维护坑 · 失败模式：maintenance: v2.19.11rc1

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v2.19.11rc1
- 对用户的影响：Upgrade or migration may change expected behavior: v2.19.11rc1
- 证据：failure_mode_cluster:github_release | https://github.com/ansible/ansible/releases/tag/v2.19.11rc1 | v2.19.11rc1

## 26. 维护坑 · 失败模式：maintenance: v2.20.7

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v2.20.7
- 对用户的影响：Upgrade or migration may change expected behavior: v2.20.7
- 证据：failure_mode_cluster:github_release | https://github.com/ansible/ansible/releases/tag/v2.20.7 | v2.20.7

## 27. 维护坑 · 失败模式：maintenance: v2.20.7rc1

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v2.20.7rc1
- 对用户的影响：Upgrade or migration may change expected behavior: v2.20.7rc1
- 证据：failure_mode_cluster:github_release | https://github.com/ansible/ansible/releases/tag/v2.20.7rc1 | v2.20.7rc1

## 28. 维护坑 · 失败模式：maintenance: v2.21.1

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v2.21.1
- 对用户的影响：Upgrade or migration may change expected behavior: v2.21.1
- 证据：failure_mode_cluster:github_release | https://github.com/ansible/ansible/releases/tag/v2.21.1 | v2.21.1

## 29. 维护坑 · 失败模式：maintenance: v2.21.1rc1

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v2.21.1rc1
- 对用户的影响：Upgrade or migration may change expected behavior: v2.21.1rc1
- 证据：failure_mode_cluster:github_release | https://github.com/ansible/ansible/releases/tag/v2.21.1rc1 | v2.21.1rc1