ownCloud 8.2.2, 8.1.5, 8.0.10 and 7.0.12 here with Sharing, LDAP fixes

The latest ownCloud stability and security updates are available, bringing improvements to sharing capabilities and performance enhancements to the ownCloud 8.2 series and LDAP, sharing and many minor fixes to the earlier releases. We recommend to upgrade as soon as possible! Please note the change in upgrade behavior for the Linux packages which require system administrators to manually run the occ upgrade command. Read on for more details about this end-of-year gift from your friends at ownCloud.

Change to Upgrade Process

Until ownCloud 8.2.1, updates coming in the form of ownCloud packages would work by putting the ownCloud server in maintenance mode, disabling apps, running the occ upgrade command, and disabling maintenance mode. The admin would then be able to re-enable apps, run their respective upgrade steps and proceed to be a happy ownCloud user.

Not all system administrators were entirely happy with this behavior as it made it harder to track and control progress in case there were many updates besides ownCloud. For ownCloud 8.2.1, the packages thus leave the ownCloud server in maintenance mode. The system administrator can then manually run the commands to finish the upgrade, keeping an eye on the process.

This behavior is now default for all ownCloud packages. We have updated our documentation and strongly recommend to follow the steps therein:

Also note that the package repository (location) for ownCloud 8.2 has been changed. You can now find packages on our own servers, see download.owncloud.org.

Improvements and Testing

Minor ownCloud releases bring stability, security and performance improvements to the stable release series. We’d like to thank everybody who reported issues and helped us fix them.

ownCloud tests releases both through automated means and through manual testing. Our releases come when we have fixed all problems we could find. You can help us find issues which might impact you by joining the Test Pilots and giving releases a whirl before they go out!

Find the ownCloud 8.2.2, 8.1.5, 8.0.10 and 7.0.12 changelogs here.

We had a snafu with a full file system which caused some unforeseen delays so please note that at the time of publishing this, some of the packages and the Appliances and virtual machine images were still building, we will have them up on owncloud.org/install in a few hours.

We wish you a wonderful time during these holidays, wherever you are!

16 Responses to “ownCloud 8.2.2, 8.1.5, 8.0.10 and 7.0.12 here with Sharing, LDAP fixes”

  1. Andyr

    I am trying to upgrade from 8.2.1 to 8.2.2. I am running Ubuntu 14.10 and I added the new repos per https://download.owncloud.org/download/repositories/stable/owncloud/. I am getting the following error:

    W: Failed to fetch http://download.owncloud.org/download/repositories/stable/Ubuntu_14.10/en_US Error reading from server. Remote end closed connection [IP: 144.76.105.220 80]

    Please help!

    • Andyr

      Oh my goodness. I just realized I am not running 14.10, but instead 14.04 LTS! Jeez. I updated the repos and am getting another error.

      owncloud: depends: owncloud-server (=8.2.2-1.1) but 8.2.1-1.1 is to be installed

      • Andyr

        I finally figured it out! Needed to update my kernel and my boot was full. cleared up some old ones and everything is good now.

  2. Pete

    Hi there,

    i tried to upgrade owncloud from version 8.1.4 to 8.2.1. as my owncloud suggested. But it crashed. Currently i am restoring my installation.
    However, i am searching for the owncloud 8.1.5. upgrade file to upgrade my installation to version 8.1.5 manuelly. Where can i find it??

    Last but not least let me say something about updating and upgrading owncloud: It is always a high risk for an owncloud installation. My experience is: 2 of 3 upgrade procedures crashes. I still use owncloud because my installation provides important information for me and my team members. I am using owncloud since version 7.0.

    • Chris

      https://owncloud.org/install/#instructions-server

      -> Looking for older versions or major releases?

    • Chris

      Btw. about the mentioned upgrading issues:

      Never had any of such issues since running oC 4.0.x. Just make sure that you’re not using the updater app and that you always delete all files and folders except /config and /data before extracting the new files of the next major version into your install folder.

  3. Eric

    I just want to agree with the other comments. This is not acceptable upgrade behavior. No other software I ever installed on a Linux server behaved like this. Please consider reverting this. I can’t see how a majority of users would be in favor of this change.

    • Jos

      It is about data safety, I’m afraid. We kept getting bug reports of server owners who broke off the upgrade process started by the package manager and were left with a broken server. Now you can say “that is stupid, they should not have done it” but that does not solve the problem. This does, and helps people, even though it creates extra work.

      I just published a blog with more information about the work we’re doing to make all this easier: https://owncloud.org/blog/making-owncloud-upgrades-more-robust/

  4. Chris Vanelli

    I completely agree with Detlev Bielz. A completely disabled server after an update is NOT acceptable. It is a full revert to pre-production levels. This is no longer useable software. It’s only for experimentation. Maybe we can take control of our data one day, but this is not it.

  5. Detlev Bielz

    Nice work from all owncloud devs, thanks for all.

    Just one remark to the upgrade process:
    I now am with owncloud since version 5.x or earlier. By then, upgrading was quite a seamless process done by just clicking on the ‘upgrade’ button in the upgrade plugin, as I remember vaguely. After upgrade, everything was just as before, except in a newer and better version.
    Later, I don’t remember the exact version, upgrading ended with disabled apps, no matter if third party or not, and required an intervention on server side before being able to continue just using calendar and contacts sync (my primary use, besides news, tasks, and notes). Not so easy to be done if being on the road and the upgrade is done by unattended upgrades on the server.
    Now the upgrade process ends with a completely disabled server. Which, besides, was referred to as bug in the beginnings of version 7 I think, and was fixed later on.
    Well, there might be server administrators out there, seeing their personal fulfillment in administering all day. But personally, I think there are also people out there who simply want to use owncloud as a helping tool and don’t really want to accompany every single step of every single update and upgrade. The group of users to which I would count myself. I really find it hard to share the view, that every update rendering the server unusable is a real progress in developement and usability. Especially in combination with unattended system upgrades. Since this already cought me in bad situations, a real pain in the ass.
    Even I try very hard, I can’t find any other server component or desktop software behaving this way. Either there is no automatic update available, and I have to download and install every update manually when I have the occasion to do so, or the update runs mostly unnoticed. In every aspect, including further accessability. I think there are good reasons for the fact, that the latter way of updating becomes more and more the favorized way of doing updates.
    Wouldn’t it be a good idea, to introduce a switch or a flag in the administration interface, called, say ‘I want to see every step of the update’, or ‘let me do updates manually’ or something like that, and let the users decide wether they want to be careless or concerned?

    Whereas, wouldn’t concerned administators refuse to use unattended upgrades anyway and do things manually?

    Wy is it so bad to activate previously activated apps again after update if they really have to be turned off for the process of upgrading? I mean, if one or another app shows a problem with the updated version of owncloud, at least I can continue to use the other apps until I have the chance to take care of the problem.

    hmm, please help me, I can’t see the point of the very special owncloud way of performing updates!

    And please rethink, if it really is sooo important for server administrators to control every single step of the upgrade process and sacrifice the usability aspect in ugrades completely. For me this is a serious drawback; so serious that it motivates me to start looking for alternatives.

    Greets to you guys,
    Detlev

    • Chris

      Hi,

      i think such feedback is better placed at https://mailman.owncloud.org/mailman/listinfo/devel where it is more likely that people are reading it. You can even create a feature request here:

      https://github.com/owncloud/core/issues

      A feature request to only disable apps on upgrades (e.g. 8.1.x -> 8.2.x) but not on updates (e.g. 8.1.1 -> 8.1.2) is available here:

      https://github.com/owncloud/core/issues/14754

    • Jos

      Hi Detlev,

      Great comment, and yes, you are right. Upgrades used to be far more automatic than they are today.

      The reason is that the automatic updates caused *problems*. For example, when an upgrade runs with apps enabled, the apps can break ownCloud’s upgrade process which can result in loss of user data. If you enable apps, each of them can break ownCloud completely if there’s a serious bug in them. So, to avoid breaking user installations and data loss, we accepted the cost of extra work and disable apps.

      The change we made here, to leave the server in maintenance mode rather than running the upgrade automatically was also done to avoid problems. The upgrade process would run for a long time on some systems, and if interrupted it leaves a broken ownCloud. Moreover, some package managers don’t show the output and possible questions or warnings from ownCloud to the user! By letting admins run the process themselves we avoid that.

      But we’re very much aware that these steps have decreased the ease of use of ownCloud and we are working hard to rectify them.

      Take the disabling of apps. We are working on detecting breakage in apps when you enable them and recovering from those errors. If we can get that to work, we’re a step closer to a perfectly smooth upgrade process.

      We are even overhauling the entire upgrade process, to get to our ideal of non-disruptive upgrades. The first changes like separating the updater from the rest of ownCloud have been made.

      But this work will take time. Help is, of course, welcome!

      Hope this answers your question.

      • Chris

        Hey Jos, thanks for this write-up.

        Something to add:

        This kept maintenance mode only affects systems where automatic updates are done. And do i really want to do automatic updates on a productive system?

        • Jos

          Well, you encounter it, of course, also with manual upgrading – you have to execute some more commands now, rather than being ready after the normal “zypper ref && zypper up” 😉

          I hope to publish a blog about our work on the new upgrade app next week.

Comments are closed.