TPM/FDE: Use ignore action in VM - #16620
Conversation
|
Could we keep it when |
Sure, should that be done only if some of the spread tests above are failing (I saw you added the tag which should trigger those nested tests, right)? |
|
Specifically this test: |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #16620 +/- ##
==========================================
- Coverage 79.05% 79.04% -0.01%
==========================================
Files 1369 1369
Lines 190708 190710 +2
Branches 2465 2465
==========================================
- Hits 150757 150756 -1
- Misses 30863 30865 +2
- Partials 9088 9089 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Closing/Reopening to ensure the nested tests are ran |
|
Mon May 4 14:25:18 UTC 2026 Failures:Executing:
Skipped tests from snapd-testing-skipIf you wish to have any of the below tests run in your PR, in your PR description, add 'unskip:' followed by a copy-and-pasted list (without variants) of the below tests you wish to run (unskip plus test list must be valid yaml)
|
3237147 to
a1f2e75
Compare
|
hum, even with those, the nested tests are still broken. Any guidance to run the setup locally for easier debugging? |
They are not stable. Maybe a re-run will help. |
|
Some nested tests passed and not others, rerunning… |
|
Maybe we will need to rebase. Not sure if the tests need fixes. |
a1f2e75 to
d4cf681
Compare
|
(rebased, let’s see for the tests) |
|
@didrocks sorry to ask you that again, but can you rebase once more? |
We relaxed in snapd 2.72 the preinstall check to allow installation in VMs. Now that we have the action API, an ignore action will be available to the rest of the system and users. Restore this. However, keep the current behaviour for nested tests as muinstaller does not support interactions to ignore errors.
New defaults does not permit VM.
d4cf681 to
5f53efa
Compare
|
Rebased |
snapd now correctly detects a VM environement and provides a corresponding error via the actions API. See canonical/snapd#16620
With our testing, we discovered that there has been some leftovers from previous snapd release to allow installation in VM without triggering the secboot ErrKind to allow users to perform the ignore action.
Restore the default then.