Bug 2091746
| Summary: | "Oh no! Something went wrong" shown after user creates MCP without 'spec' | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Xiyun Zhao <xiyuzhao> | |
| Component: | Management Console | Assignee: | Jakub Hadvig <jhadvig> | |
| Status: | CLOSED ERRATA | QA Contact: | Xiyun Zhao <xiyuzhao> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 4.11 | CC: | yapei | |
| Target Milestone: | --- | |||
| Target Release: | 4.11.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 2109346 (view as bug list) | Environment: | ||
| Last Closed: | 2022-08-10 11:15:13 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 2092832, 2109346 | |||
This bug has been verified on payload 4.11.0-0.nightly-2022-06-06-025509
Verification Step:
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. Check the result
Result:
3 1) User is able to create an MCP without ".spec" (not required parameter). Although the created MCP has no necessary information, it could be shown on the MCP list page correctly
Name Configuration Degraded Update status
example - Unknown ...
2) MachineConfigPools and ClusterSetting page is shown correctly without 404 or "Oh no! Something went wrong" error
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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/RHSA-2022:5069 |
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: