Even this simple command from host to the target system will fail: $ time ssh $USER@$SUT_IP "date; sleep 300 ; date" Thu Aug 8 15:49:46 UTC 2024 ^C real 7m50.194s user 0m0.005s sys 0m0.018s
260 seconds is not working as well. $ time sutssh 52.175.206.46 "date; sleep 260 ; date" Thu Aug 8 16:06:48 UTC 2024 ^C real 10m8.938s user 0m0.017s sys 0m0.000s 250 seconds works. $ time ssh $USER@$SUT_IP "date; sleep 250 ; date" Thu Aug 8 16:10:55 UTC 2024 Thu Aug 8 16:15:05 UTC 2024 real 4m11.454s user 0m0.020s sys 0m0.002s Now I wonder if these cases are really failing? Or they took too long to make some noise? -- You received this bug notification because you are a member of Canonical Platform QA Team, which is subscribed to ubuntu-kernel-tests. https://bugs.launchpad.net/bugs/2076241 Title: ubuntu_ltp_* tests unable to finish properly with B-azure-fips Status in ubuntu-kernel-tests: New Bug description: In sru-s20240429 and sru-s20240610, the ubuntu_ltp_* tests were found unable to finish properly with B-azure-fips kernel, and eventually trigger the `sut-test` failure on them. Here is the result from sru-s20240610 * ubuntu_ltp - report cuts-off at fs:fs_fill test, failed on Standard_D4_v4 only. * ubuntu_ltp_controllers - report cuts-off at memcg_test_3 test, failed on Standard_B1ms - report cuts-off at memcg_stress test, failed on Standard_D4_v4, Standard_D4s_v3-gen2 * ubuntu_ltp_cve - report cuts-off at cve-2016-8655 test, failed on Standard_B1ms, Standard_D4_v4 - report cuts-off at cve-2018-18559 test, failed on Standard_D4s_v3-gen2 * ubunut_ltp_syscall - report cuts-off at setsockopt06 test, failed on Standard_B1ms - report cuts-off at bind06 test, failed on Standard_D4_v4, Standard_D4s_v3-gen2 The result from sru-s20240610 is quite similar, just the ubuntu_ltp_cve this time cuts-off at cve-2016-8655 test on Standard_D4s_v3-gen2. Note that the cve-2016-8655 is actually the setsockopt06 test, and cve-2018-18559 is the bind06 test. I have done some experiments on Standard_D4s_v3-gen2 with kernel in sru-s20240610 (4.15.0-2088-azure-fips): * ubunut_ltp_controllers: - If we skip memcg_stress test, it will be able to finish properly. * ubuntu_ltp_cve: - If we skip cve-2016-8655 and cve-2018-18559 tests, it will be able to finish properly. With my manual test on Standard_D4_v4 with 4.15.0-2088-azure-fips, I noticed that my idle SSH session will hang after a certain period (I recorded one at about 7m21s). If it's running something, like htop, it will be fine. And setsockopt06, bind06 test can pass without any immediate crash. Not sure what is the cause of this failure that we see here. It's also worthy to note that "running something" seems to limited to commands that will keep generating output. Commands like "dmesg -w" and "tail -f /var/log/syslog" will hang too if there is no output to update. According to Magali, the last bionic fips openssh update is from January, so this might be something else in the kernel. == Original bug report == On azure-fips platforms multiple tests in ubuntu_ltp, ubuntu_ltp_controllers, ubuntu_ltp_cve, and ubuntu_ltp_syscalls are causing the system to be unresponsive. When running locally the tests run to completion but the system hangs sometime after. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2076241/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
