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:

As part of migration MCO configure-ovs to nmstate the attribute "addr-gen-mode" need to be set if interfaces has already a address assigned [1]

[1] https://github.com/openshift/machine-config-operator/blob/48d88a7f75e97c87b2a6f4b00862a091fccbdd72/templates/common/_base/files/configure-ovs-network.yaml#L327


Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
User can set the "addr-gen-mode" attribute at thir ipv4/ipv6 field options.


Additional info:

Hi @ellorent,

Could you please provide an acceptance criteria for this request so that we know clearly what we will need to do ? 


Thanks,

@sfaye at some scenarios the attribtue need to be copied to the bridge from the ports, adding this attribute to nmstate allows us to do it with it.


https://github.com/qinqon/configure-ovs-nmstate/blob/main/configure-ovs.sh#L292-L294

More info https://github.com/openshift/machine-config-operator/commit/e43a9f216937df5b0fc9c744be78687ac38c21f2

Patch posted to https://github.com/nmstate/nmstate/pull/1906

Example yaml:

```yaml
---
interfaces:
  - name: eth1
    type: ethernet
    state: up
    mtu: 1500
    ipv4:
      enabled: false
    ipv6:
      autoconf: true
      dhcp: true
      enabled: true
      addr-gen-mode: eui64
```

Supporting two modes: `eui64` for RFC 4862, `stable-privacy` for RFC 7217.

Tested with integration tests and manually!

Verified with:
nmstate-2.1.1-0.alpha.20220602.5accbd1.el9.x86_64
NetworkManager-1.39.6-1.el9.x86_64

The log: https://bugzilla.redhat.com/attachment.cgi?id=1890087

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