[07:33] <dholbach> good morning
[10:43] <davidcalle> dholbach: re: staging duc: So... there is still this bug where some actions (delete, publish) seem to take time or to have no effect, but reloading the page shows the action applied. This is annoying, but I think it's a fight for another day, we need to unblock API doc fixes and snappy asap.
[10:44] <dholbach> right
[10:44] <dholbach> do we have any caching in place for staging?
[10:46] <davidcalle> dholbach: same wonderful caching system as prod I think :)
[10:46] <dholbach> mh
[10:47] <dholbach> it might be good if that could be turned off as I don't really expect many to be using staging... it'd help to uncover issues unrelated to caching :)
[10:49] <davidcalle> dholbach: I'll see what I can do, it could be as simple as tweaking a value in the juju config of a service
[10:49] <dholbach> no worries...
[10:49] <dholbach> I was just thinking out loud :)
[11:00] <davidcalle> dholbach: are you testing something or can I try to redeploy without caching?
[11:00] <dholbach> please redeploy :)
[11:00] <davidcalle> :)
[11:00] <dholbach> I'm doing something else right now :)
[12:39] <davidcalle> dpm: dholbach: there were another breakage on prod this morning. The zh-cn/community page was still up but the draft would not publish. I did a quick fix by copying the page, moving children and changing paths, but I think we'll need, soon-ish, to export the db, see what's going on locally and put it back fixed (or something else), my main fear is to see the
[12:39] <davidcalle> issue taking down more pages.
[12:39] <davidcalle> was*
[12:44]  * davidcalle lunch
[12:57] <dholbach> I hope that the new django cms (using treebeard) will fix this
[13:19] <davidcalle> dholbach: caching still there /me moves on
[13:22]  * dholbach hugs davidcalle 
[14:36] <mhall119> davidcalle: how did the db migration go?
[14:38] <davidcalle> mhall119: went great following dholbach's steps!
[14:44] <mhall119> \o/
[14:44] <mhall119> are we ready to do it in production then?
[14:46] <davidcalle> mhall119: looks like it - just after testing the importer with dholbach :)
[14:47] <dholbach> davidcalle, feel free to go ahead without it
[14:47] <dholbach> the importer won't have the necessary fixes
[14:47] <dholbach> (if we go ahead without the MPs)
[14:47] <dholbach> it shouldn't break anything else :)
[14:47] <dholbach> I mean... not using the importer won't break other stuff :)
[14:49] <davidcalle> dholbach: that's right!
[14:53] <davidcalle> login.ubuntu.com down. /me grabs coffee
[14:53] <mhall119> yeah, lots of stuff down just now
[14:53] <mhall119> yay cloud!
[14:55] <davidcalle> mhall119: and d.staging.u.c is up. That's payback.
[14:55] <mhall119> lol
[16:50] <davidcalle> mhall119: last time you deployed to prod was mid-january, iirc, do you remember which branch was used?
[16:51] <davidcalle> (or if you have the rt around, the revno will tell us)
[16:54] <davidcalle> mhall119, also, do you know if the fix you applied to the spec on wendigo made it to the lp branch?
[16:56]  * davidcalle drives home, will try to finalize everything tonight and file the long, full of commands, RT
[17:04] <mhall119> davidcalle: I haven't made the fix propsal to the LP branch yet, but the spec shouldn'tbe used to update production, just a juju set
[17:04] <mhall119> AFAIK the production branch in LP matches what was last deployed to production
[17:05] <mhall119> I don't have the last RT handy, sadly, but I'll dig through my email