Bug 1915840

Summary: certificates are regenerated only when crt is missing.
Product: OpenShift Container Platform Reporter: Jeff Cantrill <jcantril>
Component: LoggingAssignee: Jeff Cantrill <jcantril>
Status: CLOSED ERRATA QA Contact: Anping Li <anli>
Severity: high Docs Contact:
Priority: high    
Version: 4.5CC: anli, aos-bugs, dahernan, gkarager, gparente, jcantril, jeder, ocasalsa, periklis, rrackow, syedriko, vlaad, wking
Target Milestone: ---Keywords: ServiceDeliveryImpact
Target Release: 4.5.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: logging-core
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1895607 Environment:
Last Closed: 2021-02-09 13:25:23 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: 1895607, 1906641    
Bug Blocks:    
Attachments:
Description Flags
Logging Upgrade failed from 4.4 to 4.5 none

Comment 3 Anping Li 2021-02-04 15:19:53 UTC
The fix wasn't built into 4.5.31 images.

Comment 5 Anping Li 2021-02-05 02:50:11 UTC
F

Comment 6 Anping Li 2021-02-05 03:55:52 UTC
Created attachment 1755170 [details]
Logging Upgrade failed from 4.4 to 4.5

The cluster-logging couldn't be upgraded to 4.5 
$ oc get csv
NAME                                           DISPLAY                  VERSION                 REPLACES                                       PHASE
clusterlogging.4.5.0-202102032236.p0           Cluster Logging          4.5.0-202102032236.p0   clusterlogging.4.4.0-202102021535.p0           Succeeded
elasticsearch-operator.4.5.0-202102041225.p0   Elasticsearch Operator   4.5.0-202102041225.p0   elasticsearch-operator.4.4.0-202102021535.p0   Succeeded

$ oc get pods
NAME                                            READY   STATUS                  RESTARTS   AGE
cluster-logging-operator-788bc9749-7zbc2        1/1     Running                 0          9m18s
curator-1612495800-8vmct                        0/1     Completed               0          13m
curator-1612496400-n2mgv                        0/1     Error                   0          3m26s
elasticsearch-cdm-e3nmr844-1-744596fbd9-clpwq   2/2     Running                 0          14m
elasticsearch-cdm-e3nmr844-2-578d7dbb9-npvm5    2/2     Running                 0          14m
elasticsearch-cdm-e3nmr844-3-746666c444-djlzv   2/2     Running                 0          14m
fluentd-9hmz6                                   1/1     Running                 0          14m
fluentd-md9p9                                   1/1     Running                 0          14m
fluentd-np7wx                                   1/1     Running                 0          14m
fluentd-rrwn9                                   1/1     Running                 0          14m
fluentd-rsh5b                                   1/1     Running                 0          14m
fluentd-vtkv5                                   0/1     Init:CrashLoopBackOff   6          8m51s
kibana-5495cfd8bd-khvnx                         2/2     Running                 0          8m49s

$oc logs 
$ oc logs fluentd-vtkv5
Error from server (BadRequest): container "fluentd" in pod "fluentd-vtkv5" is waiting to start: PodInitializing

Comment 7 Anping Li 2021-02-05 13:06:57 UTC
Please ignore commens 6. It turn of to be a partial upgrade status. The CLO was updated while EO is still 4.4

Comment 8 Anping Li 2021-02-05 13:19:54 UTC
Verified on clusterlogging.4.5.0-202102032236.p0.

Comment 10 errata-xmlrpc 2021-02-09 13:25:23 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 (OpenShift Container Platform 4.5.31 extras 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/RHBA-2021:0315