Earlier  
Posted Nick Remark
#openstack-nova - 2018-06-26
16:41:01 stephenfin I'm obviously doing an awful job of explaining this
16:41:03 stephenfin :)
16:41:13 dansmith finally, we agree on something :)
16:41:19 stephenfin heh
16:41:32 stephenfin Cool, I'll set that up tomorrow afternoon my time
16:54:17 openstackgerrit Surya Seetharaman proposed openstack/nova stable/queens: Make nova list and migration-list ignore down cells https://review.openstack.org/578152
17:28:22 openstackgerrit Merged openstack/nova master: Remove mox in test_conductor.py (1) https://review.openstack.org/564658
17:36:48 openstackgerrit jiang wei proposed openstack/nova master: Add action initiator attribute to the instance payload https://review.openstack.org/536243
17:57:02 openstackgerrit Dan Smith proposed openstack/nova master: Allow templated cell_mapping URLs https://review.openstack.org/578163
18:30:45 melwitt mriedem: I'm wondering if the https://blueprints.launchpad.net/nova/+spec/vrouter-os-vif-conversion is similar to this patch we merged earlier in the cycle https://review.openstack.org/534371 , that one was relatively simple
18:40:31 mriedem similar
18:58:28 melwitt seems like it should be okay then. I'll put it on the agenda for next meeting
19:47:39 mriedem is everyone else tired of seeing this?
19:47:40 mriedem mox_fixture = self.useFixture(moxstubout.MoxStubout())
19:47:40 mriedem nova/test.py:323: DeprecationWarning: Using class 'MoxStubout' (either directly or via inheritance) is deprecated in version '3.5.0'
19:48:10 mriedem cuz uh, i know how to make it go away
19:48:31 melwitt how
19:48:50 mriedem change to use MoxStubout from mox3 instead of oslo.test http://git.openstack.org/cgit/openstack/mox3/tree/mox3/fixture.py#n21
19:49:11 melwitt but mox3 is evil!
19:49:22 mriedem it's the devil i know
19:49:30 melwitt heh
19:51:43 openstack Launchpad bug 1778784 in OpenStack Compute (nova) "mox_fixture = self.useFixture(moxstubout.MoxStubout()) usage is deprecated from oslo.test 3.5.0" [Medium,Triaged]
19:51:43 mriedem https://bugs.launchpad.net/nova/+bug/1778784
20:18:04 openstackgerrit Matt Riedemann proposed openstack/nova master: Remove compatibility code for instance groups https://review.openstack.org/578192
20:18:05 mriedem dansmith: i think you're going to just really love this ^
20:20:06 dansmith meh
20:20:15 mriedem sounds like love to me
20:22:00 dansmith I will trade you for: https://review.openstack.org/#/c/578163/
20:22:35 mriedem i think we have a bug for that actually
20:25:01 openstack Launchpad bug 1717915 in oslo.messaging "nova services and transport_url, cannot connect to vhost if specified" [High,Incomplete] - Assigned to Ken Giusti (kgiusti)
20:25:01 mriedem https://bugs.launchpad.net/nova/+bug/1717915
20:25:06 mriedem dansmith: does that in any way solve that problem?
20:26:18 mriedem i think there is also a minimum version of oslo.db needed for this...
20:27:40 dansmith mriedem: hmm, I don't think so, and that syntax may break this
20:27:44 dansmith mriedem: a minimum oslo_db for what?
20:27:48 mriedem sec
20:28:06 mriedem https://review.openstack.org/#/c/539035/
20:28:14 mriedem i assume ^ is related
20:28:59 dansmith mriedem: that's part of their workaround
20:29:08 dansmith mriedem: that isn't needed if we have this, regardless of the oslo_db version
20:33:18 dansmith so, that bug says, I think, that oslo.msg does a split(',') on the netloc part of the url, yeah?
20:33:39 dansmith that'll break my extraction of the username and password,at least, and probably the hostname
20:36:33 dansmith ugh, yeah
20:36:53 dansmith I dunno why that was done instead of just multiple full urls..
20:56:13 mriedem dansmith: ok comments inline
20:56:40 mriedem reading mike's comment now, i suppose i should have read that first
20:57:17 melwitt does anyone know off the top of their head how instances can end up with no InstanceMapping?
20:58:11 melwitt chatting with someone from rdo cloud about it, it's happened to them a couple of times
20:58:52 mriedem no instance mapping or no cell mapping in the instance mapping?
20:58:53 melwitt it seems like something that could only happen during an upgrade, if instance(s) were somehow missed upon nova-manage cell_v2 map_instances
21:01:16 melwitt I'm not sure yet, will be looking at the details tomorrow (they're in EU time zone). but just wanted to ask in case this was a common thing other people have seen
21:01:36 openstackgerrit Merged openstack/nova master: Remove support for /os-fixed-ips REST API https://review.openstack.org/568516
21:02:04 melwitt we know CERN has hit the no cell mapping in the instance mapping, and I still don't understand how that occurs
21:07:27 mriedem i do
21:07:38 mriedem well i know one way you can hit it
21:07:42 mriedem https://review.openstack.org/#/c/576161/
21:11:21 melwitt I won't get to see what the situation is in their db until tomorrow. I doubt they're doing the ip filter though
21:13:41 mriedem well i also started https://review.openstack.org/#/c/575556/ to try and debug when this does happen
21:14:11 mriedem only need to determine if i should lookup the build request to see if we somehow missed the build request and went straight to listing instances with a marker that is on an instance not yet mapped to a cell
21:14:54 mriedem there is a window of time between when we create the instance in a cell and when we actually update the instance mapping in conductor (and then we delete the build request)
21:16:09 melwitt I think last time this happened, it was that there were a few instances in the cell0 db but they had no instance mappings, so they showed up in a 'server list' but could not be deleted because no instance mapping or no cell mapping in instance mapping
21:16:13 mriedem dansmith: yeah so if i create my cell mapping with multiple rabbit hosts using , it would mess up that urlparse - or transport_url for that matter right?
21:16:28 mriedem and transport_url is a stropt which is comma-delimited
21:16:29 dansmith mriedem: yes, but I've got a solution
21:16:38 mriedem [oslo_messaging_rabbit]/rabbit_hosts is a listopt
21:16:40 dansmith the weird chars in db thing is more annoying
21:16:48 mriedem yeah...
21:16:51 openstackgerrit Dan Smith proposed openstack/nova master: Allow templated cell_mapping URLs https://review.openstack.org/578163
21:16:52 dansmith mriedem: checkityo ^
21:23:37 dansmith mriedem: I guess I'm missing something
21:23:57 dansmith surely ? in the url anywhere other than before the query string is not valid right?
21:25:16 melwitt it could be part of the password also, right?
21:25:45 dansmith that's the assertion, but I'm just surprised most url parsing implementations would allow it
21:25:50 melwitt unless that doesn't work in general, connecting to mysql db separately
21:25:59 dansmith clearly python's does not
21:29:07 dansmith yeah, password should be url encoded
21:29:49 dansmith https://bugs.python.org/issue18140
21:29:54 dansmith so I call BS on that
21:30:48 dansmith I would take the three years of no answer to that last question as "nobody has a good reason"
21:31:06 melwitt hm, yeah. I was thinking this same question, "Where do such unencoded URLs come from?"
21:31:30 dansmith same would go for having "@" or ":" in the password.. you'd *have* to urlencode it for sanity
21:31:38 dansmith or / or any of the other reserved characters
21:31:42 melwitt yeah
21:35:24 openstack Launchpad bug 1778515 in OpenStack Compute (nova) "nova-manage list_cells doesn't work is some special characters are in the passwords" [Undecided,New] - Assigned to Surya Seetharaman (tssurya)
21:35:24 mriedem while on the subject, i saw this today https://bugs.launchpad.net/nova/+bug/1778515
21:37:25 melwitt oh yeah, similar deal
21:37:29 mriedem so apparently CERN has [ or ] but not both, or in the wrong order, in their db/mq passwords
21:37:44 mriedem urlparse thinks they are invalid ipv6 urls
21:39:28 mriedem this is the thing we use in map_cell0 https://github.com/zzzeek/sqlalchemy/blob/15ea75981305fdad8286f6803671b864ccda13f2/lib/sqlalchemy/engine/url.py#L203
21:53:25 openstackgerrit Dan Smith proposed openstack/nova master: Allow templated cell_mapping URLs https://review.openstack.org/578163
21:53:36 dansmith I think I got all the actionable feedback ^ but I gotta run off for a bit now
21:57:21 mriedem just noticed something weird, but surely i can't be the first...
21:57:29 mriedem we move instance groups and instance group members from the cell to api db yeah
21:57:47 mriedem and when we delete an instance, the instance_destroy db api code used to also remove the instance group member table entry for the deleted instance
21:57:59 melwitt yeah instance group stuff moved to api db
21:58:03 mriedem we don't have anything like that with deleting an instance, from what i can tell, when deleting an instance and the members are now in the api db
21:58:37 mriedem so if i create an instance in a group, then delete the instance, and show members on the group, will it show the deleted instance uuid?
21:58:57 melwitt hm
21:59:13 mriedem ah _get_not_deleted
21:59:36 mriedem that seems pretty inefficient

Earlier   Later