"ERROR couldn't save system state: Current machine isn't Zsys, nothing to create" on non zsys system shouldn’t be visible

Bug #1868523 reported by tofono
32
This bug affects 7 people
Affects Status Importance Assigned to Milestone
zsys (Ubuntu)
Fix Released
Undecided
Didier Roche-Tolomelli

Bug Description

Hi, when I try to update the system I get this error even if the operations seem to complete.
Hello.

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

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

Changed in gjs (Ubuntu):
status: New → Confirmed
Paul White (paulw2u)
tags: added: focal
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1868523

tags: added: iso-testing
affects: gjs (Ubuntu) → zsys (Ubuntu)
Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

Is your system a zfs one?

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

I see the same when I install zsys on a system that has zfs, but not with the layout prepared by the ubuntu installer.

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

Right, this is expected. We should just remove the Saving state message here and don’t issue an error visible to the user.

summary: "ERROR couldn't save system state: Current machine isn't Zsys, nothing
- to create"
+ to create" on non zsys system shouldn’t be visible
Changed in zsys (Ubuntu):
status: Confirmed → Fix Committed
assignee: nobody → Didier Roche (didrocks)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package zsys - 0.4.3

---------------
zsys (0.4.3) focal; urgency=medium

  [ Jean-Baptiste Lallement ]
  [ Didier Roche ]
  * Fix GC collection of failed revert or incomplete boots and add tests for
    them (LP: #1870057, #1870054)
  * Account filesystem datasets in GC bucket policy budget, as it was leading
    to under budget results once cleaned up.
  * Fix warning when mounting source is set to default (LP: #1870052)
  * Fix some issues in go-libzfs:
    - it was not assigning the correct dataset type, leading to a segfault
      if the user has a zfs volume in a pool.
    - Perf enhancements by only loading our needed properties to reduce the
      amount of C performed calls.
  * Enhance apt hook:
    - Only display output and errors if running on ZFS systems
      (LP: #1868523, #1870304).
    - Suppress the 20 minutes grace period and only prevent multiple snapshots
      when unattended-upgrades is running.
  * Transition from 19.10: change the userdata user properties on first boot
    for machines installed from 19.10 without zsys installed.
  * Add apport hook.
  * Fix various mispells, simplify some code and remove some ineffective
    assignements.
  * Fix error message typos.
  * Fix generator check on CI, update bug template and update CI to use Go 1.14
    in preparation of focal switch to 1.14.

 -- Didier Roche <email address hidden> Wed, 08 Apr 2020 14:42:21 +0200

Changed in zsys (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Deepak Ranolia (deepak-ranolia) wrote :

I have the same issue as well

my log files are is as follows

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

Hey Deepak,

I’m a little bit unclear about your issue which is the different from the original bug report. ZSys was complaining on ZSys system when doing apt install or so: your logs don’t show that up.

If you are running on a non ZSys system (meaning: you didn’t select ZFS on root installation), it’s normal that any ZSys service or command returns those error and you should remove ZSys. If this is not the case, please file another bug with ubuntu-bug zsys to report relevant informations to us, thanks!

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.