Bug 2024448

Summary: When ssh_authorized_keys is empty in form view it should not appear in yaml view
Product: OpenShift Container Platform Reporter: Yaacov Zamir <yzamir>
Component: Console Kubevirt PluginAssignee: Matan Schatzman <mschatzm>
Status: CLOSED ERRATA QA Contact: Guohua Ouyang <gouyang>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.8CC: aos-bugs, gouyang, tnisan
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-03-10 16:28:46 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
empty ssh_authorized_keys in the yaml view none

Description Yaacov Zamir 2021-11-18 06:47:25 UTC
Created attachment 1842499 [details]
empty ssh_authorized_keys in the yaml view

Description of problem:
When editing cloud init section using the create VM wizard, we can opt out filling the ssh_authorized_keys form item, but when editing the yaml view the ssh_authorized_keys is re-populated with empty string

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Use the wizard to create a VM and choose customize VM
2.Go to advanced section and choose cloud-init
3.in the form leave ssh_authorized_keys empty and toggle to yaml view

Actual results:
ssh_authorized_keys is set to empty string ''

Expected results:
no ssh_authorized_keys field in the yaml

Additional info:

Comment 2 Guohua Ouyang 2021-12-06 08:24:00 UTC
verified on 4.10.0-0.ci-2021-12-05-113922

Comment 6 errata-xmlrpc 2022-03-10 16:28:46 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 (Moderate: OpenShift Container Platform 4.10.3 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:0056