Bug 2091402 - cloud-init User check for Windows VM refuses to accept capitalized usernames
Summary: cloud-init User check for Windows VM refuses to accept capitalized usernames
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.10.z
Assignee: Yaacov Zamir
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On: 2081201
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-29 14:59 UTC by OpenShift BugZilla Robot
Modified: 2022-06-07 13:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-07 13:24:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 11592 0 None Merged [release-4.10] Bug 2091402: cloud-init User check for Windows VM refuses to accept capitalized 2022-05-31 17:38:57 UTC
Red Hat Product Errata RHBA-2022:4882 0 None None None 2022-06-07 13:24:51 UTC

Description OpenShift BugZilla Robot 2022-05-29 14:59:38 UTC
+++ This bug was initially created as a clone of Bug #2081201 +++

Description of problem:
With a Win2k19 image, trying to set up cloudbase-init, using the wizard to create a VM with cloud-init yields an error trying to provision the default (for cloudbase-init) "Admin" user with error: "Username is required. must be a valid OS username"

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

How reproducible:
Always

Steps to Reproduce:
1. Create Windows (2k19) VM with wizard
2. Customize VM and visit Advanced pane
3. Click cloud-init
4. Try to set User to "Admin"

Actual results:
"Username is required. must be a valid OS username"

Expected results:
Wizard understands capitalized usernames are valid in Windows OSes

Additional info:
Cloudbase-init default example case is to create a new administrator user called "Admin"

--- Additional comment from glekner on 2022-05-17 06:53:02 UTC ---

this is fixed in latest nightly.
please check @cwilkers

--- Additional comment from cwilkers on 2022-05-18 14:59:50 UTC ---

Do you need for me to test it in nightly before it can be put into a release, or will it be released in 4.10.1?
I don't quite have capacity at the moment to reinstall to a nightly.

--- Additional comment from gouyang on 2022-05-25 08:31:02 UTC ---

(In reply to Chandler Wilkerson from comment #2)
> Do you need for me to test it in nightly before it can be put into a
> release, or will it be released in 4.10.1?
> I don't quite have capacity at the moment to reinstall to a nightly.

QE will test it.

--- Additional comment from gouyang on 2022-05-26 03:07:52 UTC ---

(In reply to Gilad Lekner from comment #1)
> this is fixed in latest nightly.
> please check @cwilkers

The issue does not exist on kubevirt-ui, but exists on openshift/console.

--- Additional comment from yzamir on 2022-05-29 09:38:06 UTC ---

did you try a linx vm ?
it looks like the bug is for linux vm as well ?

Comment 2 Leon Kladnitsky 2022-06-01 00:01:11 UTC
Verified on v4.10.15

Comment 5 errata-xmlrpc 2022-06-07 13:24:31 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 (OpenShift Container Platform 4.10.17 bug fix 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/RHBA-2022:4882


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