On Wed, Jun 24, 2020 at 12:17 AM Mark R <ovirtlist@beanz.33mail.com> wrote:
Follow up, as well as the logged error from supervdsm.log, I see this in dmesg so it appears that it very briefly does create DMZ0 and the bond0.22 interface, but rolls everything back.
``` [ 2205.551920] IPv6: ADDRCONF(NETDEV_UP): DMZ0: link is not ready [ 2205.558366] IPv6: ADDRCONF(NETDEV_UP): bond0.22: link is not ready [ 2205.655177] DMZ0: port 1(bond0.22) entered blocking state [ 2205.655179] DMZ0: port 1(bond0.22) entered disabled state ``` Both ports for the bond are up and active (of couse, as this is currently the first host of the HE deployment so I couldn't manage it if they weren't).
``` # cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: IEEE 802.3ad Dynamic link aggregation Transmit Hash Policy: layer2 (0) MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Peer Notification Delay (ms): 0
802.3ad info LACP rate: slow Min links: 0 Aggregator selection policy (ad_select): stable System priority: 65535 System MAC address: bc:97:e1:24:c5:40 Active Aggregator Info: Aggregator ID: 1 Number of ports: 2 Actor Key: 21 Partner Key: 3 Partner Mac Address: 0a:33:5e:69:1f:1e
Slave Interface: eno33np0 MII Status: up Speed: 25000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: bc:97:e1:24:c5:40 Slave queue ID: 0 Aggregator ID: 1 Actor Churn State: none Partner Churn State: none Actor Churned Count: 0 Partner Churned Count: 0 details actor lacp pdu: system priority: 65535 system mac address: bc:97:e1:24:c5:40 port key: 21 port priority: 255 port number: 1 port state: 61 details partner lacp pdu: system priority: 4096 system mac address: 0a:33:5e:69:1f:1e oper key: 3 port priority: 8192 port number: 65 port state: 61
Slave Interface: ens2f0np0 MII Status: up Speed: 25000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: b0:26:28:cd:ec:d0 Slave queue ID: 0 Aggregator ID: 1 Actor Churn State: none Partner Churn State: none Actor Churned Count: 0 Partner Churned Count: 0 details actor lacp pdu: system priority: 65535 system mac address: bc:97:e1:24:c5:40 port key: 21 port priority: 255 port number: 2 port state: 61 details partner lacp pdu: system priority: 4096 system mac address: 0a:33:5e:69:1f:1e oper key: 3 port priority: 32768 port number: 33 port state: 61 ```
Thanks, Mark _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/FY5227PI4PUFPO...
Hello, sorry for the late response. We are failing to reproduce this issue. Can you please provide us with more info? I need to know an exact package version of nmstate and NetworkManager. Also if possible please enable trace logs for NetworkManager: Please create `/etc/NetworkManager/conf.d/debug.conf` with following content: [logging] level=TRACE domains=ALL Restart NetworkManager service and trigger the issue again. The NM log is available via journalctl -u NetworkManager. Thank you. Best regards, Ales Musil -- Ales Musil Software Engineer - RHV Network Red Hat EMEA <https://www.redhat.com> amusil@redhat.com IM: amusil <https://red.ht/sig>