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

goconserver broadcast mode failed to support xCAT hierarchy mode #48

Open
neo954 opened this issue Aug 24, 2018 · 0 comments
Open

goconserver broadcast mode failed to support xCAT hierarchy mode #48

neo954 opened this issue Aug 24, 2018 · 0 comments
Labels

Comments

@neo954
Copy link

neo954 commented Aug 24, 2018

This issue is against goconserver version 0.3.1. While goconserver introduced broadcast node in pull request #45, it failed to support xCAT hierarchy mode.

# goconserver --version
Version: 0.3.1, BuildTime: 2018-08-20T21:15:20-0400 Commit: 1a3762c6de1dab60f5f2dedac659c532c1eda76f

In my test environment, c910f03c01p09 act as xCAT management node, c910f03c01p10 act as xCAT service node, and c910f03c01p19 act as the compute node.

# lsdef c910f03c01p10 -i setupconserver
Object name: c910f03c01p10
    setupconserver=2
# lsdef c910f03c01p19 -i conserver,servicenode,xcatmaster
Object name: c910f03c01p19
    conserver=c910f03c01p10
    servicenode=c910f03c01p10
    xcatmaster=c910f03c01p10

In the configuration above, Run rcons c910f03c01p10,c910f03c01p19 will fail. See details below.

# rcons c910f03c01p10,c910f03c01p19
Could not connect to c910f03c01p10, error: Node not exist
Connection to c910f03c01p10 closed.
# rcons c910f03c01p19,c910f03c01p10
Could not connect to c910f03c01p10, error: Node not exist
Connection to c910f03c01p10 closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants