Bug 1786016 - AWS subnet prefix is ​​created with 4 added to the CIDR of the VPC when installing a cluster on AWS using IPI.
Summary: AWS subnet prefix is ​​created with 4 added to the CIDR of the VPC when insta...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.2.z
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Abhinav Dahiya
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-23 06:01 UTC by ryoji noma
Modified: 2023-03-24 16:33 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-23 13:17:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description ryoji noma 2019-12-23 06:01:30 UTC
Description of problem:
When installing a cluster on AWS using IPI, the VPC CIDR is created with machine CIDR. And subnet prefixes are ​​created with 4 added to the CIDR of the VPC. But there aren't document about subnet prefix. Is this behavior intended?
 
Version-Release number of selected component (if applicable):
openshift4.2
 
How reproducible:
Steps to Reproduce:
1.edit machineCIDR of install-cinfig.yaml.
ex) 10.105.0.0/20
2. ./openshift-install create cluster
3.confirm the prefix of the private and public subnet.
 
Actual results:
CIDR of private and public subnet is created as 10.105.X.0/24.
If edit machineCIDR to 10.105.0.0/16, CIDR of the private and public subnet are created as 10.105.X.0/20.
If edit machineCIDR to 10.105.0.0/19, CIDR of the private and public subnet are created as 10.105.X.0/23.
Is it the intended behavior? I couldn't find any documentation about this behavior.

Comment 1 Scott Dodson 2019-12-23 13:17:13 UTC
Yes, that's correct, each zone gets its own subnet therefore we need to subdivide the machineCIDR to allocate them.


Note You need to log in before you can comment on or make changes to this bug.