Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Noted downtime required due to Django 1.11 migrations.


Note

This is not a list of the features and changes that will be available in Hawthorn.  This page is only for release concerns.  See the product announcements for changes that have been made since Ginkgo.

...

Stuff that must land before Hawthorn

Stuff you'd like to complete before Hawthorn

...

Migrating from Ginkgo to Hawthorn

Database schema migrations ran smoothly between edx-platform:open-release/ginkgo.1 to a recent edx-platform:master.

However, servers running ginkgo.1 against a migrated MySQL database throw The upgrade to Django 1.11 will requires a non-backward-compatible ALTER TABLE on the auth_user table, and so some outage will be required when upgrading from Ginkgo to Hawthorn.

Testing on a recent edx.master (prior to the Django 1.11 upgrade) also noted these MySQL database exceptions for a few essential operations, and so upgrades will require some downtime.

  • Exception thrown during LMS/Studio login/registration and course enrollment:
    OperationalError: (1054, "Unknown column 'email_marketing_emailmarketingconfiguration.sailthru_activation_template' in 'field list'")
  • Exception thrown during during Studio course creation:
    ProgrammingError: (1146, "Table 'hawthornupgrade_sandbox_opencraft_hosting_edxapp.student_historicalcourseenrollment' doesn't exist")