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 applying below config:
```
---
interfaces:
- name: eth1
type: ethernet
state: up
- name: br0
type: linux-bridge
state: up
bridge:
port:
- name: eth1
ipv4:
dhcp: false
enabled: false
ipv6:
autoconf: false
dhcp: false
enabled: true
```
The nmstate will get timeout error:
libnmstate.error.NmstateLibnmError: Unexpected failure of libnm when running the mainloop: run timeout
Version-Release number of selected component (if applicable):
nmstate-0.0.7-1.el8.src.rpm
NetworkManager-libnm-1.20.0-0.1.el8.x86_64
How reproducible:
100%
Steps to Reproduce:
1. sudo ip link add eth1 type veth peer name eth2
2. save above config to `1.yml` file.
3. sudo nmstate set 1.yml
Actual results:
Expected results:
Additional info:
Since link local address will be ignored, setting with link local address
has the same effect.
Root cause:
When autoconf and dhcp disabled for IPV6 with no ipv6 address assigned,
the br0 will be set as ipv6.method == link-local.
The NetworkManager try to wait the br0 for link up:
Jun 24 15:37:23 el8 NetworkManager[1011]: <info> [1561361843.2431] device (br0): IPv6 config waiting until carrier is on
But at the stage of br0 activation, its slave profile is not created yet.
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, 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-2019:3347
Description of problem: When applying below config: ``` --- interfaces: - name: eth1 type: ethernet state: up - name: br0 type: linux-bridge state: up bridge: port: - name: eth1 ipv4: dhcp: false enabled: false ipv6: autoconf: false dhcp: false enabled: true ``` The nmstate will get timeout error: libnmstate.error.NmstateLibnmError: Unexpected failure of libnm when running the mainloop: run timeout Version-Release number of selected component (if applicable): nmstate-0.0.7-1.el8.src.rpm NetworkManager-libnm-1.20.0-0.1.el8.x86_64 How reproducible: 100% Steps to Reproduce: 1. sudo ip link add eth1 type veth peer name eth2 2. save above config to `1.yml` file. 3. sudo nmstate set 1.yml Actual results: Expected results: Additional info: Since link local address will be ignored, setting with link local address has the same effect. Root cause: When autoconf and dhcp disabled for IPV6 with no ipv6 address assigned, the br0 will be set as ipv6.method == link-local. The NetworkManager try to wait the br0 for link up: Jun 24 15:37:23 el8 NetworkManager[1011]: <info> [1561361843.2431] device (br0): IPv6 config waiting until carrier is on But at the stage of br0 activation, its slave profile is not created yet.