Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2018-02-05
19:31:50 sean-k-mooney dansmith: mriedem will i trow a path up for rocky or is this something ye want to backport?
19:33:45 openstackgerrit Ameed Ashour proposed openstack/nova master: detach instance volumes when VM creation fails https://review.openstack.org/528385
19:34:19 sean-k-mooney using os-vif is not backportable hence why i am leaning towords adding the libvirt element for the mtu. we can always delegate entirly to os-vif in rocky if we like but just wonderin if we want to fix this in queens?
19:36:06 openstackgerrit Merged openstack/nova stable/ocata: Set server status to ERROR if rebuild failed https://review.openstack.org/536904
19:36:16 ameeda mriedem, gibi patch uploaded
19:37:31 ameeda jaypipes, bauzas: could you please review this for me https://review.openstack.org/#/c/526900/
19:39:10 openstackgerrit Eric Fried proposed openstack/nova-specs master: Update Provider Tree https://review.openstack.org/540111
19:39:17 efried edleafe, cdent, jaypipes: ^
19:47:32 sean-k-mooney stephenfin: by the way i know you were looking at mtu suff last year so this might be of interest to you. https://bugs.launchpad.net/nova/+bug/1747496 it will cause issue for anyone with jumboframes who want to upgrade to the ovs conntrack driver.
19:47:33 openstack Launchpad bug 1747496 in OpenStack Compute (nova) "MTUs are not set for VIFs if using kernel ovs + hybrid plug = false" [Undecided,New]
19:48:19 mriedem sean-k-mooney: you can do a 2 part fix where the first uses the xml directly and backport that, and the other fix goes into os-vif and we remove the xml hack
19:49:03 sean-k-mooney mriedem: yep i can is that your prefence? also do we want to backport to queens et al now or wait
19:49:31 sean-k-mooney mriedem: im just heading home but i can see if i can trow up the xml patch tommorow if i get time
19:51:02 mriedem sean-k-mooney: i wouldn't consider it something we have to hold up queens rc1 for
19:51:03 mriedem if it's latent
19:52:16 ameeda mriedem: when I try to git cherry-pick -x c0aca1d333628f9174e8db53674787e281e7e0d7 I got this error -> fatal: bad object c0aca1d333628f9174e8db53674787e281e7e0d7
19:52:18 sean-k-mooney mriedem: oh i was not suggesting we hold it up just is this something ye want to review for a queens backport e.g. i should fix it right away or can be reviewd for back port later e.g. ill try and fix before ptg
19:55:58 mriedem ameeda: git fetch https://git.openstack.org/openstack/nova refs/changes/71/540871/1 && git cherry-pick -x FETCH_HEAD
19:56:48 mriedem stvnoyes: i think i what might be an issue with boot from volume with multiple instances and the new cinder volume attach flow...
19:57:36 sean-k-mooney mriedem: i have 3 patches i need to rebase for rocky later this week so ill add it to the list if it wont effect future backport or ill try to make time to fix it specificlly tomrow if it more urgent. anyway got to run enjoy your evening.
19:59:23 mriedem stvnoyes: we call this for each instance we create in a multi-create request https://github.com/openstack/nova/blob/master/nova/compute/api.py#L1253
19:59:46 mriedem and _validate_bdm will loop over the volumes passed in, and if everything is new enough, create an attachment per volume and store that on the bdm record
20:00:05 mriedem we then make a copy of that list per instance https://github.com/openstack/nova/blob/master/nova/compute/api.py#L1267
20:00:27 mriedem i'm wondering if we're overwriting or losing any of the bdm.attachment_id records when creating multiple instances
20:00:31 mriedem maybe it's ok
20:01:29 mriedem might be a decent test though, create >1 instances in the same request using the same volume and make sure each instance has unique attachments to that volume
20:02:11 mriedem i suppose if you aren't using a multiattach volume, the 2nd instance in the loop would fail to create an attachment to the volume because the volume's attach_status will be 'attaching'
20:04:29 ameeda mriedem: now the commit message have those 2 lines
20:04:30 ameeda (cherry picked from commit eba33a0e2d8aace6fbc889026fb80dc2c208bc8d) (cherry picked from commit c0aca1d333628f9174e8db53674787e281e7e0d7)
20:05:51 mriedem ameeda: those should go on separate lines
20:05:52 openstackgerrit Matt Riedemann proposed openstack/nova master: DNM: debug nova-api service version check during boot from volume https://review.openstack.org/540992
20:05:53 mriedem but that's ine
20:05:55 mriedem fine
20:08:13 mriedem dansmith: we haven't been doing proper service version checking in nova-api since pike https://review.openstack.org/#/c/539755/ - should be an easy +W
20:08:21 ameeda mriedem: yes they are , so I can do git review now ?
20:08:27 mriedem ameeda: yes
20:08:42 ameeda mriedem: Thank you !!
20:09:15 openstackgerrit Ameed Ashour proposed openstack/nova stable/ocata: add "--until-complete" option for nova-manage db archive_deleted_rows. https://review.openstack.org/540274
20:09:51 ameeda mriedem: could you please give me +2 here https://review.openstack.org/#/c/528385/ :$
20:10:10 melwitt jaypipes: replied
20:12:11 mriedem ameeda: your ocata backport is wrong
20:14:05 ameeda I see
20:23:27 openstackgerrit Ameed Ashour proposed openstack/nova stable/ocata: add "--until-complete" option for nova-manage db archive_deleted_rows. https://review.openstack.org/540274
20:27:42 ameeda mriedem: I don't know if I did the correct thing, please check it ^
20:28:33 mriedem ameeda: yes that's correct, thanks
20:29:53 ameeda Thank you !!
20:30:58 openstackgerrit Matt Riedemann proposed openstack/nova master: Add a nova-caching-scheduler job to the experimental queue https://review.openstack.org/539260
20:32:18 ameeda mriedem: please don't forget to review this https://review.openstack.org/#/c/528385/
20:56:55 mriedem efried: i think this might have broken the nova-next job but i'm not sure how https://github.com/openstack-dev/devstack/commit/49144e627120f9ec1cf72dfc84e02b9b81e669b6
20:56:59 mriedem https://bugs.launchpad.net/nova/+bug/1747511
20:56:59 openstack Launchpad bug 1747511 in OpenStack Compute (nova) "legacy-tempest-dsvm-neutron-nova-next-full fails with "Can not find requested image" since 1/31" [Undecided,New]
20:57:51 mriedem the only thing unique about the nova-next job at this point is it sets NOVA_USE_SERVICE_TOKEN=True in devstack
20:59:45 openstackgerrit Dan Smith proposed openstack/nova master: Bump compute RPC API to version 5.0 https://review.openstack.org/541005
20:59:49 dansmith gawd
21:00:00 mriedem ufta
21:06:58 efried mriedem: Is the bustage consistent?
21:07:15 mriedem efried: yeah, 100% fail
21:07:48 efried mriedem: I can propose reversion of the above, then a blank nova patch that Depends-On it, and see if that at least makes it pass. Shall I?
21:08:03 openstackgerrit Matt Riedemann proposed openstack/nova master: DNM: debug nova-next image not found failures https://review.openstack.org/541008
21:08:18 mriedem i think we could also just ignore the service_user config in nova as a test
21:08:43 efried I have to jet for a doc appt right now, will catch up with you in an hour or so.
21:12:18 jaypipes thx melwitt
21:15:05 openstackgerrit melanie witt proposed openstack/nova stable/ocata: Add release note for Aggregate[Core|Ram|Disk]Filter change https://review.openstack.org/541013
21:16:25 openstackgerrit Matt Riedemann proposed openstack/nova master: DNM: debug nova-next image not found failures https://review.openstack.org/541008
21:30:42 openstackgerrit melanie witt proposed openstack/nova master: Add release note for Aggregate[Core|Ram|Disk]Filter change https://review.openstack.org/541018
21:48:14 mriedem maciejjozefczyk: not sure why you'd +1 this :) https://review.openstack.org/#/c/540992/
21:50:32 openstackgerrit Matt Riedemann proposed openstack/nova master: DNM: debug nova-api service version check during boot from volume https://review.openstack.org/540992
21:56:19 openstackgerrit Matthew Edmonds proposed openstack/nova master: Clarify CONF.scheduler.max_attempts https://review.openstack.org/541031
21:56:46 edmondsw_ edleafe noticed this after reading your blog ^
21:59:31 edmondsw mriedem do we have a more general term that encompasses create, resize, and migrate if "build" doesn't do that?
22:02:38 mriedem scheduling?
22:02:41 mriedem like it said
22:02:42 edmondsw we can't say "schedule", because we only talk to the scheduler once.
22:03:26 melwitt it's still scheduling though, isn't it? trying alternate hosts *shrug*
22:03:42 edmondsw I guess
22:03:58 edmondsw at least the "for a chosen host" bit from the old help text is wrong, right?
22:04:09 edleafe mriedem: I think the problematic wording is "for a chosen host". But that was wrong before, too.
22:04:14 edleafe jinx
22:04:28 edmondsw edleafe yeah that is what first caught my eye
22:04:42 mriedem yes 'for a chosen host' is wrong
22:04:46 edmondsw I can change it back to scheduling and correct that part
22:05:27 edleafe "for a given VM build/move operation"
22:06:07 edmondsw I like that...
22:06:09 mriedem can we somehow make this about ironic and say, 'for a given bm movement'
22:06:32 edleafe nah, that sounds kinda crappy
22:06:33 edmondsw lol
22:07:43 openstackgerrit Matthew Edmonds proposed openstack/nova master: Clarify CONF.scheduler.max_attempts https://review.openstack.org/541031
22:08:15 efried mriedem: I have returned. Any update on the glance image snafu?
22:08:45 mriedem efried: debug patch is still running
22:08:53 jroll edleafe: "for a given VM b/m operation" :P
22:09:49 mriedem i can't wait to be in the vm bm room for 2 days in dublin
22:10:12 mriedem talking about...keystone
22:10:21 mriedem i came for the bm, stayed for the keystone
22:10:35 openstackgerrit Matthew Edmonds proposed openstack/nova master: Clarify CONF.scheduler.max_attempts https://review.openstack.org/541031
22:11:23 edleafe I'm SO glad I made it out of third grade
22:11:56 openstackgerrit Dan Smith proposed openstack/nova master: Bump compute RPC API to version 5.0 https://review.openstack.org/541005
22:11:57 openstackgerrit Dan Smith proposed openstack/nova master: Compute RPC client bump to 5.0 https://review.openstack.org/541035
22:12:06 openstackgerrit Matt Riedemann proposed openstack/nova stable/pike: Query all cells for service version in _validate_bdm https://review.openstack.org/541036
22:13:23 mriedem efried: results http://logs.openstack.org/08/541008/2/check/legacy-tempest-dsvm-neutron-nova-next-full/f24c9d2/logs/screen-n-api.txt.gz?level=TRACE
22:15:02 efried mriedem: Looks to me like neither of your glance.py messages hit.

Earlier   Later