Bug 1871770 - [IPI baremetal] The Keepalived.conf file is not indented evenly
Summary: [IPI baremetal] The Keepalived.conf file is not indented evenly
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.6
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.8.0
Assignee: Ben Nemec
QA Contact: Michael Nguyen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-24 08:57 UTC by Nataf Sharabi
Modified: 2021-07-27 22:33 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-27 22:32:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift machine-config-operator pull 2409 0 None open Bug 1871770: Remove extraneous whitespace from keepalived peer list 2021-02-17 08:25:06 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:33:31 UTC

Description Nataf Sharabi 2020-08-24 08:57:29 UTC 
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 5 Ben Nemec 2021-02-11 21:39:53 UTC 
From what I can see, IPs are listed in order of the nodes (master-0, master-1, master-2, worker-0, etc.) which I think makes sense. So I guess the only thing that needs to be cleaned up is the whitespace?
Comment 14 errata-xmlrpc 2021-07-27 22:32:47 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 (Moderate: OpenShift Container Platform 4.8.2 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-2021:2438
Note You need to log in before you can comment on or make changes to this bug.