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:
after running
@con_ipv6_remove @eth0
@ipv6_dns_manual_IP_with_manual_dns
Scenario: nmcli - ipv6 - dns - method static + IP + dns
* Add a new connection of type "ethernet" and options "ifname eth10 con-name con_ipv6 ipv4.may-fail no ipv6.method static ipv6.addresses 2001::1/126 ipv6.gateway 4000::1 ipv6.dns '4000::1, 5000::1'"
Then Nameserver "4000::1" is set in "45" seconds
Then Nameserver "5000::1" is set
Then Nameserver "10." is set in "45" seconds
I can still see
Link 158 (eth3)
Current Scopes: none
DefaultRoute setting: no
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 4000::1
5000::1
in resolvectl even if the eth3 profile is down, shouldn't this be cleaned?
Version-Release number of selected component (if applicable):
1.26 (F33)
Comment 1Beniamino Galvani
2020-10-23 13:45:56 UTC
Hi Vladimir, I can't reproduce the problem with NM 1.26.4. Can you please attach logs? Thanks!
Comment 2Beniamino Galvani
2020-10-27 15:29:41 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 (Moderate: NetworkManager and libnma security, 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/RHSA-2021:1574
Description of problem: after running @con_ipv6_remove @eth0 @ipv6_dns_manual_IP_with_manual_dns Scenario: nmcli - ipv6 - dns - method static + IP + dns * Add a new connection of type "ethernet" and options "ifname eth10 con-name con_ipv6 ipv4.may-fail no ipv6.method static ipv6.addresses 2001::1/126 ipv6.gateway 4000::1 ipv6.dns '4000::1, 5000::1'" Then Nameserver "4000::1" is set in "45" seconds Then Nameserver "5000::1" is set Then Nameserver "10." is set in "45" seconds I can still see Link 158 (eth3) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 4000::1 5000::1 in resolvectl even if the eth3 profile is down, shouldn't this be cleaned? Version-Release number of selected component (if applicable): 1.26 (F33)