-
Notifications
You must be signed in to change notification settings - Fork 125
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
Generate a new ansible rabbitmq password #289
Generate a new ansible rabbitmq password #289
Conversation
end | ||
|
||
def up | ||
auth = Authentication.find_by( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will there by multiple of these in the global, or do we not care? Should we do .in_my_region?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well it shouldn't matter but we don't want these to get out of sync so I'll do the .in_my_region
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not like the new password is deterministic so it would be particularly bad in this case
LGTM |
3743696
to
10f6739
Compare
Damn didn't realize |
10f6739
to
be0e123
Compare
If the current rabbitmq password contains special characters it will fail a new preflight check in the setup playbook. This is fixed for new installations by ManageIQ/manageiq#18092 but because we re-run the setup playbook when we upgrade the tower version, we also need to correct existing ones. https://bugzilla.redhat.com/show_bug.cgi?id=1638009
be0e123
to
ec81406
Compare
Checked commit carbonin@ec81406 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 |
👍 |
…sword Generate a new ansible rabbitmq password (cherry picked from commit af11356) https://bugzilla.redhat.com/show_bug.cgi?id=1638009
Hammer backport details:
|
If the current rabbitmq password contains special characters it
will fail a new preflight check in the setup playbook.
This is fixed for new installations by
ManageIQ/manageiq#18092 but because we
re-run the setup playbook when we upgrade the tower version, we
also need to correct existing ones.
https://bugzilla.redhat.com/show_bug.cgi?id=1638009