Remove ansible.nodejs.org
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 35/100
- issue の種類
- リファクタリング
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- ansible, docker, docker-compose
- 領域
- cloud, devops, infrastructure, security
調査の方向性
Start by reviewing ansible/inventory.yml, the ~/.ssh/config conventions, and the secrets repository for references to ansible.nodejs.org, infra-ibm-ubuntu2004-x64-1, and awx_password. Confirm that no credentials, scheduled jobs, webhooks, or workflows depend on the AWX host, then coordinate decommissioning the host and removing its DNS and Cloudflare configuration. Done means the host and related references are safely removed and exclusive credentials are rotated.
索引モデルが issue の本文から書いたものです。
説明
Summary
ansible.nodejs.org (IBM host infra-ibm-ubuntu2004-x64-1, 169.60.150.91) is an unmanaged, unwatched AWX (open-source Ansible Tower) instance that has been effectively dead for years and should be decommissioned rather than repaired.
What's running there
- AWX 17.1.0 (
ansible/awx:17.1.0), deployed via docker-compose, containers created ~5 years ago. awx_web,awx_task,awx_rediscontainers, plusawx_postgres.- No nginx/reverse proxy — the AWX web container binds host ports 80/443 directly.
Key detail: it's been idle for years, then crashed
The last time this AWX instance did anything at all was around 2023-09-29 (a project sync attempt), and the last time there's evidence of actually running a job against current code was back when the checkout was at the Feb 2022 commit. Either way, it's been sitting completely idle for roughly 2.5+ years before postgres even died in Dec 2025 — the disk-full crash-loop just finished off something that was already effectively unused.
Supporting evidence:
awx_postgreshas been crash-looping since 2025-12-29 (no space left on device, 605+ restart attempts logged), because the host's root disk is 100% full (99G/99G).- The AWX-synced checkout of
nodejs/buildunder/var/lib/awx/projectsis pinned at commit472b2953("Update README.md", #2874, merged 2022-02-21). - The project's
.git/FETCH_HEAD(updated on each pre-job sync) has an mtime of 2023-09-29 11:56 UTC, and picked up no newer commits — the last sync attempt, whatever triggered it, did nothing useful. - The host's origin TLS cert (served directly by the AWX container, not through Cloudflare) is self-signed and expired 2024-04-09. The only reason
https://ansible.nodejs.orgstill shows a valid cert to browsers is that Cloudflare is terminating TLS at the edge with the shared*.nodejs.orgwildcard cert and not validating the origin connection.
Why this should be removed, not fixed
- It's a privileged automation platform (AWX manages Ansible credentials/inventory) that nobody has been watching for 2.5+ years.
- Disk exhaustion took down its database in Dec 2025 and nobody noticed for ~9 months — reinforcing that it has no active owner.
- The AWX release (17.1.0) is multiple years out of date.
- No current build/infra workflow appears to depend on it (last real activity predates most current infra automation, which now runs through this
ansible/repo directly).
Suggested next steps
- Confirm nothing currently depends on this AWX instance (credentials stored only here, scheduled jobs, webhooks pointing at it, etc.)
- Decommission the host (
infra-ibm-ubuntu2004-x64-1/ansible.nodejs.org, IBM, 169.60.150.91) - Remove its DNS record and Cloudflare configuration
- Remove/rotate any credentials that were only ever exposed to this box (e.g.
awx_passwordin the secrets repo) - Remove references to it from
ansible/inventory.ymland~/.ssh/configconventions once decommissioned
🤖 Generated with Claude Code
- 主要言語
- Jinja
- スター
- 541
- フォーク
- 185
- 平均マージ
- 2日 19時間
- マージ済み PR（30日）
- 6
環境構築
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
nodejs/build のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
nodejs/build#4482 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
platform:ppc
難易度 1/5 1時間未満 初心者へのやさしさ 65/100
nodejs/build#4479 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
nodejs/build#4324 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
incident
難易度 4/5 3〜5日 初心者へのやさしさ 42/100
nodejs/build#4483 · コメント 3 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 45/100
nodejs/build#4477 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
似ている issue
-
bug status/needs-triage
難易度 2/5 1〜3時間 初心者へのやさしさ 86/100
prowler-cloud/prowler#12885 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
bug
難易度 1/5 1時間未満 初心者へのやさしさ 90/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
nasa/cumulus-process-py#156 ·
-
bug work in progress
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
pnp/pnpcore#1878 · コメント 3 件 · 担当者 1 名 ·
メンテナーはふだん 1 日以内に返信
-
render.yamlオープン
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100