i used the uprade script located at http://drupalcode.org/project/provision.git/blob_plain/refs/tags/6.x-2.0... to do an automatic upgrade from 2.0-rc4 to 2.0 final.

i verified my site was still running after the upgrade then renamed the directory to hostmaster-6.x-2.0-rc4.bak and thats when my site returned a 404 error.

checking i found this directory pre-upgrade-2014-01-25-0755 and this hostmaster-6.x-2.0. so i knew the script ran.

then i did a ls -lR | grep -i `hostname` which basically said that the site's config was still in the rc4 directory and was not moved to the new 2.0 final directory.
it also showed /var/aegir/clients/admin still had soft links to the rc4 directory. same applied to ~/.drush/hostmaster.alias.drushrc.php

restoring the name of the rc4 directory restored the site's functionality.

in summary the upgrade was not successful

Comments

marafa’s picture

marafa CreditAttribution: marafa commented

this is a show stopper for me. any updates pls?

marafa’s picture

marafa CreditAttribution: marafa commented

ok so i copied my sites/all/* directory over from the old version to the new version.

then i noticed that all the contrib modules i had copied over were also disabled; ubercart, hosting backup etc.

this is looks like a major upgrade bug to me.

helmo’s picture

helmo CreditAttribution: helmo commented
Status: Active » Postponed (maintainer needs more info)

The output from upgrade.sh "must have" printed some errors, do you still have it?

Otherwise debugging will be near impossible, sorry.

marafa’s picture

marafa CreditAttribution: marafa commented

@helmo
well i upgraded my environment. will need some time to roll back the changes but i fear i may have to rebuild it from backups

helmo’s picture

helmo CreditAttribution: helmo at Initfour websolutions commented
Status: Postponed (maintainer needs more info) » Closed (outdated)

The 6.x-2.x branch will go EOL along with Drupal this week. So I'm closing
this issue. If it remains a confirmed issue in 7.x-3.x, feel free to re-open,
or better yet, create a new issue referencing this one.