systemd-analyze verify reports failure

Bug #1817627 reported by Scott
58
This bug affects 12 people
Affects Status Importance Assigned to Milestone
Ubuntu Manpage Repository
Invalid
Undecided
Unassigned
systemd (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Version 237 and 238 of systemd-analyze have a known issue: https://github.com/systemd/systemd/issues/8592

When will a fix be posted?

description: updated
Revision history for this message
Joshua Powers (powersj) wrote :

Marking the Ubuntu Manpage Repository task invalid and adding the systemd (Ubuntu) task.

Changed in ubuntu-manpage-repository:
status: New → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

The commit fixing the issue is https://github.com/systemd/systemd/commit/114110cd

Could you describe why you think it's an issue important enough to justify a stable update, it seems only a warning but not having consequences? Do you use a real mount for the /tmp directory?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in systemd (Ubuntu):
status: New → Confirmed
Revision history for this message
Karlis (karlism) wrote :

I use separate mountpoint for /tmp directory and also am affected by this issue on latest Ubuntu 18.04.2 with all package updates installed.

Revision history for this message
Daniel Muñoz (danielmunoz) wrote :

I can confirm that this bug is on Ubuntu 18.04.2 LTS with all package installed. It happens on every machine I used 18.04 on.

So you can't use `systemd-analyze verify` to verify unit files on 18.04.

I think this need to be solved.

Revision history for this message
Mark Stosberg (markstos) wrote :

This is a scary bug. I was just trying to verify the syntax of a timer file using systemd v237. I got an error message back suggesting something like rm -rf / was attempted to be executed instead!

   $ sudo systemd-analyze verify /etc/systemd/system/my.timer
   Attempted to remove disk file system, and we can't allow that.

Backporting this fix could help reduce the risk of heart attacks.

Revision history for this message
Paweł Krawczyk (pawel-krawczyk) wrote :

This affects each system where /tmp is *not* on tmpfs which affects a lot of cloud-built servers and effectively prevents usage of systemd-analyze verify in Ansible, Puppet etc.

Revision history for this message
Bryant Finney (bryant-finney) wrote :

I am also very interested in this fix; it is currently preventing integration with a CI/CD pipeline for deploying my company's web app to AWS cloud-based Ubuntu 18.04 servers.

Revision history for this message
Philip Kirkbride (kirkins) wrote :

Also in need of a fix. Trying to run a very simple and popular program as a service and it's not working due to this.

Revision history for this message
Dan Streetman (ddstreet) wrote :

please reopen if this is still an issue

Changed in systemd (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Torsten Homberger (homberger) wrote :

this is still an issue

Changed in systemd (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Nick Rosbrook (enr0n) wrote (last edit ):
Changed in systemd (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.