Earlier  
Posted Nick Remark
#openstack-nova - 2020-11-03
07:37:54 brinzhang_ artom, sean-k-mooney: hello, I have a question with https://review.opendev.org/#/q/status:merged+branch:master+topic:bp/numa-aware-live-migration
07:38:47 brinzhang_ artom, sean-k-mooney: Is there an intuitive scenario to test this feature?
07:59:13 openstackgerrit Andrey Volkov proposed openstack/nova master: Functional test test_boot_reschedule_with_proper_pci_device_count https://review.opendev.org/760354
08:10:36 openstackgerrit Merged openstack/nova stable/queens: Follow up for cherry-pick check for merge patch https://review.opendev.org/761023
09:22:01 openstackgerrit Merged openstack/nova master: optimize the shelve code flow https://review.opendev.org/756665
11:16:20 openstack bug 1731668 in OpenStack Compute (nova) queens "placement: claim allocations fails with IndexError in _ensure_lookup_table_entry" [Low,In progress] https://launchpad.net/bugs/1731668 - Assigned to melanie witt (melwitt)
11:16:20 openstackgerrit Merged openstack/nova stable/queens: [stable-only] Add functional test for bug 1731668 https://review.opendev.org/756636
11:16:26 openstackgerrit Merged openstack/nova stable/queens: [stable-only] Use a separate transaction for reading after race https://review.opendev.org/756637
11:33:46 openstackgerrit Lee Yarwood proposed openstack/nova master: Add os-volume_attachments reference docs https://review.opendev.org/760971
11:59:26 mnasiadka Hi there, in kolla-ansible master CI we started getting this: https://zuul.opendev.org/t/openstack/build/28d615b8c06640afae885c3ef5a2f316/log/primary/logs/kolla/nova/nova-compute.txt#7 - is this some known issue?
12:04:54 gibi mnasiadka: that seems to be a new one for me. could you please raise a nova bug on it
12:05:08 mnasiadka gibi: sure, will do
12:05:50 gibi sean-k-mooney: wondering if this is a reincarnation of the eventlet dnspython issue somehow ^^
12:06:29 gibi mnasiadka: does it consistently fail for you?
12:06:58 gibi mnasiadka: or you only see it once?
12:07:24 gibi I did not get any hit in logstash for the error
12:08:28 mnasiadka gibi: checking zuul and we see it every 3th-4th run of the job, so it's not permanent
12:09:16 lyarwood gibi: `Delay in Elastic Search: Indexing behind by 93 hours`
12:09:24 gibi lyarwood: /o\
12:09:24 lyarwood gibi: that might be why you don't see it there tbh
12:10:07 gibi mnasiadka: do you see a specific date when this issue has started?
12:10:36 gibi lyarwood: o/
12:14:43 mnasiadka gibi: seems we get it from 3rd of November
12:14:59 mnasiadka so today
12:15:00 mnasiadka hmm
12:15:09 gibi mnasiadka: thanks, that helps checking any recently released dependencies
12:15:20 mnasiadka well, yesterday as well, but only one occurence
12:18:39 mnasiadka so actually all centos8-source and ubuntu-source jobs are failing since yesterday - https://zuul.openstack.org/builds?job_name=kolla-ansible-ubuntu-source&job_name=kolla-ansible-centos8-source&branch=master
12:21:16 openstack Launchpad bug 1902696 in OpenStack Compute (nova) "nova-compute fails with Unhandled error: TypeError: _wrap_socket_sni() got an unexpected keyword argument 'ca_certs'" [Undecided,New]
12:21:16 mnasiadka https://bugs.launchpad.net/nova/+bug/1902696
12:22:18 gibi mnasiadka: thanks!
12:45:01 artom brinzhang_, err, how do you mean intuitive? Have a VM with CPU pinning (any kind), and live migrate it?
12:49:03 gibi mnasiadka: I'm trying to figure out if some package we depend on has released a new version recently, but I don't find information in the job logs about which package versions was used to build the container images.
12:56:04 brinzhang_ artom: yeah, I want to know if I live migrate the instance, what behavior I can see with the server?
13:02:21 artom brinzhang_, with CPU pinning, if source and dest have different cpu_dedicated_set configured, then the VM's XML will be updated to reflect the dest's cpu_dedicated_set
13:03:03 mnasiadka gibi: let me deliver that in the bug
13:04:32 gibi mnasiadka: thanks. could you add the package versions from a failed run as well as a recent successful run?
13:05:52 brinzhang_ artom: do I need to config the dedicated cpu in the dest node before I execute live migrate?
13:06:30 brinzhang_ Or let the server automatically schedule
13:17:52 mnasiadka gibi: commented in the ticket
13:20:03 gibi mnasiadka: thanks
13:23:17 gibi mnasiadka: I cannot open the links you posted in the bugreport
13:23:25 gibi I get e.data.info is undefined (Unable to fetch URL, check your network connectivity, browser plugins, ad-blockers, or try to refresh this page)
13:23:35 mnasiadka gibi: let me check, I'll update to raw links maybe
13:23:45 gibi yeah, raw links would be better, thenks
13:23:47 gibi thanks
13:24:30 artom brinzhang_, yeah, I mean the cpu_dedicated_set config option
13:25:11 artom brinzhang_, https://docs.openstack.org/nova/latest/configuration/config.html#compute.cpu_dedicated_set this one
13:26:19 artom If they're different on source and destination, we would expect the vcpupin elements (https://libvirt.org/formatdomain.html#cpu-tuning) in the XML to change
13:28:34 mnasiadka gibi: should be better now ;)
13:30:07 gibi mnasiadka: thanks, links are working now. I will check the content after my afternoon meetings
14:19:12 spatel sean-k-mooney: morning
14:19:39 spatel I have question about dpdk so thought you will be right person to ask :) let me know if you have time.
15:50:45 artom spatel, he's on PTO today I believe
15:52:20 spatel artom: thanks for reply, no worry.
15:52:49 spatel My question was why CentOS 8.2 remove dpdk support from OpenVSwitch :)
15:53:15 spatel anyway i am re-compiling from source and packaging to see if that works
16:33:46 gibi mnasiadka: I found the root cause of the bug. It is a kombu and amqp package version bump that is not compatible with oslo.messaging. Details are in: https://bugs.launchpad.net/oslo.messaging/+bug/1902696
16:33:46 openstack Launchpad bug 1902696 in oslo.messaging "nova-compute fails with Unhandled error: TypeError: _wrap_socket_sni() got an unexpected keyword argument 'ca_certs'" [Undecided,New]
16:43:55 gibi mnasiadka: pushed a requirement pin to avoid ^^ https://review.opendev.org/#/c/761194/
16:50:47 stephenfin artom, gibi, (others): When listing server tags, what's more intuitive http://paste.openstack.org/show/799661/ ?
16:52:48 gibi stephenfin: openstack server show already makes the second proposal more natural as it is how the output of server show look like in other cases
16:53:02 gibi I mean server show is a big table
16:53:25 stephenfin option (a) is what's proposed at https://review.opendev.org/756019. option (b) mirrors what we do for diagnostics (openstack server show --diagnostics). option (c) simply enhances the existing 'server show' command
16:54:03 gibi wait are there three options?!
16:54:25 stephenfin Yes. I should have delineated that better :-D
16:54:25 gibi /o\
16:54:44 gibi I see now
16:55:20 gibi so I definitely dont like option B) as it changes from the big table outpot of server show to a small specific table
16:55:34 stephenfin Okay, we're on the same page there
16:55:54 stephenfin The only reason I considered it was because we have a '--diagnostics' flag that essentially does that
16:56:07 stephenfin (totally changes the content and meaning of the output based on a single flag)
16:56:10 gibi then I don't like --diagnostics either :D
16:56:15 frickler so why do you need the --tags option at all for c)? can't you just include the tags in the output if the api version supports it?
16:56:31 stephenfin frickler: Quite possibly. It's a second API call though
16:56:40 stephenfin Why, I don't know. Possibly change for a future microversion
16:56:46 frickler oh
16:56:48 stephenfin *possible
16:57:53 mnasiadka gibi: thanks!
16:58:00 gibi both a) and c) works for me, we can even have both
16:58:10 frickler then a) doesn't sound so bad any longer
16:59:15 stephenfin I'm tempted to go with (c) because we have '--tag' parameters for multiple other commands now
16:59:42 stephenfin i.e. 'openstack server create --tag TAG ...', 'openstack server set --tag TAG ...'
17:00:15 gibi stephenfin: how -c and --tag will interact in the server show case?
17:01:13 stephenfin that's a good point. I suspect we'll have to do something like https://review.opendev.org/741181
17:01:41 stephenfin It all depends on whether we want OSC to exactly mirror the API, or to smooth out some of its wrinkles
17:02:14 frickler mostly the latter I'd say
17:02:25 frickler can "openstack server list" show tags?
17:02:31 stephenfin me too
17:02:38 frickler or only filter on them?
17:02:57 stephenfin only filter afaik (it's done server-side)
17:11:01 frickler hmm, from the api-ref, both list-servers-detailed and show-server-details should contains tags. so no additional api call for c) and no need for an extra "--tags" option IMO
17:11:26 frickler also a good reason to be able to include tags in "server list", too
17:13:17 stephenfin frickler: gdi :D
17:13:41 stephenfin with zero changes on http://paste.openstack.org/show/799663/
17:13:48 stephenfin *OSC master
17:14:13 stephenfin okay, so we need to clean up that output but otherwise no changes necessary. phew
17:15:47 frickler stephenfin: one thing to look at would be how the output is formatted as yaml. there was someone having a hard time fixing the output for multiple addresses. or was it sec gps?
20:19:30 openstackgerrit Lee Yarwood proposed openstack/nova stable/victoria: libvirt: Only ask tpool.Proxy to autowrap vir* classes https://review.opendev.org/761222
20:19:45 openstackgerrit Lee Yarwood proposed openstack/nova stable/ussuri: libvirt: Only ask tpool.Proxy to autowrap vir* classes https://review.opendev.org/761223

Earlier   Later