The `Size()` function will be used in the fde device-setup helpers
to get the size of the given partition so that it then can
create the right mapping devices for systems that use e.g.
inline encryption engines.
When both variants of the test run on the same host where the TAGS are sticky
due to systemd 247+, then any TAGS added due to the first variant will break the
assumptions of the second variant. Make sure that we check proper
TAGS/CURRENT_TAGS when verifying assumptions.
Signed-off-by: Maciej Borzecki <maciej.zenon.borzecki@canonical.com>
Use core20 as base snap for focal system
The test is failing on focal with this error:
+ lxd.lxc exec ubuntu -- find /var/run/systemd/generator/ -name
container.conf
+ MATCH '/var/run/systemd/generator/snap-core18.*mount.d/container.conf'
grep error: pattern not found, got:
/var/run/systemd/generator/snap-snapd-12883.mount.d/container.conf
/var/run/systemd/generator/snap-core20-1081.mount.d/container.conf
/var/run/systemd/generator/snap-lxd-21545.mount.d/container.conf
Skip i386 because core20 is not available for pc-i386 architecture
This is failing on beta validation:
+ snap install --dangerous netplan-snap-20.snap
error: cannot perform the following tasks:
- Ensure prerequisites for "netplan-snap" are available (cannot install
snap base "core20": no snap revision available as specified)
The test tests/nested/manual/core20-cloud-init-maas-signed-seed-data is
failing trying to create the extra-snaps directory which is being
created while the test is prepared.
+ mkdir
/home/gopath/src/github.com/snapcore/snapd/tests/nested/manual/core20-cloud-init-maas-signed-seed-data/extra-snaps
mkdir: cannot create directory
‘/home/gopath/src/github.com/snapcore/snapd/tests/nested/manual/core20-cloud-init-maas-signed-seed-data/extra-snaps’:
File exists
