Errors when using update script for DB (1.6.3-2.0.0)

Steps to reproduce

TBD: Need more information from Universität zu Köln.

Activity

Show:
Rüdiger Rolf
May 13, 2016, 3:18 PM

As this ticket is about problems with the DB migration script: I had not found any issues with these in my system all the way from 1.6 to 2.2. But I only had test data. I would be thankfull for any hints, what did not work and the according DB version. I will retry with some data from our production system, too.

Rüdiger Rolf
May 13, 2016, 3:15 PM

I am currently testing the upgrades from 1.6 to 2.2.

I only created an all-in-one test environment with up to 50 recordings.

So far I found these problems:

Upgrade 1.6 to 2.0(.2)

Working:

  • The MySQL database upgrade scripts seem to work just fine (MariaDB 10.0.17).

  • All SOLR indexes seem to rebuild if deleted. SOLR indexes also seem to work without rebuilding them.

  • All 1.6 recordings are available in Media Module.

Problem: The Admin UI does not show any inherited jobs. The endpoint to create an Admin UI Elastic search index does not seem to exist yet.

Upgrade 2.0.2 to 2.1(.2)

Working:

  • DB just works, no DB upgrade needed.

  • Admin UI Elastic Search index can be created and contains recordings

Problems:

  • non Archived 1.6 recordings are just blanks lines without any metadata.

  • Search index will not rebuild and stays empty after beeing deleted. If copied over to the new location from 2.0 old recoredings can be found. Search index does also not rebuild with new ingested 2.1 recordings.

Upgrade from 2.1.2 to 2.2

Working:

  • rebuilding the admin UI eleastic search index works, like in 2.1

  • database migration script works.

Problem:

  • no search index seems to rebuild (at least search and workflow, which I saw in the logs with errors.). They can be reused from 2.1 .

Fixed and reviewed

Assignee

Rüdiger Rolf

Reporter

Sven Stauber

Severity

Incorrectly Functioning Without Workaround