Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2096210

Summary: [Machines] Can not creating vm with Cloud base image with only user name configured
Product: Red Hat Enterprise Linux 9 Reporter: Xianghua Chen <xchen>
Component: cockpit-machinesAssignee: Simon Kobyda <skobyda>
Status: CLOSED ERRATA QA Contact: Xianghua Chen <xchen>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.1CC: hongzliu, juzhou, mmarusak, mpitt, qzhang, wshi, ymao, yunyang
Target Milestone: rcKeywords: Triaged
Target Release: 9.1Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cockpit-machines-273-1.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-15 10:19:39 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:

Description Xianghua Chen 2022-06-13 09:45:18 UTC
Description of problem:
[Machines] Can not creating vm with Cloud base image with only user name configured
 
Packages:
cockpit-machines-268-1.el9.noarch
cockpit-269-1.el9.x86_64
libvirt-8.4.0-1.el9.x86_64

How reproducible:
100%

Steps:
1 Prepare a cloud image like:
rhel-guest-image-9.0-20220420.0.x86_64.qcow2

2 Click "Create VM", on Details tab, configure as following:
Installation type:   "Cloud base image" 
Installation source: the image file prepared in step1 
Operating system:Red Hat Enterprise Linux 9 Unknown (9-unknown Plow)

3 Click Automation tab, configure as following:
User login:test123

Leave other fields as blank, click "Create and run"
The "Create and run" is disabled.

4. Fill in the "Uder password"
The Create and run is enabled again

Actual results:
As shown in step3 & step4

Expected results:
1. User should be able to create vm with only user login filled in step3
2. But if there is a reason and it's intended  not be able to create a vm with only uer login, then please keep this bug to give user some error or hint that it's not allowed, etc. otherwise they don't know what happened when "Create and run" is disabled

Additional info:

Comment 1 Hongzhou Liu 2022-06-13 10:48:40 UTC
Test this option on RHEL9.1

Packages:

# rpm -q virt-manager virt-install libvirt
virt-manager-3.2.0-14.el9.noarch
virt-install-3.2.0-14.el9.noarch
libvirt-8.4.0-1.el9.x86_64

Step1:
prepare a user-data file:
# cat user-data 
#cloud-config

chpasswd:

   list: |

       root:123456

   expire: false
Step2:Run the command below to set the root password to 123456, then login to the vm
# virt-install  --memory 4096 --disk /home/RHEL-9.1.0-20220612.2-x86_64.qcow2  --cloud-init user-data=./user-data --import

expected result: password for root is "123456"
actual result : password won't be changed

Please correct me if my step was wrong, thanks

Comment 2 Xianghua Chen 2022-06-13 12:26:02 UTC
(In reply to Hongzhou Liu from comment #1)
> Test this option on RHEL9.1
> 
> Packages:
> 
> # rpm -q virt-manager virt-install libvirt
> virt-manager-3.2.0-14.el9.noarch
> virt-install-3.2.0-14.el9.noarch
> libvirt-8.4.0-1.el9.x86_64
> 
> Step1:
> prepare a user-data file:
> # cat user-data 
> #cloud-config
> 
> chpasswd:
> 
>    list: |
> 
>        root:123456
> 
>    expire: false
> Step2:Run the command below to set the root password to 123456, then login
> to the vm
> # virt-install  --memory 4096 --disk
> /home/RHEL-9.1.0-20220612.2-x86_64.qcow2  --cloud-init user-data=./user-data
> --import
> 
> expected result: password for root is "123456"
> actual result : password won't be changed
> 
> Please correct me if my step was wrong, thanks

Thank you @hongzliu for your comment with details, I think these steps is reproducer for bug https://bugzilla.redhat.com/show_bug.cgi?id=2096200 , this bug is more about whether we can create vm with only user name setted, and may need some hint if it's not allowed on the UI.
Could you paste to the other bug I mentioned ? Thank you.

Comment 3 Hongzhou Liu 2022-06-17 02:30:51 UTC
(In reply to Xianghua Chen from comment #2)
> (In reply to Hongzhou Liu from comment #1)
> > Test this option on RHEL9.1
> > 
> > Packages:
> > 
> > # rpm -q virt-manager virt-install libvirt
> > virt-manager-3.2.0-14.el9.noarch
> > virt-install-3.2.0-14.el9.noarch
> > libvirt-8.4.0-1.el9.x86_64
> > 
> > Step1:
> > prepare a user-data file:
> > # cat user-data 
> > #cloud-config
> > 
> > chpasswd:
> > 
> >    list: |
> > 
> >        root:123456
> > 
> >    expire: false
> > Step2:Run the command below to set the root password to 123456, then login
> > to the vm
> > # virt-install  --memory 4096 --disk
> > /home/RHEL-9.1.0-20220612.2-x86_64.qcow2  --cloud-init user-data=./user-data
> > --import
> > 
> > expected result: password for root is "123456"
> > actual result : password won't be changed
> > 
> > Please correct me if my step was wrong, thanks
> 
> Thank you @hongzliu for your comment with details, I think these
> steps is reproducer for bug
> https://bugzilla.redhat.com/show_bug.cgi?id=2096200 , this bug is more about
> whether we can create vm with only user name setted, and may need some hint
> if it's not allowed on the UI.
> Could you paste to the other bug I mentioned ? Thank you.

Done https://bugzilla.redhat.com/show_bug.cgi?id=2096200#c3

Comment 4 Simon Kobyda 2022-07-20 00:21:58 UTC
Patch posted: https://github.com/cockpit-project/cockpit-machines/pull/768

Comment 8 Xianghua Chen 2022-08-28 10:56:28 UTC
Verified with packages:
cockpit-machines-273-1.el9.noarch
cockpit-275-1.el9.x86_64
libvirt-dbus-1.4.1-5.el9.x86_64
libvirt-daemon-8.5.0-5.el9.x86_64

Steps:
1 Prepare a cloud image like:
rhel-guest-image-9.0-20220420.0.x86_64.qcow2

2 Click "Create VM", on Details tab, configure as following:
Installation type:   "Cloud base image" 
Installation source: the image file prepared in step1 
Operating system:Red Hat Enterprise Linux 9 Unknown (9-unknown Plow)

3 Click Automation tab, configure as following:
User login:test123

Leave other fields as blank, click "Create and run"

There will be an hint under User password line like : 
User password must not be empty when user login is set

So verified.

But after that, if you input password again, it will enable "Password quality check" which was not at first, should be consistent.
Will file another bug for this issue as the issue in this bug is fixed and the other one is with low priority.

Comment 10 errata-xmlrpc 2022-11-15 10:19:39 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 (cockpit-machines bug fix and enhancement 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:8094