*** mhen_ is now known as mhen | 01:08 | |
opendevreview | Maxim Sava proposed openstack/tempest master: Add tests for new add location api of glance https://review.opendev.org/c/openstack/tempest/+/891026 | 10:36 |
---|---|---|
opendevreview | Maxim Sava proposed openstack/tempest master: Add tests for new add location api of glance https://review.opendev.org/c/openstack/tempest/+/891026 | 11:03 |
opendevreview | Maxim Sava proposed openstack/tempest master: Add tests for new add location api of glance https://review.opendev.org/c/openstack/tempest/+/891026 | 11:09 |
mhen | hello | 12:33 |
mhen | question about Tempest: if I were to add scenario tests to the main Tempest repository that strictly need Barbican (key manager) access, how would I go about that? It seems that only the barbican-tempest-plugin repository currently provides the proper client implementation | 12:33 |
frickler | mhen: yes, barbican isn't part of the "core" services, so IMHO tests that require it do not belong into tempest. but maybe gmaan thinks otherwise | 12:46 |
mhen | context is the image encryption patchset I'm working on | 12:47 |
mhen | an appropriate scenario test would involve Glance, Cinder and Barbican | 12:47 |
mhen | is my only option to create a new repository (tempest plugin) that depends on both tempest and barbican-tempest-plugin in order to reuse as much code as possible? | 12:48 |
tkajinam | mhen, barbican-t-p already has a scenario tests with volume encryption so I guess adding it there would be better | 13:00 |
tkajinam | instead of creating another t-p | 13:00 |
tkajinam | cinder-t-p also has a scenario test to transfer encrypted volume, though | 13:00 |
mhen | tkajinam: thanks, will use barbican-t-p then | 13:01 |
tkajinam | adding it to barbican-t-p would be easier because the core flags about nova and cinder are already available in tempest and can be easily used | 13:01 |
tosky_ | yep | 13:18 |
mhen | appreciate the guidance, thank you | 13:32 |
JayF | https://review.opendev.org/c/openstack/devstack/+/950273 this already has 1x +2 and provides an early failure in case of network issues, would be very nice to get it landed. I'm trying my hardest to get my unmerged patches taken care of before I'm gone for 6 weeks :D | 15:11 |
gmaan | mhen: you can add test in either glance-tempest-plugin, cinder-tempest-pluing or barbican-tempest-plugin depends on which service major scneario it is testing | 15:22 |
gmaan | mhen: tempest plugins can have scneario tests which require other services and my suggestion to add test in the service tempest plugin for which test is manly for. service clients from tempest or tempest plugins are registered globally in tempest service client registry and can be detected and used same way in any plugins | 15:24 |
gmaan | just make sure you install/ask-job to include required tempest plugins | 15:24 |
gmaan | as long as tempest plugin is setup in env, tempest will detect and register their config, service clients etc in tempest namespace and then writing test (accessing config, service clients etc) in tempest or plugin is exactly same. | 15:26 |
gmaan | #startmeeting qa | 18:01 |
opendevmeet | Meeting started Wed Jun 11 18:01:23 2025 UTC and is due to finish in 60 minutes. The chair is gmaan. Information about MeetBot at http://wiki.debian.org/MeetBot. | 18:01 |
opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 18:01 |
opendevmeet | The meeting name has been set to 'qa' | 18:01 |
gmaan | #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours | 18:01 |
gmaan | today agenda ^^ | 18:01 |
gmaan | let's start | 18:03 |
gmaan | #topic Priority Items progress | 18:03 |
gmaan | #link https://etherpad.opendev.org/p/qa-2025-2-priority | 18:04 |
gmaan | no update on this | 18:05 |
gmaan | #topic Gate Status / Fix Checks | 18:05 |
gmaan | #link https://review.opendev.org/q/label:Review-Priority%253D%252B2+status:open+(project:openstack/tempest+OR+project:openstack/patrole+OR+project:openstack/devstack+OR+project:openstack/grenade) | 18:06 |
gmaan | no new change in this | 18:08 |
gmaan | some old one which I will review todua | 18:08 |
gmaan | today | 18:08 |
gmaan | #topic Changes with Review-Priority == +1 | 18:08 |
gmaan | #link https://review.opendev.org/q/label:Review-Priority%253D%252B1+status:open+(project:openstack/tempest+OR+project:openstack/patrole+OR+project:openstack/devstack+OR+project:openstack/grenade) | 18:08 |
gmaan | reviewed two and I can see one more new one which I will check after meeting | 18:11 |
gmaan | #topic Periodic jobs Status Checks | 18:11 |
gmaan | Periodic stable full | 18:11 |
gmaan | #link https://zuul.openstack.org/builds?job_name=tempest-full-2023-2&job_name=tempest-full-2024-1&job_name=tempest-full-2024-2&job_name=tempest-full-2025-1&pipeline=periodic-stable&skip=0 | 18:12 |
gmaan | all green | 18:12 |
gmaan | let me check if stable/2023.2 is EOL or not | 18:12 |
gmaan | seems yes | 18:13 |
gmaan | #link https://releases.openstack.org/ | 18:13 |
gmaan | I will start process to remove support from Tempest | 18:13 |
gmaan | #action gmaan to start end of support for stable/2023.2 from Tempest | 18:13 |
gmaan | Periodic stable slow | 18:13 |
gmaan | #link https://zuul.openstack.org/builds?job_name=tempest-slow-2024-2&job_name=tempest-slow-2024-1&job_name=tempest-slow-2023-2&job_name=tempest-slow-2025-1&skip=0 | 18:15 |
gmaan | all good | 18:15 |
gmaan | Periodic extra tests | 18:15 |
gmaan | #LINK https://zuul.openstack.org/builds?job_name=tempest-full-2024-2-extra-tests&job_name=tempest-full-2024-1-extra-tests&job_name=tempest-full-2023-2-extra-tests&job_name=tempest-full-2025-1-extra-tests&skip=0 | 18:15 |
gmaan | #link https://zuul.openstack.org/builds?job_name=tempest-full-2024-2-extra-tests&job_name=tempest-full-2024-1-extra-tests&job_name=tempest-full-2023-2-extra-tests&job_name=tempest-full-2025-1-extra-tests&skip=0 | 18:16 |
gmaan | all green | 18:16 |
gmaan | Periodic master | 18:16 |
gmaan | #link https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic | 18:16 |
gmaan | tempest-full-rocky failing | 18:16 |
gmaan | not sure how rocky job is still there | 18:16 |
gmaan | oh I only added it | 18:18 |
gmaan | #link https://review.opendev.org/c/openstack/tempest/+/949800 | 18:18 |
gmaan | oh its rocky-linux job not rocky cycle | 18:19 |
gmaan | Response - Headers: {'date': 'Wed, 11 Jun 2025 04:00:01 GMT', 'server': 'Apache/2.4.62 (Rocky Linux) OpenSSL/3.2.2 mod_wsgi/4.9.4 Python/3.11', 'content-length': '299', 'content-type': 'text/html; charset=iso-8859-1', 'connection': 'close', 'status': '503', 'content-location': 'https://10.210.129.18/image/v2/images/a3d66ecd-7ce8-4be6-92a2-a9f6e39fa6be'} | 18:20 |
gmaan | Body: b'<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">\n<html><head>\n<title>503 Service Unavailable</title>\n</head><body>\n<h1>Service Unavailable</h1>\n<p>The server is temporarily unable to service your\nrequest due to maintenance downtime or capacity\nproblems. Please try again later.</p>\n</body></html>\n' | 18:20 |
gmaan | image service behaved wrong in this failure but I am not seeing that is persistent as another run pass | 18:20 |
gmaan | I will check the latest run once that finish and see if anything we need to do here | 18:21 |
gmaan | #topic Distros check: | 18:21 |
gmaan | Centos 9 | 18:21 |
gmaan | #link https://zuul.openstack.org/builds?job_name=tempest-full-centos-9-stream&job_name=devstack-platform-centos-9-stream&skip=0 | 18:21 |
gmaan | all good | 18:21 |
gmaan | Debian | 18:21 |
gmaan | #link https://zuul.openstack.org/builds?job_name=devstack-platform-debian-bookworm&skip=0 | 18:22 |
gmaan | all good | 18:22 |
gmaan | Rocky Linux | 18:22 |
gmaan | #link https://zuul.openstack.org/builds?job_name=devstack-platform-rocky-blue-onyx&job_name=tempest-full-rocky&skip=0 | 18:22 |
gmaan | same here, last instance fail but yesterday it was passing and platform job passing. nothing from Rocky specific | 18:23 |
gmaan | #topic Open Discussion | 18:23 |
gmaan | no topic listed here | 18:23 |
gmaan | waiting for couple of min if anyone has any topic to discuss | 18:23 |
gmaan | if nothing let's end the meeting | 18:25 |
gmaan | #endmeeting | 18:25 |
opendevmeet | Meeting ended Wed Jun 11 18:25:23 2025 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 18:25 |
opendevmeet | Minutes: https://meetings.opendev.org/meetings/qa/2025/qa.2025-06-11-18.01.html | 18:25 |
opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/qa/2025/qa.2025-06-11-18.01.txt | 18:25 |
opendevmeet | Log: https://meetings.opendev.org/meetings/qa/2025/qa.2025-06-11-18.01.log.html | 18:25 |
opendevreview | Merged openstack/devstack master: Updated from generate-devstack-plugins-list https://review.opendev.org/c/openstack/devstack/+/951221 | 20:38 |
opendevreview | Ghanshyam proposed openstack/tempest master: End support for stable/2023.2 https://review.opendev.org/c/openstack/tempest/+/952403 | 21:23 |
opendevreview | Ghanshyam proposed openstack/tempest master: Pin stable/2025.1 constraint in tox to release 44.0.0 https://review.opendev.org/c/openstack/tempest/+/952404 | 21:30 |
opendevreview | Ghanshyam proposed openstack/tempest master: Switch back the tox constraint to master https://review.opendev.org/c/openstack/tempest/+/952406 | 21:38 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!