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:
Support change MTU with link state changes.
Version-Release number of selected component (if applicable):
nmstate-0.0.8-15.el8
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Gris, What does it mean? Is it a bug of wrong debug information?
Because I just met the situation:
changed the mtu with the file:
---
interfaces:
- name: veth1
type: ethernet
state: up
mtu: 2000
The debugger reported '2019-09-26 04:01:01,411 root DEBUG Device reapply does not support mtu changes, fallback to device activation: dev=veth1', but it works as well.
Seems it does support reapply mtu changes.
Hi Mingyu,
The `reapply()` means the link will not be bring down and up.
You may use `ip monitor dev <nic_name>` to check on link status changes.
For example, adding slaves to bridge will use `reapply` will keep the bridge interface always in up state.
(In reply to Edward Haas from comment #5)
> This issue may have been solved by https://bugzilla.redhat.com/1702657
No. NM fixed the reapply issue, but nmstate hard coded not to do reapply on MTU changes.
This bug is ask nmstate to remove that hard coded restriction.
Investigating:
RHEL-8.1.1-20191202.n.3
[root@hp-dl388g8-04 /mnt/tests/kernel/networking/nmstate/temp]0# rpm -q NetworkManager nmstate
NetworkManager-1.20.0-3.el8.x86_64
nmstate-0.1.1-5.el8.noarch
"ip monitor" command still detected the link change even do 'nmstatectl set $sameYamlFile'