17:00:03 <gibi> #startmeeting nova notification
17:00:04 <openstack> Meeting started Tue Jun 19 17:00:03 2018 UTC and is due to finish in 60 minutes.  The chair is gibi. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:05 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:07 <openstack> The meeting name has been set to 'nova_notification'
17:00:47 <mriedem> o/
17:01:07 <gibi> mriedem: hi
17:01:44 <gibi> I've sent a status mail yesterday http://lists.openstack.org/pipermail/openstack-dev/2018-June/131589.html
17:02:07 <gibi> top of that the implementation of https://blueprints.launchpad.net/nova/+spec/add-full-traceback-to-error-notifications is on the gate
17:02:15 <gibi> mriedem: thanks for the review
17:02:21 <mriedem> np
17:02:35 <mriedem> https://review.openstack.org/#/c/554212 is going to be deferred
17:02:49 <gibi> fine by me
17:03:14 <gibi> I'm happy to talk about the content of the needed notification for that spec in Denver
17:03:39 <gibi> but we need somebody that knows what the consumer exactly needs
17:03:54 <gibi> maybe johnthetubaguy can help with that
17:03:58 <mriedem> that would be johnthetubaguy or someone from cern
17:04:04 <gibi> exactly
17:04:14 <mriedem> tssurya should be in denver too so should could maybe proxy if needed
17:04:26 <gibi> cool
17:04:51 <gibi> we have some progress on https://blueprints.launchpad.net/nova/+spec/add-action-initiator-to-instance-action-notifications but still not ready yet
17:05:01 <gibi> patch is here https://review.openstack.org/#/c/536243
17:05:26 <gibi> I think it still has a chance to land during the coming weeks
17:05:57 <gibi> aaand last but not least I spent the afternoon with https://bugs.launchpad.net/nova/+bug/1777540
17:05:58 <openstack> Launchpad bug 1777540 in OpenStack Compute (nova) ""IndexError: list index out of range" in ExceptionPayload.from_exception during resize failure" [Undecided,New]
17:06:48 <gibi> I managed to produce the same execution path on 17.0.2 with the same line numbers in the UnableToMigrateToSelf traceback but then it doesn't blow up on inspect.trace() call
17:07:29 <mriedem> hmm
17:07:30 <gibi> I'm in the middle of writing the stuf up in the bugreport and in a functional test case
17:07:37 <mriedem> i wonder if they were on py3?
17:07:47 <mriedem> i know exception handling context is different in py3
17:07:47 <gibi> mriedem: that is a good point, I can test that as well
17:08:04 <gibi> so far I only run it in py27 functional
17:08:40 <mriedem> https://docs.python.org/3.5/library/inspect.html#inspect.trace
17:09:48 <gibi> the diff is to return a list of frame object or list of named tuples
17:09:56 <gibi> but both should be a list
17:10:07 <gibi> a non empty one in case we are in an exception handling context
17:11:28 <gibi> functional-py35 just run and inspect.trace produce a non-empty list for my test case there as well
17:11:49 <mriedem> hmm
17:12:04 <mriedem> that's a test on master?
17:12:33 <gibi> it is on 17.0.2
17:12:53 <gibi> I selected that as that had the same line numbers matching with the logs in the bug
17:13:36 <mriedem> ok, idk
17:13:43 <mriedem> unless they have modified code or something
17:14:12 <gibi> anyhow, i summarize what I have and try to ask question from the bug reporter
17:14:34 <gibi> that is all I had today
17:14:38 <gibi> do you have anything else?
17:15:19 <mriedem> nope
17:15:30 <mriedem> i'm out the rest of the week
17:15:31 <mriedem> fyi
17:15:51 <gibi> have a nice time out
17:15:58 <gibi> see you next week
17:16:03 <gibi> and thanks for the meeting
17:16:08 <gibi> #endmeeting