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.

Description of problem:
[Machines] The custom path was changed back to dir after press enter twice

Version-Release number of selected components (if applicable):
cockpit-machines-249-1.el9.noarch
cockpit-250-1.el9.x86_64
libvirt-dbus-1.4.1-4.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Prepare a vm, prepare a img file like:
# touch /tmp/fake.img
2. Click Add disk on vm details page, choose Custom path
Input /tmp/fake.img in Custom path field, and press enter
The img file was correctly shown as /tmp/fake.img after press enter.
3. Press enter twice 

Actual results:
In step3, the img file was changed back to /tmp/

Expected results:
In step3, the img file should not be changed again 

Additional info:

This is the exact same behavior that the component we use from Patternfly library has. https://www.patternfly.org/v4/components/select/#typeahead
Opened an issue to the relevant product - https://github.com/patternfly/patternfly-react/issues/6245 - feel free to track this there.

https://github.com/patternfly/patternfly-react/issues/6245 has landed and is now included. I just tested it and hitting enter multiple times does not have this unwanted behavior anymore.

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 vm, prepare a img file like:
# touch /tmp/fake.img
2. Click Add disk on vm details page, choose Custom path
Input /tmp/fake.img in Custom path field, and press enter
The img file was correctly shown as /tmp/fake.img after press enter.
3. Press enter twice 

The img file won't change in step3, so verified.

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