Hello
I have been using OpenSUSE for almost 40 years (1993) and I have seen a lot of changes but I never faced such a basic mess-up. Upgrade to Leap 16.0 is de facto impossible. I see in forums that I am not the only one but none of the listed “solutions” works.
As Agama works today, it would be easier to upgrade from Leap 15.x to Centos that to Leap 16.0
I support many small companies where small servers are installed using a very simple safe system.
2 partitions one for EFI and one for LVM.
LVM offers 3 virtual disks /root in BTRFS /swap and /home (Raid mirrored, LUKS encrypted XFS).
With such config, I do not need to know their critical passwords, so I do not need to see their data even for an upgrade or disk swap.
Until now, I used to do a full OpenSUSE new install just keeping /home every 18 months. A simple solution to keep the system clean and the user data untouched. But with AGAMA it’s impossible.
I do not care that the GUI are polished, even a CLI mode would better do. But without a correction, CENTOS will have to be the upgrade path.
AGAMA can read the LVM including the encrypted disk but there is no way to request to reuse an existing volume or even just to ignore it.
I do not care about the replacement of YAST (even if the text mode over ssh and serial telnet was sometime handy) but they are two missing features in AGAMA blocking me :
reusing (encrypted & RAID) logical volumes (at least for /home)
importing the passwd file
Could you please let us know when that will be available.
Dominig ar Foll
Retired Linux system architect at Intel Open Source.
I would recommend reporting these requirements to the agama project directly - these forums are user-to-user support; we don’t build the software, we just help people use it.
From what I understand, Agama can be customized in a way similar to how autoyast was done, so that may be the path to look at.
@suse_rasputin The installer works fine, it’s the edge user cases that don’t… Now, creating a profile may help here, not really in a position to test (yet).
If I want a stock standard install with btrfs and a desktop environment on a device, it works fine, no issues…
If I want a server install, using Hardware RAID it works fine, no issues…
If I want software RAID, one has to use the installer shell and command line to create, however after that the installer works fine.
@suse_rasputin That has nothing to do with the current Leap 16.0 Agama installer, that’s the development version. If you want to try that out there is the Leap 16.1 alpha/beta/use_at_your_own_risk version available…
Hello
Sorry but taking into account upgrade path should have been a major concern and clearly it was not.
The installer was definitely not production ready for a concept such as Leap distro.
It cannot even upgrade from what was the default secured install from the previous OpenSUSE release.
As I did not work/help on creating the distro, I do not want to get into hard chat.
Agama might be a nice project, I have eared several time that it was work in progress, it can do many thing BUT it’s was not ready for production.
I will see with 16.1 how it has progressed and if it’s “production” ready.
