Earlier  
Posted Nick Remark
#openstack-nova - 2023-01-17
14:47:49 kashyap "
14:48:28 sean-k-mooney bauzas: when stephen added --hostname we also added the dhcp_doamin to the dns name in neutron
14:48:37 sean-k-mooney we did nto modify what we put in the metadtaa
14:48:48 sean-k-mooney and we are not going to with artoms code because he is not changing that
14:48:59 sean-k-mooney it was only the value in the neutron port that was changed
14:49:43 bauzas you know what ? I'll play the ostrich about any kind of FQDN questions
14:50:01 bauzas once artom uploads his change, I'll review it and I'm done
14:50:04 sean-k-mooney bauzas: dont feel like you cant ask them
14:50:24 sean-k-mooney im just saying we are intentiolly not changing the behvior to not break anyone
14:50:37 sean-k-mooney and because we dont want cofnig dirven api behavior
14:50:43 bauzas the ship has sailed
14:50:47 sean-k-mooney so without removign the option entirly which would impact everyone
14:50:55 sean-k-mooney we cant really do much else
14:51:07 bauzas but honestly, I liked the fact that we were saying domain names was something unrelated to nova :)
14:51:26 sean-k-mooney yep so did i
14:51:38 sean-k-mooney this is the compromsie so that we dont have to care about them again once done
14:52:11 sean-k-mooney like all good compromises it does not make anyone happy but we can all live with it
14:52:26 bauzas the ostrich theory applied to me.
14:53:20 sean-k-mooney i prefer magpie psychology. distract people with other shiny things that matter
14:55:34 bauzas I need to learn the three-card monte
14:55:58 bauzas 'follow your card'
14:56:56 kashyap bauzas: sean-k-mooney: There's a thing called "Belgian compromise", which loosely means:
14:56:57 sean-k-mooney bauzas: added https://blueprints.launchpad.net/nova/+spec/default-ephemeral-format-unformated to meeting adjenda
14:57:00 kashyap (quote)
14:57:01 kashyap complex issues are settled by conceding something to every party concerned, through an agreement that is usually so complicated that nobody completely understands all its implications.
14:57:05 kashyap (/quote)
14:57:28 sean-k-mooney hehe ya sounds like a typical eu threaty
14:58:17 opendevreview Kashyap Chamarthy proposed openstack/nova master: libvirt: At start-up skip compareCPU() with a workaround https://review.opendev.org/c/openstack/nova/+/870794
14:59:14 sahid stephenfin: https://bugs.launchpad.net/osprofiler/+bug/2003092
15:24:50 artom bauzas, so I should just remove the ( ) about i18n?
15:32:35 opendevreview Alexey Stupnikov proposed openstack/nova stable/victoria: Test aborting queued live migration https://review.opendev.org/c/openstack/nova/+/845748
15:38:00 opendevreview Kashyap Chamarthy proposed openstack/nova master: libvirt: At start-up allow skiping compareCPU() with a workaround https://review.opendev.org/c/openstack/nova/+/870794
15:49:15 bauzas artom: yup IMHO
15:50:16 bauzas as a reminder nova meeting here in 10 mins
15:59:44 opendevreview Artom Lifshitz proposed openstack/nova master: Microversion 2.94: FQDN in hostname https://review.opendev.org/c/openstack/nova/+/869812
16:00:19 bauzas #startmeeting nova
16:00:19 opendevmeet Meeting started Tue Jan 17 16:00:19 2023 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:19 opendevmeet Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:19 opendevmeet The meeting name has been set to 'nova'
16:00:24 bauzas gdi, just in time
16:00:32 bauzas #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
16:00:36 bauzas hi everyone
16:00:40 dansmith o/
16:01:11 elodilles o/
16:01:59 gibi o/
16:02:00 bauzas okay let's start
16:02:06 gibi (I'm a bit distracted)
16:02:15 bauzas #topic Bugs (stuck/critical)
16:02:30 bauzas #info One critical bug
16:02:33 bauzas #info One critical bug
16:02:38 Uggla o/
16:03:08 bauzas #link https://bugs.launchpad.net/nova/+bug/2002951
16:03:20 bauzas gibi: I marked this one as critical for the sake of the discussion
16:03:22 gmann o/
16:03:29 bauzas but we can put it back to High
16:03:49 bauzas in general, I tend to triage CI bugs to Critical until we agree this is not holding the gate
16:04:04 bauzas do we want to discuss about it now or no ?
16:04:38 gibi sure
16:04:57 gibi I updated the bug
16:05:01 bauzas ok, so, gibi (mostly) and I looked at this one today
16:05:05 gibi I think it is tempest.api.compute.admin.test_volume.AttachSCSIVolumeTestJSON.test_attach_scsi_disk_with_config_drive test case that tirggers the OOM
16:05:11 bauzas yeah
16:05:17 bauzas and like I said, I tried to find wherer
16:06:17 bauzas but I wasn't able to see
16:06:34 bauzas context : https://github.com/openstack/tempest/blob/7c8b49becef78a257e2515970a552c84982f59cd/tempest/api/compute/admin/test_volume.py#L84-L120
16:06:46 bauzas we try to create an image
16:06:52 bauzas then we create an instance
16:07:06 bauzas and then a volume which we attach to the instance
16:07:44 gibi I haven't had time to look into the actual tc yet
16:07:45 sean-k-mooney p/
16:08:08 gibi also it would be nice to see how the python interpreter rss size grows during the test execution
16:08:11 dansmith yeah surely seems like a benign test case
16:08:38 sean-k-mooney we unfortuently dont have the memtacker stuff form devstack
16:08:50 sean-k-mooney btu it would be nice if we coudl get that and also dmsg in the tox based tests
16:08:52 bauzas I tried to grep the testname in n-api
16:09:01 bauzas but I wasn't finding it
16:09:07 bauzas so, either we no longer use it
16:09:17 bauzas or we were not yet calling the nova-api
16:09:34 bauzas which means we have the kill before creating the instance
16:09:55 bauzas but I could be wrong
16:10:53 bauzas anyway, folks are ok if we modify the bug to High ?
16:10:59 bauzas bug report*
16:11:32 gibi tomorrow I will continue looking but we can also tentatively try to disable this single test to see if that removes the OOM problem
16:12:18 gibi bauzas: I'm not against having this as High
16:12:26 bauzas ok
16:12:35 bauzas then let's look again tomorrow and we'll see what to do
16:13:08 bauzas this time I'm just afraid to remove this test because we don't know why we have a OOMkill
16:13:18 bauzas this could arrive to another test then
16:13:40 gibi yep, that would be my goal of disabling it temporary to see if the OOM just moves to another test case
16:13:44 gibi and to see which test case
16:13:48 gibi to find a pattern
16:13:48 bauzas (I also verified that nothing changed on the tempest side since 1 year for this test)
16:14:05 dansmith gibi: you could also rename it I think and change the sort ordering
16:14:10 bauzas yeah
16:14:11 dansmith afaik, we run tests sorted per worker
16:14:27 bauzas I was wondering, maybe this was a problem due to another test
16:14:28 gibi dansmith: good idea
16:14:45 bauzas dansmith: I think we can ask stestr to modifyh the sort
16:14:55 dansmith oh?
16:14:59 bauzas but I need to remember how to do it

Earlier   Later