Encourage Verify of sites before running Sync tasks. [#2121095]

I got a sync fail on my first try between two minimal sites on a barebones drupal 7 platform with only 5 modules in sites/all/modules.

No warnings or errors appeared in the Sync task form, but turns out I haven't verified the source site in a while so aegir didn't know about most of my source site.

I think you should display the "Last Verified xyz ago" of each Source site options, and link that site node to remind users to go verify their sites.

Comments

Comment #1

dsnopek

he/him

English

USA

CreditAttribution: dsnopek commented 15 November 2013 at 16:42

This is a great idea! Not sure when I'll have time to address it though.

Comment #3

helmo CreditAttribution: helmo commented 6 February 2014 at 20:41

What kind of changes had happened on the source site?
Did you add site specific modules?

I'm not sure that a time dependent message "last verify longer then x ago." solves it. A module could have been added only minutes earlier.

How far do we want to go to prevent such an error? The sync did not break anything right?

Comment #4

dsnopek

he/him

English

USA

CreditAttribution: dsnopek commented 7 February 2014 at 01:22

I've seen a similar "issue" with this with the Migrate task. The problem usually comes when I update something in the platform, so now Aegir's picture of what modules/versions are available is wrong. So, then I try to Migrate, and it says I can't because of a version mismatch. I've never seen it actually break anything though, just prevent me from going forward and it's only experience that tells me I should try verifying. :-)

Comment #5

helmo CreditAttribution: helmo commented 7 February 2014 at 09:22

We could schedule a verify every day ... but I'm not sure it would be worth it.
The 'perfect' solution would be to have realtime info ... we could try inotify to listen on a platform and verify on changes...