Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow restarting openqa-webui-daemon without downtime #5820

Merged
merged 3 commits into from
Aug 6, 2024

Commits on Aug 5, 2024

  1. Allow restarting openqa-webui-daemon without downtime

    * Allow restarting `openqa-webui-daemon` without downtime by sending SIGHUP
      to the process or reloading the systemd unit `openqa-webui.service`
    * Start the Mojolicious application with `reuse=1` as mentioned on
      https://docs.mojolicious.org/Mojolicious/Guides/Cookbook#Zero-downtime-software-upgrades
    * Note that other services are not covered but those are also not user
      facing or retried and thus not required
    * See https://progress.opensuse.org/issues/162533
    Martchus committed Aug 5, 2024
    Configuration menu
    Copy the full SHA
    3f9c16e View commit details
    Browse the repository at this point in the history
  2. Avoid restarting openqa-webui.service when other units are restarted

    This helps minimizing downtimes. It is also generally acceptable to show
    the web UI even though not all other services can be started.
    
    Related ticket: https://progress.opensuse.org/issues/162533
    Martchus committed Aug 5, 2024
    Configuration menu
    Copy the full SHA
    23a8d07 View commit details
    Browse the repository at this point in the history
  3. Reload main openQA service on updates to reduce downtimes

    * Avoid restarting the main web UI service via the rpm postrun script; only
      reload the service
    * See https://progress.opensuse.org/issues/162533
    Martchus committed Aug 5, 2024
    Configuration menu
    Copy the full SHA
    a1f44e4 View commit details
    Browse the repository at this point in the history