Description of problem: I created a cluster with "cpu_architecture": "arm64" and "user_managed_networking": false. The cluster was created, and set the user_managed_networking to "true" to enforce the requirement that all ARM clusters will be none-platform. According to MGMT-7484 and PR 2502, I should have gotten an error: "disabling User Managed Networking is not allowed for clusters with non-x86_64 CPU architecture" Version-Release number of selected component (if applicable): Integration environment Sep. 15th How reproducible: 100% Steps to Reproduce: 1. Create a cluster with "cpu_architecture": "arm64" and "user_managed_networking": false Actual results: No error. Cluster was created, but the user_managed_networking was "fixed" for you to "true". Expected results: Error
Hi Udi, Can you please attach the full request for cluster creation? If 'high_availability_mode' was set to 'None', then it's an expected behaviour. As it implies enabled 'user_managed_networking' (regardless of architecture): https://github.com/openshift/assisted-service/blob/967ff04c03836a50afe36ffac7035ff7cc140181/internal/bminventory/inventory.go#L447 So when only 'user_managed_networking' is set to false, the following error should be returned: "Non x86_64 CPU architectures are supported only with User Managed Networking"
The request body was: { "base_dns_domain": "qe.lab.redhat.com", "cpu_architecture": "arm64", "feature_usage": "{\"SNO\":{\"name\":\"SNO\"}}", "high_availability_mode": "None", "kind": "Cluster", "name": "arm-cluster", "ocp_release_image": "https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/pre-release/4.9.0-rc.4/rhcos-4.9.0-rc.4-x86_64-live.x86_64.iso", "openshift_version": "4.9", "user_managed_networking": false, "vip_dhcp_allocation": false, "pull_secret": "..." } If I don't specify "high_availability_mode: None", I get: "Non x86_64 CPU architectures are supported only with User Managed Networking" I propose also returning a descriptive error when the user sets both "high_availability_mode: None" and "user_managed_networking": false. The error should indicate that these setting contradict.
Daniel, I still don't get an error when I set both "high_availability_mode: None" and "user_managed_networking: false". Do we not want to report that the two settings contradict?
No error is returned, so I'm marking this bug back as "assigned".
(In reply to Udi Kalifon from comment #5) > Daniel, I still don't get an error when I set both "high_availability_mode: > None" and "user_managed_networking: false". Do we not want to report that > the two settings contradict? You should get the following error in this scenario: "User Managed Networking must be enabled on single node OpenShift" The fix is available in integ, so moving to MODIFIED for verifying in the upcoming build.
Verified: { "code": "400", "href": "", "id": 400, "kind": "Error", "reason": "Non x86_64 CPU architectures are supported only with User Managed Networking" }
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 (OpenShift Container Platform 4.9.7 bug fix 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/RHBA-2021:4579