Bug 1906875 - Provide an option to force backup even when API is not available.
Summary: Provide an option to force backup even when API is not available.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd
Version: 4.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.7.0
Assignee: Suresh Kolichala
QA Contact: ge liu
URL:
Whiteboard:
Depends On:
Blocks: 1987134
TreeView+ depends on / blocked
 
Reported: 2020-12-11 16:07 UTC by Suresh Kolichala
Modified: 2021-07-29 02:37 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 15:42:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-etcd-operator pull 509 0 None closed Bug 1906875: Provide an option force backup even when API is not available to check the health. 2021-02-20 09:22:15 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:42:59 UTC

Description Suresh Kolichala 2020-12-11 16:07:30 UTC
Description of problem:
Currently with changes to fix https://bugzilla.redhat.com/show_bug.cgi?id=1898954 needed API server to be available for cluster backup to be taken.

Sometimes, it is desirable to force a backup even when the API server is not available to check the health of the cluster. For example, the disruptive tests rely on taking a backup with two masters down.

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


How reproducible:


Steps to Reproduce:
1. Bring two masters down.
2. Attempt to take a backup using cluster-backup.sh script.
3.

Actual results:
backup fails with unreachable API server (error may report etcdserver timeout)

Expected results:
With --force option, which is being added, the backup should be successful even when API server is not reachable.


Additional info:

Comment 5 errata-xmlrpc 2021-02-24 15:42:41 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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633


Note You need to log in before you can comment on or make changes to this bug.