Skip to content

Conversation

@amanda11
Copy link
Contributor

Update Bash installer for 3.7 to use erlang24*

RabbitMQ have released a newer version 3.10.2 which now manages to start with erlang 25. But they still report on https://www.rabbitmq.com/which-erlang.html that the erlang 25 support is preview.
Therefore probably safer to stick with using 24*

@amanda11
Copy link
Contributor Author

amanda11 commented May 23, 2022

@armab I've cherrypicked the st2-packages for the 3.7 branch in this PR, but I'd appreciate your check as to process to what we need to do to cherry pick for 3.7. We shouldn't need new packages built as its just the bash installer we're updateing.

As per @bishopbm1 comment in slack, the new RabbitMQ 3.10.2 will now start with erlang 25 so even without this change we should be able to install ok now on EL8. But given that erlang 25 is "preview" support, would it still be better to use 24.* on erlang anyway.

Copy link
Member

@arm4b arm4b left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@arm4b
Copy link
Member

arm4b commented May 23, 2022

The latest stable branch is referenced in the st2_bootstrap.sh script which is an entry point for the curl|bash installer.

# Note: This variable needs to default to a branch of the latest stable release
BRANCH='v3.7'

From that, the installer will poin to the v3.7 branch scripts here:

ST2BOOTSTRAP="${BASE_PATH}/${BRANCH}/scripts/st2bootstrap-el${RHMAJVER}.sh"

Copy link
Member

@cognifloyd cognifloyd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, let's stick with erlang 24 for now.

@amanda11 amanda11 merged commit 8f9c3fe into v3.7 May 24, 2022
@amanda11 amanda11 deleted the use_erlang24_for_3.7 branch May 24, 2022 07:09
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.

4 participants