http://bugzilla.suse.com/show_bug.cgi?id=1130392 http://bugzilla.suse.com/show_bug.cgi?id=1130392#c2 José Iván López González changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jlopez@suse.com --- Comment #2 from José Iván López González --- Yes, after disabling a volume feature (snapshots, adjust_by_ram, or the volume itself) the disabled feature is never restored. Good catch! Definitely, [`Yast.deep_copy`](https://github.com/yast/yast-storage-ng/blob/master/src/lib/y2storage/initia...) does not work as I expected. The `VolumeSpecification` objects from `settings.volumes` need to be duplicated wherever the setting are copied. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1130392 http://bugzilla.suse.com/show_bug.cgi?id=1130392#c3 David Diaz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |dgonzalez@suse.com Resolution|--- |FIXED --- Comment #3 from David Diaz --- Fixed :) A real deep copy of settings is being made now, using Marsal[1]. So, it should work as expected in `yast-storage-ng >= 4.1.79`. PRs: - https://github.com/yast/yast-storage-ng/pull/889 - https://github.com/yast/yast-storage-ng/pull/893 --- [1] https://ruby-doc.org/core-2.6.2/Marshal.html -- You are receiving this mail because: You are on the CC list for the bug.