Bug 1226109

Summary:	Aeon installation failed with the newer installer
Product:	[openSUSE] openSUSE Aeon	Reporter:	StellarTerror <StellarTerror2>
Component:	Installation	Assignee:	Richard Brown <rbrown>
Status:	CONFIRMED ---	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P2 - High	CC:	StellarTerror2
Version:	Current	Flags:	rbrown: needinfo? (StellarTerror2)
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE Tumbleweed
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	the log file of the installation error

Description StellarTerror 2024-06-08 12:33:01 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:126.0) Gecko/20100101 Firefox/126.0
Build Identifier: 

i was prompted with a 

Command /usr/bin/cat /var/
lib/tik/mig/passwd.out FAILED

please refer to the attached tik.log file

Reproducible: Always

Steps to Reproduce:
1.Write the image on a USB
2.Boot into it
3.It shows the installion failure system is shutting down warning
Actual Results:  
I was prompted for a system shutdown

Expected Results:  
I should've been able to install properly

Comment 1 StellarTerror 2024-06-08 12:33:45 UTC

Created attachment 875384 [details]
the log file of the installation error

Comment 2 Richard Brown 2024-06-10 09:13:00 UTC

Fixing severity - migration is optional, so it could never be a critical bug

Comment 3 Richard Brown 2024-06-10 09:29:18 UTC

Hi, thanks for the bug report, but its lacking some important details that as a reporter you should have included:

During your first installation (at 12:19 on 08-06-2024)

- You were prompted that an existing backup existed (when it did not)
- You chose 'No' to delete the backup that didn't exist
- You got an error message "Command /usr/bin/rmdir /var/lib/tik/mig/mnt FAILED" and that's how your install ended

During your second installation (at 12:29 on 08-06-2024)

- You were again prompted that an existing backup existed (when it did not)
- You chose 'Yes' to use the backup that didn't exist
- You got the error message you used to report this bug with

Now I'm not writing all this to scald you, but just to help you write good bug reports in the future..I nearly wasted a lot of time debugging the second installation when infact ALL your issues were related to the first

During your first installation, the installer was probing your existing installation on your target disk

For some reason, after probing, your system refused to unmount the disk cleanly. This left a mount point lingering in /var/lib/tik

tik's migration module assumes if there is ANY files in /var/lib/tik then that's a backup which can be used.. but there was no backup..just the broken mount point from your misbehaving existing filesystem

Every other problem came after that point - your first installation failed because of the misbehaving filesystem , and your second installation failed because your tried to use a backup that wasn't actually there so it was trying to restore files that didn't exist

So, we need to address the core bug(s)

tik should use somewhere else for it's mounting than the same location we check for backups

and we need to figure out a way of more gracefully handing misbehaving existing filesystems

We'll get on it..meanwhile, a quick and dirty work around would be to backup anything you want from your existing installation, format the disk you want to install, and then Aeon will install fine.

Comment 4 Richard Brown 2024-06-10 13:15:03 UTC

Prio High - want to fix before Release

Comment 5 Richard Brown 2024-06-10 18:52:25 UTC

partly addressed in tik 1.0.7's improved mounting behaviour

Can you please retest using openSUSE-Aeon-Installer snapshot versions 20240611 or later (once they exist)?