Earlier  
Posted Nick Remark
#openstack-nova - 2017-03-09
10:23:28 asettle bauzas: he's awake ;) he's just turning on his computer to send me the logs for you
10:23:54 asettle "I updated the patch (with the comments from mriedem_away) but haven't tested the revision yet. I'll send you my nova logs."
10:24:00 asettle So, hopefully we can see what the original problem was, and move from there.
10:24:09 bauzas \o/
10:24:16 bauzas I'll have to bail out for a couple of hours
10:24:34 bauzas but I'll be back around 1pm UTC
10:24:55 asettle bauzas: no problem :) thank you for offering ot help. I've sent out to the ML too. Hopefully we can get some people looking at it too.
10:26:08 asettle Sorry andymccr and johnthetubaguy - not ignoring you both :P
10:26:15 asettle Getting the error logs from bmoss rn
10:28:43 asettle Ugh *head desk*
10:28:48 asettle And it was such a nice day too
10:29:57 bauzas alex_xu: around ?
10:30:20 bauzas alex_xu: not understood your point in https://review.openstack.org/#/c/440580/3/specs/pike/approved/scheduler-hints-in-server-details.rst@34
10:30:52 johnthetubaguy asettle: do we tell people to always install the controller first, and then the compute node?
10:31:47 bauzas "controller" is a pure non-nova thing :)
10:31:50 asettle johnthetubaguy: good question, lemme just check historically.
10:31:53 asettle Yes, we do.
10:32:01 johnthetubaguy OK, thats good
10:32:06 bauzas but yeah I remember the old docs, and it's the case
10:32:18 asettle Yep
10:32:22 asettle Controller -> Compute
10:32:27 bauzas asettle: is the problem due to an upgrade or a greenfields install ?
10:32:36 asettle bauzas: greenfields, I believe.
10:32:50 bauzas because instructions are fairly different
10:32:52 asettle We just test the install instructions, we don't test upgrades.
10:32:53 bauzas for cells
10:33:04 asettle bauzas: that documentation for upgrades should belong in the upgrade docs, no?
10:33:11 bauzas asettle: yup
10:33:20 asettle Yes, okay, I'm not going crazy then.
10:33:31 bauzas just wanted to verify that bmoss is following the fresh install procedure, that's it
10:33:59 bauzas because he's pointing to some internal BZ that mentions upgrades and TripleO hence my confusion
10:34:13 bauzas both are totally separate things
10:34:40 asettle bauzas: yes he should be. The whole idea behind doing the install guide testing ist hat you have to do a full manual install (which is also why we don't have people racing to do it)
10:36:19 bauzas yeah, I followed it in 2012 :p
10:36:32 bauzas using .deb packages :blushes:
10:37:11 bauzas glad to see it continuing even if not a lot of people are crazy pants enough to install OpenStack by hand :)
10:37:26 bauzas oh
10:37:35 lyarwood https://review.openstack.org/#/c/391597/ - pretty simple ~1k LOC removal change in favor of os-brick code if anyone has time this morning
10:37:36 bauzas asettle: my reply to your email was bounced
10:37:52 bauzas asettle: because openstack-docs@ is moderated
10:37:57 asettle bauzas: by me!
10:38:00 asettle Let me add you in
10:38:10 bauzas strange, why are you moderating it ?
10:38:14 johnthetubaguy oh, did not know there was a docs ML
10:38:16 asettle bauzas: cause i'm the PTL :p
10:38:31 bauzas well, in general, our lists are open
10:38:32 asettle johnthetubaguy: yeah we're weird like that. I dunno why we have it.
10:38:50 asettle Hence why I added the dev list into it, and the docs for others. I don't know the historical reason we have a separate ML
10:38:57 asettle I think it was because we were not a part of the dev cycle for a while there
10:38:58 asettle now we are
10:38:59 asettle Soooo ya know
10:39:02 bauzas having a separate ML is fine by me
10:39:07 johnthetubaguy that does explain why I don't see any docs chatter on the ML
10:39:12 asettle johnthetubaguy: yep :) feel free to sign up.
10:39:13 bauzas having it moderated is what I'm worried about
10:39:13 johnthetubaguy well, not much anyways
10:39:21 asettle I occasionally post to it
10:39:28 asettle bauzas: we get a *Lot* of spam, unforunatley
10:39:37 bauzas anyway, /me needs to drop off, school pick-up
10:39:43 asettle Everything is let through from people unless it's a clear spam email or bot (which, is unbelievably common)
10:39:56 bauzas soooo \o see ya in a couple of hours
10:40:10 owalsh asettle: hi
10:40:15 johnthetubaguy asettle: not sure, that kind of thing can make you accidentally make you a docs CPL
10:40:17 asettle owalsh: hi!
10:40:20 asettle bauzas: have fun!
10:40:39 asettle johnthetubaguy: *screams*
10:41:50 asettle thank you owalsh !!
10:42:53 bauzas kid's time, so \o
10:42:57 asettle bauzas: hey woah it's hardly a baby :P
10:45:37 owalsh asettle: AFAIK need to run api_db sync before map_cell0 or create_cell
10:46:39 asettle owalsh: the person to best answer that is bmoss as he has been testing. I'm just waiting for him to send me his error logs so can I appropriately address questions.
10:46:52 asettle I am currently just escalating to ensure we have eyes on it :)
10:57:04 asettle owalsh and johnthetubaguy - Brian confirmed that he initially used the dev docs in-tree to install, and those didn't work either *head desk*
10:57:39 gibi hi nova! there is a high severity bug fix that needs core attention https://review.openstack.org/#/c/437222/ . Could you check it please?
10:57:44 johnthetubaguy OK, that has worked for some people, at least apparently
10:58:29 johnthetubaguy gibi: its open in my browser, just chasing down this docs issue right now
10:58:36 gibi johnthetubaguy: thanks!
10:58:41 jaosorior gibi: thanks for the fix; that actually breaks us.
11:00:20 gibi jaosorior: hi! breaks me too :)
11:00:50 johnthetubaguy gibi: there are related quota issues to that fix, I believe
11:01:12 johnthetubaguy not that your fix breaks quotas, just that you are pointing at a wider bug / lack of code sharing
11:02:25 gibi johnthetubaguy: you mean this fix needs to be extended with some quota fix as well?
11:02:43 johnthetubaguy gibi: no, just there are other problems in that area I think
11:02:53 johnthetubaguy there is a quota bug about that, someone was working on it
11:03:19 johnthetubaguy gibi: I would love dansmith or melwitt to take a look at that bug fix, they have better context around that code
11:03:48 gibi johnthetubaguy: OK, I will ping them today
11:03:49 johnthetubaguy gibi: when I last checked it I was a bit worried about the cut and paste -ness of it, but not sure how to restructure it
11:04:43 gibi johnthetubaguy: yeah, that code path is ugly. I was affraid to touch it as I felt I will break something if I try to factor out the duplication
11:05:39 gibi johnthetubaguy: do you have the bug number for the quota bug? I would review that patch to learn something new
11:06:26 johnthetubaguy gibi: I don't was in chat previously, something about hitting over quota errors, and the quota never being removed
11:06:36 asettle johnthetubaguy: I see you pushed a patch! What's up?
11:06:40 asettle Just replied to the ML with brian's logs
11:06:44 asettle bauzas: ^^
11:06:44 cdent asettle, johnthetubaguy: do we have a more clear picture of the context that leads to "wrong" and whatever "wrong" is with that docs stuff? It feels a bit like we're all guessing
11:06:47 cdent oh good
11:06:54 cdent that'll probably answer my questions, thank you asettle
11:06:55 asettle cdent: yep take a look.
11:06:59 johnthetubaguy gibi: maybe just a function that does destroy and does the notification
11:07:26 johnthetubaguy asettle: I was worried about the order not being very clear, but also very, very important, so I refactored the docs patch while we were waiting for the logs
11:07:44 asettle cdent: the in-tree docs you guys have were also tested and although I don't have the error logs to give you, my understanding is that those instructions immediately error with "placement API is not available, you must configure the placement API."

Earlier   Later