17:00:05 #startmeeting nova notification 17:00:05 Meeting started Tue Jan 23 17:00:05 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:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:08 The meeting name has been set to 'nova_notification' 17:00:11 hi 17:00:30 o/ 17:01:10 lets make a quick meeting 17:01:29 There are two bugs I want to mention 17:01:42 https://bugs.launchpad.net/nova/+bug/1742962 17:01:43 Launchpad bug 1742962 in OpenStack Compute (nova) "nova functional test does not triggered on notification sample only changes" [High,In progress] - Assigned to Balazs Gibizer (balazs-gibizer) 17:01:53 this is basically a bug in the zuul v3 migration 17:02:03 yeah i remember that before i left 17:02:06 the fix seems to work 17:02:10 link? 17:02:35 gerrit is slow... 17:02:46 https://review.openstack.org/#/c/533210/ 17:02:59 this is adding the job to the nova tree 17:03:22 so we can override the irrelevant files right? 17:03:47 we can take the openstack-tox base job that does not have irrelevant-files and add our own functional jobs based on that 17:04:04 as soon as we have an irrelevant-files in the job we cannot override that in a child job 17:04:33 it seems really odd that a child job can't override values from the parent... 17:04:38 but that's a question for infra 17:05:25 yeah, infra stated that it is not possible 17:05:31 to override this field 17:05:46 anyhow we need some core attention on this patch 17:05:55 but I guess we are busy with FF 17:06:26 I will bring this up on the weekly meeting 17:07:04 I fear that we have other jobs in the project-config with the same mistake 17:07:23 yeah probably 17:07:45 I will try to go through them next week after the FF and file bugs at least 17:08:21 then the other bug is 17:08:30 https://bugs.launchpad.net/nova/+bug/1739325 17:08:31 Launchpad bug 1739325 in OpenStack Compute (nova) "Server operations fail to complete with versioned notifications if payload contains unset non-nullable fields" [High,In progress] - Assigned to Balazs Gibizer (balazs-gibizer) 17:09:20 this is stuck as I don't know how the original problem happened and I accept that dansmith doesn't want to merge the fix without understanding how this happens 17:09:22 i'm going to downgrade that to medium severity since we're not sure how we actually got into that state 17:09:39 mriedem: yeah, that make sens 17:09:45 yeah without a clear recreate it's pretty much stuck 17:10:00 one obvious solution is set default values for the fields that have defaults in the data model, 17:10:08 and make sure those are set before doing the versioned notification thing, but... 17:10:26 that doesn't help us if something else doesn't have a default and is nullable=False 17:11:31 I left some request for the bug author in the bug maybe if we can have more information then I can recreate the problem 17:12:09 currently it is pretty much a violation of the object model that could not happen 17:12:30 and I don't really happy coding something in the notification side to prepare for such violations 17:13:01 yup agree 17:13:17 then I keep this open and maybe it will solve itself with time :) 17:13:35 these were the important things from my side 17:13:51 i don't have anything 17:14:05 besides these there is three notification patches needing a second +2 17:14:17 ok 17:14:18 https://review.openstack.org/#/q/topic:bp/versioned-notification-transformation-queens+status:open 17:14:29 but that is all 17:14:39 let's go back to review features :) 17:14:43 thanks for the meeting 17:15:04 #endmeeting