Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stop testing rmq 3.8 #1110

Merged
merged 1 commit into from
Aug 11, 2022
Merged

Stop testing rmq 3.8 #1110

merged 1 commit into from
Aug 11, 2022

Conversation

ChunyiLyu
Copy link
Contributor

This closes #

Note to reviewers: remember to look at the commits in this PR and consider if they can be squashed

Summary Of Changes

Stop testing rmq 3.8 as it has reached end of support

  • remove 3.8.8 github action tests
  • update README to say the Operator supports 3.9 onwards

Additional Context

- remove 3.8.8 github action tests
- update README to say the Operator supports 3.9
onwards
Copy link
Contributor

@coro coro left a comment

Choose a reason for hiding this comment

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

There's also some tests that get run per-commit on this repo in our Concourse; looks like those are out of date too.

@ChunyiLyu
Copy link
Contributor Author

@ChunyiLyu ChunyiLyu merged commit 253ba87 into main Aug 11, 2022
@ChunyiLyu ChunyiLyu deleted the remove-3-8 branch August 11, 2022 16:42
ansd added a commit that referenced this pull request Aug 15, 2022
Since we bumped the minimum supported RabbitMQ version to v3.9.0 in
#1110, we can use the
CLI command `rabbitmqctl enable_feature_flag all` introduced in
rabbitmq/rabbitmq-server@ce65586.
ansd added a commit that referenced this pull request Aug 15, 2022
Since we bumped the minimum supported RabbitMQ version to v3.9.0 in
#1110, we can delete
the deprecated `cluster_formation.randomized_startup_delay_range`
configurations.

See rabbitmq/rabbitmq-server#3075.

Prior to this commit, the RabbitMQ logs contained the following warning:
```
2022-08-15 08:18:03.870480+00:00 [warn] <0.130.0> cluster_formation.randomized_startup_delay_range.min and cluster_formation.randomized_startup_delay_range.max are deprecated
```
ansd added a commit that referenced this pull request Aug 15, 2022
Follow up of #1110:
The new minimum supported version is 3.9.0.
Therefore, we should test against that version to make sure the
cluster-operator is compatible with the minimum supported version.
ansd added a commit that referenced this pull request Aug 15, 2022
Since we bumped the minimum supported RabbitMQ version to v3.9.0 in
#1110, we can use the
CLI command `rabbitmqctl enable_feature_flag all` introduced in
rabbitmq/rabbitmq-server@ce65586.
ansd added a commit that referenced this pull request Aug 15, 2022
Since we bumped the minimum supported RabbitMQ version to v3.9.0 in
#1110, we can delete
the deprecated `cluster_formation.randomized_startup_delay_range`
configurations.

See rabbitmq/rabbitmq-server#3075.

Prior to this commit, the RabbitMQ logs contained the following warning:
```
2022-08-15 08:18:03.870480+00:00 [warn] <0.130.0> cluster_formation.randomized_startup_delay_range.min and cluster_formation.randomized_startup_delay_range.max are deprecated
```
ansd added a commit that referenced this pull request Aug 15, 2022
Follow up of #1110:
The new minimum supported version is 3.9.0.
Therefore, we should test against that version to make sure the
cluster-operator is compatible with the minimum supported version.
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.

3 participants