What were you trying to do that didn't work?

RHEL 8 versions of MTR produce the below error when unexpected conditions are seen:

mtr: Address not available

This issue appears to be resolved in upstream and mtr v0.94 available with RHEL 9 and upstream versions. 

Similar issues is described here as well:

The RHEL8 mtr behavior is the same as described in upstream mtr issue:
https://github.com/traviscross/mtr/issues/357

What is the impact of this issue to you?

This prevents the customer from utilizing MTR in RHEL 8 to troubleshoot TCP connectivity issues. 

Please provide the package NVR for which the bug is seen:

mtr-0.92-3.el8.x86_64 and older RHEL 8 versions

How reproducible is this bug?:

Customer mentioned this was not consistent but this was reproduced successfully.  

Steps to reproduce:

run mtr as root, on a tight interval:

1. mtr -TP 8080 healthproxy -i .001

This was reproduced by backline engineers (with strace) using command below:

# strace -fttTvyy -o ~/mtr-kernel.strace -s 1024 – mtr-4 -TP 80 www.google.com -i 0.1 

Expected results

This error should not appear and mtr should complete as expected. 

Actual results

MTR will produce "mtr: Address not available"  if specific conditions are seen: