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 1588336 - "domifaddr --source arp" can not show correct netmask
Summary: "domifaddr --source arp" can not show correct netmask
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Michal Privoznik
QA Contact: chhu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-07 06:01 UTC by yalzhang@redhat.com
Modified: 2018-10-30 09:56 UTC (History)
5 users (show)

Fixed In Version: libvirt-4.5.0-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-30 09:55:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:3113 0 None None None 2018-10-30 09:56:51 UTC

Description yalzhang@redhat.com 2018-06-07 06:01:32 UTC 
Description of problem:
"domifaddr --source arp" can not show correct netmask

Version-Release number of selected component (if applicable):
libvirt-4.3.0-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Start a vm with interface as below:
<interface type='network'>
      <source network='default'/>
    </interface>
# virsh start rhel

2. check the vm's ip address, it shows the netmask as "/0" which is not correct
# virsh domifaddr rhel --source arp
 Name       MAC address          Protocol     Address
-------------------------------------------------------------------------------
 vnet0      52:54:00:03:fa:7d    ipv4         192.168.122.64/0


Actual results:
"domifaddr --source arp" can not show the netmask as "/0", should be "/24"

Expected results:
should show the Address as "192.168.122.64/24"

Additional info:
# virsh domifaddr rhel --source lease
 Name       MAC address          Protocol     Address
-------------------------------------------------------------------------------
 vnet0      52:54:00:03:fa:7d      ipv4         192.168.122.64/24
Comment 2 Michal Privoznik 2018-06-08 14:51:30 UTC 
Not sure if this is a bug. The documentation says '--source arp' parses ARP table. However, ARP does not have any sense of netmask. Just try 'cat /proc/net/arp'. So maybe we only need to document that not every method is capable of fetching all data.
Comment 3 Laine Stump 2018-06-08 17:33:57 UTC 
I came here to say essentially what Michal just said above. There is one possibility for getting the info, but it could be a bit involed - from the arp table you can learn the interface where the MAC is reachable. If you then search through the IP addresses configured for that interface and find the one that "contains" the IP in the ARP entry within its network, you'll have the proper prefix/netmask. (Not saying we *should* go to all that trouble for a piece of information that will almost certainly never be used, but we *could*. Changing the documentation is much simpler, and probably of just as much value to the users).
Comment 4 Michal Privoznik 2018-06-12 11:35:09 UTC 
Yeah, since I don't think ARP source is that valuable/accurate as the other two sources (leases file and agent) I don't think it's worth fixing any more than documentation.

Patch proposed upstream:

https://www.redhat.com/archives/libvir-list/2018-June/msg00931.html
Comment 5 Michal Privoznik 2018-06-13 07:19:33 UTC 
I've pushed the patch upstream:

commit d1605b5d99e847450a6cbbf752ae5dd76239b46f
Author:     Michal Privoznik <mprivozn>
AuthorDate: Tue Jun 12 13:13:06 2018 +0200
Commit:     Michal Privoznik <mprivozn>
CommitDate: Wed Jun 13 09:12:59 2018 +0200

    lib: Document limitation of virDomainInterfaceAddresses
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1588336
    
    This API takes @source argument which tells it where to get
    domain IP addresses from. However, not all sources are capable of
    providing all the information we report, for instance ARP table
    has no notion of IP address prefixes. Document this limitation.
    
    Signed-off-by: Michal Privoznik <mprivozn>
    Reviewed-by: Laine Stump <laine>

v4.4.0-234-gd1605b5d99
Comment 7 chhu 2018-09-13 07:25:21 UTC 
Verified on packages:
libvirt-4.5.0-9.el7.x86_64
libvirt-debuginfo-4.5.0-9.el7.x86_64

Test steps:
1. Install libvirt-debuginfo package

2. Check the libvirt source file: libvirt-domain.c line: 11805-11807 include the patch

# cd /usr/src/debug/libvirt-4.5.0/src/

# grep -rn VIR_DOMAIN_INTERFACE_ADDRESSES_SRC_ARP *
libvirt-domain.c:11799: * If @source is VIR_DOMAIN_INTERFACE_ADDRESSES_SRC_ARP, the host
libvirt-domain.c:11806: * might be unset (e.g. VIR_DOMAIN_INTERFACE_ADDRESSES_SRC_ARP does not
qemu/qemu_driver.c:20680:    case VIR_DOMAIN_INTERFACE_ADDRESSES_SRC_ARP:

Set the bug status to "VERIFIED"
Comment 9 errata-xmlrpc 2018-10-30 09:55:54 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/RHSA-2018:3113
Note You need to log in before you can comment on or make changes to this bug.