Bug 2090627

Summary: Git commit and branch are empty in MetalLB log
Product: OpenShift Container Platform Reporter: Sabina Aledort <saledort>
Component: NetworkingAssignee: Sabina Aledort <saledort>
Networking sub component: Metal LB QA Contact: Arti Sood <asood>
Status: CLOSED ERRATA Docs Contact:
Severity: low    
Priority: low    
Version: 4.11   
Target Milestone: ---   
Target Release: 4.11.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: 2022-08-10 11:14:33 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 Sabina Aledort 2022-05-26 07:24:44 UTC 
Description of problem:
Git commit and branch are empty in MetalLB controller and speaker logs.

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

How reproducible:
Deploy MetalLB 4.11.

Steps to Reproduce:
1. Deploy MetalLB 4.11.
2. View MetalLB controller and speaker logs.

Actual results:
From MetalLB controller log:
{"branch":"","caller":"main.go:137","commit":"","goversion":"gc / go1.18 / amd64","level":"info","msg":"MetalLB controller starting (commit 9ca1249c331e3f823a885fd8bd4fa7cc650fe51a, branch main)","ts":"2022-05-23T19:03:04Z","version":""}

Expected results:
Git commit and branch should not be empty in MetalLB controller and speaker logs.
Comment 4 errata-xmlrpc 2022-08-10 11:14:33 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.11.0 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.

https://access.redhat.com/errata/RHSA-2022:5069