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):
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"
"Username is required. must be a valid OS username"
Wizard understands capitalized usernames are valid in Windows OSes
Cloudbase-init default example case is to create a new administrator user called "Admin"
this is fixed in latest nightly.
please check @cwilkers
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.
(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.
(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.
did you try a linx vm ?
it looks like the bug is for linux vm as well ?
(In reply to Yaacov Zamir from comment #5)
> did you try a linx vm ?
> it looks like the bug is for linux vm as well ?
It's a bug for linux VM as well.
verified the bug for both windows and linux vm on master, it accepts username like "Administrator".
Apologies, but I am confused by the wording of the last update to this BZ.
To be clear, in Linux VMs, capitalized usernames are not valid, in Windows, they are.
The UI needs to allow a capitalized username for Windows based VMs, and raise an error if one is tried for a Linux VM.
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.