Skip to content

🔧 Build: Skip RabbitMQ install in CI#244

Merged
mbercx merged 1 commit intomainfrom
fix/rabbitmq
Mar 27, 2026
Merged

🔧 Build: Skip RabbitMQ install in CI#244
mbercx merged 1 commit intomainfrom
fix/rabbitmq

Conversation

@mbercx
Copy link
Copy Markdown
Collaborator

@mbercx mbercx commented Mar 27, 2026

The CI in #243 fails because a RabbitMQ issue, unrelated to the changes in that PR.

Logs show "Setting up rabbitmq-server (3.12.1-1ubuntu1.4)". This revision was uploaded a little over a week ago, after our last successful CI run:

https://launchpad.net/ubuntu/+source/rabbitmq-server/3.12.1-1ubuntu1.4

Add `ci_skip` to the RabbitMQ task to prevent CI failures when running inside a Docker
container, where no systemd is available.

The CI previously managed to start `rabbitmq-server` in Docker despite the absence of
systemd. As of `rabbitmq-server 3.12.1-1ubuntu1.3`, the Ubuntu package explicitly blocks
`dh_installinit` in favour of `dh_systemd_start`, likely removing the SysV fallback that
Ansible's `service` module was relying on. The result is:

    Could not find the requested service rabbitmq-server: host

Since the AiiDA daemon (the primary RabbitMQ consumer) is already skipped in Docker via
`when: daemon_service is defined and daemon_service`, skipping RabbitMQ itself in the CI
is reasonable.
@mbercx mbercx changed the title Fix RabbitMQ 🔧 Build: Skip RabbitMQ install in CI Mar 27, 2026
@mbercx mbercx merged commit 431afa0 into main Mar 27, 2026
5 of 6 checks passed
@mbercx mbercx deleted the fix/rabbitmq branch March 27, 2026 03:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant