|
Bugzilla – Full Text Bug Listing |
| Summary: | Selecting BtrFS snapshots sometimes doesn't preconfigure snapper | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Mindaugas Baranauskas <opensuse.lietuviu.kalba> |
| Component: | Installation | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED FEATURE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | aschnell, igonzalezsosa |
| Version: | Leap 42.2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| See Also: | https://bugzilla.suse.com/show_bug.cgi?id=1008307 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | |||
| Bug Blocks: | 1008307 | ||
| Attachments: |
y2logs.tgz
no snapper configuration exist Querying error after closing "no snapper configuration exist" error Warning about not enough space |
||
|
Description
Mindaugas Baranauskas
2016-11-03 12:12:05 UTC
Created attachment 700475 [details]
y2logs.tgz
For example, during openSUSE 42.2 RC2 installation I selected to use BtrFS with snapshoots, but YaST snapper failed to open because "no snapper configuration exist" error.
Created attachment 700477 [details]
no snapper configuration exist
Error message at opening YaST Snapper module
Created attachment 700479 [details]
Querying error after closing "no snapper configuration exist" error
Seems snapper is automatically preconfigured, if I select to install openSUSE into larger partition. I think user should be notified if snapper can not be preconfigured (when it is supposed to be) Created attachment 700920 [details]
Warning about not enough space
First of all, thanks for reporting. If you check the proposal settings, you'll see that "Enable snapshots" if disabled when there's not enough space. If you check this option and you try to continue, you'll get a warning (I've attached a screenshot). Having said that, it's not clear enough whether we should show an additional warning and where. I think that such a change should be also be discussed with UX experts. So I'm going to close this bug report and, if you want us to change the behavior, just please create a FATE on https://fate.suse.com/ so we can evaluate such a requirement. Thanks in advance! |