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:
When using the python version on RHEL 8, the route, dns and route rules stored in the interface can be shown.
In the future nmstate would store these global configurations in loopback connection, this bug is for tracking in case we need a workaround before https://bugzilla.redhat.com/show_bug.cgi?id=2060905 implements.
Version-Release number of selected component (if applicable):
nmstate-2.1.1-0.alpha.20220519.437e4a9.el9.x86_64
How reproducible:
100%
Steps to Reproduce:
echo "dns-resolver:
config:
search:
- redhat.com
- usersys.redhat.com
server:
- 10.68.5.26
- 2400:3200:baba::1
routes:
config:
- destination: 0.0.0.0/0
next-hop-address: 100.1.1.254
next-hop-interface: dummy0
table-id: 100
- destination: ::/0
next-hop-address: 100::254
next-hop-interface: dummy0
table-id: 100
route-rules:
config:
- ip-from: 8.8.8.8/24
ip-to: 200.1.1.1/24
priority: 3000
route-table: 100
- ip-to: 111::/64
priority: 4000
route-table: 100
interfaces:
- name: dummy0
type: dummy
state: up
ipv4:
enabled: true
address:
- ip: 100.1.1.1
prefix-length: 24
ipv6:
enabled: true
address:
- ip: 100::1
prefix-length: 64" | nmstatectl apply
nmstatectl show dummy0
Actual results:
---
dns-resolver: {}
route-rules: {}
routes: {}
interfaces:
- name: dummy0
type: dummy
state: up
......
Expected results:
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 (nmstate 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-2022:7991