Thursday, 2024-04-25

songwenpingsean-k-mooney: hi, is there concurrency case in tempest?09:10
sean-k-mooneysongwenping: can you be more specific? tempest can run with multiple test in parallel10:20
sean-k-mooneysimondodsley: im not entirly sure why the cinder driver woudl need the compute node uuid. we dont use that as a value we exchange between services. we use the CONF.host value which is typically the hostname but can be the fqdn10:22
sean-k-mooneyanyway to fid it you can use https://docs.openstack.org/api-ref/compute/#list-hypervisors10:23
sean-k-mooneyso /os-hypervisors?hypervisor_hostname_pattern=<host value goes here>10:24
sean-k-mooneyuse microveriosn 2.53 or higher to get teh id filed as a uuid 10:24
sean-k-mooney<2.53 the id filed is a cell speific int so you should avoid that10:25
auniyalsean-k-mooney, how to set min_microversion in temepst, this https://paste.opendev.org/show/bJLSDBLxBgj2hzBcJEiq/ in tempest.conf10:27
auniyalbut I am getting SKIPPED: The microversion range[2.11 - latest] of this test is out of the configuration range[None - None].10:28
auniyalI was refering this - https://docs.openstack.org/tempest/latest/sampleconf.html10:28
sean-k-mooneyauniyal: you set it in teh test class10:49
sean-k-mooneyyou may also be able to do it seperately but most tests seam to do it at the class level10:49
auniyalyeah, in test class min_microversion = '2.11'10:49
sean-k-mooneyyou shoudl not need to chnage the tempest.conf10:50
auniyalI am getting  SKIPPED: The microversion range[2.11 - latest] of this test is out of the configuration range[None - None]10:51
sean-k-mooneysure but devstack will produce a valid tempst conf for you10:51
*** srelf_ is now known as ContinuitySR10:51
sean-k-mooneyand you should never realy need to change the values for the micorverion range in general10:51
auniyalack, so change rearding microverion in tempest conf10:52
auniyal*no change10:52
sean-k-mooneywhat you have in the pastbin shoudl work10:52
auniyalsean-k-mooney, how can I fix skipping test then10:52
sean-k-mooneybut my guess is that is nto the actul issue10:52
sean-k-mooneycan you should be the test10:53
auniyalhttps://paste.opendev.org/show/bZgalcGsTREjXm08RT34/10:53
sean-k-mooneyhttps://github.com/openstack/tempest/blob/1c3fc43c9dae274a19683b003f78b5f50edbc062/doc/source/microversion_testing.rst that is the docs on adding microversion test by the way10:54
sean-k-mooneyit looks like you might be missing the resocue_setup funciton un less you are gettign that form the ineritied test10:55
sean-k-mooneyits not provided directly by the parent class https://opendev.org/openstack/whitebox-tempest-plugin/src/branch/master/whitebox_tempest_plugin/api/compute/base.py#L3810:56
sean-k-mooneyso we need to check BaseV2ComputeAdminTest10:56
sean-k-mooneyok it should get it form here https://github.com/openstack/tempest/blob/1c3fc43c9dae274a19683b003f78b5f50edbc062/tempest/api/compute/base.py#L12310:57
auniyalCONF.compute.min_microversion - so None10:58
sean-k-mooneyfrom what i can see you have done it correctly10:58
sean-k-mooneyauniyal: its proably best to ask about this isn the QA channel by the way10:59
auniyalsean-k-mooney, ack10:59
sean-k-mooneythat is where we gernerally discuss tempest/whitebox thigns10:59
auniyalthanks for looking10:59
sean-k-mooneythere are more people that understand it better there10:59
songwenping_sean-k-mooney: use mutli threads to process the same resource. e.g. create a flavor use the same name with two thread, one thread should raise FlavorExists exception.11:22
sean-k-mooneysongwenping_: we generally dont do that in tempest, if we need to create a flavor we either generat a randome name or a uique oen for a given test11:35
sean-k-mooneyso that shoudl either never happen or test that share names need to have the @serial decorator applied11:36
songwenping_thanks, got it.11:37
sean-k-mooneysongwenping_: we do not split singlel testcase between workers by the way so each test runs in a singel threadn adn we distribute tests between threads12:11
opendevreviewFabian Wiesel proposed openstack/nova master: Do not close returned image-chunk iterator & get_verifier early  https://review.opendev.org/c/openstack/nova/+/90947412:39
simondodsleysean-k-mooney: the `CONF.host` doesn't gaurantee a unique name when taken in the context of a storage platform that can be used by systems other than OpenStack. It is possible that hosts in an organization coul dhave the same name, but with different storage prototocls, different IQNs, etc. This is why the compute node UUID would be ideal to use as this should be unique. Is there any chance this could be added to `CONF`?22:14

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