| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2018-08-10 | |||
| 12:44:43 | mriedem_ | dansmith: re-added | |
| 12:45:26 | mriedem_ | sob, devstack overwrites my plugging timeout setting http://logs.openstack.org/08/553608/10/check/neutron-tempest-linuxbridge/2b303c2/logs/devstacklog.txt.gz#_2018-08-10_00_50_06_570 | |
| 12:49:16 | mriedem_ | but the timeout definitely happens | |
| 12:49:22 | mriedem_ | takes 30 seconds to transfer the guest | |
| 12:49:27 | mriedem_ | then tempest tears down and deletes the server | |
| 12:49:37 | mriedem_ | then we eventually see the plugging timeout after that | |
| 12:49:49 | openstackgerrit | Matt Riedemann proposed openstack/nova master: api-ref: fix GET /flavors?is_public description https://review.openstack.org/588092 | |
| 12:52:51 | lyaaaaaarwood | mriedem_: just looking at the volume reschedule lack of cleanup issue we spoke about yesterday, do you have a super simple way to cause a reschedule with two computes in devstack? | |
| 12:53:56 | lyaaaaaarwood | mriedem_: I've manually raised the Reschedule exception but instances are just ending up in an ERROR state and not being built on the other compute. | |
| 12:54:10 | lyaaaaaarwood | and that compute is fine, has resources etc | |
| 13:01:36 | mriedem_ | lyaaaaaarwood: so it's not rescheduling at all? | |
| 13:02:09 | lyaaaaaarwood | mriedem_: Nope, doesn't appear to be, that was with --min-count | |
| 13:03:10 | mriedem_ | --min-count shouldn't have anything to do with it | |
| 13:03:24 | mriedem_ | lyaaaaaarwood: anything in the compute or cell1 conductor logs? | |
| 13:03:37 | mriedem_ | are both computes reporting in? | |
| 13:03:48 | mriedem_ | i.e. openstack hypervisor list shows but computes as up? | |
| 13:03:55 | mriedem_ | and both are reporting into placement? | |
| 13:04:00 | mriedem_ | openstack resource provider list | |
| 13:06:23 | mriedem_ | gotta go, bbiab on the plane | |
| 13:13:08 | openstackgerrit | Matthew Booth proposed openstack/nova master: Move static _get_power_off_values to compute_utils https://review.openstack.org/578822 | |
| 13:17:07 | lyaaaaaarwood | huh so Alternates: [] is likely the cause | |
| 13:17:23 | lyaaaaaarwood | http://paste.openstack.org/show/727812/ is the example | |
| 13:22:09 | leakypipes | lyaaaaaarwood: aye aye matey, how be yur Friday? | |
| 13:27:34 | lyaaaaaarwood | leakypipes: morning morning, it would be grand if these instances would reschedule arghhhhh! | |
| 13:28:00 | lyaaaaaarwood | leakypipes: any news on your 2.0 blog post? | |
| 13:28:33 | leakypipes | lyaaaaaarwood: just wrapping it up now after a little feedback from mordred. I'll be publishing it in an hour or two. | |
| 13:28:57 | leakypipes | lyaaaaaarwood: everyone shall hate me, so I've been preparing for that inevitability. | |
| 13:30:43 | lyaaaaaarwood | leakypipes: dansmith isn't online yet | |
| 13:30:48 | dansmith | excuse me? | |
| 13:30:54 | lyaaaaaarwood | whops | |
| 13:31:03 | lyaaaaaarwood | morning | |
| 13:31:30 | dansmith | wassup? | |
| 13:32:02 | lyaaaaaarwood | SteelyDan: https://review.openstack.org/#/c/590439/ - would you mind? | |
| 13:32:24 | SteelyDan | oh I mind | |
| 13:32:26 | SteelyDan | I mind greatly | |
| 13:33:18 | leakypipes | hahhaha | |
| 13:38:31 | SteelyDan | lyaaaaaarwood: oh you should have told me that ^ was cleaning up a mess I made | |
| 13:38:37 | SteelyDan | I would have been less.. me.. about it | |
| 13:39:43 | lyaaaaaarwood | SteelyDan: haha no issues | |
| 13:59:25 | melwitt | . | |
| 14:21:17 | fried_rice | melwitt: Do we need bug tags to backport things to Rocky at this stage for RC2? | |
| 14:23:24 | melwitt | fried_rice: what do you mean by bug tags? | |
| 14:23:35 | melwitt | backport potential? | |
| 14:23:39 | fried_rice | melwitt: Closes-Bug: #XXXX which is required for backporting "normally". | |
| 14:23:45 | fried_rice | in the commit message | |
| 14:24:07 | fried_rice | (well, I guess the existence of the bug is the important thing) | |
| 14:24:57 | melwitt | oh, yeah ok, you're asking if we need a bug for something we want to backport. yes, usually. I can't remember if we ever do it without a bug | |
| 14:31:28 | fried_rice | lyaaaaaarwood: Do you happen to know this answer? ^ I.e. if there's a "grace period" for RCs where we don't use bugs to backport? | |
| 14:32:00 | SteelyDan | definitely needs bugs | |
| 14:32:27 | SteelyDan | unless it's something super procedural or something, but not sure what that would be | |
| 14:33:01 | SteelyDan | things going into rc2 should be very prescribed anyway | |
| 14:33:36 | melwitt | I think he means something not going into rc2, right fried_rice? | |
| 14:33:51 | fried_rice | yes, that's what I mean | |
| 14:33:55 | SteelyDan | he says "to backport" so.. | |
| 14:34:13 | fried_rice | I just didn't know if, because we haven't "released" it yet, it doesn't technically count as a "backport", even though it's a cherry-pick to a non-master branch. | |
| 14:34:33 | SteelyDan | that would be something going *into* rc2 | |
| 14:34:44 | fried_rice | right, that's what I'm asking. | |
| 14:34:52 | fried_rice | Mechanically, that still entails a cherry-pick to stable/rocky, right? | |
| 14:35:06 | SteelyDan | fried_rice: something going into rc2 right now requires a lot of scrutiny, a bug, and some agreement | |
| 14:35:06 | lyaaaaaarwood | fried_rice: no idea sorry, the stable branches are core managed until GA | |
| 14:35:30 | fried_rice | SteelyDan: Okay, that's what I was looking for, thanks. | |
| 14:37:20 | melwitt | lyaaaaaarwood: we had rc1 yesterday and we're going to have an rc2 to fix some things. | |
| 14:37:38 | fried_rice | melwitt: wherezat etherpad again? | |
| 14:37:59 | melwitt | the RC todos? https://etherpad.openstack.org/p/nova-rocky-release-candidate-todo | |
| 14:38:16 | fried_rice | thx | |
| 14:39:05 | lyaaaaaarwood | melwitt: and rc2 is tagged from the stable/rocky branch right? | |
| 14:39:34 | melwitt | lyaaaaaarwood: it must be ... this is new to me so I'm not sure. smcginnis can you enlighten me? ^ | |
| 14:39:40 | SteelyDan | yeah has to be :) | |
| 14:40:09 | melwitt | ok. so stable stays frozen for some time until the final release deadline I'm guessing | |
| 14:40:17 | lyaaaaaarwood | melwitt: yeah, so my point before was just that as a stable core I don't get +2/+W on stable/rocky until after GA | |
| 14:40:20 | openstackgerrit | Merged openstack/nova stable/pike: Make ResourceTracker.stats node-specific https://review.openstack.org/588037 | |
| 14:40:26 | melwitt | *stable/rocky | |
| 14:40:30 | SteelyDan | yes | |
| 14:40:39 | melwitt | lyaaaaaarwood: ok, got it | |
| 14:40:51 | melwitt | okay, I think I understand now, thank you | |
| 14:45:27 | fried_rice | um, if you don't get to +A stable/rocky, who does? (It ain't me - I still only have +1 powers there) | |
| 14:45:40 | fried_rice | or you just mean you're not supposed to? | |
| 14:46:20 | lyaaaaaarwood | yeah for past releases I didn't get it until after GA | |
| 14:46:23 | lyaaaaaarwood | but I have it now | |
| 14:46:38 | SteelyDan | I do too, so it must be on stable maint already | |
| 14:46:45 | lyaaaaaarwood | I guess someone just copied the stable ACLs across | |
| 14:46:51 | SteelyDan | fried_rice: why are you asking? anything you want to go to rc2 needs to be discussed heavily | |
| 14:47:24 | sean-k-mooney | fried_rice: +A on stable branch is the stable maintenance team so https://review.openstack.org/#/admin/groups/540,members | |
| 14:47:28 | fried_rice | SteelyDan: So that I know whether open bugs and tag the patches, which I clearly do, which I'm gonna do now. | |
| 14:47:44 | fried_rice | SteelyDan: Also adding them to the etherpad. | |
| 14:47:51 | fried_rice | Learning process, here. | |
| 14:48:09 | fried_rice | (As in, I'm learning what the process is) | |
| 14:49:13 | SteelyDan | fried_rice: anything you want to *propose* for rc should get rocky-rc-potential tag in launchpad | |
| 14:49:20 | SteelyDan | and then discuss here | |
| 14:49:37 | fried_rice | SteelyDan: Roger, thanks. | |
| 14:50:22 | sean-k-mooney | SteelyDan: at this point that would have to sepcificaly be a bug too and not have documentation impact? | |
| 14:50:52 | sean-k-mooney | i was never clear on how RC fixes and string freeze mixed | |
| 14:51:20 | SteelyDan | scrutiny goes up as the rc counter does | |
| 14:51:30 | SteelyDan | rc1 fixes are regressions and serious things | |
| 14:51:39 | SteelyDan | rc2 fixes are really only super serious things | |
| 14:51:44 | SteelyDan | rc3 things have to involve the queen | |
| 14:52:35 | SteelyDan | the only thing I've heard about for rc2 so far is this thing that makes live migration effectively broken for people on LB | |
| 14:52:39 | SteelyDan | which is, you know, pretty damn serious | |
| 14:53:44 | sean-k-mooney | SteelyDan: about that. the reason that was broken was basically the same reason we broke livimigraton with odl right | |
| 14:53:55 | sean-k-mooney | we cant rely on teh plug event form neutron | |