Thursday, 2021-08-05

opendevreviewzhen proposed openstack/nova stable/victoria: Fix request path to query a resource provider by uuid  https://review.opendev.org/c/openstack/nova/+/80355002:21
opendevreviewBrin Zhang proposed openstack/nova master: Replaces tenant_id with project_id from List/Update Servers APIs  https://review.opendev.org/c/openstack/nova/+/76429206:32
*** akekane_ is now known as abhishekk06:41
opendevreviewBrin Zhang proposed openstack/nova master: Replace all_tenants with all_projects in List Server APIs  https://review.opendev.org/c/openstack/nova/+/76531106:58
gibifyi the Asia friendly nova meeting starts in 29 minutes here in the channel07:31
*** rpittau|afk is now known as rpittau07:47
bauzasgibi: maybe another email for telling we have an Asian friendly meeting now ?07:58
bauzas(and good morning ;) )07:58
gibibauzas: morning07:59
gibiI think I'm late with that mail now, but good idea07:59
gibiI will note that for the next meeting08:00
bauzasnp08:00
gibi#startmeeting nova_xtra08:00
opendevmeetMeeting started Thu Aug  5 08:00:35 2021 UTC and is due to finish in 60 minutes.  The chair is gibi. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
opendevmeetThe meeting name has been set to 'nova_xtra'08:00
gibi#endmeeting08:00
opendevmeetMeeting ended Thu Aug  5 08:00:43 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:00
opendevmeetMinutes:        https://meetings.opendev.org/meetings/nova_xtra/2021/nova_xtra.2021-08-05-08.00.html08:00
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/nova_xtra/2021/nova_xtra.2021-08-05-08.00.txt08:00
opendevmeetLog:            https://meetings.opendev.org/meetings/nova_xtra/2021/nova_xtra.2021-08-05-08.00.log.html08:00
gibi#startmeeting nova_extra08:00
opendevmeetMeeting started Thu Aug  5 08:00:46 2021 UTC and is due to finish in 60 minutes.  The chair is gibi. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
opendevmeetThe meeting name has been set to 'nova_extra'08:00
gibi(interestingly it allows any name it seems)08:00
gibi\o08:01
gibiwho we have here today?08:01
bauzasgibi: yup, you can ask for any meeting name08:01
bauzas\o08:02
gibithen why we have to do a booking in the irc repo?08:02
opendevreviewYongli He proposed openstack/nova master: Smartnic support - cyborg drive  https://review.opendev.org/c/openstack/nova/+/77136208:02
opendevreviewYongli He proposed openstack/nova master: smartnic support - new vnic type  https://review.opendev.org/c/openstack/nova/+/77136308:02
opendevreviewYongli He proposed openstack/nova master: smartnic support - create arqs  https://review.opendev.org/c/openstack/nova/+/75894408:02
opendevreviewYongli He proposed openstack/nova master: smartnic support - build instance with smartnic arqs  https://review.opendev.org/c/openstack/nova/+/79824908:02
opendevreviewYongli He proposed openstack/nova master: smartnic support - cleanup arqs  https://review.opendev.org/c/openstack/nova/+/79805408:02
opendevreviewYongli He proposed openstack/nova master: smartnic support - reject server move and suspend  https://review.opendev.org/c/openstack/nova/+/77991308:02
opendevreviewYongli He proposed openstack/nova master: smartnic support - functional tests  https://review.opendev.org/c/openstack/nova/+/78014708:02
bauzasgibi: for the meeting time, that's it08:02
gibithat make sense, but the booking also contains a define ticker for the meeting bot like " Start this meeting using: #startmeeting nova_extra" https://meetings.opendev.org/#Nova_Monthly_Asia_Friendly_Team_Meeting08:03
bauzasbut for example, you'd see some nova_scheduler meetings logs in eavesdrop ;)08:03
gibithose old times...08:04
gibiwhen there was even a notification subteam meeting08:04
bauzas:) https://meetings.opendev.org/meetings/08:04
gibithat seems interesting https://meetings.opendev.org/meetings/honeybooboo/08:06
bauzas:)08:08
gibido we have some folks here today for this meeting?08:08
gibior should I just stop the recording of bauzas and me joking around08:09
gibi#endmeeting 08:12
opendevmeetMeeting ended Thu Aug  5 08:12:04 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:12
opendevmeetMinutes:        https://meetings.opendev.org/meetings/nova_extra/2021/nova_extra.2021-08-05-08.00.html08:12
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/nova_extra/2021/nova_extra.2021-08-05-08.00.txt08:12
opendevmeetLog:            https://meetings.opendev.org/meetings/nova_extra/2021/nova_extra.2021-08-05-08.00.log.html08:12
gibiwe tried at least 08:12
bauzas:)08:12
bauzasmaybe that's because we haven't told jokes08:12
gibiI keep the rights to entertain myself while waiting :D08:12
bauzasdo you know how IT folks name their bathrooms ?08:14
bauzasan I-Pee address08:14
gibilol08:14
gibiwe need more like this08:14
kashyapsean-k-mooney: Hi, when you're about: I guessed yesterday, the "concern" about moving from cirrus to virtio-vga with 1080p turned out to be a non-problem: Cirrus simply does not support 1080p.08:15
kashyapGerd from QEMU confirmed it.  So, moooving on.08:15
kashyaps/I guessed/As I guessed/ :D08:15
kashyapbauzas: :D What did you have for breakfast 08:16
bauzaskashyap: morning08:16
bauzasI'm nearly off for vacations, I guess08:16
bauzasgibi: the whole list of meetings names make me loling https://meetings.opendev.org/meetings/08:17
kashyapbauzas: Likewise; I'm off from 12-27 Aug08:17
bauzaslots of typos08:17
bauzaskashyap: quite identical, Aug 9-30 (incl.)08:18
kashyapCool08:18
gibiI guess next week we should just close the nova channel08:19
gibias stephenfin and I will be off too08:20
kashyapHeh08:48
kashyapgibi: Probably we could update the channel topic?  08:50
kashyapTo the effect of: "Bear timezones and work hours in mind | If IRC is quiet, write to the mailing list?"08:51
gibiheh08:54
gibihm I don't have OP rights 08:55
bauzasstephenfin: thanks for reviewing the mdev series, as a trade, please ping me your own DB series ;)09:21
stephenfinbauzas: nw! It starts here https://review.opendev.org/c/openstack/nova/+/799520/09:23
bauzasI'm just uploading my series again given your logs point and gibi's comment on the commit msg about more is more than less09:23
gibistephenfin: I managed to finish the packet rate series up until the last WIP patch (nova-manage heal_allocation)09:24
gibistephenfin: so if you still have time then review is appreciated09:24
stephenfincan do!09:24
gibistephenfin: I can also trade reviews :)09:24
stephenfinI was going to say, reviews on the remainder of the DB series would be appreciated :-D09:24
gibistephenfin: OK, I will do that then09:25
bauzasgibi: my last 2 days are dedicated to Gerrit looking fwiw09:27
gibibauzas: I'm affraid to ask you to look at the packet rate as you will dissappear for 3 weeks so I will be blocked waiting you to come back and re-review just before FF.  but if you have time...09:28
bauzasthat's understandable09:29
bauzasone day, feature freezes won't happen on end of Augusts09:29
bauzasfun fact, my wife is always grumbling about the fact our release cadence is always hitting our usual resting periods :)09:30
gibithis end of summer FF is not idea, the W FF happened at a better time for me at least09:31
opendevreviewSylvain Bauza proposed openstack/nova master: Change the admin-visible logs for mdev support  https://review.opendev.org/c/openstack/nova/+/80337809:31
opendevreviewSylvain Bauza proposed openstack/nova master: Provide the mdev class for every PCI device  https://review.opendev.org/c/openstack/nova/+/80291809:31
opendevreviewSylvain Bauza proposed openstack/nova master: Provide and use other RCs for mdevs if needed  https://review.opendev.org/c/openstack/nova/+/80323309:31
opendevreviewSylvain Bauza proposed openstack/nova master: Expose the mdev class  https://review.opendev.org/c/openstack/nova/+/80174309:31
opendevreviewSylvain Bauza proposed openstack/nova master: WIP: Cleanup GPU vs. mdev wording  https://review.opendev.org/c/openstack/nova/+/80337909:31
bauzas(just a rebase for other changes but https://review.opendev.org/c/openstack/nova/+/803378 which fixes two nits)09:32
bauzasgibi: right, but honestly, only europeans feel this being problematic so I'm OK to live with it09:32
gibi^^ looks good to me09:35
songwenpingsean-k-mooney: https://review.opendev.org/c/openstack/cyborg/+/797403 this patch backport to victoria, but it requires oslo.db==10.0.0, because this patch https://review.opendev.org/c/openstack/oslo.db/+/792124 resolved duplicate key error for mysql. how can we fix the cyborg tempest?09:35
opendevreviewLee Yarwood proposed openstack/nova master: Add regression test for bug 1938326  https://review.opendev.org/c/openstack/nova/+/80280109:38
opendevreviewLee Yarwood proposed openstack/nova master: compute: Query the service group API within check_instance_host  https://review.opendev.org/c/openstack/nova/+/80231709:38
lyarwoodgibi: https://bugs.launchpad.net/nova/+bug/1912310/comments/7 - TIL about logsearch, is that a local tool or something I could use?09:59
gibilyarwood: I would say highly experimental https://github.com/gibizer/zuul-log-search10:00
lyarwoodawesome10:00
gibiI'm plannig for the time when logstash will be gone10:01
gibithis logsearch needs decent net bandwidth and a plenty of local space but it does not need a always running service10:01
gibiright now I'm trying to add capability for matching build queries against stored search patterns to help figuring out why a job failed10:03
kashyaplyarwood: Once again ... thanks for the 'nova-mange libvirt update_machine_type'! :)10:04
gibilyarwood: here are my config dir too with some bug patterns https://github.com/gibizer/zuul-log-search-config10:07
gibilyarwood: and as always, pull requests are welcome :)10:08
stephenfinlyarwood, bauzas, gibi: Reworking this hostname API change. I was asked to drop the 'OS-EXT-SRV-ATTR:' prefix for the 'hostname' field from responses to make it align with the request. Do we want to drop all of these prefixes?10:13
stephenfinso 'OS-EXT-SRV-ATTR:hostname' becomes 'hostname', 'OS-SRV-USG:launched_at' becomes 'launched_at', ...10:13
stephenfinI ask because when I'm doing one and already spinning up the microversion machinery, it makes sense for me to do them all10:14
gibidoesn't make much sense to keep them, they are there only for historical reasons as far as I remember10:14
stephenfinyes, due to the old-school extension framework10:14
gibikill them with fire!10:14
stephenfinOS-EXT-SRV => os-extended-server-attributes extension; OS-SRV-USG => os-server-usage extension etc. 10:15
stephenfin(I only learned that today from https://wiki.openstack.org/wiki/NovaAPIv2tov3)10:15
stephenfin🔥🔥🔥10:16
lyarwoodstephenfin: so is this behind a microversion?10:16
stephenfinabsolutely10:16
lyarwoodright cool then burn away10:17
opendevreviewLee Yarwood proposed openstack/nova master: zuul: Skip volume and block live migrations due to bug #1912310  https://review.opendev.org/c/openstack/nova/+/80358510:59
lyarwood^ gibi / stephenfin ; okay I've had enough of https://bugs.launchpad.net/nova/+bug/1912310 borking things in the check and gate queues, lets skip things and ask the QEMU folks to look at this11:00
stephenfinagree11:02
gibilyarwood: do we have left any live migration coverage?11:04
lyarwoodah, not in the nova-live-migration job because it isn't using shared storage11:04
lyarwoodlet me respin this11:04
gibibauzas: I'm just wondering did we ever updated nova-manage placement heal_allocation to support healing vGPUs?11:08
gibibauzas: I think if today we have an instance with vGPU request and the heal_allocation CLI is used it will try to allocate VGPU resource from the root RP that will fail11:13
gibiI guess the same is true for flavor based cyborg devices11:14
gibithe code simply assumes that everything coming from the flavor need to be allocated from the root RP https://github.com/openstack/nova/blob/2ffd9738602531e93495a1feca76bbb687c3e72c/nova/cmd/manage.py#L1700-L170511:15
gibihttps://github.com/openstack/nova/blob/2ffd9738602531e93495a1feca76bbb687c3e72c/nova/scheduler/utils.py#L607-L61211:17
gibithis is a scary TODO^^11:18
gibiamending the cyborg part. If the flavor has cyborg device profile extra_spec then that is simply ignored by the heal_allocation code11:20
gibiwith a --force used it can mean that a healthy cyborg allocation is dropped from an instance11:20
gibi /o\11:20
* gibi goeas adding a big red warning to the top of the CLI 11:21
sean-k-mooney ya... that is not ideal11:36
sean-k-mooneygibi: that also affects QOS11:37
gibisean-k-mooney: not, there is explicit QoS support there11:37
gibiI'm just about to extend that with the packet rate handling11:37
gibiwhen I detected the missing pieces11:37
sean-k-mooneyoh its after this11:38
sean-k-mooneyyou fix things up later?11:38
gibihttps://github.com/openstack/nova/blob/master/nova/cmd/manage.py#L155711:39
sean-k-mooneyah https://github.com/openstack/nova/blob/master/nova/cmd/manage.py#L1609-L161011:39
gibifirst heal_allocation was added my mriedem then I added port allocation healing to it when the QoS was first done11:39
gibinow I need to fix up the QoS support due to the format change in the resource request as part of the pps feature11:40
sean-k-mooneyi was actully wonderign if we use  resources_from_flavor for any other operation in nova11:40
gibifortunetly not11:40
gibithat would be a huge bug11:40
sean-k-mooneyyep11:40
gibiwe should move that util function to the manage.py to show it is not used by any other code11:41
sean-k-mooneyah i see nov amanage trhen unit and func tests11:41
sean-k-mooneyya i guess we could11:42
sean-k-mooneyok so this would affect vGPU, Cyborg and vPMEM11:43
gibivPMEM is also not on the root provider?11:43
sean-k-mooneyi belive we have multipel namespaces fo differnet size so i think its nested11:44
sean-k-mooneyit may also impact inventories created via provider.yaml11:44
gibisean-k-mooney: vpmem is on the root according to this doc https://docs.openstack.org/nova/latest/admin/virtual-persistent-memory.html11:45
gibidoes provider.yaml today support creating child RPs?11:45
gibior inventories on child rps?11:46
sean-k-mooneyah right we are using different RC for the different namespaces so that does not need to be nested11:46
gibiwe don't have tests but I assume that anytign that is on the root healed correctly11:47
gibiI mean we have tests for basic mem, disk, vcpu and port QoS but not to the others like vpmem 11:47
sean-k-mooneygibi: so i tdoes not look like we can crete nested rps with the file but we can specifcy the uuid11:48
sean-k-mooneyso if you precreate the RPs the it can manage them11:49
gibiok, so provider yaml can add inventories to existing childs like cyborg, vgpu or QoS childs. So that is also affected11:49
sean-k-mooneyso it wont use nested RP by default but there is nothing to prevent you doing that11:49
sean-k-mooneyyes exactly11:49
gibibut there is no way I can detect that from the manage CLI. I can detect vgpu and cyborg dev profile in the flavor and blow up11:50
sean-k-mooneywell im wondering why we cant try and retrive the structure form placment initally11:50
gibisean-k-mooney: so you mean if the instance has nested allocation then we dont try to heal it11:51
gibisean-k-mooney: that can be done11:51
gibisean-k-mooney: but we cannot detect that an instance would need a nested allocation if that allocation is missig11:51
sean-k-mooneywell that could be a first step11:51
gibiand the whole reason of heal allocation is to heal missing allocations :)11:52
sean-k-mooneybut i was wondering if we could derive where the allocation should come from using the tree structure of plamcnet and its current allocation if they existis11:52
sean-k-mooneygibi: well for the we kind of can11:53
sean-k-mooneyif we se it uses a CUSTOM_CYBORG_THING11:53
sean-k-mooneyand we look at the RP tree for the host and see that is not on the root RP we know it need to be healed usign the nested RP inventory11:54
sean-k-mooneyif and only if that RC exist on only one nested RP we can heal it11:54
gibicyborg is requested via device profile name in the flavor so that can be detected easier, for any CUSTOM_FOO your idea is viable11:54
sean-k-mooneybut if the same RC exits on multiple RPS really only the virt dirver would be able to figure out what rp is correct11:55
sean-k-mooneye.g. it would have to use inform form the libvirt domain or similar to try and determin which pGPU the vGPU was allocated form11:55
gibisean-k-mooney: yes, the ambiguity cannot be resolved in the CLI, we have that thing already implemented (rejected) for the QoS healing11:56
gibithere the VF - PF - port - PF RP relationship cannot be disambiguated in the CLI11:56
sean-k-mooneypart of me thinks we should be storing some addtion info in our db to allow this11:57
sean-k-mooneybut im not sure what that should be 11:57
sean-k-mooneywhat annoys me about this problem is even if we save a copy of the inital allocation summeries and the placment query that we used to generate it im not conviced that is sufficent to reconstuct the allocations remotely12:01
gibiI stop here now. I will add some blocking and documentation to the CLI about vgpu and cyborg dev profile to prevent damage. then I will continue adding QoS support. other can take up removing the vgpu and cyborg block by implementing support12:01
sean-k-mooneygibi: it kind of feels like the only way to do this would be to have nova-manage call the virt dirver over rpc to have it fix it12:02
sean-k-mooneygibi: ack12:02
gibiyes, the full support most probably would need that12:02
opendevreviewLee Yarwood proposed openstack/nova master: zuul: Mark live migration jobs as non-voting due to bug #1912310  https://review.opendev.org/c/openstack/nova/+/80358512:03
songwenpingsean-k-mooney: we have a problem on cyborg that you may know, please give some tips if you have free time.12:03
songwenping https://review.opendev.org/c/openstack/cyborg/+/797403 this patch backport to victoria, but it requires oslo.db==10.0.0 for cybort, because this patch https://review.opendev.org/c/openstack/oslo.db/+/792124 resolved duplicate key error for mysql. how can we fix the cyborg tempest?12:03
songwenpinghttps://review.opendev.org/c/openstack/cyborg/+/797403 this patch backport to victoria, but it requires oslo.db==10.0.0 for cyborg tempest, because this patch https://review.opendev.org/c/openstack/oslo.db/+/792124 resolved duplicate key error for mysql. how can we fix the cyborg tempest?12:04
sean-k-mooneyok so you are gettign duplicate DeviceProfile uuids in this case 977806ca-4e8e-40c2-aa3a-09cef290333612:06
sean-k-mooneyand this is currently how you create your device profiles https://github.com/openstack/cyborg/blob/1052efe93b5e7aa351b1f50cfe80f504dcf48b72/cyborg/db/sqlalchemy/api.py#L499-L51712:08
sean-k-mooneyso this is the contraing that is filing 12:10
sean-k-mooney pymysql.err.IntegrityError: (1062, "Duplicate entry 'fpga_same_test' for key 'device_profiles.uniq_device_profiles0name'")12:10
sean-k-mooneyok i see12:14
sean-k-mooneyhttps://review.opendev.org/c/openstack/oslo.db/+/792124/6/oslo_db/sqlalchemy/exc_filters.py12:14
sean-k-mooneyso thet way that code is ment to work is it parses device_profiles.uniq_device_profiles0name12:15
sean-k-mooneyand it should extract the unique constrait by firsts discarding eveything before uniq_ leaving device_profiles0name12:16
sean-k-mooneythe it splits that on the 0 to get the table device_profiles and columns in this case name12:16
sean-k-mooneyso the unique constrati you were expecting was device_profiles name not the uuid12:17
sean-k-mooneywithout that fix it was using all colums as unique constriats? i guess at least that the oslo db level12:19
sean-k-mooneyoh i see12:19
sean-k-mooneyIn mysql 8.0.19 , Duplicate key error information is extended to12:20
sean-k-mooneyinclude the table name of the key.Previously, duplicate key error12:20
sean-k-mooneyinformation included only the key value and key name.12:20
bauzasgibi: sorry was out for lunch12:21
sean-k-mooneysongwenping: im surpised that affect https://github.com/openstack/cyborg/blob/1052efe93b5e7aa351b1f50cfe80f504dcf48b72/cyborg/db/sqlalchemy/api.py#L511-L51612:22
bauzasgibi: about the VGPU healed allocations, well, we already verify the VGPU RC for the audit command but we don't do this for the heal_allocations12:22
bauzasgibi: also, given we would now use other custom RCs, maybe we could also modify both the audit and heal_allocs commands to have a new attribute for telling which RCs to look at12:22
songwenpingsean-k-mooney: yes, the mysql version is update.12:25
sean-k-mooneysongwenping: without the oslo.db patch teh colum will be named "device_profiles.uniq_device_profiles0name" with it it will be "name"12:25
sean-k-mooneyoh i see12:25
sean-k-mooneyok i get what is happening now so e.columns is a dict12:25
sean-k-mooney  if 'name' in e.columns: is checkking if there is a key that exactly match12:26
sean-k-mooneythe keey has chaned to now have the table name prefixed12:26
sean-k-mooneyso the fix you can do in cyborg is to add an elif12:26
songwenpingright, the e.columns isnot ['name'] any more.12:27
sean-k-mooneyya so we just need to make the comparisone a little more robost12:29
songwenpingif i make the name and id all conflict, the e.columns is ['id'] and isnot ['id','name']12:30
sean-k-mooneyhttps://paste.opendev.org/show/807904/12:31
sean-k-mooneyi think this will work ^12:31
songwenpingthis is good for now.12:32
sean-k-mooneyhttps://paste.opendev.org/show/807905/12:32
sean-k-mooneyor maybe that 12:33
sean-k-mooneyadd an else just in case we have a conflicat that is not on name or uuid although it would be treated as a uuid conflict today12:33
sean-k-mooneysongwenping: but ya the other way to do this is to preporcess the columns dict and stip the table prefix12:34
songwenpingdoes other projects have the same problems?12:35
songwenpingi see only cyborg distingush the uuid and name conflict.12:36
sean-k-mooneyi think we might define unique constraints differently then cyborg does12:36
sean-k-mooneysongwenping: so this is the other way to fix it https://paste.opendev.org/show/807908/12:39
sean-k-mooneyall that has changed here is instead of using e.colums directly i have generated a new columns dict and then the exsitng if else just uses that12:39
songwenpingthis is same as the oslo.db does.12:39
sean-k-mooneyyep more or less12:40
songwenpingbut whether it depends on mysql version12:40
sean-k-mooneyso on brances that cant use the new version fo oslo db you can backport that in cyborg12:40
sean-k-mooneysongwenping: this will work for any mysql verion12:41
sean-k-mooneyif you have old mysql it will be a noop as none of the column names will have 0 in them12:41
songwenpingok, this is a good idea, thanks.12:41
sean-k-mooneyso columns and e.columns will be the same12:41
songwenpingright12:42
sean-k-mooneythat is proably the minimal change let me see quickly what is different between how nova defines unique constraints an cyborg12:42
songwenpingnova doesnot distingush the conflict types12:44
sean-k-mooneyah ok that wold make sense then12:46
sean-k-mooneyi guess if any of them fail we dont realy care why we know the request is invlaid12:46
songwenpingyes, i also wonder if we should distinguish them12:47
sean-k-mooneyyou proably do it today to have a better error message but you likely could do tha tdifferently12:48
songwenpingack12:48
sean-k-mooneyoh https://github.com/openstack/nova/blob/35ddf1ad40207dee681a3c92cc9e86b061234edd/nova/db/sqlalchemy/api.py#L545-L55012:49
sean-k-mooneyso we do have that patteren12:50
sean-k-mooneythat would have changed form ServiceBinaryExists to ServiceTopicExists silently12:50
songwenpingso this also have problem12:52
songwenpingthe tempest doesnot check the ServiceBinaryExists exception?12:52
sean-k-mooneykind of becaue we use .get it wont fail12:53
sean-k-mooneyya we likely dont have tempest coverage for this12:53
sean-k-mooneyalthough we should have and api funct tests for thsi12:53
songwenping+112:53
gibibauzas: OK, so you have plans to amend the audit support for MDEV. then that is really a good time to add some support for heal if possible.12:53
bauzasgibi: well, I have around 12 hours for doing this until 3 weeks :p12:54
songwenpingi will commit one patch to coverage it.12:54
bauzas8 hours for tomorrow and 4 jours this afternoon :)12:54
bauzashours*12:54
gibibauzas: I'm not saying that you have to do it now. :D12:54
gibibauzas: it is totally ok to do it in Yoga12:54
gibibauzas: I just noted that we have a gap in heal 12:55
bauzasgibi: create a bug report and I'll own it12:55
gibiI will make sure that it is now documented12:55
gibibauzas: OK I can file a bug too12:55
bauzasor a blueprint maybe12:55
gibithat is a good idea12:55
gibiI will create a bug and later on we can transform that to a bp12:55
bauzasthis is a tech debt fix12:55
gibiif we ever get to it12:55
opendevreviewPierre Libeau proposed openstack/nova master: Reset state during service nova-compute init  https://review.opendev.org/c/openstack/nova/+/80360013:24
opendevreviewMerged openstack/nova master: trivial: Cleanup a comment about a now removed libvirt version check  https://review.opendev.org/c/openstack/nova/+/80261713:37
gibibauzas: filed the bug about heal_allocation https://bugs.launchpad.net/nova/+bug/193902013:51
bauzasgibi: and triaged13:51
opendevreviewBalazs Gibizer proposed openstack/nova master: Block servers wit vGPU and device profile in heal_allocations  https://review.opendev.org/c/openstack/nova/+/80360313:53
gibibauzas: thanks, and here is the doc and block ^^13:53
bauzasgibi: looking13:57
melwittbauzas: I'm gonna respond on the review too but the "unknown" is not a default consumer type, it's a cosmetic-only label for friendliness to the user. (same with the "all" label as a query parameter). a consumer with no type has NULL in the column. the reproposal of the spec has removed mention of the original proposed "UNKNOWN" official default type. during review reviewers preferred to leave NULL to represent the absence of a consumer15:08
melwitt type15:08
bauzasmelwitt: oh ok15:08
bauzasI only looked at the train spec15:08
bauzaswhen this was something as a gerrit spec :p15:09
melwittah gotcha15:09
bauzasmelwitt: will then remove my -115:09
melwittcool thanks :)15:09
bauzas(and yeah sorry I cheated :p )15:10
melwitthaha no worry15:11
lyarwoodhttps://review.opendev.org/c/openstack/nova/+/803585 btw gibi / stephenfin / melwitt ; moving the LM jobs to NV for the time being while someone looks at the underlying QEMU failure(s)15:14
melwitt /sad trombone sound15:14
melwittkashyap: I see you have commented on https://launchpad.net/bugs/1912310 before ^ but no leads yet right?15:18
kashyapmelwitt: Hi, /me looks15:18
kashyap(The bot doesn't seem to higlight the summary on IRC anymore)15:19
melwitthm yeah not sure what happened to the bot15:20
kashyapmelwitt: Yeah, no leads yet15:20
kashyapmelwitt: Is it hitting more often?  Looks like so from gibi's #7 on 31Jul15:22
melwittkashyap: yeah, lyarwood is proposing above making the live migration job non-voting because of it 15:22
kashyapmelwitt: Oh, yeah - just saw that15:23
bauzaslyarwood: unfortunately +Wd the live-mig job be non-votign 15:55
lyarwoodack thanks15:56
*** akekane_ is now known as abhishekk16:01
gibiabout the bug resolver bot I asked infra they said that https://meetings.opendev.org/irclogs/%23opendev/%23opendev.2021-08-03.log.html#t2021-08-03T16:31:3216:06
melwittthanks gibi 16:11
gibiso probably we lost the both the topic handling and the bug resolving capability of the bot during that transformatin16:14
*** rpittau is now known as rpittau|afk16:41
gibiIf I had time I would be happy working on those bots16:43
* gibi needs a time machine16:43
opendevreviewMerged openstack/nova master: zuul: Mark live migration jobs as non-voting due to bug #1912310  https://review.opendev.org/c/openstack/nova/+/80358518:11
-opendevstatus- NOTICE: The Gerrit service on review.opendev.org is going down for a quick restart to adjust its database connection configuration, and should return to service momentarily20:03
nurdieHey OS nova! I had to evacuate a failed compute node (it's super dead) on shared storage (ceph). 3 instances are hanging in "nova migration-list" as "accepted" but are already on another compute node. Does anyone know what galera db.table I can edit real quick to clear that up?21:12
opendevreviewmelanie witt proposed openstack/placement master: Add consumer_types migration, database and object changes  https://review.opendev.org/c/openstack/placement/+/66917023:23
opendevreviewmelanie witt proposed openstack/placement master: Microversion 1.38: API support for consumer types  https://review.opendev.org/c/openstack/placement/+/67944123:24
opendevreviewmelanie witt proposed openstack/placement master: Switch ConsumerType to use an AttributeCache  https://review.opendev.org/c/openstack/placement/+/67948623:24
melwittbauzas: updated first patch per your comments ^23:24

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!