Loading...

XML

Word

Printable

Severity:
Informational
Story Points:
1
Sprint:
Sprint 225, Sprint 226, Sprint 227, Sprint 228
sprint_count:
4
Release Blocker:
Rejected
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Release Note Text:

Hide
Cause: The fix in OpenShift 4.11.0 for Bug 2094932 added a log statement with incorrect format.

Consequence: After an upgrade from OpenShift 4.10 to 4.11, the Ingress Operator would log the following string, including literal "%" formats: 'Patched %q ingress config defaultPlacement status to %q {"cluster": "Workers"}'.

Fix: The log format has been fixed.

Result: The Ingress Operator now logs the following: 'Patched ingress config defaultPlacement status {"cluster": "Workers"}'.

Show
Cause: The fix in OpenShift 4.11.0 for Bug 2094932 added a log statement with incorrect format. Consequence: After an upgrade from OpenShift 4.10 to 4.11, the Ingress Operator would log the following string, including literal "%" formats: 'Patched %q ingress config defaultPlacement status to %q {"cluster": "Workers"}'. Fix: The log format has been fixed. Result: The Ingress Operator now logs the following: 'Patched ingress config defaultPlacement status {"cluster": "Workers"}'.
Release Note Type:
Bug Fix
Target Version:

4.13.0

Description of problem:

The ingress operator has a log message with weird formatting during startup handleSingleNode4Dot11Upgrade function

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

4.11

How reproducible:

100%

Steps to Reproduce:

1. Install 4.10 single node cluster
2. Upgrade to 4.11

Actual results:

Ingress operator prints badly formatted log message

Expected results:

Ingress operator prints correctly formatted log message

Additional info:

links to