[08:20] good morning [09:03] davidcalle: did you see the MP I sent? I think it'd be good to include it if that's still easily possible [09:03] dholbach: I haven't looked at it yet, will do in a short moment :) [09:04] * dholbach hugs davidcalle [09:14] davidcalle: let me know if you want me to split it up into two MPs [10:04] dholbach: I'd like mhall119 to give the upgrade a try on staging, it's throwing back a lot of errors at me and it's getting a bit cryptic. I'm fixing them one by one: both migration failures (eg, having to run manually "'ALTER TABLE django_content_type DROP COLUMN name'" on the db) and Mojo issues (eg. floating ips need to be manually linked to apache [10:04] instances). [10:04] hohum........ [10:05] do you have the error message on the migration failures? [10:06] http://stackoverflow.com/questions/29917442/error-creating-new-content-types-please-make-sure-contenttypes-is-migrated-befo [10:07] dholbach: pretty much this ^ [10:13] davidcalle: what does migrate -l say? [10:28] dholbach: I've moved to a clean instance to try again, it's still processing, but it was showing all migrations checked [10:28] bizarre :-/ === davidcalle is now known as davidcalle_3g [14:28] davidcalle_3g: did you get anywhere with the migrations? [14:28] mhall119: ^ do you know how this can reproduced somehow? [14:28] dholbach: a migration failure? [14:28] I wished I could help, but I have no clue what to do as it just works locally [14:29] http://paste.ubuntu.com/14695636/ [14:29] * mhall119 looks [14:31] on mobile right now no network, mike if you can try a deploy you'll see what I mean, i'd like your opinion on what's going on [14:32] davidcalle_3g: what's the state of staging now? does it have clean prod data? Has the 1.8 code been deployed to it? [14:33] clean prod data, yes, 1.8 in a broken state because of these migrations failures [14:35] one thing we should try is to clear out all */*migrations/*.pyc [14:35] just to be sure we don't have south leftovers [14:35] as just looking at https://docs.djangoproject.com/en/1.8/topics/migrations/#upgrading-from-south [14:36] maybe we need to run python manage.py migrate --fake-initial too? [14:37] mhall119 I've been on it all morning without much success, there is also a networking issue: you need to add floating ips manually, cf the conversation in #webops from yesterday with caio, we need IS to fix it [14:56] davidcalle_3g: I can't even get juju status to do anything on wendigo :/ [14:58] mhall119 ? [14:59] davidcalle_3g: juju status just hangs, it never returns [15:03] it's not even returning an error, it's just stuck [15:36] at which stage? [15:59] dholbach: stage? [16:00] dholbach: #webops is restarting the juju control node [16:01] you said that it's stuck [16:01] I wondered at which stage it was stuck [16:02] dholbach: the juju client can't talk to the environment [16:03] 'juju status' times out [16:04] oh ok [16:04] so that's unrelated to the migration and django project issues [16:05] I think so, yes [16:05] at least, I don't see any way that a problem with django could cause the environment to become unreachable [16:08] ok good === davidcalle_3g is now known as davidcalle