This repository was archived by the owner on Feb 8, 2024. It is now read-only.
CORTX-33789: Hare Config stage fail with Motr Clients #2146
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pavankrishnat
requested review from
Shreya-18,
d-nayak,
mssawant and
vaibhavparatwar
Contributor
|
retest this please |
pavankrishnat
force-pushed
the
CORTX33789
branch
from
a786fb1 to
27a08fa
Compare
Contributor
|
@mssawant @d-nayak @Shreya-18 please review this PR. Premerge failure is because of some infra issue. |
|
@pavankrishnat can you please elaborate the problem and solution in the commit message? |
pavankrishnat
force-pushed
the
CORTX33789
branch
from
38b5881 to
64950ba
Compare
Contributor
|
@pavankrishnat request you to add appropriate commit message |
pavankrishnat
force-pushed
the
CORTX33789
branch
from
64950ba to
18e0722
Compare
vaibhavparatwar
approved these changes
Aug 4, 2022
mssawant
reviewed
Aug 4, 2022
Contributor
|
With below image: Deployed 6N cluster without motr client successfully at https://eos-jenkins.colo.seagate.com/job/Cortx-Automation/job/RGW/job/setup-cortx-rgw-cluster/10407/console Deployed 6N cluster with motr client successfully at https://eos-jenkins.colo.seagate.com/job/Cortx-kubernetes/job/setup-cortx-cluster-solution-input/657/console Within data pods, able to run hare mini provisioning stages with the consul source type It's generates hare config files successfully |
mssawant
approved these changes
Aug 4, 2022
mssawant
left a comment
mssawant
left a comment
There was a problem hiding this comment.
Please add a comment mentioning presently, both client and data pods are returned by the conf store search query. But data pods are filtered out while creating node in _create_node().
|
Tried 3N bootstrap using |
Contributor
Author
|
@mssawant, Manually bootstrapped a Single Node setup with current PR branch which worked. |
pavankrishnat
force-pushed
the
CORTX33789
branch
from
cc0a89b to
f1d4643
Compare
Problem: If num_client_inst is specified a non-zero value, deployment is failing. Issue is with search key. For data nodes we used 'io':'motr', it returns the list of machine IDs which includes both data node and motr client nodes, because of which deployment was failing. Solution: Separated search key for data node and motr client node. Signed-off-by: pavankrishnat <[email protected]>
pavankrishnat
force-pushed
the
CORTX33789
branch
from
a9b592a to
addefdb
Compare
d-nayak
approved these changes
Aug 5, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CORTX-33789: Hare Config stage fail with Motr Clients
Problem:
If num_client_inst is specified a non-zero value, deployment is failing.
Issue is with search key. For data nodes we used
'io':'motr', it returns thelist of machine IDs which includes both data node and motr client nodes,
because of which deployment was failing.
Solution:
Separated search key for data node and motr client node.
Signed-off-by: pavankrishnat [email protected]