Jammy is tested. There are multiple tests here, and I did some extra tests that are not in the testplan. Due to the amount of data that is tested, I attached it as a .txt file, but the following tests were performed:
1. Testing that multipathd.service is restarted on upgrade from the current package
2. Testing downgrade to previous package
3. Installing a fresh package (no warning message here because dpkg compare is lt-nl)
4. Upgrading to a future package
5. Testing functionality after upgrading to the new package with multipath devices
6. Testing that multipath devices are still usable after upgrading
Jammy is tested. There are multiple tests here, and I did some extra tests that are not in the testplan. Due to the amount of data that is tested, I attached it as a .txt file, but the following tests were performed:
1. Testing that multipathd.service is restarted on upgrade from the current package
2. Testing downgrade to previous package
3. Installing a fresh package (no warning message here because dpkg compare is lt-nl)
4. Upgrading to a future package
5. Testing functionality after upgrading to the new package with multipath devices
6. Testing that multipath devices are still usable after upgrading
The only contentious thing I noticed is that on upgrade or install, the socket is inactive. This is captured already in https:/ /bugs.launchpad .net/ubuntu/ +source/ multipath- tools/+ bug/2034471 but worth mentioning here. The utility works fine even with this.