Bug 1803766

Summary:	Remove glog package in favor of klog
Product:	OpenShift Container Platform	Reporter:	Alexander Demicev <ademicev>
Component:	Cloud Compute	Assignee:	Alexander Demicev <ademicev>
Cloud Compute sub component:	BareMetal Provider	QA Contact:	Milind Yadav <miyadav>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	stbenjam
Version:	4.4
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-08-27 22:34:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alexander Demicev 2020-02-17 11:47:48 UTC

Description of problem:
We are using 2 different logging libraries for no reason. One of them should be removed


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Milind Yadav 2020-03-11 06:38:51 UTC

Steps 

Validated few logs printed on console , seems good .

[miyadav@miyadav bugs1104]$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.5.0-0.nightly-2020-03-10-204444   True        False         62m     Cluster version is 4.5.0-0.nightly-2020-03-10-204444
[miyadav@miyadav bugs1104]$ 
Some commands ran to validate :

oc logs -f cluster-autoscaler-operator-d979c885c-mrvc7 -c cluster-autoscaler-operator 

oc logs -f machine-api-controllers-64f5d7dfc-pwff8 -c machine-controller 

Actual : logs worked as expected
Expected : logs printed

Comment 4 Luke Meyer 2020-08-27 22:34:56 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:2409'