Skip to content

v2.3.1

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 08 Nov 17:31
v2.3.1
5b2e915
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Docs and CI only, no changes to the stack itself. Found by running the install docs on a machine with leftovers: busy ports, an old Grafana volume, an upgrade over existing data, Compose and Ansible on one host. Write-up: https://dev.to/airat71/i-installed-my-stack-on-a-machine-with-leftovers-three-green-signals-stayed-green-5211

Changed

  • Quick Start, README and Installation Guide verify the stack with scripts/smoke-check.sh instead of docker compose ps, list the ports that must be free, and say to use either Option A or Option B on a host.
  • docs/UPGRADE.md: upgrade steps for the Docker Compose path.
  • docs/TROUBLESHOOTING.md: port conflicts, the Grafana password after the first start, dashboards after the v2.2.0 to v2.3.0 upgrade, Ansible on a host that already runs a stack or a Node Exporter.

Added

  • scripts/upgrade-check.sh and an upgrade job in the smoke test: starts the latest release with data, upgrades to the commit under test on the same volumes, and checks that the smoke check passes, the Grafana folder and Prometheus data survive and every dashboard file is provisioned without errors.

Known, not fixed

  • Upgrading from v2.2.0 to v2.3.0 over an existing Grafana volume leaves three new dashboards unapplied (nginx, postgresql, redis). docker compose up -d still exits 0. The workaround that was verified is in docs/TROUBLESHOOTING.md.
  • The Prometheus healthcheck runs inside the container and cannot detect a port taken by another process. The Ansible playbook does not check targets after it starts.

Full list: CHANGELOG.md.

Assets 2
Loading