Bug 1931529 - SNO: mentioning of 4 nodes in error message - Cluster network CIDR prefix 24 does not contain enough addresses for 4 hosts each one with 25 prefix (128 addresses)
Summary: SNO: mentioning of 4 nodes in error message - Cluster network CIDR prefix 24 ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: assisted-installer
Version: 4.8
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.8.0
Assignee: vemporop
QA Contact: Yuri Obshansky
URL:
Whiteboard: AI-Team-Core
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-22 16:08 UTC by Alexander Chuzhoy
Modified: 2021-07-27 22:48 UTC (History)
2 users (show)

Fixed In Version: OCP-Metal-v1.0.19.1
Doc Type: Bug Fix
Doc Text:
Cause: When calculating network per host, it was assumed that a cluster cannot be made up of less than three nodes. This assumption became incorrect after the introduction of single-node OpenShift (SNO). Consequence: A user could not use a network prefix that was sufficient for a single-node cluster. Fix: One node is now accepted as a valid cluster size for the network size calculation. Result: When creating a cluster, it is possible to specify a CIDR and network prefix that provide just enough addresses for a single-node cluster, even if they are not sufficient for three nodes.
Clone Of:
Environment:
Last Closed: 2021-07-27 22:47:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:48:13 UTC

Description Alexander Chuzhoy 2021-02-22 16:08:15 UTC 
Version:
Application Path:
    /openshift/assisted-installer/clusters/090f8ca9-7e61-4809-95b6-aab1c67d07c7
Chrome Version:
    485700e169f5bbfc1243cc0c6d6546ae095351c6
Dashboard Version:
    4a22a325b15bc52105800c6c962465d12f97c420
Inventory Version:
    f4da32fba7a46cda8f2fbbc1a964e400f5d85920
Remediations Version:
    db6236b2cd8acacbe7be94f66d36ec5f6abe9329
Vulnerability Version:
    f75b1cae3deaea53672447367deba6dbfc04c959
Compliance Version:
    71dda364bc4169f6a2460bf1b427c84567504648
Cost Management Version:
    208cf56c7d466a10efde5ec70191ec931299c63c
Advisor Version:
    7406c3730539344a9872ec59a19c166c9b6023ec
Drift Version:
    ffd062b81d8304542d0ae7f14c3a3bfd6316e47a
Migration Analytics Version:
    0d3e6ed385c4607ecd9991f4dfe5d47e1ea5937e
Automation Hub Version:
    9f9b2d0222c37b2deead557f2dcf180220cf9014
Automation Analytics Version:
    870555ac74c256974c26b79e0b0318f49bad26b5
Policies Version:
    8b8cb5c60ea4a8ab1cf9f2866f86d7885f1ffcc1
Patch Version:
    67108faa326bd2fabaa1e45a3ee942e9649cc752
Automation Services Catalog Version:
    fa11ef1161aea9d11bc025b45642fa8c3b3b2b8a
Approval Version:
    fca5bcc816e921d25c96194ce2a5824116045cfb
Sources Version:
    ce2768b40fa822c375812541db2d961dbd7c181e


Steps to reproduce:
Attempt to create an SNO cluster:
1. Cluster Network CIDR : 10.10.10.0/24
2. Set Cluster Network Host Prefix  to 25
3. Try to validate the cluster.



Result:
Danger alert:Failed to update the cluster
Cluster network CIDR prefix 24 does not contain enough addresses for 4 hosts each one with 25 prefix (128 addresses)

Expected result:
we only have 1 node with SNO, why 4 nodes are mentioned.
Comment 1 Alexander Chuzhoy 2021-05-03 18:50:46 UTC 
Version:
Assisted-ui-lib version:  1.5.19


Was able to set the "Cluster Network CIDR" to 10.10.10.0/24 and "Cluster Network Host Prefix" to 25.
The validation passed.
Comment 4 errata-xmlrpc 2021-07-27 22:47:38 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.