** Description changed: + [ Impact ] + + The fence-agents autopkgtest "delay" test fails when executed inside a + container (LXD), blocking proposed-migration on the affected releases and + holding back unrelated package migrations (e.g. sg3-utils). + + The test runs: + + sudo /usr/sbin/sysctl -w net.ipv4.ping_group_range="0 2147483647" + + and fails with: + + sysctl: setting key "net.ipv4.ping_group_range": Invalid argument + + The upper bound "2147483647" is a valid GID inside a VM, where the GID map + is the full range: + + $ cat /proc/self/gid_map + 0 0 4294967295 + + but inside a container the GID map is restricted: + + $ cat /proc/self/gid_map + 0 1000000 1000000000 + + so the kernel rejects the value as out of range and the test fails. This is + purely a test-environment problem; the fence-agents package itself works + correctly. + + This is a test-only change. Users do not receive any functional change; the + upload exists solely to fix the autopkgtest so the package can migrate and to + unblock future SRUs. + + [ Test Plan ] + + On the affected release (Questing / Resolute): + + 1. Build the package with the proposed change. + 2. Run the autopkgtest in a container + 3. Verify the "delay" test now passes (previously it failed with + "Invalid argument" on net.ipv4.ping_group_range). + + [ Where problems could occur ] + + The change only touches the autopkgtest (debian/tests); The risk is therefore + limited to the test infrastructure: + + [ Other Info ] + + * This upload is being staged in -proposed and kept there until a future + functional SRU bundles it. + + --- Original bug report --- + + 336s Setting up python3-osc-lib (4.4.0-2) ... 336s Setting up python3-oslo.log (8.1.0-3) ... 336s Setting up python3-openstackclient (9.0.0-3) ... 337s Setting up python3-neutronclient (1:11.8.0-2) ... 337s Setting up fence-agents-ironic (4.17.0-1ubuntu1) ... 337s Setting up fence-agents-extra (4.17.0-1ubuntu1) ... 340s autopkgtest [11:35:44]: test delay: [----------------------- 341s sysctl: setting key "net.ipv4.ping_group_range": Invalid argument 341s autopkgtest [11:35:45]: test delay: -----------------------] 341s autopkgtest [11:35:45]: test delay: - - - - - - - - - - results - - - - - - - - - - 341s delay FAIL non-zero exit status 1 342s autopkgtest [11:35:46]: test delay: - - - - - - - - - - stderr - - - - - - - - - - 342s sysctl: setting key "net.ipv4.ping_group_range": Invalid argument 342s autopkgtest [11:35:46]: test fence-dummy: preparing testbed 349s autopkgtest [11:35:53]: testbed dpkg architecture: amd64 349s autopkgtest [11:35:53]: testbed apt version: 3.2.0 349s autopkgtest [11:35:53]: @@@@@@@@@@@@@@@@@@@@ test bed setup Reference --- https://autopkgtest.ubuntu.com/results/autopkgtest-stonking/stonking/amd64/f/fence-agents/20260528_113727_0eb60@/log.gz
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2155622 Title: autopkgtest fails on Ubuntu Stonking because of bad sysctl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/2155622/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
