autonomic-bot
9a7772563a
Push builds have been RED on the lint step since ~build 209 from accumulated formatting drift. This is the mechanical cleanup: ruff format + ruff --fix (UP038 isinstance unions, SIM105 contextlib.suppress, UP031 f-strings, SIM115 tempfile context manager), shfmt -i 2 -ci, nixpkgs-fmt/statix/deadnix (merged attrsets, dropped unused lib args), yamllint, and shell quoting fixes in tests/lasuite-docs/setup_custom_tests.sh. No behaviour changes intended; lint: PASS, unit tests: 138 passed.
25 lines
1.0 KiB
Python
25 lines
1.0 KiB
Python
"""ghost — UPGRADE overlay (Phase 1e HC3 / Phase 2 P4): assertion-only + additive.
|
|
|
|
ops.pre_upgrade seeded ci_marker='upgrade-survives' into the MySQL `ghost` DB before the upgrade op
|
|
(HC1 chaos redeploy prev-published → PR head). The mysql data volume persists across the redeploy,
|
|
so the seeded row must still be there afterwards — proving the upgrade preserved app data, not just
|
|
that the new version came up healthy. Read via the `mysql` CLI in the `db` service.
|
|
"""
|
|
|
|
import os
|
|
import sys
|
|
|
|
sys.path.insert(0, os.path.join(os.path.dirname(__file__), "..", "..", "runner"))
|
|
from harness import lifecycle # noqa: E402
|
|
|
|
|
|
def _mysql(domain, sql):
|
|
cmd = 'MYSQL_PWD="$(cat /run/secrets/db_password)" ' f'mysql -u root -N -s ghost -e "{sql}"'
|
|
return lifecycle.exec_in_app(domain, ["sh", "-c", cmd], service="db").strip()
|
|
|
|
|
|
def test_upgrade_preserves_state(live_app):
|
|
assert (
|
|
_mysql(live_app, "SELECT v FROM ci_marker;") == "upgrade-survives"
|
|
), "the seeded ghost MySQL marker did not survive the upgrade redeploy (data loss on upgrade)"
|