Update form openSUSE Leap 15.6 to 16.0

WalterH · 2026-04-13T16:12:44+00:00

openSUSE 15.6 is nearly at the end of its life cycle. The Grommunio developers have resolved the dependency issues for the openSUSE 16.0 packages, so it is t...

Duese6

I noticed yesterday that after the first reboot, the repo file (/etc/zypp/repos.d/grommunio-base.repo), which contains the base repo for Leap 16.0, was no longer there. You might not notice this right away.

dneuhaeuser

Duese6
I can confirm this:

# zypper lr

# | Alias             | Name                                         | Enabled | GPG Check | Refresh
--+-------------------+----------------------------------------------+---------+-----------+--------
1 | grommunio         | grommunio                                    | Ja      | (r ) Ja   | Ja

I have no idea when and how this happened...

WalterH

Duese6 I have the openSUSE repositories in the file /etc/zypp/repos.d/bas.repo.

millilenium

Vielen Dank für die Anleitung, habe es nun (auch mit der aktualisierten Anleitung) versucht und erhalte immer nach dem Reboot bei Schritt 20 folgende Fehlermeldungen.
Ein Login via ssh, WinSCP, putty etc. ist nicht mehr möglich....
Welche Ursache könnte das haben? Es läuft alles virtualisiert auf einer DS1621xs+ - die CPU-Voraussetzungen sind erfüllt...

Danke!

crpb

millilenium

To temporary disable that buggy "thing" you can do the following:

Hold left Alt + Cursor to the right
Press Return
Login as "root" with your password.
run: systemctl --now disable grommunio-cui@.service

externa1

millilenium
I had the same on one supported appliance installion, after disabling (mask) grommunio-cui i now get further but stops with no network as seeh here:

Not able to connect to console (vm on prosmox) as the console stuck without network has to rollback the snapshot

what the hell is opensuse distribution - every dist upgrade is like rolling dices

rg
Christian

DVCon

Duese6 But this "killed" the complete index and all old archived mails were not visible anymore. In my case this is still a testsystem.

Yes, that wasn't a nice surprise this morning.
I got the mails back with reindex -a -p, though the total message count in the search window is wrong now. It's my own server. So I can live with this. But the whole thing should better not happen on the servers of my clients.

millilenium

crpb Thanks for the fast reply, I will have a try

Duese6

I just successfully migrated a second test VM. This one even has an LDAP connection. I didn't notice any issues at this point.
But it is true that the .repo file "disappears" during the update process itself, and quite a lot is deleted from /usr/lib. Among other things, the part containing grommunio-archiv. For whatever reason.

DVCon

I was again able to connect to the server with filezilla after replacing
Subsystem sftp /usr/lib/ssh/sftp-server
with
Subsystem sftp /usr/libexec/ssh/sftp-server
in /etc/ssh/sshd_ config and restarting sshd.

Duese6

DVCon
okay I did not ran in that problem as I changed to @crpb 's suggestion with using override config in folder sshd_config.d which only contains "PermitRootLogin yes"
So I assume you used an older version of sshd_config with the wrong path in it

crpb

I didn't loose any repo but i did this part a bit different i guess.

https://community.grommunio.com/d/2439-upgrade-grommunio-appliance-von-leap-156-auf-leap-16-erfahrungen/5

update opensuse repositories

`rm /etc/zypp/repos.d/grommunio-base.repo /etc/zypp/repos.d/base.repo``

add opensuse repos..

zypper addrepo http://cdn.opensuse.org/distribution/leap/16.0/repo/non-oss openSUSE:repo-non-oss
zypper addrepo http://cdn.opensuse.org/distribution/leap/16.0/repo/oss openSUSE:repo-oss

sed 's/15.6/16.0/g' /etc/zypp/repos.d/grommunio.repo
zypper --gpg-auto-import-keys refresh

Or even easier.

rm /etc/zypp/repos.d/*
zypper addrepo http://cdn.opensuse.org/distribution/leap/16.0/repo/non-oss openSUSE:repo-non-oss
zypper addrepo http://cdn.opensuse.org/distribution/leap/16.0/repo/oss openSUSE:repo-oss
zypper addrepo --enable --refresh --no-keep-packages 'https://download.grommunio.com/community/openSUSE_Leap_16.0' grommunio
# optional
grommunio-repo supported

Duese6

crpb
One question regarding the repository setup:
Is OSS + non‑OSS currently sufficient for Leap 16.0, or should an update repository be expected as well?
On Leap 15.6 the /update repo played an important role, so I just want to confirm this is expected behavior for 16.0 at the moment.

crpb

crpb update opensuse repositories

click in the link above, it is all explained

Andy

WalterH I have the openSUSE repositories in the file /etc/zypp/repos.d/bas.repo.

Same here with the single repo

crpb Or even easier

Therefore I will try this after clone my VM, will see.

millilenium

externa1 Same problem here after cui masking…

Duese6

externa1
Hi.

I’m running VMs on PVE 9.1.x myself and didn’t see comparable issues during the Leap upgrade.
When dbus can’t start and wicked fails completely, my guess would be a broken base system after the distro upgrade (possibly VM/device related).

DVCon

Duese6
At first, I didn't notice an issue with SSH, because I login with a key. The sftp issue came later, and I couldn't fix it with the override.

externa1

Duese6
I have a test system (grommunio community) and a supported grommunio installation both on the same PVE Server 9.1
the community system is a bit younger than the supported installation (but both with the appliance that introduced xfs file system as default)- there the upgrade went with minor issues (plymouth, ssh) as already reported by others and solved - on the supported vm the dbus error came up after reboot and no network at all.
have to say that the testsystem is HW configured with UEFI and EFI Disk, where else the support is legacy but thats the only difference between the two vm's

rg
Christian

millilenium

Even a change to UEFI and Type Q35 makes no difference, the failure is the same as mentioned above

crpb

Well, there is an easy solution if dhcp-configured, otherwise you need to adapt.

~~wicked~~ => systemd-networkd

this will prevent network-configuration via yast / grommunio-cui so think or backup before you do this.

systemctl disable wicked ; 
systemctl enable systemd-networkd systemd-resolved ; 
printf "[Match]\n#Name=e*\nType=ether\n\n[Network]\nDHCP=yes\n\n[DHCPv4]\nUseDomains=true\nClientIdentifier=mac\n" | tee /etc/systemd/network/eth.network ;
reboot

EDIT: well, if that fixes your dbus problem i'm not sure

millilenium

externa1 mine is also supported version, I even tried step 5 with grommunio-update update supported --noreboot

crpb

The one test-system i upgraded was also with the supported repo. No issues here other than silly plymouth.

« Previous Page Next Page »