Adam Miller f5b0ad7134 fix(packaging): add upgrade migration docs and podman socket retry (#1507) ...

After #1415 ships, users upgrading from previous releases need guidance
on the gateway.env deprecation, port/bind/database path changes, and
the podman.socket restart requirement.

- docs(rpm): add 'Migrating from gateway.env' section to TROUBLESHOOTING
  covering backward compatibility, env-to-TOML key mapping, and three
  breaking changes (default port 8080->17670, bind address 0.0.0.0->127.0.0.1,
  database path move). Add podman.socket restart step to upgrade procedure.
- docs(rpm): add upgrade callout to CONFIGURATION.md pointing at migration
  section.
- fix(podman): retry PodmanComputeDriver ping up to 5 times with 2s delay
  to tolerate transient socket unavailability after package upgrades.
  The systemd unit uses Wants=podman.socket (not Requires) so the gateway
  can start while the socket is briefly re-activating after an RPM upgrade
  changes its unit file on disk.
- chore(rpm): update EnvironmentFile comment in RPM spec to explain
  backward-compatibility intent.

Signed-off-by: Adam Miller <admiller@redhat.com>

2026-05-21 15:57:13 -07:00

..

CONFIGURATION.md

fix(packaging): add upgrade migration docs and podman socket retry (#1507)

2026-05-21 15:57:13 -07:00

gateway.toml.default

fix(rpm): restore 0.0.0.0 bind address for Podman via default gateway.toml (#1438)

2026-05-18 16:48:35 -07:00

QUICKSTART.md

fix(rpm): restore 0.0.0.0 bind address for Podman via default gateway.toml (#1438)

2026-05-18 16:48:35 -07:00

TROUBLESHOOTING.md

fix(packaging): add upgrade migration docs and podman socket retry (#1507)

2026-05-21 15:57:13 -07:00