Bug 1786259

Summary: "Edit YAML" leads to 404 error on Create NAD page
Product: OpenShift Container Platform Reporter: Guohua Ouyang <gouyang>
Component: Console Kubevirt PluginAssignee: Phillip Bailey <phbailey>
Status: CLOSED ERRATA QA Contact: Nelly Credi <ncredi>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.3.0CC: aos-bugs, gouyang, spadgett
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-04 11:21:22 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:
Attachments:
Description Flags
nad edit none

Description Guohua Ouyang 2019-12-24 06:18:25 UTC
Created attachment 1647451 [details]
nad edit

Description of problem:
There is an "Edit YAML" on Create NAD page, click the button leads to a 404 page.
The button should be removed.

Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2019-12-19-050538

How reproducible:
100%

Steps to Reproduce:
1.In the web console, click Networking → Network Attachment Definitions.
2. Click Create Network Attachment Definition .
3.

Actual results:


Expected results:


Additional info:

Comment 1 Tomas Jelinek 2020-01-06 12:30:14 UTC
Actually the "edit yaml" button should still be there, just clicking it should not lead to 404 but to the yaml editor.

Comment 2 Guohua Ouyang 2020-01-07 02:56:44 UTC
Just checked other pages, like storage class, it has "edit yaml" as well. So it's okay to have this button.
Then it just needs to fix the 404 issue.

Comment 7 errata-xmlrpc 2020-05-04 11:21:22 UTC
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, 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-2020:0581