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 1377244 - --show-DIALOG-WINDOW doesn't imply --no-conn-autostart option
Summary: --show-DIALOG-WINDOW doesn't imply --no-conn-autostart option
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-manager
Version: 7.3
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Pavel Hrdina
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-19 09:45 UTC by Xiaodai Wang
Modified: 2017-08-01 21:02 UTC (History)
4 users (show)

Fixed In Version: virt-manager-1.4.1-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 21:02:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2072 0 normal SHIPPED_LIVE virt-manager bug fix and enhancement update 2017-08-01 18:36:34 UTC

Description Xiaodai Wang 2016-09-19 09:45:06 UTC 
Description of problem:
--show-DIALOG-WINDOW doesn't imply --no-conn-autostart option

Version-Release number of selected component (if applicable):
virt-manager-1.4.0-2.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Check man page of virt-manager, --show-DIALOG-WINDOW implies --no-conn-autostart.
       --show-DIALOG-WINDOW
           Display the corresponding "DIALOG-WINDOW" when launching "virt-manager". This function implies --no-conn-autostart and the manager window will not be shown at startup in this
           case.
2. Add two connections by virt-manager and make them auto connect.
3. Run "virt-manager --show-DIALOG-WINDOW -c qemu:///system"

Actual results:
A dialog pops up and asks for another connection's password to connect after connecting to qemu:///system.

Expected results:
--no-conn-autostart should be implied and only qemu:///system should be connected.

Additional info
Comment 1 Pavel Hrdina 2017-01-17 16:59:35 UTC 
Upstream commit:

commit ceda7a5dbfcd9b94bbe65916e7f41f213d9d3629
Author: Pavel Hrdina <phrdina>
Date:   Tue Jan 17 15:34:14 2017 +0100

    virt-manager: don't autostart other connection if --show-* was specified
Comment 3 zhoujunqin 2017-03-16 09:45:57 UTC 
I can reproduce this bug with package:
virt-manager-1.4.0-2.el7.noarch

Then try to verify this bug with new build:
virt-manager-1.4.1-1.el7.noarch
virt-install-1.4.1-1.el7.noarch
virt-manager-common-1.4.1-1.el7.noarch
libvirt-3.1.0-2.el7.x86_64

Steps:
Scenario-1 Quit whole virt-manager window.
1. Add two connections by virt-manager and make them Autoconnect.
   eg: QEMU/KVM & QEMU/KVM: 10.66.4.XX
   Then close virt-manager.
2. Run "virt-manager --show-DIALOG-WINDOW -c qemu:///system".
2.1 
# virt-manager  -c qemu:///system --show-domain-creator
Result: Just "New VM(on localhost.localdomain)" window pops up.
2.2
# virt-manager -c qemu:///system --show-domain-editor=myVm2raw
Result: Vm details window pop up.
2.3
# virt-manager -c qemu:///system --show-domain-performance=myVm2raw
Result: Vm details window pop up and show performance tab.
2.4
# virt-manager -c qemu:///system --show-domain-console=myVm2raw
Result: Vm's console pop up
2.5
# virt-manager -c qemu:///system --show-host-summary
Result:  Host details window pop up and show overview tab.

Result:No dialog pops up and asks for another connection's password to connect after connecting to qemu:///system.


Scenario-2 Leave virt-manger main window.
1. Add two connections by virt-manager and make them Autoconnect.
   eg: QEMU/KVM & QEMU/KVM: 10.66.4.XX
   Then disconnect both connections(by right click connection->click "Disconnect")

2. Run "virt-manager --show-DIALOG-WINDOW -c qemu:///system".
2.1 # virt-manager  -c qemu:///system --show-domain-creator
Result: 2.1.1 "New VM(on localhost.localdomain)" window pops up.
        2.2.2 No dialog pops up and asks for another connection's password to connect after connecting to qemu:///system in virt-manager main window.
2.2 Disconnect connection "QEMU/KVM", then Repeat step2.2 to step2.5 in Scenario-1 again.

Result: No dialog pops up and asks for another connection's password to connect after connecting to qemu:///system.

So move this bug from ON_QA to VERIFIED.
Comment 4 errata-xmlrpc 2017-08-01 21:02:03 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-2017:2072
Note You need to log in before you can comment on or make changes to this bug.