Bug 1804169 - the minKubeVersion should be v1.16.0
Summary: the minKubeVersion should be v1.16.0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.3.z
Assignee: Jeff Cantrill
QA Contact: Anping Li
URL:
Whiteboard:
Depends On: 1804166
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-18 11:37 UTC by Anping Li
Modified: 2020-03-10 23:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1804166
Environment:
Last Closed: 2020-03-10 23:53:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-logging-operator pull 370 0 None closed Bug 1804169: set minKube version for 4.3 2020-03-04 21:14:42 UTC
Github openshift elasticsearch-operator pull 241 0 None closed Bug 1804169: set minKube version for 4.3 2020-03-04 21:14:42 UTC
Red Hat Product Errata RHBA-2020:0676 0 None None None 2020-03-10 23:54:11 UTC

Description Anping Li 2020-02-18 11:37:30 UTC 
+++ This bug was initially created as a clone of Bug #1804166 +++

Description of problem:

minKubeVersion is 1.14.0 in operator.v4.3.0.clusterserviceversion.yaml. It should be v1.16.0 (or v1.16.2)

elasticsearch-operator/4.3/elasticsearch-operator.v4.3.0.clusterserviceversion.yaml:  minKubeVersion: 1.14.0

cluster-logging/4.3/cluster-logging.v4.3.0.clusterserviceversion.yaml:  minKubeVersion: 1.14.0



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

How reproducible:
Alawys

Steps to Reproduce:
1. Check the minKubeVersion  in manifests.
2.
3.

Actual results:


Expected results:
Comment 3 Anping Li 2020-02-27 15:31:55 UTC 
Verified in clusterlogging.4.3.4-202002270831 and elasticsearch-operator.4.3.4-202002270831
Comment 5 errata-xmlrpc 2020-03-10 23:53:54 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:0676
Note You need to log in before you can comment on or make changes to this bug.