[Bug 1991829] Re: machinectl read-only does not work

[Steve Langasek]

The release of this SRU has been rolled back in jammy because of bug
#2035406 which appears to be a regression introduced in the new version
of systemd.

** Changed in: systemd (Ubuntu Jammy)
       Status: Fix Released => Triaged

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

Title:
  machinectl read-only does not work

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Won't Fix
Status in systemd source package in Jammy:
  Triaged
Status in systemd source package in Kinetic:
  Fix Released

Bug description:
  [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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1991829/+subscriptions