Fail in when installing RabbitMQ/Erlang versions not possible

Current behaviour with just pinning on Ubuntu/Debian leads to potential
situations, when there's no selected version available in repo to
proceed with what's available based on set priorities.
Instead, it might be worth to fail explicitly when requested version is
not available. This also aligns behaviour with EL distros.
Change-Id: Iad69cc4b5f8ca40246bcbc604e77eef7975eb104
This commit is contained in:
Dmitriy Rabotyagov
2024年10月08日 16:48:40 +02:00
parent d1fd62e445
commit 2f686f4bfd

View File

@@ -37,12 +37,14 @@ _rabbitmq_erlang_repo:
architectures:"{{ rabbitmq_architecture_mapping.get(ansible_facts['architecture']) }}"
state:"{{ (rabbitmq_install_method == 'external_repo') | ternary('present', 'absent') }}"
_rabbitmq_erlang_version_spec:"{{ (rabbitmq_install_method == 'external_repo') | ternary('=1:' ~ rabbitmq_erlang_package_version, '') }}"
rabbitmq_dependencies:
- erlang-base
- erlang-diameter
- erlang-eldap
- erlang-nox
- "erlang-base{{ _rabbitmq_erlang_version_spec }}"
- "erlang-diameter{{ _rabbitmq_erlang_version_spec }}"
- "erlang-eldap{{ _rabbitmq_erlang_version_spec }}"
- "erlang-nox{{ _rabbitmq_erlang_version_spec }}"
- socat
rabbitmq_distro_packages:
- rabbitmq-server
- "rabbitmq-server{{ (rabbitmq_install_method == 'external_repo') | ternary('=' ~ rabbitmq_package_version, '') }}"
Reference in New Issue
openstack/openstack-ansible-rabbitmq_server
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.

The note is not visible to the blocked user.