Bug 2101423

Summary: wrong user name on using ignition
Product: Container Native Virtualization (CNV) Reporter: Dominik Holler <dholler>
Component: User ExperienceAssignee: Hilda Stastna <hstastna>
Status: CLOSED ERRATA QA Contact: Guohua Ouyang <gouyang>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.11.0CC: gouyang, upalatuc, ycui
Target Milestone: ---   
Target Release: 4.12.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: 2023-01-24 13:36:58 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
screenshot
none
yaml for vm none

Description Dominik Holler 2022-06-27 12:59:09 UTC
Created attachment 1892953 [details]
screenshot

Description of problem: On creating a RHCOS VM, in the "Guest login credentials" the username is shown as "[".


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

How reproducible:
100%

Steps to Reproduce:
1. create VM from attached yaml
2. have a look at the guest credentials in the "Console" tab
3.

Actual results:
User name: [



Expected results:
User name: coreos
or
"Ignition not supported"
or
No guest credentials shown

Additional info:

Comment 1 Dominik Holler 2022-06-27 12:59:47 UTC
Created attachment 1892954 [details]
yaml for vm

Comment 2 Ugo Palatucci 2022-07-08 14:02:09 UTC
Is there some documentation about this type of userData format (JSON)?

Comment 3 Dominik Holler 2022-07-12 14:55:54 UTC
(In reply to Ugo Palatucci from comment #2)
> Is there some documentation about this type of userData format (JSON)?

The format is ignition, please find the documentation in https://coreos.github.io/ignition/configuration-v3_3/ .

Comment 4 Guohua Ouyang 2022-08-19 00:39:41 UTC
verified on v4.12.0-106

Comment 8 errata-xmlrpc 2023-01-24 13:36:58 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 (Important: OpenShift Virtualization 4.12.0 Images 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-2023:0408