Thursday, 2023-05-11

*** dmellado9 is now known as dmellado05:04
opendevreviewSoniya Murlidhar Vyas proposed openstack/tempest master: Enable new servies in tempest.conf  https://review.opendev.org/c/openstack/tempest/+/88291506:15
opendevreviewSoniya Murlidhar Vyas proposed openstack/tempest master: Enable new servies in tempest.conf  https://review.opendev.org/c/openstack/tempest/+/88291506:25
opendevreviewSoniya Murlidhar Vyas proposed openstack/tempest master: Enable new servies in tempest.conf  https://review.opendev.org/c/openstack/tempest/+/88291509:16
kopecmartingmann: hi, any chance we could make tempest create VMs on specific node?12:55
opendevreviewribaudr proposed openstack/tempest master: [WIP] Test tempest for Nova and Manila  https://review.opendev.org/c/openstack/tempest/+/83874313:58
*** spotz is now known as Guest113314:06
*** spotz_ is now known as spotz14:06
opendevreviewzoumingzhe proposed openstack/hacking master: handle from-style in hacking_import_alphabetical  https://review.opendev.org/c/openstack/hacking/+/88299016:18
opendevreviewzoumingzhe proposed openstack/hacking master: handle from-style in hacking_import_alphabetical  https://review.opendev.org/c/openstack/hacking/+/88299016:49
gmannkopecmartin: you mean on specific compute node?16:54
gmannkopecmartin: hen yes, you can do via scheduler hint and if you want guaranteed booting then use force-host in create server requsest 16:54
opendevreviewzoumingzhe proposed openstack/hacking master: handle from-style fro H306  https://review.opendev.org/c/openstack/hacking/+/88299017:00
opendevreviewzoumingzhe proposed openstack/hacking master: handle from-style for H306  https://review.opendev.org/c/openstack/hacking/+/88299017:02
opendevreviewzoumingzhe proposed openstack/hacking master: handle from-style for H306  https://review.opendev.org/c/openstack/hacking/+/88299017:12
dansmithgmann: kopecmartin: would be good to get this in to validate the CVE if you have time: https://review.opendev.org/c/openstack/tempest/+/88287617:27
gmanndansmith: sure17:28
dansmithgmann: note that this will fail on clouds that don't have the fix17:29
dansmithI dunno how you reconcile that with like stable interfaces and stuff, but it seems more valuable to have the indication than not17:29
gmanndansmith: as long as it is green on all supported branches as fixes are backported and  are proposed/merging, tempest is good. we have older version of tempest for EM or old branches17:30
dansmithcool17:31
gmannyeah, as know this case and we have to introduce some back incompatible things which is nothing but better for users than think of breaking them17:31
dansmithyep17:31
gmannI have a quick internal call and after that will review tempest change17:32
dansmithgmann: no problem thanks17:32
opendevreviewAshley Rodriguez proposed openstack/devstack-plugin-ceph master: [WIP][DNM] Remote Ceph with cephadm  https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/87674717:36
dansmithgmann: (or maybe sean-k-mooney) do you recognize the first failure here? https://17bb12c4d334815c4390-11a2e186f8f6505f790122d590a395c2.ssl.cf2.rackcdn.com/882955/2/check/cinder-plugin-ceph-tempest-mn-aa/f9c0ed1/testr_results.html18:17
dansmithkinda looks like the job is configured to try something that assumes non-shared storage?18:18
sean-k-mooneyhum 18:22
sean-k-mooneywell that message implies the test pass block-migration=true with the old microverion right18:22
sean-k-mooneysince that parematner is now auto and noone should normally pass it anymore18:22
sean-k-mooneyi wonder why that is happening18:22
dansmithright that's why I'm wondering if that should ever work in this job configuration18:23
sean-k-mooneyi think there is a tempest config option for this18:23
dansmithit's marked n-v so it's possible it just never worked18:23
sean-k-mooneydo you have a link to the zuul job18:23
sean-k-mooneyi just eant to look at the jobs cofnig18:24
dansmithhttps://review.opendev.org/88295518:24
sean-k-mooneythanks18:24
dansmithit's about to report18:24
sean-k-mooneyso there is this https://github.com/openstack/tempest/blob/master/tempest/config.py#L493C36-L49618:25
sean-k-mooney'block_migration_for_live_migration'18:25
sean-k-mooneythat should be false18:25
dansmithI wonder if this is related: https://github.com/openstack/cinder/blob/master/playbooks/cinder-multibackend-matrix.yaml#L1418:27
dansmithblock_migration_for_live_migration = True18:28
dansmithit's getting set18:28
sean-k-mooney i dont think so18:28
sean-k-mooneyok form where i was tracking up the job parents18:28
sean-k-mooneyi dont see it set as a devstack paramter18:28
dansmithso that should be true when, when we're not on ceph?18:29
dansmith(or nfs or other shared storage for root)18:30
sean-k-mooneymother rang brb18:31
gmannbut this is set to True in this job https://zuul.opendev.org/t/openstack/build/f9c0ed1331854ae1a57c8be97bd18215/log/controller/logs/tempest_conf.txt#8118:35
dansmithgmann: right18:36
dansmithand I'm wondering if it should not be18:36
dansmithbut I also don't know where it's getting set from18:36
gmanndansmith: yeah checking how it is set but if you see nova live migration ceph job it is explicitly set to false https://opendev.org/openstack/nova/src/branch/master/.zuul.yaml#L21818:37
dansmithcool18:38
dansmithso I guess I can just set it false at least and see how that goes18:38
gmanndansmith: from here it is set https://github.com/openstack/tempest/blob/master/zuul.d/base.yaml#L8118:38
dansmithah okay18:39
gmannwe need to make it false explicitly in ceph base multinode job18:39
gmannhere https://opendev.org/openstack/devstack-plugin-ceph/src/branch/master/.zuul.yaml#L12218:39
dansmithokay18:39
gmanndansmith: but was it working in this? https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/88248318:40
dansmithgmann: they don't even run that job in their config18:40
dansmithgmann: and the only one that I knew about was nova's live migration ceph job18:40
gmannohk18:41
gmannah right, just saw18:42
dansmithI'll just add it to that patch and depends-on that18:42
opendevreviewDan Smith proposed openstack/devstack-plugin-ceph master: Make multinode ceph job use cephadm  https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/88248318:43
dansmithoh wait, I can't do that because it doesn't work for multinode yet18:44
gmannmay be separate change18:46
dansmithyup18:46
dansmithalso need to enable validations on that base job anyway18:46
opendevreviewDan Smith proposed openstack/devstack-plugin-ceph master: WIP Make multinode ceph job use cephadm  https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/88248318:47
opendevreviewDan Smith proposed openstack/devstack-plugin-ceph master: Enable validation and disable block-migration  https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/88298718:47
dansmithgmann: not sure if you saw my note in nova this morning, but this cinder job is the only one I still see throwing volume detach failures (that aren't caused by other things)18:48
dansmithnot critical to fix, but it seems to be failing a *lot* and if it has config that means it never passes.. probably not very useful :)18:48
dansmithfailing with volume detach a lot I mean18:48
sean-k-mooneyok back18:48
sean-k-mooneyblock_migration_for_live_migration = True18:49
sean-k-mooneyshould only  really be set if you are trying to test old migrovition i think18:49
dansmithokay it's on by default in the devstack-multinode job18:50
sean-k-mooneyand where the job does not have ceph or nfs18:50
sean-k-mooneywell the default behavior since like 6+ years i think has been auto18:50
gmanndansmith: ohk18:50
sean-k-mooneyhttps://docs.openstack.org/nova/latest/reference/api-microversion-history.html#id1218:50
sean-k-mooney2.1418:51
sean-k-mooneyso form mitaka nova will fiture it out and do the right thing18:51
sean-k-mooneyso tempest proably should just remove that config option at this point18:51
sean-k-mooneyactully 2.25 was for live migration18:52
sean-k-mooneystill mitaka https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#maximum-in-mitaka18:52
sean-k-mooney2.14 was for evacuation18:52
gmannyeah but it is still supported for older mivroversion so keeping in tempest is ok18:52
sean-k-mooneyit should not be on by default18:53
sean-k-mooneyonly in a job tha tis not usign ceph and does not have nova /var/lib/nova/instance on nfs18:53
sean-k-mooneygmann: im wondiring is thre a way to not pass any value in tempets or pass auto18:55
dansmithsean-k-mooney: that's the job it's default on in,18:55
gmannyeah18:55
dansmithit's just we need to flip it off on the job that implements ceph18:55
dansmithwhich I'm doing18:55
gmannyes, like nova did for ceph job18:55
dansmithright18:55
dansmithnova's job should also get it from the flag I'm setting in devstack-ceph-plugin eventually18:56
sean-k-mooneysure im just concend that tempest might not be testign the default behavior that we have for new microveion which is what we expect people to actully use18:56
gmannyeah that will be good for all ceph job hoping they inherit from ceph plugin jobs18:56
sean-k-mooneylike https://github.com/openstack/tempest/blob/e5da6756b9e7fb8fbedade5d3a428e0a8bff94ff/tempest/api/compute/admin/test_live_migration_negative.py#L36-L3718:56
sean-k-mooneyis always setting true or false18:56
gmannsean-k-mooney: we do https://github.com/openstack/tempest/blob/master/tempest/api/compute/admin/test_live_migration.py#L37718:57
sean-k-mooneyok cool18:57
gmannmicroversion specific test are with microversion caps so that it does not fail for older version. 18:58
gmannand we keep testing older behavior also with existing tests18:58
sean-k-mooneyim not going to hold my breat to get my wish to bumnp the min microversion nova supports anytime soon18:59
gmann:)18:59
dansmithgood :)18:59
sean-k-mooneybut i would deally like to bump it to 2.6019:00
sean-k-mooneyhttps://docs.openstack.org/nova/latest/reference/api-microversion-history.html#maximum-in-queens19:00
gmanndansmith: reviewed CVE fix tests. can we move those to scenario test as they are good tests to validate the cross services things ?19:41
dansmithgmann: reading now19:41
gmannsome doc string comment, and what you think of this test https://review.opendev.org/c/openstack/tempest/+/882876/2/tempest/api/volume/test_volumes_negative.py#55319:41
gmannk19:41
dansmithgmann: I don't actually know what the distinction is supposed to be.. scenario are just "full stack" sorts of things?19:41
dansmithin this case, these tests are *only* testing the cinder change, not the nova one and not the brick/glance ones either19:42
gmanndansmith: our negative tests are mainly API interface validation tests and less of cross service operation  validation19:42
dansmithso it seems pretty specific to cinder19:42
dansmiththis is pretty much just cinder api behavior, so seems probably correct for api negative to me19:43
gmannbut it involve the nova service if attachment is there or not righ19:43
dansmithit requires attaching to an instance yes, but it could be nova from zed and it'd still work19:43
dansmithbut if that's enough to move to scenario, that's fine19:43
gmannI feel cinder talk to nova for these operation and test the cross service things. so putting these in scneario can be good place19:44
dansmithokay, sure19:44
gmannour negative tests are more like just a very upper level interface/DB validation which is almost done by service side unit tests but we kept them due to interop using them19:45
dansmithwell, this is kinda that, but since it checks with nova to determine if it should enforce it, it's a little blurred I agree19:45
gmannI do not want these good test falling in those catagory and someday we just delete all negative tests make these tests also go19:45
dansmithack19:45
dansmithgmann: okay can I make the changes you describe and do the reno and work on the additional (good) test case in a follow-on patch?19:46
gmannreno and additional test is all good to do in followup but you mean moving them to scneario test too?19:47
dansmithno, I'll do the move to scenario, the reno, and the fixes now19:48
dansmithjust save the new case for follow-on19:48
gmannsure, make sense19:48
dansmithso new file in tempest/scenario or is there one in there that could take these?19:49
dansmithvolume_boot_scenario is not quite right19:49
gmannyeah,  may be new file, I also could not find relevant file 19:50
dansmithokay19:51
dansmithgmann: I assume you want these separate test cases folded into a more scenario-like single test that boots one server and tries a bunch of things against it right?19:58
opendevreviewAshley Rodriguez proposed openstack/devstack-plugin-ceph master: [WIP][DNM] Remote Ceph with cephadm  https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/87674720:13
gmanndansmith: yeah that will be much better20:19
dansmithgmann: ack, I gotta restack so it'll probably be monday before I get going on this much20:19
gmannack20:19
dansmithgmann: I also noticed none of these wait for sshable so they needed work there as well20:19
dansmithsort of showed up in parallel so I wasn't thinking about that20:19
dansmith(and I didn't write them)20:20
gmannyeah20:20
dansmiththat fixed the cinder ceph multinode test, except for the second failure which is also what seems like a job misconfiguration related to volume retype20:33
dansmithbut, progress at least20:33

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