Bug 2092832 - "Oh no! Something went wrong" shown after user creates MCP without 'spec'
Summary: "Oh no! Something went wrong" shown after user creates MCP without 'spec'
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.11
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.z
Assignee: Jakub Hadvig
QA Contact: Xiyun Zhao
Depends On: 2091746
TreeView+ depends on / blocked
Reported: 2022-06-02 10:33 UTC by OpenShift BugZilla Robot
Modified: 2023-03-09 01:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2023-03-09 01:20:37 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console pull 11629 0 None open [release-4.10] Bug 2092832: Check if spec is available in MCP details page 2022-07-08 08:18:58 UTC

Description OpenShift BugZilla Robot 2022-06-02 10:33:07 UTC
+++ 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):

How reproducible:

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
  name: example   

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:

Comment 4 Xiyun Zhao 2022-07-21 02:44:23 UTC
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

Comment 6 Shiftzilla 2023-03-09 01:20:37 UTC
OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira.


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