Bug 1471469 - Cannot migrate from owncloud 9.1.5 to nextcloud 10.0.4 [NEEDINFO]
Cannot migrate from owncloud 9.1.5 to nextcloud 10.0.4
Status: NEW
Product: Fedora
Classification: Fedora
Component: nextcloud (Show other bugs)
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: James Hogarth
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2017-07-16 03:15 EDT by Marek Greško
Modified: 2018-05-03 11:49 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
germano.massullo: needinfo? (james.hogarth)

Attachments (Terms of Use)

  None (edit)
Description Marek Greško 2017-07-16 03:15:05 EDT
Description of problem:
I am not able to migrate from owncloud 9.1.5 to nextcloud 10.0.4 because it reports downgrade is not possible. As I searched for a solution it seems nextcloud 10.0.5 is needed tosolve the issue.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Get working owncloud.
2. Configure nextcloud.
3. Try to migrate from owncloud to nextcloud.

Actual results:

# sudo -u apache php /usr/share/nextcloud/occ upgrade
An unhandled exception has been thrown:
OC\HintException: [0]: Downgrading is not supported and is likely to cause unpredictable issues (from to ()

Expected results:
Seemless upgrade.

Additional info:
Comment 1 bugzilla 2017-08-15 16:07:55 EDT
hello guys!

I've got the same issue.
If nextcloud 10.0.5 is the solution, is there a plan for release this version?
Even updates-testing doesn't provide an update to it.
Comment 2 Marek Greško 2017-08-16 04:33:26 EDT
Nextcloud 10.0.5 definitely is a solution. I prepared rpm packages myself, updated and it works.

But remember, the version 10.x of nextcloud is rather outdated now. It is better to upgrade to currently supported version.
Comment 3 Kamichr 2017-08-16 06:34:59 EDT
Hi Marek,

the issue is, that FC 26 doesn't ship NC 11.
The current versions of OC and NC are:

Name         : nextcloud
Version      : 10.0.4
Release      : 2.fc26

Name         : owncloud
Version      : 9.1.5
Release      : 1.fc26

If one (and I did) uses the migration description shipped with Fedora (/usr/share/doc/nextcloud/MIGRATION.fedora) then it is not possible to migrate due to the version mismatch.

NC should be updated to 10.0.5 anyway. CVE-2017-0893 would be fixed then (despite the low risk level).
Comment 4 Marek Greško 2017-08-16 09:01:13 EDT
Yes, fedora does not ship nextcloud 11. But nextcloud 10 is not supported any more. Only 11 and 12. It should not be a problem. Owncloud was upgraded from 8 to 9 as a regular update during fedora 24. Compare fedora 24 release and updates repositories. Definitely, at least 10.0.5 version is required to migrate.
Comment 5 bugzilla 2017-08-16 16:15:35 EDT
I can confirm that migration works with installed nextcloud version 10.0.5.
Comment 6 Russell Odom 2018-01-20 07:24:46 EST
Note that either bug 1444007 or 1433919 could fix this, depending on the exact versions eventually built.
Comment 7 Germano Massullo 2018-02-07 09:15:37 EST
(In reply to bugzilla from comment #5)
> I can confirm that migration works with installed nextcloud version 10.0.5.

James, can't we upgrade Nextcloud to 10.0.5 so that Owncloud users can migrate to Nextcloud, and then finally move to Nextcloud >= 11?
Comment 8 Fedora End Of Life 2018-05-03 04:40:36 EDT
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Note You need to log in before you can comment on or make changes to this bug.