Univention 5.2 & NextCloud

Well, well, well, we may need to differentiate between contractual and perhaps moral obligations, or business sense here.

You say “It’s UCS’s responsibility to ensure compatibility and not simply refer to the application developer” and IMHO that is the biggest issue here, because actually the delineation of responsibilties between Univention and its 3rd party providers has likely never been properly defined.

And the base of that problem im my eyes is that Univention has failed to properly define their strategy and service offerings. Instead they have followed a creeping featurism approach, where they picked up things that seemed cool at the time, but now turn out to be too expensive or difficult to handle without those 3rd party contracts in place.

I believe NextCloud and Univention agreed to collaborate at one point to promote each other, but now have diverging priorities without a contract (or a budget) to bind them. And the first issue is obviously who is to pay for the continued integration effort. Univentions evidently expects a sponsor, NextCloud probably doesn’t see how they earn money from Univention support contracts.

And since I, like many others, never paid a single penny to Univention (nor NextCloud), we may cry and howl, but can’t really talk about obligations.

They are completely free to be unusable!

Of course my chances of selling Univention to my employer, or even shelling out a subscription for my own private family use, have fallen to zero because of this: investing into projects that seem on a death spiral is very hard.

So I very much doubt that is a smart idea or will get them other paying customers ready to escape M$ or Google clutches, but that’s just me.

I’ve tried to motivate them a little, but so far without effect, most likely because money is tight, even if the window of opportunity won’t open much wider.

I’ve heard that Snap or container deployments of NextCloud aren’t that difficult, but these are also 3rd party efforts, nothing that NextCloud themselves support officially: like many other open source software projects, they may believe they can’t make things too easy for freeloaders.

Well, paid or not paid, I think you have to be judged by your words! Quote: “This app meets all of Univention’s quality criteria for use in a professional environment. These include, among other things, timely updates, commercial support offers, integration with UCS Identity Management, and support for the current UCS version.”

I share your frustration. There is a new version of the Nextcloud App in the Test App Center which currently doesn’t succeed in all upgrade scenarios. We are waiting since weeks for Nextcloud to look into this.

3 Likes

Thank you for the clarification. Is this test version available somewhere such that potentially the community could help with testing and bug fixing?

The resources needed are linked below. Not sure if you can actually help, as the build & release can only be done by Nextcloud:

On a test machine, you can activate the Test App Center (DO NOT DO THAT ON ANY PRODUCTION ENVIRONMENT):
https://docs.software-univention.de/app-center/latest/en/lifecycle.html#testing-test-app-center

Source Code of the App is hosted by Nextcloud:

4 Likes

You made my day with this comment.

I could almost see you walking into the room, stomping your feet and throwing teddies :rofl:

You’ve been on the forum for about 5 year, so I’m guessing you’ve been happily using UCS all this time. All of a sudden, UCS’ and Nextcloud’s behaviour are unacceptable?

It’s been said, time and time again that things like UCS, Nextcloud, OX etc, are really hard to coordinate, especially if you demand a single uniform interface. But they do work well on their own and do integrate too.

If you spend half a day to set up everything properly (in their own little spaces) you will never have to worry of apps staying behind or compatibility. This is the beauty of open source.

I’m glad the teacher enters the room with a raised finger and explains that Nextcloud can be used independently of UCS! I see you’ve understood the problem! Not!!!

Have a nice Day

2 Likes

Thank you very much for the thumbs up!

I don’t mind waiting but I guess everyone would appreciate some timeline and updates every now and then, be it in one of the discussions here or in the rather frequent newsletter you send.

Thank you very much.

1 Like

Thanks for pointing to the Test App Center.

Are the test reports which fail somewhere available?

I recommend to join the discussion in the Nextcloud GitHub issue: Bump to NC 30 by blizzz · Pull Request #208 · nextcloud/univention-app · GitHub

done. Now the ball is on Univention’s side.

3 Likes

Hi, the updated Nextcloud App has been released last night for UCS 5.0 and 5.2.

4 Likes

Thanks Ingo, I know it’s not been from your lack of trying!

I’ve started the preparations, updated all 5.2 and 5.0 VMs to the lastest patches and upgraded the NextCloud plugins on the NextCloud instances, which now proclaim to be ready to update from 5.0 to 5.2, including the Debian 11 underneath.

Before I proceed, I’ll have to do another Proxmox patch run and then do a full set of backups, even if Univention 5.0 to 5.2 upgrade have worked remarkably well in January… , but it’s September now.

I’ll report again, when I’m done, just wanted to send out my thanks as soon as possible!

Let’s just hope that Trixie won’t be such an arduous exercise again!

I tried earlier and failed. There was an error about the domain join failing on Nextcloud update. Ended up testing the upgrade for UCS as well while I was at it since the new version was installed, and I didn’t have enough space on the boot partition to complete that. I ended up rolling back to my snapshot. I will probably revisit this during the weekend when I can so I have more time to troubleshoot things.

I have just upgraded

  • Keycloak
  • Nextcloud
    After this I get a message that I have to run the domain join script for Nextcloud again which results in the error in the screenshot.

Right now I’m a bit at a loss what to do (first).

Essentially I can see three errors:

  • Cannot append Nextcloud Hub to service, value exists
  • No commands defined in “saml:config” namespace
  • Could not configure Keycloak as Nextcloud Identity Provider

Thank you for your support.

Very nice! Upgrading from 5.0 to 5.2.x with Nextcloud worked perfectly. Tip: Uninstall Rkhunter beforehand, as it causes problems (if anyone else is using it).

:top:

My attempts to upgrade to 5.2 have all failed.

I am currently stuck on 5.1-0. I have an error that says:

“Further release updates are available but cannot be installed. The currently installed version of the application Keycloak is not available for all newer UCS releases.”

I did upgrade to the latest available Keycloak before running the 5.2 update. App center is showing 26.2.5-ucs1 even though 26.3.1-ucs1 was what I had before I started the update. I have rolled back to my pre-update snapshot and verified this as I know it’s weird.

It looks like I need to clear up more space on my boot partition, but I can’t. I had to go down to only the installed kernel to get the update to start. I have 350 free, but it looks like the process of going to 5.1.0 loads a new very similar kernel and eats up some space and then the jump to 5.2 fails, but if I clear up space again I still can’t get to 5.2 because of the Keycloak weirdness.

I am certainly glad I didn’t run this bare metal. It would have been a nightmare.

So now I’m back on 5.0 again.

I think my next attempt is probably going to need to be after I fix this too small boot partition. Not sure what the best way to do that is. Probably need to create a new disk slightly larger and manually partition it to match the old except have a bigger boot partition. Then I can copy things across and boot the VM off the new disk. If anyone knows an easier way to do that let me know.

I had the same problem with full boot partition.

If I remember correctly, I dropped all but used and latest kernels to get past it.

uname -a
dpkg --list | egrep -i --color 'linux-image|linux-headers'
apt-get --purge remove linux-image-<NUMBERS FROM THE ABOVE>

Yes, I did that. I was down to only the used kernel and it seems that the 5.1-0 intermediate update installs another kernel which then drops my space below the 300MB free threshold, which then prevents the automatic upgrade to 5.2.

I think I either have to risk removing the 300MB limit and hope there is enough space for a third kernel with 5.2 or I have to expand the boot partition.

Since I’m running all Univention instances on VMs, I saw little point in using partitions/drives etc.: it’s so much easier to just fix any issue with innoticed overflow or capacity management etc. by juggling with the virtual disks instead.