snapd doesn't regenerate existing mount units when mountunit template changes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Triaged
|
High
|
Unassigned |
Bug Description
I have a cluster that is supposed to have two identical members. However I've spotted inconsistencies although the versions of snap and snap core are the same. The only difference that I was able to spot is the order of installation, note that on qbs01 core18 was installed before core and on qbs02 it is the other way round:
support@qbs01:~$ diff -u <(cat /etc/systemd/
--- /dev/fd/63 2021-05-19 20:58:22.400729632 +0200
+++ /dev/fd/62 2021-05-19 20:58:22.396729637 +0200
@@ -1,12 +1,13 @@
[Unit]
Description=Mount unit for core18, revision 2066
Before=
+After=
[Mount]
What=/
Where=
Type=squashfs
-Options=
+Options=
LazyUnmount=yes
[Install]
support@qbs01:~$ diff -u <(snap info core core18 --abs-time) <(ssh qbs02 snap info core core18 --abs-time)
--- /dev/fd/63 2021-05-19 21:02:59.508319436 +0200
+++ /dev/fd/62 2021-05-19 21:02:59.508319436 +0200
@@ -9,7 +9,7 @@
type: core
snap-id: 99T7MUlRhtI3U0Q
tracking: latest/stable
-refresh-date: 2021-05-
+refresh-date: 2021-05-
channels:
latest/stable: 16-2.50 2021-05-
latest/
@@ -27,7 +27,7 @@
type: base
snap-id: CSO04Jhav2yK0uz
tracking: latest/stable
-refresh-date: 2021-05-
+refresh-date: 2021-05-
channels:
latest/stable: 20210507 2021-05-
latest/
affects: | snapcraft → snapd |
Changed in snapd: | |
status: | Expired → New |
summary: |
- snap core update yields different results depending on the order of - installation + snapd doesn't regenerate existing mount units when mountunit template + changes |
Most likely the mount units on qbs01 and qbs02 were generated by different versions of snapd. I suspect that qbs01 was seeded (maybe even pre-seeded) by an older version of snapd, which is why it does not have the dependency on zfs. TBH, looks like qbs02 is using an edge version of snapd?
Can you attach a similar diff for the snapd snap? Also the output of snap changes from both hosts would be useful.