Version: $ openshift-install version 4.9.25 Platform: AWS IPI What happened? When provisioning a cluster using pre-provisioned VPC/subnets, if the dhcp-options-set is misconfigured for the subnet, installation will fail with no detailed error beyond bootstrap failed. For example, if you use the following dhcp-options-set that lacks DNS server configuration, installation will not complete: aws ec2 create-dhcp-options --dhcp-configurations '[{"Key":"domain-name","Values":["ec2.internal"]}]' What did you expect to happen? The installer to do either pre-flight verification that basic settings like DNS don't work, or the installer to provide guidance as to what part of the installation failed in order to allow the user to diagnose and correct it. How to reproduce it (as minimally and precisely as possible)? Create a VPC/subnets with default settings, but create a faulty DHCP options set above. Pass the subnets into the openshift-installer, and proceed with an IPI install with default settings.
Linking https://bugzilla.redhat.com/show_bug.cgi?id=2072195 here
This should be solved via https://github.com/openshift/installer/pull/5816
Verified on 4.13.0-0.nightly-2023-01-27-051537 Reproduce the issue on 4.9.25-x86_64. The issue was successfully reproduced.And on 4.13.0-0.nightly-2023-01-27-051537, the installer successfully provides guidance for the failed part of the installation.
But when I verify the bug, I notice that the error result of the release image to be verified is the same as the error result of its previous release image that without fixing the bug. Verification release image:4.13.0-0.nightly-2023-01-27-051537 Unfixed bug release image:4.13.0-0.nightly-2023-01-24-061922 My verification steps are as follows: 1.Use the following command to create a dhcp-options-set that lacks DNS server configuration aws ec2 create-dhcp-options --dhcp-configurations '[{"Key":"domain-name","Values":["ec2.internal"]}]' 2.Create a vpc aws cloudformation create-stack --stack-name shaozhanteststack --region us-east-2 --template-body file://01_vpc.yaml 3.Change the dhcp-options-set associated with the vpc Modify the dhcp-options-set of my vpc in the Amazon VPC console. 4.Creating a installation configuration file ./openshift-install create install-config --dir cluster 5.Customize the installation configuration file to specify subnets created above vi cluster/install-config.yaml 6.Deploying the cluster ./openshift-install create cluster --dir cluster
Adding dhcp-options-set that lacks DNS server configuration will cause bootstrap instance fetching ignition file fail, so it looks like the PR 6611 is not a solution for Bug 2072202.
OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira. https://issues.redhat.com/browse/OCPBUGS-9207