On Thu, 2015-03-26 at 15:35 -0600, Chris Murphy wrote:
Custom partitioning does not allow convenient removal of volume
including snapshots (btrfs, LVM)
This might seem like it snuck up on us, but I predicted it would
become a problem in two different RFEs one of which is ~18 months
 Neverthless, openSUSE's default highly snapshottycentric behavior
enhances this problem; but so does Docker on Btrfs; and now in
systemd-219 it's using Btrfs snapshots for container cloning. So
things are going to continue coming out of our ears.
So anaconda team got in touch and said they don't believe this should
be a blocker and would like it to be re-considered:
I'm therefore dropping the AcceptedBlocker tag which makes it back
into a proposed blocker.
We can wait for the next blocker meeting to re-consider it, or come to
a consensus here.
I think Chris makes a good case that it's a significant issue, but on
the other hand, anaconda devs make a fair point that this isn't
exactly a 'bug', but a case where anaconda's current design and
implementation doesn't work well; 'fixing' it isn't a simple case of
'make this code do what it's supposed to do', but 'come up with and
implement a design with a new capability', it's new engineering, it's
not bug fixing.
There are ways to deal with the issue; remove the volume using another
tool before running anaconda, do it from a console while anaconda is
The criterion involved here says the installer must be "able" to
"Remove existing storage volumes", including LVM and btrfs volumes.
Removing all the snapshot volumes is possible - tedious, but possible.
So personally I'm OK with the bug not being a release blocker. Other
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net