I thought this was failing on all metal instances (this test "passes" on the openstack ones because we just skip the test) but in the s2024.10.28 cycle (kernel version 4.4.0-1108.115) this test passed on rumford.amd64.
-- 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/2071606 Title: fips_test failed on X-fips because VM failed to start Status in ubuntu-kernel-tests: New Bug description: Open a new bug for this to make SRU testing more smoother. After we modified our test case to install FIPS userspace packages for the test (in cycle s2024.03.04), the fips_test will fail because the VM failed to start: Starting Load AppArmor profiles managed internally by snapd... [ OK ] Started Load AppArmor profiles managed internally by snapd. [ OK ] Started Set console font and keymap. [ OK ] Created slice system-getty.slice. [ OK ] Found device /dev/ttyS0. [ OK ] Found device Virtio network device. [ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. [ 7.888732] intel_rapl: no valid rapl domains found in package 0 (it stuck here) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2071606/+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
