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 ipv4/ipv6.enabled is not mentioned, rust automatically configures it as "enabled: false".
Full editing is reasonable, but it breaks the old behavior on RHEL 8, need to evaluate it.
Version-Release number of selected component (if applicable):
nmstate-2.1.1-0.alpha.20220519.437e4a9.el9.x86_64
DISTRO=RHEL-9.1.0-20220531.0
How reproducible:
100%
Steps to Reproduce:
1. echo "
interfaces:
- name: veth0
type: veth
state: up
ipv4:
enabled: true
dhcp: true
ipv6:
enabled: true
dhcp: true
autoconf: true
veth:
peer: veth0_ep
" | nmstatectl apply
# for example if I want to disable autoconf
2. echo "
interfaces:
- name: veth0
type: veth
state: up
ipv6:
autoconf: false
" | nmstatectl apply
Actual results:
After applied, nmstate reported OK and returned this state:
---
dns-resolver: {}
route-rules: {}
routes: {}
interfaces:
- name: veth0
type: veth
state: up
ipv6:
enabled: false # this option was appended automatically
autoconf: false
ovs-db: {}
Expected results:
Like on RHEL 8, only change the explicitly mentioned options
Additional info:
Some other similar actions that differ with nmstate python:
interfaces:
- name: veth0
ipv6:
enabled: true
autoconf: false
=> "dhcp" is not mentioned but set to false automatically
interfaces:
- name: veth0
ipv4:
enabled: true
auto-dns: false
=> [2022-06-01T21:24:00Z WARN nmstate::nm::checkpoint] Timeout on waiting rollback
NmstateError: VerificationError: Verification failure: veth0.interface.ipv4.enabled desire 'true', current 'false'
Assume successfully changed auto-dns to false, then try applying:
interfaces:
- name: veth0
ipv4:
enabled: true
dhcp: true
=> "auto-dns" will be changed to true again.
Patch posted to upstream: https://github.com/nmstate/nmstate/pull/1959
Hi Mingyu,
Since we are changing the IP stack code with big impact of many tier 1 use case, could you run your tests against the copr build of that PR?
Thank you!
(In reply to Mingyu Shi from comment #2)
> Hi Gris
>
> It looks good in the direct related test, I've submitted a full test for the
> copr build, will update the result here when it finishes.
No new issues found.
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
Description of problem: When ipv4/ipv6.enabled is not mentioned, rust automatically configures it as "enabled: false". Full editing is reasonable, but it breaks the old behavior on RHEL 8, need to evaluate it. Version-Release number of selected component (if applicable): nmstate-2.1.1-0.alpha.20220519.437e4a9.el9.x86_64 DISTRO=RHEL-9.1.0-20220531.0 How reproducible: 100% Steps to Reproduce: 1. echo " interfaces: - name: veth0 type: veth state: up ipv4: enabled: true dhcp: true ipv6: enabled: true dhcp: true autoconf: true veth: peer: veth0_ep " | nmstatectl apply # for example if I want to disable autoconf 2. echo " interfaces: - name: veth0 type: veth state: up ipv6: autoconf: false " | nmstatectl apply Actual results: After applied, nmstate reported OK and returned this state: --- dns-resolver: {} route-rules: {} routes: {} interfaces: - name: veth0 type: veth state: up ipv6: enabled: false # this option was appended automatically autoconf: false ovs-db: {} Expected results: Like on RHEL 8, only change the explicitly mentioned options Additional info: Some other similar actions that differ with nmstate python: interfaces: - name: veth0 ipv6: enabled: true autoconf: false => "dhcp" is not mentioned but set to false automatically interfaces: - name: veth0 ipv4: enabled: true auto-dns: false => [2022-06-01T21:24:00Z WARN nmstate::nm::checkpoint] Timeout on waiting rollback NmstateError: VerificationError: Verification failure: veth0.interface.ipv4.enabled desire 'true', current 'false' Assume successfully changed auto-dns to false, then try applying: interfaces: - name: veth0 ipv4: enabled: true dhcp: true => "auto-dns" will be changed to true again.