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 1750706 - vm's name could not be added into settings file
Summary: vm's name could not be added into settings file
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: virt-viewer
Version: 8.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Victor Toso
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1623756
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-10 09:59 UTC by zhoujunqin
Modified: 2020-12-20 08:46 UTC (History)
5 users (show)

Fixed In Version: virt-viewer-7.0-9.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1623756
Environment:
Last Closed: 2020-04-28 16:03:45 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1727 0 None None None 2020-04-28 16:03:47 UTC

Comment 3 Victor Toso 2019-11-13 14:44:23 UTC 
Issue is fixed but need to be backported. Moving to POST
Comment 5 zhoujunqin 2019-12-18 07:27:15 UTC 
I can reproduce with version:
virt-viewer-7.0-8.el8.x86_64

Then try to verify this bug with new build:
virt-viewer-7.0-9.el8.x86_64

Steps:
1. Make sure there is a running guest:
# virsh dominfo spice
Id:             1
Name:           spice
UUID:           0f247bbd-ee54-4225-840e-0207402724fc
OS Type:        hvm
State:          running
...

2. Edit the virt-viewer setting file, and add uuid to the setting file, then add a comment before uuid.

Test scenario-1: Comment content doesn't contain the $guest-name string

2.1.1 
$ cat .config/virt-viewer/settings 
[virt-viewer]
ask-quit=false

#test-comment
[0f247bbd-ee54-4225-840e-0207402724fc]

2.1.2 After edit the file, use virt-viewer connect the guest
$ virt-viewer -c qemu:///system spice

2.1.3 Close virt-viewer window, and check the setting file
$ cat .config/virt-viewer/settings 
[virt-viewer]
ask-quit=false

#test-comment

#spice
[0f247bbd-ee54-4225-840e-0207402724fc]

Result: VM's name is added before its uuid successfully.

Test scenario-2: Comment content contains the $guest-name string

2.2.1
$ cat .config/virt-viewer/settings 
[virt-viewer]
ask-quit=false

#testspice
[0f247bbd-ee54-4225-840e-0207402724fc]

2.1.2 After edit the file, use virt-viewer connect the guest
$ virt-viewer -c qemu:///system spice

2.1.3 Close virt-viewer window, and check the setting file
$ cat .config/virt-viewer/settings 
[virt-viewer]
ask-quit=false

#testspice

[0f247bbd-ee54-4225-840e-0207402724fc]


Result: VM's name isn't added again, it's as expected.

So I move this bug from ON_QA to VERIFIED based on above testing.
Comment 7 errata-xmlrpc 2020-04-28 16:03:45 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, 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-2020:1727
Note You need to log in before you can comment on or make changes to this bug.