| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-06-16 | |||
| 16:29:59 | mriedem | superdan: i reckon we probably need to audit nova-status for multi-cell support at some point too | |
| 16:30:10 | mriedem | i know parts of it are counting things like compute nodes across cells | |
| 16:46:33 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Add a status check for enabled filters https://review.openstack.org/427200 | |
| 16:46:35 | mriedem | superdan: bauzas: ^ finally cleaned this up - not sure if we want to consider backporting that or not - if we did, we'd have to adjust it a bit | |
| 16:48:02 | mriedem | we should also see those warnings show up in the grenade logs because of the CoreFilter | |
| 16:49:24 | openstackgerrit | Chris Friesen proposed openstack/python-novaclient master: 2.47: Show flavor info in server details https://review.openstack.org/435141 | |
| 16:53:25 | sdague | mriedem: https://github.com/sdague/nova-bug-tools/blob/master/stable-series-cleanup.py | |
| 16:55:44 | sdague | though if launchpad had reasonable search interfaces I wouldn't have to abuse their system so hard to find these series only bugs | |
| 16:58:13 | mriedem | sdague: ok | |
| 16:58:23 | mriedem | at some point that should probably live in the release-tools repo | |
| 17:00:43 | sdague | mriedem: maybe, right now I'm trying to build out some automation specific to experiments in nova. That one is probably more generic release oriented, but the rest of it seems like we're going to get more specific pretty quickly | |
| 17:00:57 | sdague | I have a bunch of uncommitted local work of experiments | |
| 17:01:56 | mriedem | ok. i'm going to be going down the placement rabbit hole this afternoon | |
| 17:02:13 | figleaf | mriedem: bring a lantern | |
| 17:05:48 | mriedem | i bring a ray of sunshine everywhere i go | |
| 17:13:34 | eandersson | mriedem: We should add an regression test for that commit imo | |
| 17:14:11 | mriedem | eandersson: oh your functional test? | |
| 17:14:26 | eandersson | Also, while this may fix master (actually not yet convinced), I don't think we can back port these changes to Mitaka/Newton | |
| 17:15:16 | mriedem | eandersson: we can backport dan's change to ocata and newton | |
| 17:15:19 | eandersson | I didn't write one for mine, but mostly because I had no clue how to write a test, but pretty sure we could write something simple | |
| 17:15:20 | mriedem | mitaka is basically eol upstream | |
| 17:15:53 | eandersson | It's funny because that is actually the fix I originally suggested :p | |
| 17:16:02 | mriedem | dan's change is 13 minutes from merge | |
| 17:16:43 | mriedem | we could still write a regression test and backport that before backporting the fix | |
| 17:16:53 | mriedem | if a regression test can be written | |
| 17:19:29 | openstack | Launchpad bug 1635367 in OpenStack Compute (nova) "Ram filter is broken since Mitaka" [High,In progress] - Assigned to Erik Olof Gunnar Andersson (eandersson) | |
| 17:19:29 | melwitt | this is the bug eandersson opened last year https://bugs.launchpad.net/nova/+bug/1635367 on overcommit being broken | |
| 17:24:21 | openstackgerrit | Merged openstack/nova master: Fix regression preventing reporting negative resources for overcommit https://review.openstack.org/474994 | |
| 17:27:59 | melwitt | oh, already marked as duplicate. mriedem, that will hide that it's fixed to people searching though right? should the dupe be the other way around? | |
| 17:28:51 | mriedem | i didn't dupe it | |
| 17:29:23 | mriedem | it should probably be the other way around now though yes | |
| 17:29:24 | melwitt | oh. okay I'll fix it then | |
| 17:29:46 | eandersson | A little funny that it would be a dupe of a 3 hour old bug report :D | |
| 17:30:25 | mriedem | we can go either way i think | |
| 17:30:27 | melwitt | eandersson: it is, but I think that's the only way to make it look reasonable and not hide bug that shows the fix etc | |
| 17:30:45 | melwitt | I think someone told me the ones that get marked as dupes don't show up in searches etc | |
| 17:30:57 | mriedem | we can also dupe dan's against the original and change the status to fix released | |
| 17:31:00 | mriedem | on the originla | |
| 17:31:02 | mriedem | *original | |
| 17:31:27 | melwitt | okay, I can do that | |
| 17:31:53 | eandersson | Just don't mark it as fixed for Mitaka | |
| 17:32:21 | melwitt | yeah, will have to put that as won't fix I think | |
| 17:34:03 | melwitt | mriedem: are we gonna backport to mitaka? we still have a stable/mitaka branch | |
| 17:34:35 | eandersson | This is the kind of horrible issue that you will run in production, but won't notice until you reach capacity. So we should make it obvious that it's an issue for anyone running overcommit in Mitaka. | |
| 17:34:53 | mriedem | melwitt: mitaka is closed i think - the branch is there but i don't know if any ci works on it | |
| 17:35:19 | melwitt | okay | |
| 17:35:24 | mriedem | clarkb: is mitaka CI all dead now? | |
| 17:35:30 | clarkb | uh | |
| 17:35:35 | clarkb | no idea | |
| 17:35:39 | mriedem | ok | |
| 17:36:02 | superdan | didn't tony already announce mitaka as eol? | |
| 17:36:13 | mriedem | announcing and making it happen are different things | |
| 17:36:23 | eandersson | no mitaka eol tag yet at least | |
| 17:36:35 | superdan | I figured I'd have to backport it downstream only for mitaka, fwiw | |
| 17:37:18 | superdan | eandersson: do you want to propose backports of that to ocata and newton at least? | |
| 17:37:31 | mriedem | i was working on the ocata one | |
| 17:37:36 | superdan | eandersson: I'm happy to, but if you do, I can vote on them :P | |
| 17:42:35 | sdague | unless mitaka gets another release though it doesn't help much to stick it in git | |
| 17:43:44 | superdan | well, it helps people that pull from the git trees, but yeah | |
| 17:43:46 | mriedem | fwiw we did a novaclient mitaka release a week or two ago | |
| 17:46:20 | sdague | I'm not opposed to doing another mitaka release honestly, that fix seems like it would be worth it | |
| 17:47:21 | sdague | mriedem: ok, well I just closed out the kilo/liberty bug cruff, and moved all the Fix Committed => Fix Released in mitaka | |
| 17:50:21 | mriedem | ocata backport is posted for your viewing pleasure | |
| 17:50:30 | mriedem | https://review.openstack.org/475044 | |
| 18:08:31 | Redcavalier | Hi, I believe I've found a bug in nova and I haven't seen any similar bug report. However, before I report it, I'd just like to validate it with someone if possible. | |
| 18:10:13 | Redcavalier | Essentially, when using the virtio-scsi driver for block devices, I get an error when I try to add additional block devices through cinder. The error is as follow : libvirtError: internal error: unable to execute QEMU command '__com.redhat_drive_add': Duplicate ID 'drive-scsi0-0-0-0' for drive | |
| 18:11:43 | Redcavalier | It seems that Nova is not providing a good address to libvirt when adding an additional block device to an existing VM using the virtio-scsi driver. Or so that's what I understand from this. | |
| 18:12:25 | Redcavalier | This is in the latest RDO newton release, btw. | |
| 18:14:17 | smcginnis | Redcavalier: Are you using config drive? | |
| 18:14:28 | Redcavalier | smcginnis, nope | |
| 18:15:33 | Redcavalier | neutron metadata because I live dangerously (and it's been working better than my expectations until now, tbh) | |
| 18:27:45 | openstackgerrit | Jay Pipes proposed openstack/nova master: placement: produce set of alternative allocations https://review.openstack.org/473377 | |
| 18:28:26 | openstackgerrit | Jay Pipes proposed openstack/nova master: placement: produce set of allocation candidates https://review.openstack.org/473377 | |
| 18:33:31 | leakypipes | figleaf: hey, I renamed the ProviderAlternatives to AllocationCandidates above | |
| 18:33:36 | leakypipes | figleaf: naming is hard... | |
| 18:37:25 | mriedem | leakypipes: comments posted https://review.openstack.org/#/c/473377/3 | |
| 18:40:16 | openstackgerrit | Matthew Edmonds proposed openstack/nova master: [WIP] Implement virt driver set_host_enabled https://review.openstack.org/472794 | |
| 18:42:18 | openstackgerrit | Matthew Edmonds proposed openstack/nova master: [WIP] Implement virt driver set_host_enabled https://review.openstack.org/472794 | |
| 18:42:18 | openstackgerrit | Matthew Edmonds proposed openstack/nova master: [WIP] Deactivate powervm compute until ready https://review.openstack.org/471773 | |
| 18:43:11 | figleaf | leakypipes: will review shortly | |
| 18:43:50 | figleaf | leakypipes: I would still like to get a clearer picture in my mind as to where this is heading. Hard to evaluate things otherwise | |
| 18:44:24 | figleaf | leakypipes: I realize that you're coding to the strawman spec, but that strawman spec was just one small piece of the plan | |
| 18:45:25 | openstackgerrit | Matthew Edmonds proposed openstack/nova master: [WIP] Deactivate powervm compute until ready https://review.openstack.org/471773 | |
| 18:45:40 | leakypipes | figleaf: ack | |
| 18:45:51 | leakypipes | figleaf: working on the followup patches which add that to the picture now. | |
| 18:46:48 | figleaf | leakypipes: kewl | |
| 18:50:32 | openstackgerrit | Matthew Edmonds proposed openstack/nova master: [WIP] Deactivate powervm compute until ready https://review.openstack.org/471773 | |
| 18:57:24 | leakypipes | figleaf: link for your extra specs patch pls? | |
| 19:03:21 | openstackgerrit | Matthew Edmonds proposed openstack/nova master: [WIP] Implement virt driver set_host_enabled https://review.openstack.org/472794 | |
| 19:05:54 | mriedem | eandersson: superdan: newton backport https://review.openstack.org/475057 | |
| 19:10:18 | eandersson | Looks good - that patch is identical to the patch we have been running since last year | |
| 19:24:21 | figleaf | leakypipes: https://review.openstack.org/#/c/473627/ | |
| 19:25:25 | figleaf | leakypipes: your input on handling the exception for an invalid extra_spec value would be appreciated on that | |
| 19:27:38 | openstackgerrit | Takashi NATSUME proposed openstack/python-novaclient master: Microversion 2.48: Standardization of VM diagnostics https://review.openstack.org/473228 | |
| 19:27:58 | openstackgerrit | Takashi NATSUME proposed openstack/python-novaclient master: Microversion 2.49 - Enable cold migration with target host https://review.openstack.org/406707 | |
| 19:28:16 | openstackgerrit | Takashi NATSUME proposed openstack/python-novaclient master: Microversion 2.49 - List/Show all server migration types https://review.openstack.org/430839 | |
| 19:29:23 | NostawRm | heh, I never know if what I'm asking is appropriate for this channel. Wouldn't it be useful to have the option to recreate config_drive on boot/reboot? I'm doubting it would be simple enought to do it only if data has changed, but as it stand right now, the only way to get up-to-date data in the drive is to manually remove the existing drive, or am I missing something? | |
| 19:29:41 | mriedem | NostawRm: yes that's a thing people have talked about for awhile | |
| 19:30:02 | NostawRm | okay, cool, I couldn't find anything about it and I wasn't sure if I was missing something on it | |
| 19:30:22 | mriedem | i believe harlowja was also talking about this in an operators ML thread at one point | |