Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
we can see a race when a profile is up (with ipv4.may-fail no) but we cannot ping domain for a short time as probably DNS records are not done properly.
@con_ipv4_remove @eth0
@ipv4_dns-search_remove
Scenario: nmcli - ipv4 - dns-search - remove dns-search
* Add a new connection of type "ethernet" and options "ifname eth0 con-name con_ipv4 ipv4.may-fail no ipv4.dns-search google.com"
* Modify connection "con_ipv4" changing options "ipv4.dns-search ''"
* Bring "up" connection "con_ipv4"
Then Domain "google.com" is not set
Then Unable to ping "maps"
Then Ping "maps.google.com"
Version-Release number of selected component (if applicable):
NetworkManager-1.32.10-2.el8.x86_64
How reproducible:
once in 20 cycles
Steps to Reproduce:
1. download NMCI tests
2. test=ipv4_dns-search_remove; a=0; while ./test_run.sh $test; do :;((a++)); echo "ATTEMPT $a"; if [ $a -eq 100 ]; then break; fi ; done
Actual results:
fail in less than 100
Expected results:
should end after 100 cycles
Additional info:
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/RHEA-2022:1985
Description of problem: we can see a race when a profile is up (with ipv4.may-fail no) but we cannot ping domain for a short time as probably DNS records are not done properly. @con_ipv4_remove @eth0 @ipv4_dns-search_remove Scenario: nmcli - ipv4 - dns-search - remove dns-search * Add a new connection of type "ethernet" and options "ifname eth0 con-name con_ipv4 ipv4.may-fail no ipv4.dns-search google.com" * Modify connection "con_ipv4" changing options "ipv4.dns-search ''" * Bring "up" connection "con_ipv4" Then Domain "google.com" is not set Then Unable to ping "maps" Then Ping "maps.google.com" Version-Release number of selected component (if applicable): NetworkManager-1.32.10-2.el8.x86_64 How reproducible: once in 20 cycles Steps to Reproduce: 1. download NMCI tests 2. test=ipv4_dns-search_remove; a=0; while ./test_run.sh $test; do :;((a++)); echo "ATTEMPT $a"; if [ $a -eq 100 ]; then break; fi ; done Actual results: fail in less than 100 Expected results: should end after 100 cycles Additional info: