ephemeral-disk-warning yields /mnt 0444 immutable on package update when /mnt is bind-mounted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
walinuxagent (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Both /etc/init/
We had one customer who had a large number of yarn nodes go bad because of this. Output from `journalctl -u ephemeral-
-- Logs begin at Thu 2018-03-01 00:08:50 UTC, end at Tue 2018-03-13 22:33:22 UTC. --
Mar 01 00:09:14 wn103-limitl systemd[1]: Starting Write warning to Azure ephemeral disk...
Mar 01 00:09:14 wn103-limitl systemd[1]: Started Write warning to Azure ephemeral disk.
Mar 05 06:31:44 wn103-limitl systemd[1]: Stopped Write warning to Azure ephemeral disk.
Mar 05 06:32:41 wn103-limitl systemd[1]: Starting Write warning to Azure ephemeral disk...
Mar 05 06:32:41 wn103-limitl ephemeral-
Mar 05 06:32:41 wn103-limitl ephemeral-
Mar 05 06:32:41 wn103-limitl ephemeral-
Mar 05 06:32:41 wn103-limitl ephemeral-
Mar 05 06:32:41 wn103-limitl ephemeral-
Mar 05 06:32:41 wn103-limitl systemd[1]: Started Write warning to Azure ephemeral disk.
Which was right after the walinuxagent package was updated to 2.2.21+
I was able to repro the problematic lines on my dev box, where I have two directories bind-mounted to my home dir:
$ dev_resource=
$ dev_resource_
$ echo $dev_resource_mp
/mnt /home/paulmey/
$ cat /proc/mounts |grep sdb1
/dev/sdb1 /mnt ext4 rw,relatime,
/dev/sdb1 /home/paulmey/
/dev/sdb1 /home/paulmey/
It looks like this script needs to be more specific in determining the mountpoint, or maybe even make its own temporary mount point for the ephemeral drive, since /proc/mount does not indicate which mounts are bind mounts (and what the source directory for that bind mount was).
It looks like LP#1626318 is also an example of this bug.
tags: | added: server-triage-discuss |
tags: | removed: server-triage-discuss |
Changed in walinuxagent (Ubuntu): | |
importance: | Undecided → Medium |
status: | Confirmed → Triaged |
Status changed to 'Confirmed' because the bug affects multiple users.