OCPBUGS-84695: podman-etcd single-node cluster handling and transitions#2155
OCPBUGS-84695: podman-etcd single-node cluster handling and transitions#2155jaypoulz wants to merge 1 commit into
Conversation
|
Can one of the project admins check and authorise this run please: https://haci.fast.eng.rdu2.dc.redhat.com/job/resource-agents/job/resource-agents-pipeline/job/PR-2155/1/input |
jaypoulz
changed the title
jaypoulz
force-pushed
the
single-node-support
branch
2 times, most recently
from
2d74c72 to
7e16970
Compare
|
Can one of the project admins check and authorise this run please: https://haci.fast.eng.rdu2.dc.redhat.com/job/resource-agents/job/resource-agents-pipeline/job/PR-2155/3/input |
jaypoulz
force-pushed
the
single-node-support
branch
from
7e16970 to
4d7a89a
Compare
|
Can one of the project admins check and authorise this run please: https://haci.fast.eng.rdu2.dc.redhat.com/job/resource-agents/job/resource-agents-pipeline/job/PR-2155/4/input |
jaypoulz
force-pushed
the
single-node-support
branch
from
4d7a89a to
dde2aa5
Compare
|
Can one of the project admins check and authorise this run please: https://haci.fast.eng.rdu2.dc.redhat.com/job/resource-agents/job/resource-agents-pipeline/job/PR-2155/5/input |
jaypoulz
force-pushed
the
single-node-support
branch
from
dde2aa5 to
0d09525
Compare
|
Can one of the project admins check and authorise this run please: https://haci.fast.eng.rdu2.dc.redhat.com/job/resource-agents/job/resource-agents-pipeline/job/PR-2155/6/input |
|
Proof of the rabbit: |
jaypoulz
force-pushed
the
single-node-support
branch
from
0d09525 to
c097465
Compare
|
Can one of the project admins check and authorise this run please: https://haci.fast.eng.rdu2.dc.redhat.com/job/resource-agents/job/resource-agents-pipeline/job/PR-2155/7/input |
…sitions Add comprehensive single-node cluster support to podman-etcd resource agent, including initial deployment, restart scenarios, and transitions between single-node and two-node configurations. Changes: - Add is_single_node() helper function for clean single-node detection - Handle single-node mode in peer management (clean up learners, set standalone_node) - Set standalone_node during single-node start to mark standalone state - Fix monitor path to set standalone_node during two-node to single-node transitions - Clean up learner members during 2→1 node transitions in monitor path - Fix restart failures by skipping revision comparison when no peer exists - Ensure standalone_node attribute is properly maintained across all transitions Fixes restart failures, 2→1 node transitions, and initial single-node deployments. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
jaypoulz
force-pushed
the
single-node-support
branch
from
c097465 to
a1290c6
Compare
1 participant
OCPBUGS-84695: fix(podman-etcd): single-node cluster handling and transitions
Add comprehensive single-node cluster support to podman-etcd resource agent,
including initial deployment, restart scenarios, and transitions between
single-node and two-node configurations.
This PR works in tandem with openshift/cluster-etcd-operator#1605
Changes:
Fixes restart failures, 2→1 node transitions, and initial single-node deployments.
Co-Authored-By: Claude Sonnet 4.5 noreply@anthropic.com