Thursday, 2021-10-21

*** masayukig_ is now known as masayukig01:10
*** pojadhav is now known as pojadhav|ruck04:57
*** jpena|off is now known as jpena06:53
*** bhagyashris_ is now known as bhagyashris07:46
yoctozeptofrickler: :-)08:43
frickleryoctozepto: same thing for cs8. they have 15:5.2.0-16.el8 from whatever source devstack installs there by default08:43
yoctozeptooh, nice, so they have upgraded too08:43
yoctozeptopossibly why the job became flaky08:44
yoctozeptothanks for confirming :-)08:44
frickleryoctozepto: thanks for the idea, now we can tell rh folk to fix it instead of having to deal with qemu ourselves ;)09:15
opendevreviewDr. Jens Harbott proposed openstack/devstack master: DNM: Test debian with OVN  https://review.opendev.org/c/openstack/devstack/+/81489110:08
*** dviroel|rover|out is now known as dviroel|rover10:51
*** jpena is now known as jpena|lunch11:29
opendevreviewDr. Jens Harbott proposed openstack/devstack master: DNM: Test debian with OVN  https://review.opendev.org/c/openstack/devstack/+/81489111:36
opendevreviewLajos Katona proposed openstack/tempest master: Scenario test for routed provider networks  https://review.opendev.org/c/openstack/tempest/+/66515512:00
yoctozeptofrickler: :-)))12:13
*** jpena|lunch is now known as jpena12:22
*** pojadhav is now known as pojadhav|ruck12:33
*** redrobot is now known as Guest365612:59
opendevreviewJames Parker proposed openstack/whitebox-tempest-plugin master: Update cpu model for deployment  https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/81491413:15
opendevreviewLajos Katona proposed openstack/tempest master: Scenario test for routed provider networks  https://review.opendev.org/c/openstack/tempest/+/66515513:58
yoctozeptofrickler: wunderbar, ovn works in devstack :-)14:03
yoctozeptotesting also in kolla14:04
yoctozepto(I mean Debian ovn)14:04
yoctozeptozigo: ^14:04
zigoyoctozepto: Ah, great ! :)15:17
opendevreviewClark Boylan proposed openstack/devstack master: Use Nehalem CPU model by default  https://review.opendev.org/c/openstack/devstack/+/81502015:19
yoctozeptozigo: it works in kolla too15:31
yoctozeptozigo: and even better news - Debian will be an official tested platform in Yoga15:32
zigo:)15:42
zigoyoctozepto: Wonderful !15:42
*** jpena is now known as jpena|off15:52
johnsomgmann We have an interesting situation I would like you advice on around the system_admin credential. refstack is having a job fail due to system_admin being missing: https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_eaf/809450/10/check/interop-next-refstack-client-wallaby/eaf8996/job-output.txt16:16
johnsomI see they have a accounts override file. My first thought is that just needs to be updated, but I am also hearing that they use an older tempest version pinned.16:17
johnsomShould we be putting conditionals around all of our "credentials = ["admin", "system_admin", "primary"]" lines too? Or is it really that everyone with "use_dynamic_credentials = False" will need to update their files?16:19
*** bhagyashris_ is now known as bhagyashris16:27
gmannjohnsom: it is not yet implemented in pre-provisioned account yet ("use_dynamic_credentials = False") . 17:10
gmannjohnsom: I think we can out a assert/log in tempest/test.py or in pre-provisioned account saying it is not supported yet17:11
johnsomgmann So your advice is to put conditionals around all of the "credentials =" in the test classes?17:11
gmannjohnsom: no17:11
gmannjohnsom: i was thinking to put a generic condition check and either 1. fail if test need system scoped and env using "use_dynamic_credentials = False" or 2. if "use_dynamic_credentials = False" fallback system admin to project admin17:12
gmann2nd might not work or confusing when debugging the failure17:13
johnsomIt's breaking refstack, so option 1 probably is not good17:13
gmannhumm17:13
johnsomThe tests themselves all use a conditional, it's just the base credential setup that bombs out.17:14
gmannyeah, we can just skip the creating the system scoped token if enforce_scope if false but for that we need a global enforce_scope_ config along with service wise17:15
gmannwhich is what we agreed to do in devstack so not bad17:15
opendevreviewLajos Katona proposed openstack/tempest master: Scenario test for routed provider networks  https://review.opendev.org/c/openstack/tempest/+/66515517:17
johnsomI'm going to propose a patch for designate to extend the service level config check to the credential creation. Feel free to comment, etc. Then if that is the right path I will update Octavia was well.17:18
johnsomThanks!17:19
gmannjohnsom: that will be needed in every tests. let me push something in tempest as generically if that works fine ?17:19
johnsomOk17:19
johnsomPing me and I will do a designate patch to test it.17:20
gmannk17:26
gmannjohnsom: there are two issue here18:24
gmannjohnsom: for this failure https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_eaf/809450/10/check/interop-next-refstack-client-wallaby/eaf8996/job-output.txt18:24
gmannit seems old tempest with master designate is used in the job?18:24
gmann*designate-tempest-plugin18:24
opendevreviewGhanshyam proposed openstack/tempest master: DNM: Test if system creds request pass if enforce scope is disabled  https://review.opendev.org/c/openstack/tempest/+/81504818:28
gmannjohnsom: 2nd problem of 'if enforce scope if false then requested system creds fail or skipped?' I am going to test ^^ 81504818:29
gmannjohnsom: for refstack problem you are encountering , compatible tempest and designate-tempest-plugin versions needs to be used. 18:30
johnsomgmann That is a refstack job that I am not super familiar with, but I think they said they use a pinned tempest. Not sure.18:45
gmannkopecmartin: do you know if refstack or ansible-role-refstack-client use master Tempest? because it is attribute error which does not exist in old tempest (<26.1.0) and exist in new one18:45
gmannjohnsom: yeah, I am trying to debug it in devstack logs of that job but tempest is disabled there and some other way is it is installed not via devstack18:45
johnsomOur main jobs in designate still run with enforce scope disabled just fine.18:46
gmannbut only way it is failing there is if tempest <26.1.0 is used with master designate-tempest-plugin18:46
johnsomI wonder why refstack would have it pinned.....18:46
gmannjohnsom: yeah, dynamic creds are good and I am going to verify the pre-provisioned creds also in 815048 if we need some condition there if enforce_scope disable18:47
johnsomack18:48
gmannlet's wait for kopecmartin on why tempest is pinned or how it is installed there. 18:48
kopecmartingmann: 2 year old tempest is used in refstack-cient - https://opendev.org/openinfra/refstack-client/src/branch/master/setup_env#L418:51
gmannwow18:51
kopecmartinhistoric reasons, we slowly update that whenever we need newer changes 18:51
kopecmartinwe can definitely try to bump tempest version higher18:51
gmannkopecmartin: but main issue is  *-tempest-plugins are used from master which is never going to be compatible18:52
kopecmartinyeah, true, it was working till now, so I didn't want to pin in it it wasn't necessary 18:52
gmannkopecmartin: whatever tempest it use same compatible *-tempest-plugins it needs to use otherwise we will see similar issue18:52
gmannkopecmartin: yeah, just by luck :)18:52
kopecmartinwell :) 18:53
kopecmartini tried to pin designate-tempest-plugin - https://review.opendev.org/c/openinfra/ansible-role-refstack-client/+/815030 .. i hit compact error again 18:54
kopecmartini though i fixed that already18:54
kopecmartin*compat18:54
gmannkopecmartin:  in destack stable/stein it is fixed https://review.opendev.org/c/openstack/devstack/+/81209218:56
gmannjohnsom: kopecmartin right way is to pin all the tempest-plugins in refstack with the compatible tempest it use.18:56
johnsomWith the services starting to test the secure RBAC stuff, it might be a good time to bump the pin18:56
gmannjohnsom: yeah, it was attribute error so easily located otherwise it might become hard to debug 18:57
gmannand I will continue the pre-provisioned creds condition tomorrow or next week based on 815048  result18:58
johnsomOk19:00
redrobotHi QA friends!19:18
redrobotI have a question about how y'all handle Tempest stuff on stable branches.19:18
redrobotWe landed some fixes on master that I need to backport.  It's a chain of 3 patches that fix a bug, but I can't land the first one because the gate is failing on stable/xena19:19
redrobotlooks like the tempest test being run are from master, which is kind of expected since we don't branch our tempest plugin19:20
redrobotNot sure if I need to squash all patches into one, or disable the gate job temporarily while I land all three patches and then re-enable it19:20
clarkbredrobot: how did you land them on master?19:22
gmannredrobot: that is main reason of using tempest/plugins master on stable19:22
gmannit should run/pass as it was in master19:22
gmannredrobot: if test are modified in master ( hoping in backward compatible change modification) and gate is passing then it should pass  in stable branch(using master tempest) also19:23
redrobotso, we landed the patches in Barbican proper, then added the tests to barbican-tempest-plugin19:26
gmannredrobot: or if it is depends on backport to pass test then we go like this process -  https://docs.openstack.org/tempest/latest/HACKING.html#bug-fix-on-core-project-needing-tempest-changes19:26
gmannok19:26
redrobotit was a chain of 3 patches, then a Depends-On: patch for the plugin19:26
gmannredrobot: i see, in that case you can skip the tests and enable it again during backports. 19:27
redrobotgmann, ack, that makes sense.  I wish I'd seen that HACKING note before I got into this mess, lol19:27
gmannit could be added with feature flag though like what we do in tempest https://docs.openstack.org/tempest/latest/HACKING.html#new-tests-for-new-features19:28
gmannredrobot: we tried to document such info of getting it done in branchless nature in HACKING as that is a common things to take care for branchless tests19:29
redrobotI'll have to review that stuff.  Thanks for the help, y'all!19:29
*** dviroel|rover is now known as dviroel|rover|afk21:58
clarkbQA folks review of https://review.opendev.org/c/openstack/devstack/+/815020 would probably start to be good at this point. I haven't been able to find any test failures related to teh chagne yet and this allows centos9-stream/rhel9 to boot on devstack22:17

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