[Touch-packages] [Bug 1862667] Re: systemd autopkgtest 'boot-and-services' fails with linux-kvm
after checking the focal linux-kvm kernel, it does have dm-multipath enabled as a module, so there should be no change needed in the systemd test. ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: systemd (Ubuntu Bionic) ** No longer affects: linux-kvm (Ubuntu Bionic) ** Changed in: linux-kvm (Ubuntu Focal) Status: New => Fix Released ** Changed in: systemd (Ubuntu Focal) Status: In Progress => Won't Fix ** Changed in: linux-kvm (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1862667 Title: systemd autopkgtest 'boot-and-services' fails with linux-kvm Status in linux-kvm package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Won't Fix Status in linux-kvm source package in Eoan: Won't Fix Status in systemd source package in Eoan: Won't Fix Status in linux-kvm source package in Focal: Fix Released Status in systemd source package in Focal: Won't Fix Bug description: [impact] systemd autopkgtest 'boot-and-services' fails when running with linux- kvm kernel, because that kernel does not set CONFIG_DM_MULTIPATH, so the test detects failed services. [test case] check the autopkgtest results, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/systemd/20200210_144351_da247@/log.gz test_no_failed (__main__.ServicesTest) No failed units ... journal for failed service multipathd.service --- -- Logs begin at Mon 2020-02-10 03:26:38 UTC, end at Mon 2020-02-10 13:56:23 UTC. -- Feb 10 13:56:07 autopkgtest systemd[1]: Starting Device-Mapper Multipath Device Controller... Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module scsi_dh_alua not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module scsi_dh_emc not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module scsi_dh_rdac not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module dm-multipath not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest multipathd[195]: start up Feb 10 13:56:07 autopkgtest multipathd[195]: read /etc/multipath.conf Feb 10 13:56:07 autopkgtest multipathd[195]: DM multipath kernel driver not loaded Feb 10 13:56:07 autopkgtest systemd[1]: multipathd.service: Main process exited, code=exited, status=1/FAILURE Feb 10 13:56:07 autopkgtest systemd[1]: multipathd.service: Failed with result 'exit-code'. Feb 10 13:56:07 autopkgtest systemd[1]: Failed to start Device-Mapper Multipath Device Controller. FAIL == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.WQ5GyY/build.RUe/src/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['multipathd.service loaded failed failed [38 chars]ler'] != [] First list contains 1 additional elements. First extra element 0: 'multipathd.service loaded failed failed Device-Mapper Multipath Device Controller' + [] - ['multipathd.service loaded failed failed Device-Mapper Multipath Device ' - 'Controller'] [regression potential] This updates the test case to ignore failure of multipathd.service if it looks like the dm-multipath module isn't available, so any regression would be limited to incorrectly passing or failing test case. [scope] This is needed at least in Eoan, and probably Focal. This doesn't fail on Bionic or Xenial, but that seems to be because the multipath-utils package (which provides multipathd.service) is not installed during the test for those releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1862667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862667] Re: systemd autopkgtest 'boot-and-services' fails with linux-kvm
marking Eoan as wontfix; it's EOL in weeks and this is a minor bug ** Changed in: linux-kvm (Ubuntu Eoan) Status: New => Won't Fix ** Changed in: systemd (Ubuntu Eoan) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1862667 Title: systemd autopkgtest 'boot-and-services' fails with linux-kvm Status in linux-kvm package in Ubuntu: New Status in systemd package in Ubuntu: In Progress Status in linux-kvm source package in Eoan: Won't Fix Status in systemd source package in Eoan: Won't Fix Status in linux-kvm source package in Focal: New Status in systemd source package in Focal: In Progress Bug description: [impact] systemd autopkgtest 'boot-and-services' fails when running with linux- kvm kernel, because that kernel does not set CONFIG_DM_MULTIPATH, so the test detects failed services. [test case] check the autopkgtest results, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/systemd/20200210_144351_da247@/log.gz test_no_failed (__main__.ServicesTest) No failed units ... journal for failed service multipathd.service --- -- Logs begin at Mon 2020-02-10 03:26:38 UTC, end at Mon 2020-02-10 13:56:23 UTC. -- Feb 10 13:56:07 autopkgtest systemd[1]: Starting Device-Mapper Multipath Device Controller... Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module scsi_dh_alua not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module scsi_dh_emc not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module scsi_dh_rdac not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module dm-multipath not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest multipathd[195]: start up Feb 10 13:56:07 autopkgtest multipathd[195]: read /etc/multipath.conf Feb 10 13:56:07 autopkgtest multipathd[195]: DM multipath kernel driver not loaded Feb 10 13:56:07 autopkgtest systemd[1]: multipathd.service: Main process exited, code=exited, status=1/FAILURE Feb 10 13:56:07 autopkgtest systemd[1]: multipathd.service: Failed with result 'exit-code'. Feb 10 13:56:07 autopkgtest systemd[1]: Failed to start Device-Mapper Multipath Device Controller. FAIL == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.WQ5GyY/build.RUe/src/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['multipathd.service loaded failed failed [38 chars]ler'] != [] First list contains 1 additional elements. First extra element 0: 'multipathd.service loaded failed failed Device-Mapper Multipath Device Controller' + [] - ['multipathd.service loaded failed failed Device-Mapper Multipath Device ' - 'Controller'] [regression potential] This updates the test case to ignore failure of multipathd.service if it looks like the dm-multipath module isn't available, so any regression would be limited to incorrectly passing or failing test case. [scope] This is needed at least in Eoan, and probably Focal. This doesn't fail on Bionic or Xenial, but that seems to be because the multipath-utils package (which provides multipathd.service) is not installed during the test for those releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1862667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1862667] Re: systemd autopkgtest 'boot-and-services' fails with linux-kvm
** Description changed: [impact] systemd autopkgtest 'boot-and-services' fails when running with linux- kvm kernel, because that kernel does not set CONFIG_DM_MULTIPATH, so the test detects failed services. [test case] check the autopkgtest results, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/systemd/20200210_144351_da247@/log.gz - test_no_failed (__main__.ServicesTest) No failed units ... journal for failed service multipathd.service --- -- Logs begin at Mon 2020-02-10 03:26:38 UTC, end at Mon 2020-02-10 13:56:23 UTC. -- Feb 10 13:56:07 autopkgtest systemd[1]: Starting Device-Mapper Multipath Device Controller... Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module scsi_dh_alua not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module scsi_dh_emc not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module scsi_dh_rdac not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module dm-multipath not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest multipathd[195]: start up Feb 10 13:56:07 autopkgtest multipathd[195]: read /etc/multipath.conf Feb 10 13:56:07 autopkgtest multipathd[195]: DM multipath kernel driver not loaded Feb 10 13:56:07 autopkgtest systemd[1]: multipathd.service: Main process exited, code=exited, status=1/FAILURE Feb 10 13:56:07 autopkgtest systemd[1]: multipathd.service: Failed with result 'exit-code'. Feb 10 13:56:07 autopkgtest systemd[1]: Failed to start Device-Mapper Multipath Device Controller. FAIL - == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): - File "/tmp/autopkgtest.WQ5GyY/build.RUe/src/debian/tests/boot-and-services", line 68, in test_no_failed - self.assertEqual(failed, []) + File "/tmp/autopkgtest.WQ5GyY/build.RUe/src/debian/tests/boot-and-services", line 68, in test_no_failed + self.assertEqual(failed, []) AssertionError: Lists differ: ['multipathd.service loaded failed failed [38 chars]ler'] != [] First list contains 1 additional elements. First extra element 0: 'multipathd.service loaded failed failed Device-Mapper Multipath Device Controller' + [] - ['multipathd.service loaded failed failed Device-Mapper Multipath Device ' - 'Controller'] - [regression potential] - TBD + This updates the test case to ignore failure of multipathd.service if it + looks like the dm-multipath module isn't available, so any regression + would be limited to incorrectly passing or failing test case. [scope] This is needed at least in Eoan, and probably Focal. This doesn't fail on Bionic or Xenial, but that seems to be because the multipath-utils package (which provides multipathd.service) is not installed during the test for those releases. - - [other info] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1862667 Title: systemd autopkgtest 'boot-and-services' fails with linux-kvm Status in linux-kvm package in Ubuntu: New Status in systemd package in Ubuntu: In Progress Status in linux-kvm source package in Eoan: New Status in systemd source package in Eoan: In Progress Status in linux-kvm source package in Focal: New Status in systemd source package in Focal: In Progress Bug description: [impact] systemd autopkgtest 'boot-and-services' fails when running with linux- kvm kernel, because that kernel does not set CONFIG_DM_MULTIPATH, so the test detects failed services. [test case] check the autopkgtest results, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/systemd/20200210_144351_da247@/log.gz test_no_failed (__main__.ServicesTest) No failed units ... journal for failed service multipathd.service --- -- Logs begin at Mon 2020-02-10 03:26:38 UTC, end at Mon 2020-02-10 13:56:23 UTC. -- Feb 10 13:56:07 autopkgtest systemd[1]: Starting Device-Mapper Multipath Device Controller... Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module scsi_dh_alua not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module scsi_dh_emc not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module scsi_dh_rdac not found in directory
[Touch-packages] [Bug 1862667] Re: systemd autopkgtest 'boot-and-services' fails with linux-kvm
marking as affecting linux-kvm, as I'm not sure the lack of CONFIG_DM_MULTIPATH was intentional or not. ** Also affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Tags added: sts-sponsor-volunteer -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1862667 Title: systemd autopkgtest 'boot-and-services' fails with linux-kvm Status in linux-kvm package in Ubuntu: New Status in systemd package in Ubuntu: In Progress Status in linux-kvm source package in Eoan: New Status in systemd source package in Eoan: In Progress Status in linux-kvm source package in Focal: New Status in systemd source package in Focal: In Progress Bug description: [impact] systemd autopkgtest 'boot-and-services' fails when running with linux- kvm kernel, because that kernel does not set CONFIG_DM_MULTIPATH, so the test detects failed services. [test case] check the autopkgtest results, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/systemd/20200210_144351_da247@/log.gz test_no_failed (__main__.ServicesTest) No failed units ... journal for failed service multipathd.service --- -- Logs begin at Mon 2020-02-10 03:26:38 UTC, end at Mon 2020-02-10 13:56:23 UTC. -- Feb 10 13:56:07 autopkgtest systemd[1]: Starting Device-Mapper Multipath Device Controller... Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module scsi_dh_alua not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module scsi_dh_emc not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module scsi_dh_rdac not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module dm-multipath not found in directory /lib/modules/5.3.0-1010-kvm Feb 10 13:56:07 autopkgtest multipathd[195]: start up Feb 10 13:56:07 autopkgtest multipathd[195]: read /etc/multipath.conf Feb 10 13:56:07 autopkgtest multipathd[195]: DM multipath kernel driver not loaded Feb 10 13:56:07 autopkgtest systemd[1]: multipathd.service: Main process exited, code=exited, status=1/FAILURE Feb 10 13:56:07 autopkgtest systemd[1]: multipathd.service: Failed with result 'exit-code'. Feb 10 13:56:07 autopkgtest systemd[1]: Failed to start Device-Mapper Multipath Device Controller. FAIL == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.WQ5GyY/build.RUe/src/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['multipathd.service loaded failed failed [38 chars]ler'] != [] First list contains 1 additional elements. First extra element 0: 'multipathd.service loaded failed failed Device-Mapper Multipath Device Controller' + [] - ['multipathd.service loaded failed failed Device-Mapper Multipath Device ' - 'Controller'] [regression potential] TBD [scope] This is needed at least in Eoan, and probably Focal. This doesn't fail on Bionic or Xenial, but that seems to be because the multipath-utils package (which provides multipathd.service) is not installed during the test for those releases. [other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1862667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
