Right now, we tell people to delete the Aegir site from the backend, using provision delete. Unfortunatly, that means that the site detected from the frontend is *not* removed and is basically "rogue" in that it doesn't really reflect the backend anymore: any task performed on the site will fail and it is impossible to disable/delete it, because of #529348: disable can still fail disabling damaged sites.

Not sure what is the right way to do this.

Comments

anarcat’s picture

Title: current UPGRADE.txt instructions leave a rogue site in the old platform » cannot upgrade aegir with itself because the frontend doesn't follow
Component: Documentation » Code

a better title: this is not a documentation problem, there's a real problem here that doesn't depend only on #529438: google search box and location .

we're looking at implementing a hosting migrate command that would migrate the frontend. this is related with #454312: self-provisionning support.

anarcat’s picture

Status: Active » Needs review

So the work on the git branch (588114_hosting_migrate continues and is now able to upgrade a frontend site. We are considering moving it to the backend...

anarcat’s picture

Issue tags: +aegir-0.3-hotfix
StatusFileSize
new8.19 KB

The branch was merged in mainline, but I'm still maintaining it for the benefit of 0.3 users wanting to upgrade. We're still unsure if this code is going to stay in hosting or migrate (no pun intended) to provision so that upgrades are going to be easier.

In the meantime, people wanting to upgrade from 0.3 to 0.4-cvs should use the attached patch on hosting and follow the instructions (soon to be updated) in UPGRADE.txt in the profile.

anarcat’s picture

Issue tags: +Upgrade path
anarcat’s picture

StatusFileSize
new6.12 KB

Last patch was touching too much stuff and was git-formatted. This one doesn't touch the frontend stuff and just adds the drush commands. Make sure you specify the platform paths exactly as they are in the frontend as path sanitisation is not enforced in 0.3.

anarcat’s picture

Status: Needs review » Needs work

So the code was moved to the backend (the provision module) now so the documentation needs to be updated. The above patch is still valid as a hotfix for people that want to upgrade through that, but the prefered way is to upgrade without the patch, through the backend (since you should upgrade the backend first anyways).

adrian’s picture

Status: Needs work » Fixed

this was documented in UPGRADE.txt

Status: Fixed » Closed (fixed)
Issue tags: -Upgrade path, -aegir-0.3-hotfix

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

  • Commit bf10251 on 599758_edit_main_site, 640952_client_preview, dev-dns, dev-features, dev-headless_install, dev-log_directory, dev-migrate_aliases, dev-multiserver-install, dev-newsiteform, dev-nginx, dev-platform_management, dev-ports, dev-purgebackup, dev-relationships, dev-restore, dev-server_nodetype, dev-services, dev-site_rename, dev-ssl, dev_dns, prod-koumbit, ssl, dev-ssl-ip-allocation-refactor, dev-1205458-move_sites_out_of_platforms, 7.x-3.x, dev-588728-views-integration, dev-1403208-new_roles, dev-helmo-3.x authored by anarcat:
    create a hosting migrat task #588114
    
    this introduces hosting migrate,...

  • Commit bf10251 on 599758_edit_main_site, 640952_client_preview, dev-dns, dev-features, dev-headless_install, dev-log_directory, dev-migrate_aliases, dev-multiserver-install, dev-newsiteform, dev-nginx, dev-platform_management, dev-ports, dev-purgebackup, dev-relationships, dev-restore, dev-server_nodetype, dev-services, dev-site_rename, dev-ssl, dev_dns, prod-koumbit, ssl, dev-ssl-ip-allocation-refactor, dev-1205458-move_sites_out_of_platforms, 7.x-3.x, dev-588728-views-integration, dev-1403208-new_roles, dev-helmo-3.x authored by anarcat:
    create a hosting migrat task #588114
    
    this introduces hosting migrate,...