/srv/irclogs.ubuntu.com/2017/04/07/#juju-dev.txt

axwbabbageclunk: you said in standup you wanted some advice on something?01:06
blahdeblahAnyone started looking at lp:1618212 ?  Just got it after upgrading from 2.0.3 to 2.1.2, which means that I can't upgrade any of the models, because I can't list them.04:07
anastasiamacblahdeblah: m looking at a bug that feels related04:14
blahdeblahWell, let me know if you need to look at anything in this env.04:14
anastasiamacblahdeblah: but this bug is about model destruction not listing...04:14
anastasiamacblahdeblah: logs r always helpful, mayb even a db dump (altho with 40+models sounds scary...)04:15
blahdeblahanastasiamac: I just took a backup, so you can have that if needed.  (This is the same env which led me to create lp:1680683.)04:16
blahdeblahThe backup is 6 GB04:16
anastasiamacblahdeblah: m saying that the bug u referenced above is about destruction, not listing... altho frankly i am ware and kind of looking at both issues - the destruction of the model as well as lsiting of models...04:17
anastasiamacaware even04:17
blahdeblahanastasiamac: you must be reading a different bug to me; 1618212 is definitely about listing models04:18
anastasiamacblahdeblah: the title says "juju models fails during model destruction"04:19
blahdeblahanastasiamac: Every commenter on that bug says they're getting the error from "juju models".04:19
blahdeblahIt might be related to destruction in some way under the covers, but where it shows up in the user experience is listing models.04:20
blahdeblahAnd I've just encountered it while listing models after an upgrade, no destruction involved.04:21
anastasiamacblahdeblah: i think the problems r related - we cannot cleanly destroy models under some circumstance, and list models gets confused04:21
anastasiamacblahdeblah: specifically for list models, I have: https://bugs.launchpad.net/juju/+bug/1674805 and https://bugs.launchpad.net/juju/+bug/167627904:21
mupBug #1674805: list-models fails after model is destroyed after model migration <ci> <intermittent-failure> <list-models> <model-migration> <juju:Triaged by anastasia-macmood> <https://launchpad.net/bugs/1674805>04:21
mupBug #1676279: juju 2.1.1 controller not removing models correctly (list-models showing "info: settings not found") <destroy-model> <list-models> <juju:Triaged> <https://launchpad.net/bugs/1676279>04:21
blahdeblahmaybe one of those will match my problem better04:22
* blahdeblah looks04:22
anastasiamacblahdeblah: definitely worth a comment on any related bug that matches ur case ;)...04:22
blahdeblah1676279 seems like a dup of 1618212 to me04:23
blahdeblahso does 1674805, TBH04:24
blahdeblahBut neither matches better, so 1618212 will do for now04:26
blahdeblahI think, however, that destroy-models might be a distraction, since I got the error message without trying to destroy anything.04:26
anastasiamacblahdeblah: yeah... i think the underlying cause is the same but all are coming from slightly different angles.. yes, there is an issue in both destroy and list - slightly different issue...04:27
anastasiamacblahdeblah: hence, i said that the bug u referenced was for destroy... ppl just started putting list models comments into it04:28
anastasiamacblahdeblah: at the end of the day, both issues needs to b fixed so feel free to update whichever bugs feels closer to u :D04:28
blahdeblahWell, you know the code better than I04:29
* anastasiamac laughs04:29
anastasiamacblahdeblah: u made my day, really04:29
blahdeblahThere was no model destruction involved in my case, yet I ended up with the same error message.  So if you want a new bug that says "juju models fails after juju-upgrade", I'm happy to supply one.04:30
blahdeblahNumber of anastasiamac PRs on juju > number of blahdeblah PRs on juju; hence, you know the code better than I. ;-)04:31
blahdeblah(where number of blahdeblah PRs on juju == 0)04:31
anastasiamacblahdeblah: my first, almost knee-jerk reaction is "no! i don't want another bug"04:39
blahdeblahI figured ;-)04:39
anastasiamacblahdeblah: but i think it'd b better if u did report it separately... besides i do want to see ur logs and db...04:39
anastasiamacblahdeblah: coz we have not heard (I *think*) of probelms when upgrading...04:40
anastasiamacblahdeblah: *after* upgrading04:41
blahdeblahSo, is that a "yes, I do want another bug"?04:41
anastasiamacblahdeblah: and m pretty sure we test upgrades extensively...04:41
blahdeblahanastasiamac: Personally, I don't think it would achieve much04:41
anastasiamacblahdeblah: no, let's not for now :)04:42
blahdeblahI think what's happening is there were models which were marked as destroying when I started the upgrade.04:42
anastasiamacblahdeblah: yeah, that's the symptoms m seeing in all other similar failures04:43
anastasiamaclingering/ghosting models04:43
blahdeblahyeah - given axino's comments in 1676279, I think once you fix one, you'll fix them all04:45
anastasiamacblahdeblah: i wonder if his db surgery on the models marked as 'destroying' will get u unblocked.. at least while we r sorting the issue..04:46
blahdeblahI still disagree that this isn't a bug in listing; regardless of whether a previous destroy left some models lingering, "juju models" should keep working.04:47
anastasiamacblahdeblah: but since u r dealing with production as well, mayb not the most desirable way forward...04:47
anastasiamacblahdeblah: there is nothing to disagree - I agree that listing has a bug04:47
blahdeblahNo, not the most desirable way forward, but if we can't list models, JAAS will probably be a bit dead in the water, so it may be necessary.04:48
blahdeblahurulama: ^ See discussion above; looks like there are at least 3 bugs about destroyed/ing models staying in DB05:33
urulamajuju bugs for breakfast \o/05:33
urulama:)05:33
blahdeblahanastasiamac: How likely is it that those model listing/destroying bugs will be fixed in a 2.1.x update?06:14
anastasiamacblahdeblah: i thought u said that u r seeing in after the upgrade to 2.1.x already... 2.1.2 specifically?..06:15
blahdeblahYep06:16
blahdeblahSo how likely is it that we'll see a fix in 2.1.[3-5]?06:16
anastasiamacblahdeblah: we have not planning another 2.1.x... most likely in 2.2...? unless the sky falls?...06:16
blahdeblahI thought that might be your answer.  :-)06:17
blahdeblahthanks06:17
anastasiamacblahdeblah: just for reference, m still trying to figure out what goes wrong... i can reproduce destroy failure... i also *know* what's causing issues on list... but until i can nail it down, i don't know if it is easy to backport and release another 2.1.x...06:18
blahdeblahNo worries - just trying to work out best course of action for this controller on which models can't be listed.06:19
blahdeblahurulama: ^ You mind checking whether us-east-1 is still functional from your perspective?06:19
anastasiamacblahdeblah: m guessing that u have tried the standard?06:19
blahdeblahanastasiamac: "the standard"?06:20
blahdeblahnot as yet, but I will06:20
urulamablahdeblah: that was aws, right?06:21
blahdeblahyep06:21
urulamaok, looks fine, but i'll check with some big users as well06:22
=== frankban|afk is now known as frankban
wpkhttps://drive.google.com/open?id=0BwYF43OiGvHjWkFnLVJCVlFaRFk10:25
wpk^^^ that's a dependency graph for juju/juju/api/10:26
rogpeppeanyone around to review this large but mechanical code-move branch: https://github.com/juju/juju/pull/721311:04
=== frankban is now known as frankban|afk
cmarsanyone available this friday afternoon for a quick review?18:27
cmarsi've got https://github.com/juju/juju/pull/7214 which fixes critical bug https://bugs.launchpad.net/juju/+bug/168088318:28

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!