Bug 1836607 - arping exits with error when should not
Summary: arping exits with error when should not
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: iputils
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-17 08:45 UTC by Ido Schimmel
Modified: 2020-12-07 01:15 UTC (History)
3 users (show)

Fixed In Version: iputils-20200821-1.fc33 iputils-20200821-1.fc32
Clone Of:
Environment:
Last Closed: 2020-11-03 00:59:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ido Schimmel 2020-05-17 08:45:36 UTC
Description of problem:

arping exits with error when it in fact received the correct number of replies. This is broken in Fedora 31 that uses iputils-20190515. Should be broken in Fedora 32 and 33 as they use the same version.

Fixed in upstream by commit [1]. Please consider updating the package.

Version-Release number of selected component (if applicable):

iputils-20190515

How reproducible:

Always

Steps to Reproduce:

With broken version:

```
# arping -V
arping from iputils s20190515-14-g368c345

# arping -I swp5 -b -c 1 -w 1 10.1.1.102
ARPING 10.1.1.102 from 10.1.1.101 swp5
Unicast reply from 10.1.1.102 [B6:40:AE:F6:F6:95]  0.677ms
Sent 1 probes (1 broadcast(s))
Received 1 response(s)

# echo $?
1
```

With the fix from commit [1]:

```
# arping -V
arping from iputils s20190515-15-g84ca65c

# arping -I swp5 -b -c 1 -w 1 10.1.1.102
ARPING 10.1.1.102 from 10.1.1.101 swp5
Unicast reply from 10.1.1.102 [B6:40:AE:F6:F6:95]  0.709ms
Sent 1 probes (1 broadcast(s))
Received 1 response(s)

# echo $?
0
```

Additional info:

[1] https://github.com/iputils/iputils/commit/84ca65ca980315c73f929fed8b6f16bbd698c3a0#diff-f160be89ab84bdd931aff275599e905c

Comment 1 Fedora Admin user for bugzilla script actions 2020-10-29 14:57:24 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 2 Fedora Admin user for bugzilla script actions 2020-10-30 02:52:59 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 3 Fedora Update System 2020-11-01 00:12:21 UTC
FEDORA-2020-96bb0deb25 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-96bb0deb25

Comment 4 Fedora Update System 2020-11-01 00:12:22 UTC
FEDORA-2020-e049168198 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-e049168198

Comment 5 Fedora Update System 2020-11-01 01:08:11 UTC
FEDORA-2020-e049168198 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-e049168198`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-e049168198

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2020-11-01 01:09:35 UTC
FEDORA-2020-96bb0deb25 has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-96bb0deb25`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-96bb0deb25

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2020-11-03 00:59:45 UTC
FEDORA-2020-96bb0deb25 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2020-12-07 01:15:55 UTC
FEDORA-2020-e049168198 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.