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
Cluster resource provider incorrectly determines node type? #476
Labels
Comments
Yes, the |
@pauldmccann so it's in the cluster node type change action. Please submit a PR that corrects it. It should be a lower risk change than I expected at first. |
michaelklishin
changed the title
RAM Nodes vs Disc Nodes
Cluster resource provider incorrectly determines node type?
Feb 9, 2018
Thanks Michael. There should be a PR available now
…On Fri, Feb 9, 2018 at 11:18 AM, Michael Klishin ***@***.***> wrote:
@pauldmccann <https://github.com/pauldmccann> so it's in the cluster node
type change action. Please submit a PR that corrects it. It should be a
lower risk change than I expected at first.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#476 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOP-pAomrMtC8Oh6ZRQtKyBOByUAtaljks5tTG_YgaJpZM4SAEWw>
.
|
We believe #477 addressed this at least somewhat. The entire logic in that provider needs to be revisited. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I believe there is an error on line 259 of cluster.rb
currently it is using the following to determine what the cluster node type should be:
var_cluster_node_type = parse_cluster_nodes_string(new_resource.cluster_nodes).each { |node| node['name'] == var_node_name }.first['type'] # ~FC039
I believe it should be using .select. Right now, all nodes are using the nodetype of the first node in the list.
var_cluster_node_type = parse_cluster_nodes_string(new_resource.cluster_nodes).each { |node| node['name'] == var_node_name }.first['type'] # ~FC039
The text was updated successfully, but these errors were encountered: