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:
Nmstate user might not know IPv6 has `autconf` property, so they might only have
```
ipv6:
enabled: true
dhcp: true
```
The state nmstate applied is not what customer desired as DHCPv6 does not have IPv6 routing information.
Hence nmstate should generate a warning message to user indicating nmstate is auto-fixing the desire state by enabling autoconf also.
Version-Release number of selected component (if applicable):
nmstate-2.2
How reproducible:
100%
Steps to Reproduce:
1. Use nmstate to apply this YAML:
```yml
---
interfaces:
- name: eth1
state: up
ipv6:
enabled: true
dhcp: true
```
2.
3.
Actual results:
Only DHCPv6 enabled on this interface. Hence no IPv6 routing.
Expected results:
Both autoconf and DHCPv6 are enabled.
Additional info:
Description of problem: Nmstate user might not know IPv6 has `autconf` property, so they might only have ``` ipv6: enabled: true dhcp: true ``` The state nmstate applied is not what customer desired as DHCPv6 does not have IPv6 routing information. Hence nmstate should generate a warning message to user indicating nmstate is auto-fixing the desire state by enabling autoconf also. Version-Release number of selected component (if applicable): nmstate-2.2 How reproducible: 100% Steps to Reproduce: 1. Use nmstate to apply this YAML: ```yml --- interfaces: - name: eth1 state: up ipv6: enabled: true dhcp: true ``` 2. 3. Actual results: Only DHCPv6 enabled on this interface. Hence no IPv6 routing. Expected results: Both autoconf and DHCPv6 are enabled. Additional info: