[Bug 1991829] [NEW] machinectl read-only does not work

Launchpad Bug Tracker 1991829 at bugs.launchpad.net
Thu Oct 6 15:30:15 UTC 2022


You have been subscribed to a public bug by Simon Chopin (schopin):

[impact]

machinectl read-only does not work

[test case]

On a system where the systemd machines dir is *not* on a btrfs volume
(e.g. it's on a normal ext4 fs), create an image 'test' and then:

$ sudo machinectl image-status test
test
            Type: directory
            Path: /var/lib/machines/test
        Hostname: ubuntu
              OS: Ubuntu 20.04.5 LTS
              RO: writable
         Created: Wed 2022-10-05 13:41:15 EDT; 34s ago

$ sudo machinectl read-only test
Could not mark image read-only: Access denied

[regression potential]

failure marking images ro or rw

[scope]

this is needed in all releases that include machinectl

this is fixed upstream by 137d162c42ed858613afc3d7493d08d4ae6d5c1b

** Affects: systemd (Ubuntu)
     Importance: Low
         Status: Triaged

** Affects: systemd (Ubuntu Focal)
     Importance: Low
         Status: New

** Affects: systemd (Ubuntu Jammy)
     Importance: Low
         Status: New

** Affects: systemd (Ubuntu Kinetic)
     Importance: Low
         Status: Triaged

-- 
machinectl read-only does not work
https://bugs.launchpad.net/bugs/1991829
You received this bug notification because you are a member of Ubuntu Foundations Bugs, which is subscribed to the bug report.



More information about the foundations-bugs mailing list