test: Add testNetworking.testBondActive #8736
Conversation
NetworkManager 1.10 has a regression here, so let's test this explicitly. testBondingMain also hits the regression, but because the active interface has "manual" ipv4 settings, and Cockpit copies those to the bond, the bond ends up looking okay although it doesn't really work. testBond also hits the regression, but because it has one inactive interface, the bond ends up being functional (with just one slave). Fixes cockpit-project#8735
|
The new test will fail on some images. Let's see where. |
|
Test fails on rhel-7-5, fedora-27, fedora-atomic, fedora-i386, debian-testing, and ubuntu-stable. Ubuntu-stabe is a surprise. |
|
@mvollmer: None of our images have network-manager 1.10 yet. They all are at 1.8. 1.10 is in current Ubuntu devel and Fedora 28. Maybe the regression already is in 1.8 then? |
|
rhel-7-5 has NetworkManager-1.10.2-12.el7.x86_64, but the regression might well be in 1.8. Or in a config file. I am hoping that the NM people can tell us the details in https://bugzilla.redhat.com/show_bug.cgi?id=1548265 |
|
I am trying out a workaround in #8769. |
|
Lets only have the workaround PR, and include the new tests there. |
ubuntu-stable has some version >= 1.8.2, so it also fits into the picture. |
NetworkManager 1.10 has a regression here, so let's test this
explicitly.
testBondingMain also hits the regression, but because the active
interface has "manual" ipv4 settings, and Cockpit copies those to the
bond, the bond ends up looking okay although it doesn't really work.
testBond also hits the regression, but because it has one inactive
interface, the bond ends up being functional (with just one slave).
Fixes #8735