With some of the big changes recently (i.e., pulling hosting out of hostmaster, Views integration), it's possible we need an update hook to ensure a clean upgrade path.

For our intrepid alpha-/beta-testers, please document any challenges you may experience here.

Comments

anarcat’s picture

anarcat commented

Here after running a weird and screwed up updatedb, i am missing the site and servers views.

anarcat’s picture

anarcat commented

In fact, a clean install doesn't setup the sites menu or views.

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
commented

A clean install works for me... I'll test the upgrade path to see if I can reproduce this.

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
commented
Status: Active » Needs review

Here's the testing procedure that I'm using, starting from a working fresh install of the latest 6.x-2.x:

  1. Rollback hosting repo prior to the Views integration commit (git checkout 4e642b2c7e41d12f)
  2. Rollback hostmaster repo prior to the Views integration commit (git checkout 19620d9ed44908a)
  3. Remove Views and VBO from the platform (rm -rf /var/aegir/hostmaster-6.x-2.x/profiles/hostmaster/modules/views*)
  4. Uninstall the front-end (drush @hostmaster hostmaster-uninstall)
  5. Install the front-end (drush hostmaster-install)
  6. Check the front-end to ensure custom menu items and lists exist as before
  7. Upgrade the front-end to the latest 6.x-2.x (drush @hostmaster hostmaster-migrate <front-end_url> <new_platform> --makefile=/var/aegir/.drush/provision/aegir.make)

Repeating this should just entail steps 4-7, making sure to install (in step 5) onto the pre-Views platform (which is the default behaviour).

Following this procedure, I haven't been able to replicate the reported issue. I have found some funky stuff in the update hook ( hosting_update_6016()), so I'll look into that. But otherwise, I'm not sure how to proceed.

deciphered’s picture

deciphered commented

I used a simpler upgrade test:

1. I had a backup of the database prior to Views upgrade
2. Code base is all upto date
3. Import old database over the current db
4. Run update.php

I had no issues with the upgrade, worked as expected.

anarcat’s picture

anarcat commented
Status: Needs review » Active

damnit, i had an old version of views, sorry about that. ignore my problems. :/

anarcat’s picture

anarcat commented
Status: Active » Fixed

oh, i see, so according to tests done by deciphered, i assume the upgrade path is ok. thanks!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.