Add a way to disable error mesages about missing RAs about crmsh HOT 9 CLOSED

Actually, I don't understand why resource-discovery would cause this problem. I suspect that this is related to another change to crmsh. Could you attach output from crm -d when you get this message?
Thank you.

from crmsh.

Ah, the issue is that I use default symmetric-cluster=true, and use location constraints for symmetric cluster (e.g. 'rule -inf: #kind ne remote',) with resource-discovery=never.

location test-instance-on-remote-nodes cl-test-instance resource-discovery=never
rule -inf: #kind ne remote
location vlan002-on-cluster-nodes vlan002 resource-discovery=never
rule -inf: #kind ne cluster
location vlan003-on-cluster-nodes vlan003 resource-discovery=never
rule -inf: #kind ne cluster
location vlan004-on-cluster-nodes vlan004 resource-discovery=never
rule -inf: #kind ne cluster

from crmsh.

Still, this should not cause such messages, since they are related to primitive resources and not constraints.

from crmsh.

Sorry, very busy day here. Cannot switch context properly.

Yes, in addition, remote nodes have different set of resource agents. resource-discovery=never with -inf makes it possible to never probe for resources handled by not installed RAs in addition to never run them there.
So pacemaker produces no errors. But crmsh does.

from crmsh.

Ah, that makes sense. The problem is the remote node resources. We would need some way for crmsh to get the agent metadata for remote resources, or somehow detect that those resources don't have local agents and suppress the warnings. I am not sure how to handle this in the best way yet.

from crmsh.

Yes, exactly.

This is not a major issue, but it would make sense to keep in mind, that it may become major at some point.

I agree, that it is very hard to guess, why RA is not available on a given node. That's why original intention was to just add a configuration option to suppress that errors.

from crmsh.

I agree, that it is very hard to guess, why RA is not available on a given node. That's why original intention was to just add a configuration option to suppress that errors.

That's not such a bad idea. Somebody could even want to do some
configuration on an unrelated host where not all RAs are present.

from crmsh.

Added option to suppress these warnings, let me know if there are any other problems with not having the metadata available. Thanks :)

from crmsh.

Closing this, thanks!

from crmsh.