Bug 1890286 - ovnkube-master ends in CrashLoopBackOff during master node replacement; ovsdb-server: ovsdb error: error reading record 6439 from OVN_Northbound log: record 6439 indicates server has left the cluster; it cannot be added back
Summary: ovnkube-master ends in CrashLoopBackOff during master node replacement; ovsdb...
Keywords:
Status: CLOSED DUPLICATE of bug 1885675
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Ben Bennett
QA Contact: Anurag saxena
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-21 19:39 UTC by Marius Cornea
Modified: 2020-10-21 19:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-21 19:52:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Marius Cornea 2020-10-21 19:39:53 UTC 
Description of problem:

ovnkube-master ends in CrashLoopBackOff during master node replacement; nbdb reports: ovsdb-server: ovsdb error: error reading record 6439 from OVN_Northbound log: record 6439 indicates server has left the cluster; it cannot be added back (use "ovsdb-tool join-cluster" to add a new server)


Version-Release number of selected component (if applicable):
4.6.0-rc.4

How reproducible:
100%

Steps to Reproduce:
1. Deploy a baremetal IPI setup with OVNKubernetes

2. Run throught the master node replacement procedure according to:

https://access.redhat.com/documentation/en-us/openshift_container_platform/4.5/html-single/backup_and_restore/index#restore-replace-stopped-etcd-member_replacing-unhealthy-etcd-member

Actual results:

When the master node replacement comes up ovnkube-master pod ends up in CrashLoopBackOff

Expected results:
ovnkube-master starts without errors

Additional info:
Comment 2 Tim Rozet 2020-10-21 19:52:41 UTC 

*** This bug has been marked as a duplicate of bug 1885675 ***
Note You need to log in before you can comment on or make changes to this bug.