Bug 1224824 - Install fails if a previous installation has been aborted during migration backup
Summary: Install fails if a previous installation has been aborted during migration ba...
Status: RESOLVED FIXED
Alias: None
Product: openSUSE Aeon
Classification: openSUSE
Component: Installation (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Richard Brown
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-22 03:18 UTC by Martin Abele
Modified: 2024-05-23 20:04 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
logfile (3.87 KB, text/x-log)
2024-05-22 03:18 UTC, Martin Abele
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Abele 2024-05-22 03:18:01 UTC
User-Agent:       Mozilla/5.0 (Windows NT 10.0; rv:126.0) Gecko/20100101 Firefox/126.0
Build Identifier: 

Installation on a Aeon RC1 was started normal. The installations was terminated by the user during the backup of home (because it took longer than expected and the user had to terminate the installation). Subsequent installations failed, even with newly flashed installations devices. The reason seems to be that a snapshot of /home on the source installation already exists and a creating a new snapshot fails.

Reproducible: Always

Steps to Reproduce:
1. Start installation on a system with Aeon installed
2. Select to migrate existing users
3. Interrupt the installation during the backup
4. All subsequent installations with migration fails
Actual Results:  
Installation with migration not possible anymore

Expected Results:  
Previous snapshots (/home/homebk) should be deleted before a new snapshot is created
Comment 1 Martin Abele 2024-05-22 03:18:55 UTC
Created attachment 875008 [details]
logfile
Comment 2 Richard Brown 2024-05-22 10:52:56 UTC
This log doesn't look valid, so I'd like to understand what you did that you didn't document in your report first

/dev/disk/by-id/dm-name-cr_root doesn't seem like a valid device path I'd expect the get_disks function to detect

Can you please explain your hardware/disk setup here? I don't want to prioritise bugs on artificial scenarios/not-real hardware :)
Comment 3 Richard Brown 2024-05-22 12:52:22 UTC
Even with the mysterious disk..addressed in https://github.com/sysrich/tik/pull/15
Comment 4 Richard Brown 2024-05-22 13:58:05 UTC
Fixed in tik 1.0.0
Comment 5 Martin Abele 2024-05-23 16:35:43 UTC
My Aeon RC1 is installed on a LUKS encrypted drive. After startup with the installer USB, I opened a terminal to open the LUKS drive. Then started the installer as normal. The migration runs through like normal (if there wasn't a previous terminated migration as described in this bug report).
Comment 6 Richard Brown 2024-05-23 20:04:54 UTC
That’s fine, what you did manually tik now does itself as a feature 

Sweet