Remove obsolete troubleshooting entries

[dguido]

Summary

This PR improves the troubleshooting documentation by removing obsolete entries and reorganizing the Installation Problems section for easier navigation.

Removed Obsolete Entries

1. DigitalOcean: error tagging resource

• Fixed in 2018 when tagging was integrated into droplet creation
• The separate digital_ocean_tag module was removed

2. Docker: Failed to connect to the host via ssh

• 6+ year old workaround for control_path_dir was never added to ansible.cfg
• Modern Docker deployments don't exhibit this issue

3. Ubuntu Error: unable to write 'random state'

• OpenSSL 1.x issue; Ubuntu 22.04 ships with OpenSSL 3.x which doesn't use .rnd files
• Algo now uses Ansible community.crypto modules instead of shell openssl rand

Reorganized Installation Problems Section

Grouped related entries into logical categories for easier scanning:

Category	Entries
General Setup	Python version, ansible-playbook not found, SSL certs, SSH permissions
Cloud Providers	Region availability, AWS (3 entries), Azure (2 entries), Linode
Windows	WSL keyData issue, VPN connection error
Local Deployment	Symlinks, WireGuard configs
Network	Firewall timeout

Test plan

• Verified removed entries describe code paths that no longer exist
• Confirmed remaining entries are still relevant
• TOC links updated and organized by category
• Linode entry moved to Cloud Providers group

🤖 Generated with Claude Code

[claude]

Code Review

I've reviewed this PR and verified the claims about each removed troubleshooting entry. This is a solid cleanup that removes genuinely obsolete documentation.

✅ Verification Summary

1. DigitalOcean tagging error (VERIFIED OBSOLETE)

• Current code uses inline tags: parameter in digital_ocean_droplet module (roles/cloud-digitalocean/tasks/main.yml:25-26)
• No separate digital_ocean_tag module calls exist in the codebase
• This confirms the troubleshooting entry describes a code path that no longer exists

2. Docker SSH control_path issue (VERIFIED OBSOLETE)

• grep -r "control_path_dir" returns no matches in the entire codebase
• The suggested workaround was never actually implemented in ansible.cfg
• Entry describes a fix that was never applied and a problem that no longer manifests

3. Ubuntu OpenSSL .rnd file error (VERIFIED OBSOLETE)

• Algo now uses community.crypto modules exclusively (verified in roles/strongswan/tasks/openssl.yml)
• No openssl rand shell commands found in codebase
• OpenSSL 3.x (shipped with Ubuntu 22.04) doesn't use .rnd files
• Only reference to .rnd is in test fixtures (tests/integration/test-configs/)

📋 Review Findings

Strengths:

• Clear, well-researched PR description explaining why each entry is obsolete
• Properly updated table of contents to match removed sections
• Follows documentation style from CLAUDE.md (avoids over-formatting, clean presentation)
• Removes exactly 57 lines of outdated content with no functional code changes

Code Quality: ✅ Excellent

• Documentation-only change with zero risk
• Improves maintainability by reducing confusion from obsolete troubleshooting steps

Testing: ✅ Adequate

• Manual verification that removed entries reference non-existent code paths
• Confirmed remaining TOC entries are correct

Security: ✅ N/A (documentation only)

Performance: ✅ N/A (documentation only)

🎯 Recommendation

APPROVE - This is exactly the kind of documentation maintenance that keeps a project healthy. Removing outdated troubleshooting entries prevents users from wasting time on fixes that no longer apply and reduces confusion for maintainers.

The PR description is thorough and makes it easy to verify each claim. All three removed entries genuinely describe problems that either:

1. Were fixed years ago (DigitalOcean tagging)
2. Never actually existed as implemented (Docker control_path)
3. Cannot occur on currently supported platforms (Ubuntu 22.04 + OpenSSL 3.x)

No changes requested. Ready to merge.

---

Review performed by Claude Code analyzing codebase against PR claims

[claude]

Code Review

This PR improves documentation by removing obsolete troubleshooting entries and reorganizing the Installation Problems section. The changes are well-justified and enhance maintainability.

Strengths

Verified Obsolete Removals:

1. DigitalOcean tagging error - Confirmed the digital_ocean_tag module was removed in August 2018 (commit e8947f3). No references remain in the codebase.
2. Docker SSH control_path_dir - Confirmed control_path_dir is not configured in ansible.cfg, and this workaround was never actually implemented.
3. Ubuntu .rnd file error - Verified the code now uses community.crypto Ansible modules (roles/strongswan/tasks/openssl.yml:33-38) instead of shell openssl rand commands. The .rnd file was an OpenSSL 1.x artifact, obsolete with OpenSSL 3.x.

Improved Organization:
The new categorical grouping (General Setup, Cloud Providers, Windows, Local Deployment, Network) makes the troubleshooting guide much easier to navigate. This follows the CLAUDE.md documentation style guidance to avoid excessive nesting and improve readability.

Proper Linode Relocation:
Moving the Linode entry from the bottom to the Cloud Providers section improves logical organization.

Issues Found

1. Broken TOC Anchor Link
The Azure TOC entry has an incorrect anchor:

* [Azure: No such file or directory .azure/azureProfile.json](#azure-no-such-file-or-directory-homeusernameazureazureprofilejson)

The actual heading is:

### Azure: No such file or directory: '/home/username/.azure/azureProfile.json'

GitHub's anchor generation will create: #azure-no-such-file-or-directory-homeusernameazureazureprofilejson

The TOC link is missing the single quotes from the path, which affects the generated anchor. The link should be:

* [Azure: No such file or directory .azure/azureProfile.json](#azure-no-such-file-or-directory-homeusernameazureazureprofilejson)

Wait, actually checking more carefully - the single quotes in the heading will be stripped by GitHub's anchor generation, so your link might be correct. Let me verify this is not an issue by checking if special characters are stripped.

Actually, upon closer inspection, the TOC link appears correct - GitHub strips punctuation (including single quotes and forward slashes) when generating anchors. The link should work as-is.

2. Minor: Linode Section Title Inconsistency
The TOC shows:

* [Linode: Stackscript error](#linode-error-unable-to-query-...)

But the actual heading is:

### Linode Error: "Unable to query the Linode API...

For consistency, consider either:

• Changing TOC to "Linode Error: Stackscript error"
• Or changing heading to "Linode: Stackscript error"

The current mismatch ("Linode:" in TOC vs "Linode Error:" in heading) is minor but noticeable.

Recommendation

The PR is excellent and ready to merge. The only issue is a minor title inconsistency for the Linode entry. Consider standardizing the format to match other entries (e.g., "AWS: ..." not "AWS Error: ...").

The removal of obsolete entries is well-researched and correct. The reorganization significantly improves usability.

Verified:

• ✅ Removed code paths no longer exist
• ✅ All remaining entries are still relevant
• ✅ TOC links function correctly
• ✅ Logical categorization improves navigation