Bug 1924913 - A valid etcd endpoint should have the URL scheme prepended
Summary: A valid etcd endpoint should have the URL scheme prepended
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd
Version: 4.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.5.z
Assignee: Suresh Kolichala
QA Contact: ge liu
Depends On: 1924964
TreeView+ depends on / blocked
Reported: 2021-02-03 21:07 UTC by Suresh Kolichala
Modified: 2021-03-03 04:40 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1924964 (view as bug list)
Last Closed: 2021-03-03 04:40:35 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-etcd-operator pull 536 0 None closed Bug 1924913: A valid etcd endpoint should have the URL scheme prepended. 2021-02-08 15:04:09 UTC
Red Hat Product Errata RHSA-2021:0428 0 None None None 2021-03-03 04:40:55 UTC

Description Suresh Kolichala 2021-02-03 21:07:07 UTC
Description of problem:
rollbackcopier is not complaint of the endpoint specification. However, it appears to be working fine, but the endpoint URL should be prefixed with "https://".

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

How reproducible:

Steps to Reproduce:
1. Install 4.5 or 4.4 OCP.
2. Make sure rollbackcopier is running.
3. Notice the backup of etcd db is taken hourly on the leader.

Actual results:
Backup is taken as expected.

Expected results:
Backup is taken as expected.

Additional info:
Although there is no perceivable difference in behavior, we should fix the non-compliance of endpoint specification.

Comment 8 errata-xmlrpc 2021-03-03 04:40:35 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 (Important: OpenShift Container Platform 4.5.33 bug fix and security 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.


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