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

[RA OCF HA] Ignore stderr when calling rabbitmqctl eval() #3524

Closed
wants to merge 4 commits into from
Closed

[RA OCF HA] Ignore stderr when calling rabbitmqctl eval() #3524

wants to merge 4 commits into from

Conversation

bogdando
Copy link

Proposed Changes

Please describe the big picture of your changes here to communicate to the RabbitMQ team why we should accept this pull request.
If it fixes a bug or resolves a feature request, be sure to link to that issue.

A pull request that doesn't explain why the change was made has a much lower chance of being accepted.

If English isn't your first language, don't worry about it and try to communicate the problem you are trying to solve to the best of your abilities.
As long as we can understand the intent, it's all good.

Types of Changes

What types of changes does your code introduce to this project?
Put an x in the boxes that apply

  • Bug fix (non-breaking change which fixes issue #NNNN)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause an observable behavior change in existing systems)
  • Documentation improvements (corrections, new content, etc)
  • Cosmetic change (whitespace, formatting, etc)
  • Build system and/or CI

Checklist

Put an x in the boxes that apply.
You can also fill these out after creating the PR.
If you're unsure about any of them, don't hesitate to ask on the mailing list.
We're here to help!
This is simply a reminder of what we are going to look for before merging your code.

  • I have read the CONTRIBUTING.md document
  • I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
  • I have added tests that prove my fix is effective or that my feature works
  • All tests pass locally with my changes
  • If relevant, I have added necessary documentation to https://github.com/rabbitmq/rabbitmq-website
  • If relevant, I have added this change to the first version(s) in release-notes that I expect to introduce it

Further Comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc.

In newer Erlang, beam.smp no longer writes a pidfile, until the rabbit
applicataion starts. It also no longer passes -mneisa dir and -sname,
which are required in order to start the node only delaying
the application start up.
Handle that so the Pacemaker HA setup keeps working with newer Erlang
and rabbitmq-server versions.

Fix '[ x == x ]' bashisms as well to silence errors in the RA logs.

Signed-off-by: Bogdan Dobrelya <bogdando@mail.ru>
Signed-off-by: Bogdan Dobrelya <bogdando@mail.ru>
Signed-off-by: Bogdan Dobrelya <bogdando@mail.ru>
Every time we recompile the erlang/elixir/rebar/rabbitmq stack there is
one or more fresh new warnings that will completely trip up any parsing
of these commands. Most end up being bugs that get fixed later on [1].

Since stderr is rarely interesting and just holds any rebase up, let's
ignore it when running these rabbitmqctl commands.

[1] https://elixirforum.com/t/mix-local-hex-warning-authenticity-is-not-established-by-certificate-path-validation/39665

Authored-by: Michele Baldessari <michele@acksyn.org>
Signed-off-by: Bogdan Dobrelya <bogdando@mail.ru>
@bogdando
Copy link
Author

@mbaldessari PTAL

@michaelklishin
Copy link
Member

Our team would prefer to not add any more CI services, both for practical and company policy reasons. Would it be possible to remove the CircleCI integration bits?

@michaelklishin
Copy link
Member

@bogdando in fact, our team is leaning towards not having this OCF script in our repo at all. Would the OpenStack community look into finding a new home for it? For example, the script is not even tested against the latest RabbitMQ version, so why do we have it in our repo in this day and age?

@bogdando
Copy link
Author

bogdando commented Sep 30, 2021

I tested it and it worked well

@bogdando
Copy link
Author

sorry, I actually confused the patches in this PR :)

@bogdando bogdando closed this Sep 30, 2021
@bogdando bogdando deleted the ocf_ha_fix branch October 1, 2021 11:02
@bogdando
Copy link
Author

bogdando commented Oct 1, 2021

@bogdando in fact, our team is leaning towards not having this OCF script in our repo at all. Would the OpenStack community look into finding a new home for it? For example, the script is not even tested against the latest RabbitMQ version, so why do we have it in our repo in this day and age?

Got it @michaelklishin , thank you for the info!
Proposed a new home for it ClusterLabs/resource-agents#1698

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.

2 participants