v1.4.2

Release Notes - RabbitMQ Forge BOSH Release v1.4.2

Release Date: August 27, 2025

Overview

This release fixes an important issue with memory limit configuration handling in the BPM configuration, improving deployment flexibility and reliability.

releases:

- name: rabbitmq-forge
  version: 1.4.2
  url: https://github.com/blacksmith-community/rabbitmq-forge-boshrelease/releases/download/v1.4.2/rabbitmq-forge-1.4.2.tgz
  sha1: sha256:a7c6697684f37fac5fb3202cb234df6466ca93d08d10fe648ed8cf9b97489342

Software Versions (Unchanged)

RabbitMQ

• Version: 3.13.6
• Type: Stable release

Erlang/OTP

• Version: 26.2.5.14
• Type: Stable release

Key Improvements

Memory Limit Configuration Fix

• Fixed: Memory limit configuration handling in BPM configuration
• Removed: Hard-coded default memory limit of 1024MB from job specification
• Improved: Memory limit is now only applied when explicitly configured and valid
• Enhancement: Better handling of memory configuration edge cases

Technical Details

• Modified jobs/rabbitmq/spec to remove the default value for vm.memory_mb property
• Updated jobs/rabbitmq/templates/config/bpm.yml to conditionally apply memory limits
• Memory limit is now only set when vm.memory_mb is provided and greater than 0
• Prevents potential issues with invalid or zero memory configurations

Compatibility

• Fully compatible with existing RabbitMQ 3.13.x deployments
• Configuration Impact: Deployments relying on the default 1024MB memory limit should explicitly set vm.memory_mb property
• Supports in-place upgrades from v1.4.1

Upgrade Instructions

1. Download the release tarball: rabbitmq-forge-1.4.2.tgz
2. Upload to your BOSH Director
3. Important: Review your deployment manifests to ensure vm.memory_mb is explicitly set if memory limits are desired
4. Deploy using your existing deployment manifest

Configuration Changes Required

If your deployment previously relied on the default 1024MB memory limit, you should now explicitly set:

instance_groups:
- name: rabbitmq
  properties:
    vm:
      memory_mb: 1024  # or your desired memory limit in MB

Testing Recommendations

• Verify RabbitMQ starts correctly with your memory configuration
• Test cluster connectivity after upgrade
• Confirm memory limits are applied as expected using bosh ssh and process monitoring
• Validate message publishing and consumption
• Check management UI accessibility

Known Issues

None at this time.

Support

For issues or questions, please open an issue in the GitHub repository or contact the Genesis Community support channels.