Bug 1823465
| Summary: | keepalived virtual routerids can easily clash when running several clusters | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Victor Voronkov <vvoronko> |
| Component: | Installer | Assignee: | Antoni Segura Puimedon <asegurap> |
| Installer sub component: | OpenShift on Bare Metal IPI | QA Contact: | Aleksandra Malykhin <amalykhi> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | asegurap, bbennett, bperkins, kboumedh, kgarriso, smilner, stbenjam, vvoronko, yboaron |
| Version: | 4.4 | Keywords: | Triaged |
| Target Milestone: | --- | ||
| Target Release: | 4.4.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause:
There's a limited amount of Virtual Router IDs that can be used in a cluster. The Virtual Router IDs to be used in a cluster are computed from the cluster name.
Consequence:
It could be that the computed Virtual Router IDs conflicted with other Virtual Router IDs currently in use in the broadcast domain. This would generate conflicts in managing the Virtual IPs.
Fix:
Make a tool that shows which Virtual Router IDs would be used before starting the deployment.
Result:
The user can see the Virtual Router IDs and change the cluster name in case the generated IDs conflict with other Virtual Routers in the broadcast domain.
|
Story Points: | --- |
| Clone Of: | 1821667 | Environment: | |
| Last Closed: | 2020-06-02 11:17:47 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1821667 | ||
| Bug Blocks: | |||
|
Comment 3
Victor Voronkov
2020-04-20 08:45:44 UTC
Verified on 4.4.0-0.nightly-2020-05-25-115719
on master node:
[core@master-0-0 ~]$ sudo crictl exec $(sudo crictl ps --name keepalived-monitor | awk 'FNR==2{ print $1}') runtimecfg vr-ids cnf10
APIVirtualRouterID: 147
DNSVirtualRouterID: 158
IngressVirtualRouterID: 2
[core@master-0-0 ~]$ sudo crictl exec $(sudo crictl ps --name keepalived-monitor | awk 'FNR==2{ print $1}') runtimecfg vr-ids cnf11
APIVirtualRouterID: 228
DNSVirtualRouterID: 239
IngressVirtualRouterID: 147
Checked on external host by documentation provided here https://github.com/openshift/installer/blob/master/docs/user/metal/install_ipi.md
[~]# podman run quay.io/openshift/origin-baremetal-runtimecfg:4.4 vr-ids cnf11
APIVirtualRouterID: 228
DNSVirtualRouterID: 239
IngressVirtualRouterID: 147
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:2310 |