Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1783448

Summary:	etcd backup/restore should also save and restore kube apiserver static resources
Product:	OpenShift Container Platform	Reporter:	Suresh Kolichala <skolicha>
Component:	Etcd	Assignee:	Suresh Kolichala <skolicha>
Status:	CLOSED ERRATA	QA Contact:	ge liu <geliu>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	geliu, sbatsche
Target Milestone:	---
Target Release:	4.3.0
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1783445	Environment:
Last Closed:	2020-01-23 11:19:25 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1783445
Bug Blocks:

Description Suresh Kolichala 2019-12-13 19:04:39 UTC

+++ This bug was initially created as a clone of Bug #1783445 +++

Description of problem:
If etcd is backing up a snapshot of the database, it behooves to copy the static pod resources of kube-apiserver at the time of backup. When we restore, the revision of the static pod resources must match with the restored database.

Version-Release number of selected component (if applicable):
4.3

How reproducible:
Encrypted etcd failed without matching configuration.

Steps to Reproduce:
1. Take an etcd snapshot of encrypted configuration.
2. Restore it on all masters (esp. if the revision of apiserver changed)


Actual results:
kube-apiserver doesn't fully recover.

Expected results:
The cluster recovers and becomes fully functional.

Additional info:
Related to discussion in Bug https://bugzilla.redhat.com/show_bug.cgi?id=1776811

Comment 4 errata-xmlrpc 2020-01-23 11:19:25 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0062