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
Fix change node type #263
Fix change node type #263
Conversation
…. This action would fail each time it tried to change the cluster type. Once I changed it to each, it now performed the task correctly
…disc type, this would break on a second run of chef-client. I made sur ethat it validated if it indeed found a ram or a disc type
👍 |
Hi @linuxdynasty! Can you please update your PR to replace |
I take a look at tests. For now it seems there is very few tests related to the cluster part. |
@@ -89,7 +93,11 @@ def disc_nodes(cluster_status) | |||
pattern = '({disc,\[)(.*?)(\]})' | |||
result = match_pattern_cluster_status(cluster_status, pattern) | |||
Chef::Log.debug("[rabbitmq_cluster] disc_nodes : #{result}") | |||
result.split(',') | |||
if result.nil? | |||
result = [] |
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.
Rubocop doesn't like this :(
I'm going to close this due to no activity. |
This will fix the action change_node_type and as well not break on a 2nd run, since provider expected that a ram type will always be in the output of cluster_status