Earlier  
Posted Nick Remark
#openstack-nova - 2018-04-18
19:00:22 dansmith melwitt: tab queued
19:00:40 dansmith melwitt: tssurya: need a cells meeting today? I again have nothing new
19:00:58 tssurya dansmith: me neither
19:01:00 melwitt (was about to ask the same thing) are we having a cells meeting today? that was the only thing I think I wanted to highlight. mriedem isn't around on IRC today
19:01:29 dansmith sweet
19:01:32 melwitt okay, sounds like we're good to skip today. only thing to keep in mind is anything you'd like to get in for r-1 tomorrow
19:02:29 melwitt lettuce know
19:02:34 tssurya also question about this nova-manage bug -> https://bugs.launchpad.net/nova/+bug/1746530 I marked it as won't fix because it felt more like an oslo_db issue, however please revert the status if there is a possible fix in nova part
19:02:34 openstack Launchpad bug 1746530 in OpenStack Compute (nova) "nova-manage api_db sync - NotSupportedWarning ['use_tpool']" [Medium,Won't fix]
19:03:43 tssurya infact we would be interested if there is a fix on the nova side for the warning that comes up in Queens all the time
19:07:16 melwitt looks like that oslo.db fix landed in queens, but we didn't bump our requirements for oslo.db and we can't now that queens is a stable branch. so yeah, would have to do something in nova if anything
19:08:13 tssurya melwitt: oh I didn't know that fix landed in queens as well,
19:08:32 melwitt er, maybe it didn't. sorry, I got confused looking at the nova commit
19:08:54 tssurya yea I guess the oslo_db fix is also only in master
19:09:34 melwitt yeah if it was fixed recently then it would be for rocky and even if it was backported, we couldn't bump the requirement on stable to consume it
19:10:00 tssurya I know that its just a warning, but was just wondering if there was a work around by any chance in nova
19:10:15 melwitt yeah. it's possible, I dunno off the top of my head
19:10:16 tssurya oh okay, shall I keep it as won't fix ?
19:11:03 melwitt yeah, I would since it's fixed for master and probably not worth trying to do a one-off for queens since it's just a warning IMHO
19:11:29 tssurya yep,
19:11:31 tssurya cool
19:18:37 openstackgerrit Merged openstack/nova-specs master: Fix typo in GET os-instance-actions url. https://review.openstack.org/557143
19:45:42 cdent melwitt: Is there still a gate job that runs with postgres? I seem to recall an experimental one or something?
19:48:51 openstackgerrit Merged openstack/osc-placement master: Initialize 'result' variable in functional.base https://review.openstack.org/560004
19:49:44 melwitt hm, not sure. looking
19:52:22 cdent the reason I ask is because I've stumbled upon a postgres-related problem in some of the placement sql and I can't figure out when it started and I'm exploring my options for finding it
19:53:35 melwitt I see. having trouble finding where our list of experimental jobs is, I can't remember where things are supposed to be since zuul v3
19:54:44 cdent yeah, had the same problem
19:54:51 melwitt but not finding hardly anything related to postgres in openstack-zuul-jobs
19:55:55 melwitt or project-config
19:56:16 cdent ditto
19:56:38 openstackgerrit Jackie Truong proposed openstack/nova master: Implement certificate_utils https://review.openstack.org/479949
19:56:39 openstackgerrit Jackie Truong proposed openstack/nova master: Plumb trusted_certs through libvirt driver image paths https://review.openstack.org/561262
19:56:40 cdent so it's either gone or hiding. I know Matt was keen on it existing, but don't know if it stayed aline
19:56:40 openstackgerrit Jackie Truong proposed openstack/nova master: Add trusted_image_certificates to REST API https://review.openstack.org/486204
19:56:41 openstackgerrit Jackie Truong proposed openstack/nova master: Add certificate validation docs https://review.openstack.org/560158
19:57:18 cdent i'll try faking it locally
19:57:32 openstackgerrit Matt Riedemann proposed openstack/nova stable/ocata: libvirt: Block swap volume attempts with encrypted volumes prior to Queens https://review.openstack.org/561604
20:05:15 spotz Hey all do you want me to file a bug for nova where the error message in the nova client is typoed? I'm guessing I can track it down and fix it possibly
20:07:50 melwitt spotz: sure, you can file a novaclient bug here https://bugs.launchpad.net/python-novaclient
20:08:07 melwitt (assuming the typo is in novaclient)
20:08:56 spotz Thanks melwitt, trying to track it down. It might be a little larger then just the message. stable/ocata won't associate a floating IP even though it says after Pike
20:11:42 spotz If I change the api version as the message suggests it works so, I'lljust bug the typo
20:12:47 melwitt cdent: you might be able to use a technique similar to this if you can find a postgres job in another project https://review.openstack.org/#/c/427668
20:15:01 cdent thanks melwitt
20:15:02 openstackgerrit Matt Riedemann proposed openstack/nova stable/ocata: Modify incorrect debug meaasge in _inject_data https://review.openstack.org/519950
20:18:45 melwitt spotz: okay. link me the bug after you file it, I'm not sure what message this is about. starting in newton, the nova API stopped proxying to neutron so floating IP association has to be done through neutron or openstackclient. so I'm not sure what message is saying "after Pike"
20:19:09 spotz melwitt https://bugs.launchpad.net/python-novaclient/+bug/1765192
20:19:10 openstack Launchpad bug 1765192 in python-novaclient "floating-ip-associate deprecation message typo" [Undecided,New]
20:19:35 spotz melwitt: I can't find it in the code base, could it possibly be something added by devstack?
20:23:09 cfriesen spotz: msg_deprecate_net in novaclient/v2/shell.py
20:25:10 spotz cfriesen: And no errors in stable/ocata. Let me peek at Pike and master
20:25:13 openstackgerrit Matt Riedemann proposed openstack/nova stable/ocata: Handle spawning error on unshelving https://review.openstack.org/548622
20:25:46 melwitt thanks cfriesen. found one here https://github.com/openstack/python-novaclient/blob/stable/pike/novaclient/v2/shell.py#L88
20:26:07 openstackgerrit Matt Riedemann proposed openstack/nova stable/ocata: Clean up volumes on boot failure https://review.openstack.org/545086
20:26:42 melwitt spotz: ^
20:27:02 spotz melwitt: I can patch if you like
20:27:05 melwitt spotz: so, you used stable/ocata novaclient and saw that message? seems like the message only started in pike
20:27:30 spotz melwitt: Yeah just realized this is a Pike packstack, not the Ocata devstack I thought I was on:)
20:27:40 spotz I have too many servers running:(
20:29:01 melwitt spotz: heh, okay. glad it's just the typo then. yeah, if you want to propose a patch to stable/pike, we can review it
20:29:45 openstackgerrit Chris Dent proposed openstack/nova master: WIP: Add root provider uuid to group by clause https://review.openstack.org/562379
20:30:16 spotz melwitt: Only other odd behavior is I had to set the api-version to less then 2.44 but that's part of the warning and I seem to be running 2.53
20:32:31 openstackgerrit Matt Riedemann proposed openstack/nova stable/ocata: Clean up volumes on boot failure https://review.openstack.org/545086
20:32:32 openstackgerrit Matt Riedemann proposed openstack/nova stable/ocata: Detach volumes when VM creation fails https://review.openstack.org/545087
20:32:42 melwitt spotz: the novaclient CLI will default to the latest available nova server API microversion (through version discovery) that it supports. on the nova server, the add/remove fixed/floating IP were removed in microversion 2.44, that's why you have to tell novaclient to request an earlier microversion of the API in order to do it
20:32:51 melwitt https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#id39
20:33:17 spotz melwitt: So expected behavior:)
20:33:29 melwitt so if you're working with pike, the max microversion in pike is 2.53, so that's what novaclient will default to
20:34:09 melwitt yes, because of the CLI defaulting to latest available and supportable
20:35:21 cfriesen melwitt: I wonder if there should be a checker for implicitly continued strings that don't have a space either at the end of one line or the beginning of the next.
20:35:21 melwitt spotz: the recommended way to associate IPs these days is to use openstackclient as it will make the appropriate calls to neutron (because the association actually happens in neutron)
20:35:30 spotz melwitt: Good to know, I'm trying to be more thorough about using the openstack CLI and the various project CLIs
20:35:58 spotz melwitt: And looks like Neutron is looking for a total depcreation of their client in the near future
20:36:08 melwitt cfriesen: there could be. but I don't wanna figure out how to write it
20:36:22 cfriesen melwitt: have you noticed that openstackclient won't let you live-migrate unless you specify a destination host?
20:37:17 melwitt spotz: yeah, that's the direction, for openstackclient to be the way to do everything. unfortunately for certain nova operations, the openstackclient doesn't support things properly or requires extra steps whereas the novaclient does one step. we need to fix that stuff :(
20:37:34 openstackgerrit Chris Dent proposed openstack/nova master: WIP: Add root and parenet provider uuid to group by clause https://review.openstack.org/562379
20:38:10 melwitt cfriesen: I haven't. but I do know that the one-step boot-from-volume in openstackclient was removed relatively recently. and we need to get that fixed too
20:38:24 spotz melwitt: There's a lot of disparity in the commands as far as functionality. We'll get there eventually, I just try to teach folks as many ways as possible
20:40:44 mriedem dansmith: melwitt: is there a cells meeting happening today?
20:41:05 melwitt mriedem: nay, we didn't have anything for today. do you have anything for today?
20:41:39 mriedem two things kind of
20:41:50 mriedem 1. wanted to know if dansmith is ok with the plan laid out in https://review.openstack.org/#/c/560674/2/nova/api/openstack/compute/services.py@222
20:41:51 openstackgerrit Chris Dent proposed openstack/nova master: WIP: Add root and parenet provider uuid to group by clause https://review.openstack.org/562379
20:42:01 mriedem wrt the get_uuids_by_host performance thing
20:42:17 melwitt spotz: yeah. one thing to know about openstackclient and nova is that the openstackclient does *not* discover the latest version, so if you want to do anything newer in the nova API, you have to pass along the desired microversion on the command line. that trips people up a lot
20:42:33 mriedem 2. was wondering if tssurya was investigating the functional test failures in https://review.openstack.org/#/c/554920/ because they look unrelated but i don't know why they'd fail here
20:43:45 mriedem nvm i think i just figured out #2
20:44:11 melwitt sweet
20:44:23 mriedem have to step away for a few days to realize your mistakes
20:45:00 cdent mriedem: while you're back: are you aware of the life or death of the experimental job that once tested nova with postgres? Is that still around somewhere?
20:45:13 mriedem cdent: neutron has one in their experimental queue
20:45:18 mriedem we don't, but we easily could
20:45:48 cdent something in a recent placement change tweaked things: https://review.openstack.org/#/c/562379/
20:46:07 mriedem ok, give me a sec and i can wip something up
20:46:42 cdent cool, thanks, i'll be back in a few, I need to do dishes etc
20:48:59 melwitt mriedem: earlier today, bmace reported that novaclient 9.1.1 (queens) does not work with multi-attach, making it not possible to use multi-attach with the client in queens. I assumed this is because the max supported microversion in the client is < the multi-attach microversion
20:49:33 mriedem it's in 10.x
20:49:55 mriedem https://github.com/openstack/releases/blob/master/deliverables/queens/python-novaclient.yaml#L16

Earlier   Later