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

clush doesn't see groups.d definitions? #552

Open
skwde opened this issue Jan 30, 2024 · 6 comments
Open

clush doesn't see groups.d definitions? #552

skwde opened this issue Jan 30, 2024 · 6 comments

Comments

@skwde
Copy link

skwde commented Jan 30, 2024

I installed clush via conda in a environment. All config files are under <conda env location>/clush/etc/clustershell

In my groups.conf I have

[Main]
default: roles
confdir: /etc/clustershell/groups.conf.d $CFGDIR/groups.conf.d
autodir: /etc/clustershell/groups.d $CFGDIR/groups.d

Next I have groups.d/cluster.yaml where I have my node definitions.
The syntax of the file is fine because running nodeset -LL shows all my definitions.

If I run

clush -a date

I expect to get the date from all machines.

Instead I get

Usage: clush [options] command

clush: error: No node to run on.

so what am I missing here?

@degremont
Copy link
Collaborator

degremont commented Jan 30, 2024 via email

@skwde
Copy link
Author

skwde commented Jan 30, 2024

Thanks for your immediate reply.

Here is the output:

$ clush -d -v -a date
DEBUG:root:clush: STARTING DEBUG
Adding nodes from option -a: 
Usage: clush [options] command

clush: error: No node to run on.

and

$ nodeset -f -a

Obviously that is not what I would expect :)

@degremont
Copy link
Collaborator

degremont commented Jan 30, 2024 via email

@skwde
Copy link
Author

skwde commented Jan 30, 2024

Well I have no explicit all definition.

To my understanding all should be everyting in roles since I have default: roles in groups.conf.

Ok, here is a simplified example:

My cluster.yaml

roles:
    dev: '@dev:all'


dev:
    dev: 'dev01'

with

$ nodeset -LL
@dev 
@dev:dev dev01

@degremont
Copy link
Collaborator

degremont commented Jan 30, 2024 via email

@skwde
Copy link
Author

skwde commented Jan 30, 2024

I don't get your reference to dev: ***@***.***:*'

But it now works with the following.
My cluster.yaml should actually look like

roles:
    dev: '@dev:*'


dev:
    dev: 'dev01'

Ok the reference was (at least for me) a bit hard to find.
In https://clustershell.readthedocs.io/en/latest/tools/nodeset.html#working-with-range-sets it mentions that all is a external call. Then one actually should look at https://clustershell.readthedocs.io/en/latest/config.html#group-source-upcalls under External calls and see the description of all.

I think it would be good if a note is already under https://clustershell.readthedocs.io/en/latest/config.html#yaml-group-files.

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

No branches or pull requests

2 participants