Post-release 24.04 HA #3237
Post-release 24.04 HA #3237
Conversation
|
versioned_docs/version-24.04/administration/centreon-ha/operating-guide.md
Outdated
Show resolved
Hide resolved
versioned_docs/version-24.04/administration/centreon-ha/operating-guide.md
Outdated
Show resolved
Hide resolved
versioned_docs/version-24.04/administration/centreon-ha/operating-guide.md
Outdated
Show resolved
Hide resolved
versioned_docs/version-24.04/administration/centreon-ha/operating-guide.md
Show resolved
Hide resolved
versioned_docs/version-24.04/administration/centreon-ha/operating-guide.md
Outdated
Show resolved
Hide resolved
versioned_docs/version-24.04/administration/centreon-ha/operating-guide.md
Show resolved
Hide resolved
versioned_docs/version-24.04/administration/centreon-ha/operating-guide.md
Outdated
Show resolved
Hide resolved
versioned_docs/version-24.04/installation/installation-of-centreon-ha/overview.md
Outdated
Show resolved
Hide resolved
versioned_docs/version-24.04/administration/centreon-ha/operating-guide.md
Outdated
Show resolved
Hide resolved
| The situation has stabilized, and you can perform a failover by moving the **centreon** resource. | ||
|
|
||
| ```shell | ||
| pcs resource move centreon |
There was a problem hiding this comment.
Not sure why we do this here. But if we do, we must clear the constraints afterwards...
There was a problem hiding this comment.
@tanguyvda it seems there is a problem with the "loss of the active node" procedure. Can you check it thoroughly and flag any parts that need to be removed?
There was a problem hiding this comment.
yeah, that can be confusing. But the purpose of this part is to go back to the initial state. To do so, this documentation tells us to move the centreon resource. Which can feel weird since we were talking about the ms_mysql resource a few lines ago.
But due to the constraint mecanism (since it is a two nodes cluster in the example), moving the centreon resource will move the ms_mysql resource too.
what is not good is that the documentation switches from a 4 nodes cluster to a 2 nodes cluster at some point and then many command line result are not portraying what is described in the documentation
versioned_docs/version-24.04/administration/centreon-ha/operating-guide.md
Show resolved
Hide resolved
versioned_docs/version-24.04/administration/centreon-ha/operating-guide.md
Outdated
Show resolved
Hide resolved
versioned_docs/version-24.04/administration/centreon-ha/operating-guide.md
Show resolved
Hide resolved
cg-tw
force-pushed
the
MON-37984-ha-24-04
branch
from
6b84ae7 to
9a60aa8
Compare
| The situation has stabilized, and you can perform a failover by moving the **centreon** resource. | ||
|
|
||
| ```shell | ||
| pcs resource move centreon |
There was a problem hiding this comment.
yeah, that can be confusing. But the purpose of this part is to go back to the initial state. To do so, this documentation tells us to move the centreon resource. Which can feel weird since we were talking about the ms_mysql resource a few lines ago.
But due to the constraint mecanism (since it is a two nodes cluster in the example), moving the centreon resource will move the ms_mysql resource too.
what is not good is that the documentation switches from a 4 nodes cluster to a 2 nodes cluster at some point and then many command line result are not portraying what is described in the documentation
|
|
||
| * All resources appear stopped on the passive node (this is because the passive node does not see the quorum device anymore, as "partition WITHOUT quorum" indicates below. The resources are stopped.) | ||
| * The active node is seen as `offline` (as the passive node is cut off from the rest of the cluster): | ||
|
|
There was a problem hiding this comment.
from now on, every crm_mon/pcs status is made using a 2 nodes cluster instead of the 4 nodes cluster at the beginning
we need to either change the beginning to match a 2 nodes cluster or change the end to match a 4 nodes cluster
Description
Please include a short summary of the changes and what is the purpose of the PR. Any relevant information should be added to help reviewers.
Target version (i.e. version that this PR changes)