Bug 2090627 - Git commit and branch are empty in MetalLB log
Summary: Git commit and branch are empty in MetalLB log
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.11
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.11.0
Assignee: Sabina Aledort
QA Contact: Arti Sood
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-26 07:24 UTC by Sabina Aledort
Modified: 2022-08-10 11:14 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 11:14:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift metallb pull 55 0 None open Bug 2090627: Dockerfile: Set git commit and branch flags 2022-05-26 07:26:27 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:14:54 UTC

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
Note You need to log in before you can comment on or make changes to this bug.