Skip to content

Unmanage the cluster only when rebooting poolmaster#40

Merged
2 commits merged intomasterfrom
fix/unmanage-poolmaster-only
Jun 28, 2016
Merged

Unmanage the cluster only when rebooting poolmaster#40
2 commits merged intomasterfrom
fix/unmanage-poolmaster-only

Conversation

@remibergsma
Copy link
Copy Markdown
Member

In case the poolmaster was to be skipped, we'd still unmanage the cluster and immediately manage it again. This PR fixes that and doesn't unmanage/manage when the poolmaster is skipped resulting in a better service.

@ghost ghost merged commit db5db65 into master Jun 28, 2016
@remibergsma remibergsma deleted the fix/unmanage-poolmaster-only branch June 28, 2016 07:35
This pull request was closed.
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

Successfully merging this pull request may close these issues.

1 participant