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.
Verified with: nmstate-1.4.0-0.alpha.20221017.el8.x86_64 nispor-1.2.7-1.el8.x86_64 NetworkManager-1.40.2-1.el8.x86_64
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