15:00:02 #startmeeting oslo 15:00:03 Meeting started Mon May 3 15:00:02 2021 UTC and is due to finish in 60 minutes. The chair is hberaud. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:04 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:06 The meeting name has been set to 'oslo' 15:00:12 Courtesy ping for hberaud, stephenfin, moguimar, jungleboyj, bnemec, johnsom, bcafarel, kgiusti, gmann, valleedelisle, sboyron, damani 15:00:18 o/ 15:00:26 o/ 15:00:26 #link https://wiki.openstack.org/wiki/Meetings/Oslo#Agenda_for_Next_Meeting 15:00:40 o/ 15:00:44 Will just wait a couple minutes for folks. 15:00:47 o/ 15:03:07 #topic Red flags for/from liaisons 15:03:18 From an Oslo point of view I think that we need to socialize this point => http://lists.openstack.org/pipermail/openstack-discuss/2021-April/022094.html 15:03:24 Nothing from Cinder. 15:04:03 Ah, ok. I will share that with the Cinder team. 15:04:13 Last week we merged some related fixes and we released a new version of oslo.db to land these patches => https://opendev.org/openstack/releases/commit/b1683206f7562842d283ab86a30679c28cafea56 15:04:21 o/ 15:06:17 ack I will forward that sqlalchemy link for neutron folks (and on the other way, no complaint heard on oslo topics) 15:06:19 AFAIK these patches fixed the issue on oslo.db itself, however, by looking at the logs of the functional tests related to services (nova etc...) I think that some pieces of code need to be updated on them too (services) => https://review.opendev.org/c/openstack/requirements/+/788339/ 15:07:00 thanks jungleboyj and bcafarel 15:07:10 That's all for Oslo 15:07:13 :-) 15:08:05 #topic Releases liaison 15:08:33 sorry i'm late 15:08:44 From a release point of view as I said previously a new version of oslo.db has been released 15:08:56 damani: o/ 15:09:31 o/ 15:09:40 damani: Do you want to share something new about release? 15:10:11 hberaud, nothing to share right now 15:10:49 ack np, I don't think that we have lot things to release right now too 15:10:58 #topic Security liaison 15:11:08 bnemec: The floor is yours 15:11:33 Nothing new from me. 15:11:42 bnemec: ok thanks 15:11:55 #topic TaCT SIG liaison 15:12:10 moguimar, sboyron: any update from your side? 15:14:37 AFAIK I didn't noticed TaCT SIG topics related to Oslo 15:15:02 #topic Action items from last meeting 15:15:08 * hberaud hberaud to propose Xena's courtesy ping list => Done 15:15:13 * hberaud hberaud to update our wiki page with active meeting weeks => Done 15:15:31 That's all 15:15:36 #topic Weekly Wayward Wallaby Review 15:16:42 https://review.opendev.org/c/openstack/pycadf/+/757446 15:17:52 I think that this one could be abandonned as we moved to "py3" rather than using a specific version of python 3, any objection. 15:17:54 ? 15:18:07 Did pycadf get that update? 15:18:25 Good question 15:18:25 I would expect this to be in merge conflict if it did. 15:18:32 I was thinking that yes 15:18:42 Yes you're right 15:19:16 Someone proposed this kind of patch => https://review.opendev.org/c/openstack/pycadf/+/787168 15:19:42 but the patch was stuck by the LC story 15:19:50 Okay, then let's merge that one and abandon the other. 15:20:01 I just "recheck" the right one 15:20:05 +1 15:20:38 I +2'd the py3 one so it should be ready to go when the recheck goes through. 15:20:45 hberaud, sorry got trapped, no I did not have any update on TaCT SIG 15:21:06 bnemec: ack thanks 15:21:13 I abandonned the other 15:21:23 sboyron: ack thanks 15:21:34 Cool, two patches down in one wayward review. :-) 15:21:40 \o/ 15:21:48 (we probably need to change the name of this meeting section, sadly) 15:21:59 lol 15:22:11 #topic Xena Courtesy Ping 15:24:11 Looks like a few people have already added themselves. 15:24:27 Just a friendly reminder about our new courtesy ping list, if you want to continue to be notified during each meeting then please add your name here => https://wiki.openstack.org/wiki/Meetings/Oslo#Xena_Courtesy_Ping 15:24:41 Thanks for your attention :) 15:24:56 And so... 15:25:00 #topic Open discussion 15:25:23 Anything else to share with us? 15:25:55 dansmith: Do you want retrying your question now? :) 15:26:12 oh, i guess :) 15:26:21 does anyone here know of a oslo.log quirk where sometimes you do something like LOG.warning() inside an exception handler and you get a stack trace you didn't expect in the logs? 15:26:37 as if you had passed exc_info= to the LOG.warning call ? 15:27:13 at least once in the past I think this came up, and we have a LOG.info(..., exc_info=False) call in nova as a result 15:27:30 basically we're seeing a stack trace on a log call we're not expecting, 15:27:41 but it also might be privsep logging the exception for us, we're not sure 15:27:45 * hberaud at first glance I've no idea 15:28:09 it seems like when glance makes this call, we get the trace.. when nova makes this same call, we get just the log message 15:30:17 okay, sounds like no obvious ideas :) 15:30:36 There is some exception funny business, but I don't think it should log an entire stack trace: https://opendev.org/openstack/oslo.log/src/branch/master/oslo_log/formatters.py#L110 15:30:49 I don't know if that can help => https://opendev.org/openstack/oslo.privsep/src/branch/master/oslo_privsep/tests/test_daemon.py#L49-L59 15:30:49 yeah I've looked through that a bit, 15:31:09 definitely magic, but I didn't see anything 15:31:56 hberaud: ack, I guess I should look at the brick code to see the privsep stuff it's doing 15:32:04 just weird because nova doesn't seem to trigger the trace 15:32:22 ack 15:33:46 dansmith: let us know if you find something useful, that could be added to oslo.log's docs 15:33:52 ack, thanks 15:34:01 you're welcome 15:34:07 Anything else? 15:36:36 OK, thanks everyone. Let's wrap up. 15:37:00 #endmeeting