Misleading error message if VM name starts with a character in _0123456789-
#7234
Assignees
Labels
affects-4.1
This issue affects Qubes OS 4.1.
C: core
diagnosed
Technical diagnosis has been performed (see issue comments).
P: default
Priority: default. Default priority for new issues, to be replaced given sufficient information.
pr submitted
A pull request has been submitted for this issue.
T: bug
Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
ux
User experience
Comments
DemiMarie
added
T: bug
andrewdavidwong
added
the
diagnosed
|
The current regex logic for VM Name validation demands alphabet for the 1st character. Thus you can not choose It has to be decided if the current logic is fine or has to be changed to allow underscore and other forbidden characters as 1st character. Then the code could be fixed or the issue could be closed accordingly. |
alimirjamali
added a commit
to alimirjamali/qubes-core-admin
that referenced
this issue
Jul 5, 2024
alimirjamali
added a commit
to alimirjamali/qubes-core-admin
that referenced
this issue
Jul 5, 2024
andrewdavidwong
added
the
pr submitted
alimirjamali
added a commit
to alimirjamali/qubes-core-admin
that referenced
this issue
Jul 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How to file a helpful issue
Qubes OS release
R4.1
Brief summary
qvm-create _fails with “VM name contains illegal characters”, which is misleading since_is perfectly valid in a qube name.Steps to reproduce
qvm-create _Expected behavior
Better error message, such as “VM names cannot start with an underscore”
Actual behavior
Misleading error message
The text was updated successfully, but these errors were encountered: