+++ This bug was initially created as a clone of Bug #2091746 +++ Description of problem: The page MCP will be down, after user creates a MachineConfigPool (in YAML) without properties ‘spec', "Oh no! Something went wrong" will be shown on the page Version-Release number of selected component (if applicable): 4.11.0-0.nightly-2022-05-25-193227 How reproducible: Always Steps to Reproduce: 1. Login OCP, navigate to Compute -> MachineConfigPools page 2. Click "Create MachineConfigPool" button, create with below format apiVersion: machineconfiguration.openshift.io/v1 kind: MachineConfigPool metadata: name: example 3. Actual results: 2.1. "Oh no! Something went wrong" will be shown on the page 2.2. The MCP page will be broken with upon error unless the user deletes the issue MCP with command through CLI $ oc delete mcp example Expected results: 2. Console should not allow users to create MCP without "spec" in Console or through CLI Additional info:
@jhadvig Please help to double check if this issue has any conflict on OCP4.10 code level This issue has failed to verify on payload 4.10.0-0.nightly-2022-07-19-210744 Cluster setting page will crash after create MVP without spec attribute
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-9298