The GitHub Actions job "Tests AMD" on airflow.git/v3-1-test has failed.
Run started by GitHub user potiuk (triggered by potiuk).

Head commit for run:
51ff37d83fd9cb3662c3726bbef29d1575f3b0ab / github-actions[bot] 
<41898282+github-actions[bot]@users.noreply.github.com>
[v3-1-test] Fix systemd service files issues (#57126) (#57231)

This commit addresses multiple bugs in systemd service files reported
in issue #53706:

1. Fix incorrect command in airflow-api.service
   - Changed 'airflow api' to 'airflow api-server' (correct CLI command)

2. Standardize environment configuration approach
   - Changed airflow-api.service and airflow-triggerer.service to use
     EnvironmentFile=/etc/sysconfig/airflow instead of inline Environment
   - This provides consistency with other services and allows admins
     flexibility to manage custom environment variables centrally

3. Fix service dependencies
   - Added proper After= and Wants= clauses for database and message
     queue services (postgresql, mysql, redis, rabbitmq) to
     airflow-api.service and airflow-triggerer.service
   - Services now wait for required dependencies before starting

4. Additional bug fixes discovered during review
   - airflow-flower.service: Removed duplicate ExecStart line
   - airflow-kerberos.service: Fixed command from 'kerberos' to
     'airflow kerberos'

5. Consistency improvements
   - Added Type=simple and RestartSec=5s to airflow-api.service and
     airflow-triggerer.service for consistency with other services

All systemd service files now follow the same configuration pattern,
making them easier to maintain and more reliable during system startup.

Fixes #53706
(cherry picked from commit b37016084ed73318eaff1a871b42d9cc2e599b55)

Co-authored-by: Ashir Alam <[email protected]>

Report URL: https://github.com/apache/airflow/actions/runs/18805871091

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to