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 1814557 - [NMCI] ipv6_routes_with_src test failed
Summary: [NMCI] ipv6_routes_with_src test failed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Beniamino Galvani
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-18 08:58 UTC by Vladimir Benes
Modified: 2020-11-04 01:49 UTC (History)
8 users (show)

Fixed In Version: NetworkManager-1.25.1-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 01:49:00 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4499 0 None None None 2020-11-04 01:49:28 UTC

Description Vladimir Benes 2020-03-18 08:58:08 UTC
Description of problem:
sometimes I see a failure:
    @ipv6_routes_with_src
    Scenario: nmcli - ipv6 - routes - set route with src
    * Add a new connection of type "ethernet" and options "ifname eth3 con-name con_ipv6 autoconnect no ipv6.method manual ipv6.addresses 2000::2/126 ipv6.route-metric 256 ipv6.routes '2806:aabb:abba:abab:baba:bbaa:baab:bbbb/128 src=2000::2'"
    * Bring "up" connection "con_ipv6"
    Then "2806:aabb:abba:abab:baba:bbaa:baab:bbbb dev eth3 proto static src 2000::2 metric 256" is visible with command "ip -6 route" in "5" seconds
   ^^ here

     And "2000::\/126 dev eth3\s+proto kernel\s+metric 256" is visible with command "ip -6 route"

as Beniamino told me at some point we add a link-local address and to maintain the right order of addresses, we remove 2000::2 and readd it. So, it becomes tentative again even if DAD was terminated. Then adding the route fails because the address is tentative. So a race in NM.

Version-Release number of selected component (if applicable):
1.22.11-24744.4b07cb9d3c.el8

logs:
http://pastebin.test.redhat.com/845756 (stored forever)

Comment 1 Beniamino Galvani 2020-03-18 21:47:43 UTC
Upstream merge request:

  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/444

A practical way to check the correct behavior is the following:

  # ip -6 monitor address &

  # nmcli connection add \
      type ethernet ifname eth5 con-name ipv6+ autoconnect no \
      ipv4.method disabled \
      ipv6.method manual ipv6.addresses 2000::2/126

  # nmcli connection up ipv6+

Bad behavior: the address is added, then removed and then added again:

  8: eth5    inet6 2000::2/126 scope global tentative noprefixroute
         valid_lft forever preferred_lft forever
  8: eth5    inet6 2000::2/126 scope global tentative noprefixroute
         valid_lft forever preferred_lft forever
  Deleted 8: eth5    inet6 2000::2/126 scope global tentative noprefixroute
         valid_lft forever preferred_lft forever
  Deleted 8: eth5    inet6 2000::2/126 scope global tentative noprefixroute
         valid_lft forever preferred_lft forever
  8: eth5    inet6 fe80::8626:d487:130:3139/64 scope link tentative noprefixroute
         valid_lft forever preferred_lft forever
  8: eth5    inet6 fe80::8626:d487:130:3139/64 scope link tentative noprefixroute
         valid_lft forever preferred_lft forever
  8: eth5    inet6 2000::2/126 scope global tentative noprefixroute
         valid_lft forever preferred_lft forever
  8: eth5    inet6 2000::2/126 scope global tentative noprefixroute
         valid_lft forever preferred_lft forever
  8: eth5    inet6 fe80::8626:d487:130:3139/64 scope link noprefixroute
         valid_lft forever preferred_lft forever
  8: eth5    inet6 fe80::8626:d487:130:3139/64 scope link noprefixroute
         valid_lft forever preferred_lft forever

Good behavior: addresses are added and never removed:

  8: eth5    inet6 2000::2/126 scope global tentative noprefixroute
         valid_lft forever preferred_lft forever
  8: eth5    inet6 2000::2/126 scope global tentative noprefixroute
         valid_lft forever preferred_lft forever
  8: eth5    inet6 fe80::8626:d487:130:3139/64 scope link tentative noprefixroute
         valid_lft forever preferred_lft forever
  8: eth5    inet6 fe80::8626:d487:130:3139/64 scope link tentative noprefixroute
         valid_lft forever preferred_lft forever
  8: eth5    inet6 fe80::8626:d487:130:3139/64 scope link noprefixroute
         valid_lft forever preferred_lft forever
  8: eth5    inet6 fe80::8626:d487:130:3139/64 scope link noprefixroute
         valid_lft forever preferred_lft forever
  8: eth5    inet6 2000::2/126 scope global noprefixroute
         valid_lft forever preferred_lft forever
  8: eth5    inet6 2000::2/126 scope global noprefixroute
         valid_lft forever preferred_lft forever

Comment 5 Vladimir Benes 2020-05-20 12:05:14 UTC
We cannot see a failure anymore.

Comment 8 errata-xmlrpc 2020-11-04 01:49:00 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 (NetworkManager bug fix and enhancement update), 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-2020:4499


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