Wednesday, 2023-06-28

opendevreviewGhanshyam proposed openstack/tempest master: Test Nova and Glance RBAC policy old defaults  https://review.opendev.org/c/openstack/tempest/+/88476403:32
opendevreviewGhanshyam proposed openstack/tempest master: Make glance-multistore-cinder-import voting  https://review.opendev.org/c/openstack/tempest/+/88581003:32
kopecmartinfrickler: hmm, i see also 4 non devstack patches there - https://review.opendev.org/q/topic:drop-old-distros06:16
fricklerkopecmartin: now I see those, too. maybe gerrit was slow with updating caches or so after you changed the topics yesterday06:18
slaweqfrickler hi, quick question - can You +W https://review.opendev.org/c/openstack/devstack/+/882770 now as yoga patch was merged already? Thx in advance08:51
whoami-rajatdamiandabrowski, no problem, thanks for the fixes08:55
fricklerslaweq: done09:22
slaweqThx09:23
opendevreviewMerged openstack/devstack stable/xena: Fix installation of OVS/OVN from sources  https://review.opendev.org/c/openstack/devstack/+/88277010:48
opendevreviewMaxim Sava proposed openstack/tempest master: Add image admin test to list public image  https://review.opendev.org/c/openstack/tempest/+/88634012:18
opendevreviewMaxim Sava proposed openstack/tempest master: Add image admin test to list public image  https://review.opendev.org/c/openstack/tempest/+/88634012:19
melwittdoes anyone know if there is anything in flight for addressing job timeouts? I feel like I'm getting a timeout every run ... should we consider increasing some of the timeouts or?17:32
gmannmelwitt: I am also seeing that since last week, nothing up for fix as we do not knwo the reason why it started now17:43
gmannsome job like tempest-slow are already at max time which i think needs to split the test but for other jobs its something else slow as they do not have large number of tests17:43
gmannand we already refactored tempest-full and few more job in last month or so17:44
melwittgmann: ack, thanks. weirdly one I'm seeing a lot is tempest-integrated-compute17:46
gmannhumm17:46
melwittbut I see some pretty long test times there like17:47
melwitt2023-06-28 17:14:13.107467 | controller | {0} tempest.scenario.test_security_groups_basic_ops.TestSecurityGroupsBasicOps.test_cross_tenant_traffic [187.746724s] ... ok17:47
melwitt2023-06-28 17:16:36.239756 | controller | {0} tempest.scenario.test_security_groups_basic_ops.TestSecurityGroupsBasicOps.test_in_tenant_traffic [143.121620s] ... ok17:47
melwittaside, I think it would be nice to have stestr output the names of the N slowest tests after the result to make it easier to look at the slowest ones. if I can figure out where to do that I will propose a patch17:48
gmannI think those are ok, actual issue is all three worker are ideal and 4th one got all the remaining test execution so timeout 17:50
gmannhttps://ca38b56652cffb3b5e17-289b34983b13ece36a1a19c591f4d0ce.ssl.cf5.rackcdn.com/877056/5/check/tempest-integrated-compute/87764a4/controller/logs/stackviz/index.html#/stdin/timeline?test=tempest.api.compute.servers.test_server_rescue.ServerStableDeviceRescueTest.test_stable_device_rescue_disk_scsi17:50
gmannwe have seen these before also when dansmith reported unbalancing of test run on all workers17:50
gmannnot sure how to solve this. one way is group the tests but that can make situation worst in many cases17:51
gmannmelwitt: +1 that will be good data.17:58
gmannand in this timeout, we can see worker3 is taking another 30 min when all other worker are idea https://zuul.opendev.org/t/openstack/build/87764a41607b420297f35d4e13a2b4d9/log/job-output.txt#21053-2105817:58
gmannthis is success case with distributed load on all worker https://zuul.opendev.org/t/openstack/build/fc83c60a34504c8da3dab0bd1fef83c3/log/job-output.txt#21002-2100717:58
melwittgmann: oh, nice insight. I didn't even notice that17:59
melwittI'll probably poke at it a bit to see if I get any ideas17:59
gmannone idea i see to increase the concurrency in tempest run if we have any node with more than 4 cpu will utilize all cpu to run test18:00
melwittgmann: ah yeah.. by default stestr uses concurrency based on how many cpus detected but I guess we must be setting it to 4 always18:18
opendevreviewGhanshyam proposed openstack/tempest master: Increase concurrency for tempest-slow jobs  https://review.opendev.org/c/openstack/tempest/+/88721818:22
gmannmelwitt: ^^ one is this we set as two on slow job and that might be cause for long time in this job18:23
gmannbut rest other I think we are letting stestr only to decide but checking if we are restricting it to 4 somewhere18:23
melwittI feel like i saw something recently /me looks18:24
melwittnot sure what I was thinking of, but while looking I found this https://opendev.org/openstack/tempest/src/branch/master/roles/run-tempest/tasks/main.yaml#L1818:30
melwittI dunno whether that connects to stestr somehow18:31
melwittoh yeah, derp https://opendev.org/openstack/tempest/src/branch/master/roles/run-tempest/tasks/main.yaml#L12618:31
opendevreviewDan Smith proposed openstack/devstack master: nova: Bump timeout-per-gb for BFV rebuild ops  https://review.opendev.org/c/openstack/devstack/+/88711018:32
melwittiiuc that is setting concurrency to be number of cpus // 218:32
* dansmith is not very smart18:32
gmannmelwitt: yeah, I am looking the same. it make 8 cores to 4 here18:32
gmannlet me remove this logic and not set concurrency as default_concurrency18:33
melwitt++18:33
gmannand this confirm 4 passed to tempest run and to stestr https://zuul.opendev.org/t/openstack/build/fc83c60a34504c8da3dab0bd1fef83c3/log/job-output.txt#2100818:34
melwittyeah, I def saw that early on but didn't know where it was coming from until now18:34
melwittaside, looks like mtreinish had worked on dynamic worker balance in the past https://github.com/mtreinish/stestr/pull/271 but still WIP18:38
melwittI was thinking that's what we need and then wondered if anyone proposed it yet, and the answer is yes :)18:39
opendevreviewGhanshyam proposed openstack/tempest master: Do not set the concurrency for tempest run  https://review.opendev.org/c/openstack/tempest/+/88722018:41
gmannmelwitt: ah right, that will be good way18:42
dansmithdynamic balance would be hella better18:52
gmannyeah18:54
opendevreviewGhanshyam proposed openstack/tempest master: Do not set the concurrency for tempest run  https://review.opendev.org/c/openstack/tempest/+/88722019:43
opendevreviewDan Smith proposed openstack/devstack master: nova: Bump timeout-per-gb for BFV rebuild ops  https://review.opendev.org/c/openstack/devstack/+/88711021:13
opendevreviewGhanshyam proposed openstack/tempest master: Do not set the concurrency for tempest run  https://review.opendev.org/c/openstack/tempest/+/88722021:17
opendevreviewGhanshyam proposed openstack/tempest master: Run slow tests parallely  https://review.opendev.org/c/openstack/tempest/+/88723723:52
gmanntempest-slow job run test serially so no impact of increasing the concurrency. I think running parallel is not causing much issue, let's try that in main job too23:53
opendevreviewGhanshyam proposed openstack/tempest master: Run slow tests parallely  https://review.opendev.org/c/openstack/tempest/+/88723723:56

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