Earlier  
Posted Nick Remark
#openstack-nova - 2020-09-15
10:13:52 lyarwood bauzas: yup less of a priority with the workaround in Tempest but still a valid Nova bug
10:14:02 bauzas ack, triaged.
10:14:48 lyarwood just cleaning up my untriaged but fix released bugs btw, appears launchpad/gerrit hasn't been keeping up
10:15:35 sean-k-mooney lyarwood: this might be realted to a change that merged recently. i think the if need to be split. it currently prints that message if the device does not exist or if it does not have a mac
10:16:28 sean-k-mooney lyarwood: is it causing the job to fail
10:17:18 sean-k-mooney that would be a yes it is
10:17:20 kashyap lyarwood: No news yet :-( - but I haven't forgotten; Was responding to something more pressing elsewhere
10:17:42 lyarwood sean-k-mooney: yeah AFAICT the instances aren't getting ipv4 dhcp leases and so ssh verification is failing
10:17:50 lyarwood kashyap: ack np just chasing up
10:17:58 kashyap lyarwood: Shortly, I'm going to try this experiment:
10:18:15 lyarwood sean-k-mooney: just finished a tox -e full tempest run on f32 without failures FWIW
10:18:21 sean-k-mooney lyarwood: yep from the cirros console output it has no ipv4 ip just the link local ipv6 one
10:18:41 kashyap lyarwood: (1) Run this vCPU-consuming 'workload' in the guest: `sha256sum /dev/zero | sha256sum /dev/zero`; (2) Attach and detach a device (or a bunch) in a loop
10:18:50 sean-k-mooney lyarwood: there have been issue with load and the dhcp agent in the past so you could be right that that might be the cause
10:20:20 bauzas gibi: I'm tempted to close https://bugs.launchpad.net/nova/+bug/1894966 as invalid since it's a configuration problem, but we could be more preventive on the API side and serve a HTTP40x here
10:20:20 openstack Launchpad bug 1894966 in OpenStack Compute (nova) "Create servergroup failed with unexpected error" [Undecided,New]
10:20:45 bauzas gibi: I feel the schema needs to be improved
10:20:50 bauzas you agree ?
10:21:27 gibi looking
10:22:20 gibi bauzas: agree, we need to add a better validation to the API for that
10:22:26 bauzas weirdo
10:22:36 bauzas the schema already has an enum
10:23:04 bauzas gibi: https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/schemas/server_groups.py#L37
10:23:23 openstackgerrit Lee Yarwood proposed openstack/nova master: Include removal of ephemeral backing files in the image cache manager https://review.opendev.org/689422
10:23:29 bauzas I'm not an API schema specialist, but would it prevent to have the 'policies' field to be an empty list ?
10:23:41 bauzas gmann: ^ (once you're up)
10:25:29 bauzas nevermind, we don't know the release for this bug, asking for it
10:27:05 gibi good point about the release and the api microversion used
10:29:31 bauzas but, the fact is, from v2.1 we ask policies to be set
10:29:43 bauzas and we only extend the enum with later microversions
10:30:37 bauzas so, I feel the schema allows an empty list although the comments say it shouldn't
10:30:52 bauzas I don't have an env started now, but the verification should be quick
10:31:00 gibi let me try
10:31:13 bauzas thanks
10:33:02 openstackgerrit Merged openstack/nova stable/ussuri: tests: Add reproducer for bug #1879878 https://review.opendev.org/751349
10:33:02 openstack bug 1879878 in OpenStack Compute (nova) ussuri "VM become Error after confirming resize with Error info CPUUnpinningInvalid on source node " [Undecided,In progress] https://launchpad.net/bugs/1879878 - Assigned to Stephen Finucane (stephenfinucane)
10:38:53 openstackgerrit Merged openstack/nova stable/ussuri: Add generic reproducer for bug #1879878 https://review.opendev.org/751350
10:38:53 openstack bug 1879878 in OpenStack Compute (nova) ussuri "VM become Error after confirming resize with Error info CPUUnpinningInvalid on source node " [Undecided,In progress] https://launchpad.net/bugs/1879878 - Assigned to Stephen Finucane (stephenfinucane)
10:39:22 stephenfin elod++ Thanks for the reviews :)
10:40:08 elod stephenfin: np :)
10:49:30 gibi bauzas: with microversion 2.1 - 2.63 I can reproduce https://bugs.launchpad.net/nova/+bug/1894966 on master
10:49:30 openstack Launchpad bug 1894966 in OpenStack Compute (nova) "Create servergroup failed with unexpected error" [Undecided,Incomplete]
10:49:47 gibi bauzas: 2.64 changed the API in a way that this problem cannot happen any more
10:50:02 gibi so this is a low prio bug to fix the validation of an old microversion
10:50:13 gibi at least for me
10:56:09 kashyap gibi: Hey, a random non-Nova thing :-) -- on online conferencing, I've heard really good things on this FOSS tool: 'BigBlueButton' - from the recently concluded Linux Plumbers (I didn't attend it)
10:56:19 kashyap gibi: But here's some notes from the co-organizer: https://lwn.net/Articles/817146/
10:56:31 kashyap [quote]
10:56:33 kashyap To summarize, while both Jitsi and BigBlueButton are capable video-conferencing systems, BigBlueButton appears to be a more solid and feature-complete offering. In particular, the administration features and shared whiteboard capability stand out. The free-software community often struggles to create top-quality graphical applications; here we have (at least) two of them. It would appear that
10:56:39 kashyap there is no real need to be using proprietary solutions in this area.
10:56:41 kashyap [/quote]
10:57:44 gibi kashyap: hi!
10:58:23 gibi kashyap: never heard of BigBlueButton. We tried Jitsi in the last PTG and it was good except for PRC users
10:58:27 kashyap (Although, the above is suitable for smaller, developer events, rather than big, "red carpet public conferences")
10:59:22 kashyap gibi: I see; yeah, I haven't heard of BigBlueButton either, but I just heard several good reviews about from a few Linux developers :D
11:00:41 gibi kashyap: opendev provides a jitsi service so if you are interested in bbb then the next step would be get a bbb service up somewhere (maybe in infra) and try it out
11:01:02 bauzas gibi: ack thanks
11:01:30 kashyap gibi: Ah, I didn't know that OpenDev++ provides Jitsi. Cool
11:01:46 gibi kashyap: https://meetpad.opendev.org/
11:02:44 gibi bauzas: enjoy
11:03:31 bauzas gibi: which cyclist wanna me to support ?
11:03:38 bauzas ;)
11:03:43 bauzas anyway, me goes off
11:04:07 gibi bauzas: I have no idea. I did not follow cycling sport
11:23:15 sean-k-mooney if ye want to try BigBlueBotton i can proably deploy a copy on my home cloud for ye to play around with or give ye access to it so ye can
11:23:17 sean-k-mooney https://docs.bigbluebutton.org/2.2/install.html
11:23:23 sean-k-mooney it does not seeam that invovled
11:23:50 sean-k-mooney they also have a test sight
11:23:52 sean-k-mooney https://test.bigbluebutton.org/
11:23:58 sean-k-mooney *site
11:37:20 kashyap sean-k-mooney: Cool
11:38:55 openstackgerrit Balazs Gibizer proposed openstack/nova master: Use absolute path during qemu img rebase https://review.opendev.org/739246
11:39:10 sean-k-mooney i think that prc contibutors will have the same issue with jisi or bbb
11:39:46 sean-k-mooney its a firewall issue e.g. the servers wehre its hosted are blocked by the china goverment firewall
11:40:28 sean-k-mooney so if infra ended up hosting bbb as well i doubt it would help
11:42:48 gibi sean-k-mooney: I agree ^^ we switched to zoom as it seems to be allowed in PRC
12:04:22 gibi it seems that the gate is broken due to mirror issue: 'No matching distribution found for python-designateclient===4.1.0'
12:20:47 openstackgerrit Balazs Gibizer proposed openstack/nova master: Ignore HW_CPU_HYPERTHREADING trait in named groups https://review.opendev.org/735947
12:22:57 sean-k-mooney gibi: interesting
12:23:08 sean-k-mooney should we ignore or raise an error
12:23:29 sean-k-mooney i think the flavor validation code should raise an error no?
12:23:40 gibi I can change that to an error
12:24:08 gibi I choose to ignore as alex_xu said that we will never use that trait in a named group
12:24:09 sean-k-mooney im kind of ok ignoring but when creating or updating a flavor i think the validation code should make it an error
12:24:15 sean-k-mooney so ignore where your currently ignoring
12:24:16 gibi and it made the code a lot simpler
12:24:39 sean-k-mooney well we might
12:24:53 sean-k-mooney but we dont right now
12:25:39 sean-k-mooney so the reason that HW_CPU_HYPERTHREADING was originally not ment ot be set by the virt driver
12:25:52 sean-k-mooney was if we have numa in placment you might want to treat each numa node differently
12:26:29 sean-k-mooney but when stephenfin implemented the pcpus in placment feature we chose to allow the virt driver to report it
12:26:41 sean-k-mooney whihc broke tha tuse case
12:26:52 sean-k-mooney so right now we wont use it in a named group
12:27:30 sean-k-mooney the intent was to allow the isolate policy to work by only whitelisting half the treads on the scond numa node
12:27:55 sean-k-mooney instead of having to partion you cloud into servers with hypertreading enabled and servers with it disabled
12:28:25 sean-k-mooney as i said we decided to drop that usecase
12:29:59 gibi OK. I will try to add a case to the extra_spec validation
12:30:10 gibi to reject this trait in a named group
13:03:25 openstackgerrit Lee Yarwood proposed openstack/nova master: libvirt: Don't age swap files in the image cache https://review.opendev.org/641093
13:30:00 openstackgerrit Balazs Gibizer proposed openstack/nova master: Reject HW_CPU_HYPERTHREADING trait in named groups https://review.opendev.org/735947

Earlier   Later