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.
To solve this problem, we agree to introduce support of `type: ignore` for ip address like:
```yaml
---
interfaces:
- name: eth1
type: ethernet
state: up
ipv4:
address:
- ip: 192.0.2.251
prefix-length: 24
- ip: 192.168.111.4
prefix-length: 24
ignore: true
dhcp: false
enabled: true
```
With this, nmstate will ignore the existence(or not) of 192.168.111.4 IP address.
Let me do a demo to confirm this actually solve the problem.
Considering the VIP might change or expand in the future, asking user to set it ignore explicitly add extra maintenance efforts.
Change the approach to use `allow-extra-address: true` for ignoring extra IP address found after apply in verification stage. By default, nmstate will not allow extra IP address in verification stage.
I have created test rpm with `allow-extra-address` set to `true` by default so no changes required for kubernetes-nmstate required:
https://people.redhat.com/fge/bz_2111945/
Patch sent to upstream: https://github.com/nmstate/nmstate/pull/2038
With this patch, nmstate will not fail the verification when found extra ip adress than desired.
To force strict IP address verification, please use `allow-extra-address: false`.
RHEL 8.6 backport patch been tested.
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-2023:2772
To solve this problem, we agree to introduce support of `type: ignore` for ip address like: ```yaml --- interfaces: - name: eth1 type: ethernet state: up ipv4: address: - ip: 192.0.2.251 prefix-length: 24 - ip: 192.168.111.4 prefix-length: 24 ignore: true dhcp: false enabled: true ``` With this, nmstate will ignore the existence(or not) of 192.168.111.4 IP address. Let me do a demo to confirm this actually solve the problem.