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 1094628 - The connection name shows incorrect for remote ipv6 host
Summary: The connection name shows incorrect for remote ipv6 host
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager
Version: 6.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Giuseppe Scrivano
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1094631
TreeView+ depends on / blocked
 
Reported: 2014-05-06 07:51 UTC by tingting zheng
Modified: 2015-03-05 09:11 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1094631 (view as bug list)
Environment:
Last Closed: 2014-05-08 17:50:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
sceenshot of connection name issue (78.72 KB, image/png)
2014-05-06 07:51 UTC, tingting zheng 		no flags Details
View All

Description tingting zheng 2014-05-06 07:51:24 UTC 
Created attachment 892797 [details]
sceenshot of connection name issue

Description
The connection name shows incorrect for remote ipv6 host

Version:
virt-manager-0.9.0-20.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.On Client host,configure ipv6 global addr
#ifconfig eth0 inet6 add 3ffe::101/64

2.On Server1 host,configure ipv6 global addr
#ifconfig eth0 inet6 add 3ffe::102/64

3.On Server2 host,configure ipv6 global addr
#ifconfig eth0 inet6 add 3ffe::103/64

3.On client host,launch virt-manager to add server1 as remote ipv6 connection.

4."File"->"Add connection"->"Hypervisor(QEMU/KVM)->"Connect to remote host"->"method(ssh)->"Hostname([3ffe::102])->"Connect".

5.After the connection created,the connection shows as: [3ffe (QEMU)

6.Add server2 as remote ipv6 connection,after the connection created,the connection shows as: [3ffe (QEMU),which is misleading as the connection name is the same as server1,details see the screenshot.

Actual results：
As description,host [3ffe::102] and host [3ffe::103] shows the same connection name as [3ffe (QEMU).

Expected results:
The connection name shows correct for remote ipv6 host,and different host shows different host name,eg:host [3ffe::102] shows as [3ffe::102](QEMU)

Additional info:
Details see the screenshot.
Comment 2 Giuseppe Scrivano 2014-05-08 17:50:05 UTC 
closing as a duplicate as the patch for 870383 fixes also this problem.

*** This bug has been marked as a duplicate of bug 870383 ***
Comment 3 Cui Lei 2014-06-24 09:52:29 UTC 
As this issue was submitted before bug 870383, we should close it as 'CURRENTRELEASE'
Note You need to log in before you can comment on or make changes to this bug.