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.

Sign up for GitHub

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

Jump to bottom

Volume profiling flag is not set as instructed always #418

Closed
nthomas-redhat opened this issue Sep 14, 2017 · 2 comments
Closed

Volume profiling flag is not set as instructed always #418

nthomas-redhat opened this issue Sep 14, 2017 · 2 comments
Assignees
@shtripat

Comments

@nthomas-redhat
Copy link
Contributor

When the volume profiling is enabled already, this fails and flag is not appropritately in etcd
@nthomas-redhat nthomas-redhat mentioned this issue Sep 16, 2017
Closed
shtripat pushed a commit to shtripat/gluster_bridge that referenced this issue Sep 20, 2017
Added logic to check already started/stopped profiling for volumes
96cc01b 
If profiling is already started for few volumes from CLI and we
import the cluster, by no means these volumes were marked as
profiling on in tendrl. Modified to tackle this scenario.

tendrl-bug-id: Tendrl#418
Signed-off-by: Shubhendu <[email protected]>
@shtripat shtripat mentioned this issue Sep 20, 2017
Merged
@nnDarshan
Copy link
Contributor

@shtripat Looks like the fix is merged. Could you please confirm and update accordingly

@shtripat
Copy link
Member

shtripat commented Sep 26, 2017 •
edited
Loading

@nthomas-redhat plz do the needful ^^^

@r0h4n r0h4n closed this as completed Sep 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shtripat shtripat

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@r0h4n @nnDarshan @nthomas-redhat @shtripat