Thursday, 2023-04-20

*** jpena|off is now known as jpena07:23
lajoskatonakopecmartin: Hi, I opened a bug against Neutron/Tempest and Nova: https://bugs.launchpad.net/neutron/+bug/201702307:32
lajoskatonakopecmartin: this is to track the old network APIs in Nova question07:32
lajoskatonakopecmartin: I plan to check the coverage of such tests under tempest/api/compute to compare with tempest/api/network and tempest/scenario07:33
lajoskatonakopecmartin: please check it if you have some free time, and I am happy to join QA meeting or similar if you think it is necessary to discuss and see all aspects of this topic07:34
dansmithwe're good to drop any py38 unit and functional jobs from master now right?14:11
kopecmartinlajoskatona: thanks, i was thinking about that recently, i put it to qa-priority goals so that i find time for that 14:35
kopecmartinlajoskatona: or it's not the same thing as this https://etherpad.opendev.org/p/neutron-tempest-test_duplications14:37
lajoskatonakopecmartin: thanks, on nova channel there was some comments, I add those with links to the lp bug14:37
lajoskatonakopecmartin: no, that is just Neutron tests between tempest and neutron-tempest-plugin14:37
kopecmartinright14:38
opendevreviewIhar Hrachyshka proposed openstack/devstack master: git: support git checkout for a commit hash  https://review.opendev.org/c/openstack/devstack/+/88089215:08
*** jpena is now known as jpena|off16:17
gmannkopecmartin: lajos moving to neutron API is good but nova API should keep working, do you know where they are broken ?16:28
gmanndansmith: yes, py38 is not needed on master. unit test jobs are dropped by common template unless projects explicitly adding them.16:29
dansmithgmann: ack, we still have functional jobs on 38 in glance, some of which are failing now because castellan has required >=3.9 apparently16:30
dansmithso just want to make sure we're good to bump those, but found a patch from rosmaita already proposed so that's cool16:30
dansmithhowever, there are functional fips jobs still pinned to 3.8 apparently, so not sure how we're going to work around those16:30
gmannkopecmartin: lajos, commented on bug to keep those tests https://bugs.launchpad.net/neutron/+bug/201702316:33
gmanndansmith: ok, yeah we need to move those to py39. and slowly projects will be making in their setup.cfg >=3.9 then py3.8 will be not testable also16:34
dansmithyeah, apparently castellan has already done that16:34
clarkbis grenade done running on focal on the old side? (focal is 3.8)16:35
dansmithno, grenade is still on focal AFAIK16:35
gmannI think it is on jammy as 2023.1 was testing jammy as main distro16:38
gmannyes on master grenade (2023.1->master) running on jammy https://github.com/openstack/grenade/blob/d8294440e7dede370b5ee80facf49a511dc7eb09/.zuul.yaml#L16316:39
dansmithis it? I thought it was still focal16:39
gmannskip level is on focal16:39
dansmithah right right, I'm thinking of skip level16:39
gmannoh no, skip level also on jammy and we said let's see how long it is ok on jammy16:40
gmannbecause focal is not supported in master so running on focal is issue16:40
gmannbest chance was trying zed on jammy -> master upgrade16:40
gmann*skip-level-always job 16:41
dansmithmeaning zed->master?16:43
dansmithlocalhost | Label: ubuntu-jammy16:43
gmannyeah16:43
dansmithjammy wasn't official on zed right? maybe we just said "it happens to work on jammy" ?16:44
gmannyeah, that is best bet we discussed 16:44
gmannbecause there are more chance to have master failing on focal than zed on jammy16:45
dansmithyeah okay I guess that's why I thought it was still focal16:45
dansmithbecause yeah: https://governance.openstack.org/tc/reference/runtimes/zed.html16:45
dansmithand I guess grenade was still on focal for 2023.116:45
dansmithso this is the problem for us: https://opendev.org/openstack/openstack-zuul-jobs/src/branch/master/zuul.d/jobs.yaml#L62-L6616:47
gmanndansmith: grenade on stable/2023.1 which does zed->2023.1 is on focal16:47
dansmithfips still runningon focal16:47
dansmithoh, no,16:48
dansmiththere's a jammy above16:48
gmannyeah it is with branch variant 16:48
dansmithright okay lemme try to put up a patch16:48
dansmithrosmaita's patch to glance said we couldn't convert yet, but maybe he was mis-reading that16:48
gmannAFAIK i think ceph job is still running on focal therwise all are on jammy on master16:49
gmannk16:49
dansmithooh16:49
dansmithbecause of the cephadm stuff?16:49
gmannyeah16:49
gmannthis is still failing https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/86531516:50
gmannwhich tried to move to Jammy16:50
dansmithyeah16:51
dansmithgmann: so I don't see a 310-fips job (or 39 for that matter)16:51
dansmithhttps://opendev.org/openstack/openstack-zuul-jobs/src/branch/master/zuul.d/jobs.yaml#L86516:51
clarkbwith fips jammy didn't have the kernel available yet. Focal does but then iscsi uses md5 inappropriately16:51
dansmithah16:52
clarkbI think the idea was to pause fips on ubuntu until jammy got the kernel stuff16:52
dansmiththe above job is centos-based, fwiw16:52
dansmithcentos8 that is16:52
gmannah right. that is also on focal. 16:53
gmannade_lee: might know the plan16:53
ade_leegmann, dansmith yup - the kernel stuff needed for iscsi is in jammy, but fips support is not available for jammy16:56
ade_leeso we can use ubuntu focal or fips only if you don't need iscsi16:57
ade_leelike for ironic perhaps16:57
ade_leejammy fips is supposed to be available sometime next year.16:58
ade_leetill then, we have centos - and if need be for stability, rocky16:58
ade_leegmann, btw - I responded to the comment on the review -- I can change to checking enable_fips if you prefer16:59
dansmithade_lee: yeah problem is some projects have already put python>=3.9 in their requirements, which means any project/job that requires that other package can't run on focal anymore16:59
ade_leedansmith, yeah - so no dice on ubuntu till next year then 17:01
ade_leedansmith, when enabling fips, the subscription agent just errors out on jammy.  I can check with canonical to see if there is any other option17:02
dansmithack, I'm just saying we've got a potentially conflicting set of requirements coming here :)17:03
gmannyeah those will start breaking fips job17:03
gmannade_lee: thanks, I will the comment today17:03
ade_leeyup - and this might be a problem when we get fips on jammy, because by then we'll be using python>=3.10 or whatnot ..17:04
dansmithjammy is 3.1017:05
gmannade_lee: for current master 2023.2 it can be >-py3.9 and in future if we bump the python min version to py310 then it can be >=py3.1017:05
gmannbut py3.9 is min version supported a it is in debian 1117:05
ade_leecool17:06
gmannhttps://governance.openstack.org/tc/reference/runtimes/2023.2.html#python-runtimes-for-2023-217:06
opendevreviewGhanshyam proposed openstack/tempest master: DNM: testing volume attachments  https://review.opendev.org/c/openstack/tempest/+/88089117:16
opendevreviewGhanshyam proposed openstack/tempest master: DNM: testing volume attachment  https://review.opendev.org/c/openstack/tempest/+/88113218:08
opendevreviewGhanshyam proposed openstack/tempest master: DNM: testing volume attachment  https://review.opendev.org/c/openstack/tempest/+/88113219:41
opendevreviewGhanshyam proposed openstack/tempest master: DNM: testing volume attachment  https://review.opendev.org/c/openstack/tempest/+/88113221:20
gmannade_lee: agree with your point in FIPs change, +A 22:19
gmannhttps://review.opendev.org/c/openstack/devstack/+/87160622:19
opendevreviewMerged openstack/devstack master: Modify devstack-base to allow for fips  https://review.opendev.org/c/openstack/devstack/+/87160623:55

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