Tuesday, 2020-04-21

gmannmasayukig: can you check this also. though I need to fix the patrole gate for glance test failure before release - https://review.opendev.org/#/c/721305/00:01
masayukiggmann: thanks. And https://review.opendev.org/#/c/721305/ can be improved.00:11
masayukiggmann: And I found that I missed the same thing on the tempest release note patch.. :p00:12
gmannmasayukig: ohk, let me modify the patrole one.00:15
openstackgerritGhanshyam Mann proposed openstack/patrole master: Add releasenote to tag the Patrole for Ussuri release  https://review.opendev.org/72130500:16
openstackgerritGhanshyam Mann proposed openstack/tempest-plugin-cookiecutter master: [ussuri][goal] Update contributor documentation  https://review.opendev.org/72137200:23
openstackgerritGhanshyam Mann proposed openstack/qa-specs master: [ussuri][goal] Update contributor documentation  https://review.opendev.org/72137300:23
openstackgerritGhanshyam Mann proposed openstack/karma-subunit-reporter master: [ussuri][goal] Update contributor documentation  https://review.opendev.org/72137400:23
openstackgerritGhanshyam Mann proposed openstack/devstack-plugin-cookiecutter master: [ussuri][goal] Update contributor documentation  https://review.opendev.org/72137500:23
gmannmasayukig: ^^ few easy one00:23
masayukiggmann: thanks. but for patrole, needed to make it like this https://opendev.org/openstack/patrole/src/branch/master/releasenotes/notes/intermediate-ussuri-release-8f7bb2140bca827c.yaml00:37
openstackgerritMerged openstack/tempest master: Add releasenote to tag the Tempest for Ussuri release  https://review.opendev.org/72130000:42
*** Liang__ has joined #openstack-qa01:03
openstackgerritMerged openstack/patrole master: [ussuri][goal] Update contributor documentation  https://review.opendev.org/72110901:07
*** rh-jelabarre has quit IRC01:53
*** paras333 has quit IRC02:42
*** hongbin has joined #openstack-qa03:00
*** ricolin has joined #openstack-qa04:31
*** evrardjp has quit IRC04:35
*** evrardjp has joined #openstack-qa04:35
*** hongbin has quit IRC04:35
*** ricolin has quit IRC04:52
*** ricolin has joined #openstack-qa04:56
*** ricolin_ has joined #openstack-qa05:06
*** ricolin has quit IRC05:09
*** vishalmanchanda has joined #openstack-qa05:09
*** udesale has joined #openstack-qa05:10
*** udesale_ has joined #openstack-qa05:21
*** udesale has quit IRC05:24
openstackgerritAndreas Jaeger proposed openstack/patrole master: Cleanup py27 support  https://review.opendev.org/72152505:44
*** gcheresh has joined #openstack-qa05:50
*** yamamoto has quit IRC06:08
*** udesale_ has quit IRC06:14
soniya29gmann: done06:36
*** yamamoto has joined #openstack-qa06:36
*** udesale has joined #openstack-qa06:37
*** udesale has quit IRC06:43
*** gfidente|afk is now known as gfidente06:46
*** Aditi20 has joined #openstack-qa06:49
Aditi20Hi, I am seeing recent failures in IBM Power CI arising because of new tests being added to tempest in https://review.opendev.org/#/c/70081306:50
Aditi20These are the test cases failing -  {3} tempest.api.compute.servers.test_server_rescue.ServerStableDeviceRescueTest.test_stable_device_rescue_cdrom_ide [19.418171s] ... FAILED06:50
Aditi20tearDownClass (tempest.api.compute.servers.test_server_rescue.ServerStableDeviceRescueTest) [0.000000s] ... FAILED06:50
Aditi20Detail logs - https://oplab9.parqtec.unicamp.br/pub/ppc64el/openstack/nova/41/712741/7/check/tempest-dsvm-full-bionic-py3/dfc495f/job-output.txt06:51
Aditi20Is there anything that needs to be fixed in the CI to make the rescue test cases work?06:51
fricklerAditi20: I would assume that you need to skip these tests in your environment: "Instance fa6bec08-78d1-4a30-ab05-e86d6d506db0 cannot be rescued: Driver Error: unsupported configuration: IDE controllers are unsupported for this QEMU binary or machine type"07:00
frickleror maybe tempest should be better and check and skip by itself07:00
*** rpittau|afk is now known as rpittau07:03
*** nightmare_unreal has joined #openstack-qa07:03
fricklerlyarwood: ^^ that's your patch07:04
fricklerAditi20: otoh, iiuc those tests should be off by default, did you explicitly enable them? https://review.opendev.org/#/c/700813/11/tempest/config.py,unified07:06
openstackgerritzhufl proposed openstack/tempest master: Adding description for testcases - image part1  https://review.opendev.org/72153607:08
*** slaweq_ has joined #openstack-qa07:11
Aditi20frickler Thanks for checking!  I am currently testing all tempest api test cases -   tempest run --regex '^tempest\.api' --blacklist-file=/home/zuul/pkvm_blacklist.txt --concurrency=4 --black-regex=07:12
Aditi20Guess will have to add these tests in blacklist07:12
*** yamamoto has quit IRC07:20
*** yamamoto has joined #openstack-qa07:25
*** ccamposr has joined #openstack-qa07:26
*** ccamposr__ has quit IRC07:28
*** tosky has joined #openstack-qa07:44
*** ricolin_ has quit IRC07:47
*** ricolin has joined #openstack-qa07:47
openstackgerritPavlo Shchelokovskyy proposed openstack/tempest master: Fix test_get_console_output_server_id_in_shutoff_status  https://review.opendev.org/71020607:53
*** ralonsoh has joined #openstack-qa07:57
*** jpena|off is now known as jpena07:57
lyarwoodfrickler / Aditi20 ; Morning, https://review.opendev.org/#/c/700814/7/lib/tempest@573 controls this for most jobs upstream FWIW, we can extend this to cover power.08:01
*** lennyb has joined #openstack-qa08:04
openstackgerritzhufl proposed openstack/tempest master: Adding description for testcases - image part2  https://review.opendev.org/72154408:07
*** lucasagomes has joined #openstack-qa08:07
lyarwoodAditi20: actually maybe just blacklisting this is the way to go given this is also a LIBVIRT_TYPE=kvm based job.08:08
Aditi20yes thanks Iyarwood08:14
*** udesale has joined #openstack-qa08:16
*** udesale_ has joined #openstack-qa08:22
*** udesale has quit IRC08:22
lyarwoodAditi20: sorry for breaking your job :)08:22
*** udesale has joined #openstack-qa08:22
Aditi20haha no issues :D08:29
*** Aditi20 has quit IRC08:45
*** dtantsur|afk is now known as dtantsur09:00
*** vishalmanchanda has quit IRC09:09
openstackgerritKashyap Chamarthy proposed openstack/tempest master: WIP: Use SATA bus for CDROM  https://review.opendev.org/72155509:09
*** Liang__ has quit IRC10:03
openstackgerritAndreas Jaeger proposed openstack/patrole master: Cleanup py27 support  https://review.opendev.org/72152510:16
*** rpittau is now known as rpittau|bbl10:31
*** slaweq_ is now known as slaweq10:43
*** ricolin has quit IRC11:00
*** ricolin has joined #openstack-qa11:00
*** udesale has quit IRC11:09
brtknrclarkb: rather than mirroring, is it possible to download and unxz in advance?11:32
brtknrclarkb: the list of images we want to download are here: https://builds.coreos.fedoraproject.org/streams/stable.json11:33
brtknrclarkb: at the moment, the unxz is burning 16 minutes of CPU for every Zuul job11:34
*** jpena is now known as jpena|lunch11:35
*** nweinber has joined #openstack-qa11:52
*** rh-jelabarre has joined #openstack-qa11:53
*** raildo has joined #openstack-qa12:07
brtknrcore, please review this, we need it for magnum CI: https://review.opendev.org/72121312:15
brtknrCores, please review this, we need it for magnum CI: https://review.opendev.org/72121312:15
*** soniya29 is now known as soniya29|afk12:15
brtknrAJaeger: gmann ^12:16
toskybrtknr: in ~70 minutes from now the QA team office hour starts, and there is a point about urgent reviews12:19
*** brinzhang has quit IRC12:30
*** dtantsur is now known as dtantsur|brb12:30
*** rpittau|bbl is now known as rpittau12:31
*** jpena|lunch is now known as jpena12:35
*** paras333 has joined #openstack-qa12:56
openstackgerritAndreas Jaeger proposed openstack/tempest master: Set TOX_CONSTRAINTS_FILE  https://review.opendev.org/72160613:02
*** soniya29|afk is now known as soniya2913:07
AJaegerbrtknr: I'm not a core here...13:08
*** rcernin has quit IRC13:14
*** toabctl has quit IRC13:25
brtknrhmm who is?13:25
*** toabctl has joined #openstack-qa13:27
*** gfidente has quit IRC13:28
gmannoffice hour time13:31
gmann#startmeeting qa13:31
openstackMeeting started Tue Apr 21 13:31:11 2020 UTC and is due to finish in 60 minutes.  The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot.13:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:31
*** openstack changes topic to " (Meeting topic: qa)"13:31
openstackThe meeting name has been set to 'qa'13:31
gmannwho all here today13:31
masayukighi13:31
kopecmartinhello13:31
toskyhi13:31
soniya29hello13:31
gmannlet's start13:33
gmann#link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours13:33
gmanntoday agenda ^^13:33
gmann#topic Announcement and Action Item13:33
*** openstack changes topic to "Announcement and Action Item (Meeting topic: qa)"13:33
gmannone action item i had about cleaning up the few of the QA projects core list.13:34
gmannI did that.13:34
gmannand added masayukig in qa-release team as PTL.13:34
masayukiggmann: ++ thanks :)13:35
gmannif anyone would like to help in hacking side, please let us know13:35
gmannwe still looking for few more members there13:35
gmannannouncement is about wiki pages updates13:35
gmannI have updated the QA wiki to reflect all the projects and their link for doc, source code etc13:36
gmann#link https://wiki.openstack.org/wiki/QA13:36
gmann^^ this is up to date now13:36
masayukigcool13:36
gmannnext was release page13:36
gmann#link https://wiki.openstack.org/wiki/QA/releases13:36
gmannI have added the release things and steps with example for all the projects under QA13:37
gmannwith project releases and extra infra setup we need to do for every release in devstack and grenade13:37
gmannmasayukig: it will help you13:38
paras333gmann:  I can help but I am not much aware of hacking plugins so might need some time to get up to the speed13:38
gmannparas333: thanks, this is the project https://github.com/openstack/hacking13:38
masayukiggmann: thanks, that must be helpful13:38
tosky(technically https://opendev.org/openstack/hacking )13:38
gmannmasayukig: i am doing the ussuri release things and will add you in review. and then ball is in your court :)13:39
masayukiggmann: sure, I see13:39
paras333gmann:  This is good, I will take a look. Is there any doc as well that help me getting up to the speed to understand this plugin?13:39
gmannparas333: you can look at that and do some review etc not so many incoming request though13:39
paras333gmann:  sure13:39
gmannparas333: https://docs.openstack.org/hacking/latest/13:40
gmann#link https://docs.openstack.org/hacking/latest/13:40
gmannthis one ^^13:40
paras333gmann:  awesome, thanks!13:40
gmannthanks13:40
gmannif you find something missing on those wiki page please let me or masayukig know.13:40
gmannat the end we wanted to move this to QA level doc which is not available yet but let's discuss it in PTG13:41
paras333gmann: sure13:41
gmann#topic Ussuri Priority Items progress13:41
*** openstack changes topic to "Ussuri Priority Items progress (Meeting topic: qa)"13:41
gmann#link https://etherpad.opendev.org/p/qa-ussuri-priority13:42
gmannRemove/migrate the .testr.conf to .stestr13:42
gmannor sanity blacklist removal13:42
masayukigI've listed up the candidates for the migration/removing #link https://etherpad.opendev.org/p/enkM4eeDHObSloTjPGAu13:43
gmannmasayukig: any update on these ^^13:43
gmannmasayukig: nice. I think doing those in V cycle will be good to avoid any issue in Ussuri release13:43
masayukigI pushed one patch already, and preparing pushing the others for patches of removing .testr.conf13:43
masayukigyeah,13:43
gmannok. +113:44
masayukigI don't want to bother the Ussuri release13:44
gmannthanks. can you add the link on etherpad also13:44
masayukigwhich etherpad?13:44
gmann#link https://etherpad.opendev.org/p/qa-ussuri-priority13:44
gmannthis one13:44
gmannRBAC testing strategy (reader/member/admin X project/domain/system)13:45
masayukigI already put the link https://etherpad.opendev.org/p/enkM4eeDHObSloTjPGAu to the priority page13:45
gmannohk, then link of this etherpad13:45
gmannits there, thanks13:45
gmannno progress on this, this was pending on review. I will be able to spend some time now13:45
gmannAdding New glance tests to tempest13:46
*** gfidente has joined #openstack-qa13:46
gmannnot sure if glance team need help on this. devstack side it was all good for multi store feauture.13:46
gmannfeature13:46
gmanni will check with abhishek and close this13:46
gmannmproving Tempest cleanup13:46
gmannkopecmartin: ^^13:46
kopecmartinwaiting for some reviews there13:47
kopecmartinno other updates13:47
gmannok, I think that was close.if i remember correctly did you update the patch for two separate var for init saved and actual cleanup ?13:48
kopecmartinyeah, i think so, i added some variables there  .. i answered your questions and suggestions, so maybe you can have a look after the meeting13:49
kopecmartinif it's enough or should i change anything else13:49
gmannsure, thanks13:49
gmannlet's move13:49
gmann#topic OpenStack Events Updates and Planning13:49
*** openstack changes topic to "OpenStack Events Updates and Planning (Meeting topic: qa)"13:49
gmann#link https://etherpad.opendev.org/p/qa-victoria-ptg13:49
gmannthis is etherpad to collect the topic ^^13:49
gmannwe need to signup for the virtual PTG, I think deadline is 28th April.13:51
gmannlet me find the email13:51
masayukigoh, I missed that.. :p13:51
gmann#link http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014126.html13:51
openstackgerritLee Yarwood proposed openstack/tempest master: remote_client: Use blkid -L to find config drive by filesystem label  https://review.opendev.org/71086413:51
gmannmasayukig: can you prepare for that? like topic and time required and accordingly signup.13:52
masayukiggmann: ok, I'll try that13:52
gmannmasayukig: thanks.13:52
gmann#topic Sub Teams highlights13:53
*** openstack changes topic to "Sub Teams highlights (Meeting topic: qa)"13:53
gmannTempest13:53
gmannTempest is going to be released for ussuri as final release. I will update the hash to release patch.13:53
gmannany other things to updates on Tempest ?13:53
soniya29gmann: With regards to scenario manager, I found certain methods are already well defined but still the tempest plugins have duplicated the code in the method. So in this usecase, do we require to work at plugin side or is there something we can do at tempest as well?13:54
gmannPatrole13:54
gmannsoniya29: thanks. we did copy everything on plugins side to avoid breaking them if we change anything on tempest scenario manager13:55
gmannsoniya29: so plan is 1. once we declare the scenario manager stable after doing some work to make each method more consistent etc 2. remove the copy of scenario manager from plugins side and replace them with import tempest.scenario.manager13:56
gmannsoniya29: so whatever cleanup is required on tempest scenario manager side, feel free to propose without worry about plugins copy13:56
soniya29gmann: okay, I wasn't aware of this concept13:57
gmannsoniya29: sorry for not giving that background.13:58
gmannsoniya29: also as you noticed about mixin or single base class idea among scenario or api tests to avoid duplicate code.13:58
soniya29gmann: that's okay :)13:59
gmannanything else on Tempest side ?13:59
gmannPatrole14:00
gmanni am in process of final release of patrole for ussuri but gate is blocked and failure happening for glance tests14:00
gmannthere are some change in glance policy and the config option admin_role which might have caused it14:00
gmannI need to debug that and see if we can fix it. almost all the glance tests are failing14:01
masayukigoh.. :(14:01
gmannas per glance releasenotes, default policy user should not effect but seems patrole is being effected14:02
gmannlet me debug more on that and find what happened and how it can be fixed14:02
gmannGrenade14:03
gmannzuulv3 job14:03
gmann#link https://review.opendev.org/#/q/topic:native-zuulv3-migration+(status:open+OR+status:merged)14:03
toskyyep, patches ready for review14:03
gmanni was half way on the re-review and could not finish14:03
gmanntosky: thanks. give me today or tomorrow time. I should be able to finish that14:03
toskyanything relevant that you think should be changed so far?14:03
gmanni am trying to check on target and base branch var14:04
toskybut I can wait for the review14:04
gmannbut could not finish so nothing as of now.14:04
gmannmain goal is we should have a easy way to change them over the releases.14:05
toskyand we do14:05
gmannyeah, i need to revisit that.14:05
gmanntarget is to get this in before V cycle when tosky will start the zuulv3 migration goal.14:06
gmannlet's move next14:07
gmannCommunity goal tracking14:07
gmann#link https://etherpad.openstack.org/p/qa-community-wide-goals-tracking14:07
gmannpy2 drop goal is done for QA14:08
gmanncontributor guide is in progress and should be finished before ussuri release14:08
masayukiggreat14:08
brtknrwhen its a good time, i'd like to raise a couple of points if thats okay14:08
gmannthere are few devstack plugins repo where I need to add some doc place or use devstack contribution guide. I think 4 of them are left14:08
gmannbrtknr: we can discuss in open discussion14:09
gmann#topic Bug Triage14:09
*** openstack changes topic to "Bug Triage (Meeting topic: qa)"14:09
gmannkopecmartin: go ahead14:09
brtknrgmann: thanks14:09
kopecmartini don't have many updates, i didn't focu on bug triaging much this week, anyway, the numbers still look ok , or are decreasing14:10
kopecmartinand the etherpad is up to date, so have a look anyone for reviews, or bugs to dicscuss14:10
kopecmartin#link https://etherpad.opendev.org/p/qa-bug-triage-ussuri14:10
gmannkopecmartin: ok thanks.14:10
masayukig++14:11
gmanneveryone please review the bug fixes mentioned in etherpad ^^14:11
gmann#topic Critical Reviews14:11
*** openstack changes topic to "Critical Reviews (Meeting topic: qa)"14:11
gmannany critical review ?14:11
kopecmartingmann: we can +w this, we added a note to the scenario manager work as you asked: https://review.opendev.org/#/c/701434/14:12
gmannkopecmartin: i was waiting for the test result which was not present in last gate result14:12
gmannit should be ready now, I will look after meeting14:13
kopecmartingmann: and one question regarding this, where should we make a note regarding technical dept? https://review.opendev.org/#/c/701352/ there is one thing that should be done as a follow up14:13
gmannkopecmartin: i have not checked that yet. let me review and reply on review14:14
kopecmartingmann: ok,thanks14:14
gmann#topic Open Discussions14:14
*** openstack changes topic to "Open Discussions (Meeting topic: qa)"14:14
gmannbrtknr: go ahead14:14
brtknrokay so i wanted to mention the patch to support upload of qcow2.xz14:15
openstackgerritGhanshyam Mann proposed openstack/patrole master: Add releasenote to tag the Patrole for Ussuri release  https://review.opendev.org/72130514:15
gmannbrtknr: link?14:15
brtknrhttps://review.opendev.org/72121314:16
brtknrwe are migrating migrating magnum CI to Zuulv314:16
gmann#link https://review.opendev.org/72121314:16
brtknrbut also moving towards fedora coreos image because fedora atomic is EOL14:17
brtknrthe second point i wanted to make was about mirroring fedora coreos locally14:17
gmanni think we are on latest fedora image right?14:18
brtknrbut as well as mirroring, running an unxz operation when the image is downloaded so that we save 16 minutes of CI time14:18
gmannmay be ianw or lyarwood knows14:18
gmanni see. is it very heavy image? size14:18
brtknrgmann: i dont think it includes fedora-coreos14:18
brtknryes, 460M before unxz, 1.7G after14:19
lyarwoodhey14:19
lyarwoodno that's not me14:19
lyarwoodmaybe the TripleO folks?14:19
masayukigbrtknr: yeah, I think "fedora" and "fedora core" are different. So, maybe, more description in the commit message is preferable.14:19
brtknrhttps://getfedora.org/en/coreos/14:20
lyarwoodgmann: oh sorry I see your actual question now14:20
lyarwoodgmann: fedora-31 is fedora-latest now14:20
gmannyeah i also find fedora-31 as latest14:20
brtknrfedora-coreos uses fedora as base layer but adds additional bits on top14:21
brtknrso not the same14:21
gmannbrtknr: let 's wait for ianw or yoctozepto review on https://review.opendev.org/72121314:21
brtknrgmann: okaay thanks, 4 PS depend on this, 2 in magnum and 2 in magnum-tempest-plugin :)14:22
gmannbrtknr: not sure about fedora-coreos support as per current bandwidth, I would like to know ianw yoctozepto opinion on that14:23
*** ricolin has quit IRC14:23
*** ricolin has joined #openstack-qa14:23
*** yamamoto has quit IRC14:23
brtknrok thanks14:24
gmannin devstack we have been supporting a single fedora version which is latest(as we move to new one)14:24
* yoctozepto reporting for duty14:24
gmannyoctozepto: is here :)14:24
yoctozeptois not that patch related just to image upload?14:24
gmannwe can discuss after office hour on that14:24
brtknryoctozepto: for your attention : https://review.opendev.org/#/c/721213/14:24
gmannanything else to discuss today ?14:25
brtknryoctozepto: i am discussing the possiblity of mirror+unxz, no patches yet14:25
brtknrhappy to talk after office hour14:25
brtknrhappy to talk after "office hour"14:25
gmannlet's close the office hour and continue the discussion.14:25
gmannthanks all for joining14:25
masayukig++14:25
gmann#endmeeting14:25
*** openstack changes topic to "Discussion of OpenStack Quality Assurance Projects (tempest, devstack, grenade, and friends) | docs https://wiki.openstack.org/wiki/QA | specs https://review.openstack.org/#/q/project:openstack/qa-specs | channel logs http://eavesdrop.openstack.org/irclogs/%23openstack-qa/"14:25
masayukigthanks!14:25
openstackMeeting ended Tue Apr 21 14:25:56 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:25
openstackMinutes:        http://eavesdrop.openstack.org/meetings/qa/2020/qa.2020-04-21-13.31.html14:26
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/qa/2020/qa.2020-04-21-13.31.txt14:26
openstackLog:            http://eavesdrop.openstack.org/meetings/qa/2020/qa.2020-04-21-13.31.log.html14:26
gmannyoctozepto: apart from that patch brtknr is asking about  fedora-coreos  support ?14:26
gmannfrickler: ^^14:26
brtknrgmann:  is right14:26
*** gcheresh has quit IRC14:26
brtknrbecause downloading the images is quick (460M) but unxz operation costs 16 mins in the CI14:26
yoctozeptolike instead of cirros?14:27
brtknrwe use fedora-coreos as the supported image in magnum14:27
yoctozeptoah, this usecase14:27
brtknrsince fedora atomic is EOL14:27
yoctozeptowell, it's huge if it's 460M xzipped14:27
brtknrthere was a fedora atomic mirror which is now no longer being updated14:28
brtknryoctozepto: yep, its 1.7G unxzipped14:28
yoctozeptooh my, then it's a no-no to carry this in infra images14:28
yoctozeptoso the only solution is to put it on mirror14:29
clarkbbrtknr: generally producing CI specific artifacts like that shpuld be avoided because now when you go to production you either need extra steps or you rely on CI resources14:30
brtknryoctozepto: mirror zipped or unzipped version?14:30
yoctozeptowell, that's tricky, either should help here14:31
brtknronly the zipped version is distributed upstream14:31
yoctozeptobut if unxzipping takes a lot of time, it might be interesting to consider unxzipped too14:31
yoctozeptoand then clarkb's point applies14:31
yoctozeptohow much time does the whole scenario take?14:32
brtknrunxz takes 16 mins14:32
brtknrthe whole job takes 56 mins14:32
brtknrso 25% of the time14:33
brtknrslightly more in fact14:33
brtknr28.6%14:33
yoctozeptois only xz version available there?14:34
brtknryoctozepto: thats right14:35
brtknr:(14:35
yoctozeptooh my, I wonder if upstream could not just use gz14:35
yoctozeptothis compression ratio is not that great and having like 10x decompression time is absurd14:36
clarkbyoctozepto: I think qcow2 is already gzipped14:37
brtknryes i put that questions forward in #fedora-coreos channel14:37
brtknrthey said they are working to improve the image size14:37
yoctozeptoclarkb: I thought it's optional?14:37
yoctozeptoqcow2 has zeroes removed for sure but that's it I guess14:38
brtknryoctozepto: gziping it reduces the image down to 698M14:38
brtknrnot sure why they didnt just go for that option14:39
yoctozeptothat's what I thought14:40
clarkbqcow2 uses zlib14:40
yoctozeptoand decompression takes like... tens of seconds?14:40
clarkbsoaybe they arent compressing the qcow214:40
yoctozeptoclarkb: yeah, they likely don't14:40
clarkbsince zlib is basically gzip14:40
yoctozeptoI think most qcow2 in the wild have 0 compression14:41
clarkbthats my suggestion then. They should stop xz'ing qcow2 and have it zlib compress as supported by qcow214:41
yoctozepto++14:41
*** yamamoto has joined #openstack-qa14:41
yoctozeptoplan minimum is they just do gzip instead of xz14:41
*** yamamoto has quit IRC14:42
*** yamamoto has joined #openstack-qa14:42
*** yamamoto has quit IRC14:42
*** yamamoto has joined #openstack-qa14:43
*** gcheresh has joined #openstack-qa14:44
*** yamamoto has quit IRC14:44
*** yamamoto has joined #openstack-qa14:44
*** yamamoto has quit IRC14:44
yoctozeptoand we obviously can mirror this compressed so it's more reliable14:44
*** yamamoto has joined #openstack-qa14:44
clarkbanother potential option is to reduce the xz settings14:46
clarkbxz is far more cpu intensive than gzip as you bump compression levels14:46
clarkbyou may still get better than gzip compression at reasonable cpu cost if lowering the level14:47
*** dtantsur|brb is now known as dtantsur14:47
yoctozepto^ but it could also happen that similar performance earns worse compression14:47
yoctozeptobut this decompression time is ridiculuosly high compared to saved space14:48
yoctozeptofar from eco solution ;p14:48
*** dmellado has quit IRC14:49
*** yamamoto has quit IRC14:49
brtknrwhile we work out what to do, can we take this in in the meantime: https://review.opendev.org/#/c/721213/15:02
yoctozeptoyeah, works for me15:03
clarkbbrtknr: isn't the inline unxz the source of the swift errors?15:03
clarkbwe should unxz then upload15:04
clarkb(this was my comment yseterday)15:04
yoctozeptoclarkb: swift timeouts?15:04
yoctozeptoor what happens?15:04
clarkbyoctozepto: yes glance connection to swift times out15:05
yoctozeptoah, imaginable15:05
clarkbI think beacuse glance starts the connection when the push starts but then xz doesn't write bytes in a consistent stream15:05
yoctozeptostill, writing this locally may be painful15:05
yoctozeptoyeah, it likely does not15:05
clarkbeh mktemp, unxz, upload rm tmp15:06
clarkbits not the worst things15:06
yoctozeptowell, it's still 1.7G15:06
yoctozeptoonce in tmp, once in swift15:06
yoctozeptoI guess we *could* run out of space in some cases15:07
yoctozeptobut maybe I'm worrying too much15:07
yoctozeptoI guess this is one of the things we would discuss in fungi's proposed sig15:08
fungino need to wait for a sig to have discussions ;)15:08
yoctozeptofungi: sure, I'm just examining the potential scope15:08
clarkbyoctozepto: ya but its also self testing15:09
clarkbso if that is a problem we'll know15:09
yoctozeptowell, sure; there is still no better idea if streaming times out15:10
brtknryoctozepto: could the default timeout be increased?15:10
brtknrto infinite?15:10
brtknror 1 hour?15:10
yoctozeptoI don't think infinite is fine :-)15:10
yoctozepto15 mins I guess would do15:10
yoctozeptoit likely streams it in portions15:11
clarkbwe should ask swift what the side effects of that are15:11
yoctozeptoglanceclient <-> glance could time out too15:11
yoctozeptoalso, I think glance does this inefficient way if it does not know the file size ahead of time15:12
yoctozeptoso maybe the 16 minutes come from that too?15:12
yoctozeptoas it has to resize the object size15:12
*** dmellado has joined #openstack-qa15:17
clarkbbasically if we are adding that feature to devstack we shouldn't require swift not be running without checking for that15:18
clarkband ideally since this is a client side interaction we would make it work with and without swift15:18
clarkb(so I Think we should try for that before anything else)15:18
openstackgerritBharat Kunwar proposed openstack/devstack master: Support upload of qcow2.xz image format  https://review.opendev.org/72121315:31
brtknrclarkb: yoctozepto: I have addressed your comment^15:31
*** dmellado has quit IRC15:35
*** dmellado has joined #openstack-qa15:37
*** udesale_ has quit IRC15:41
yoctozeptowould not it make sense to put time around these invocations (unxz and upload) - it should be easier for profiling (could use seeing the user and system time)15:42
clarkbyoctozepto: devstack will trace with log timestamps15:44
clarkbto start you can probably go off of that15:44
yoctozeptoclarkb: yeah, but this is only *real* time15:46
yoctozeptoI wonder where it spends it15:47
yoctozeptobrtknr: ^^^15:47
brtknryoctozepto: the -v arg means verbose15:47
brtknrthis prints out the amount of time + MB/s in the devstack logs15:48
brtknri have added -v arg to unxz15:48
yoctozeptoyeah, I'm just interested in whether this is properly threaded, io-bound etc.15:49
yoctozeptoyou don't get either with any of suggested sources15:49
*** ricolin has quit IRC15:49
brtknryoctozepto: are you suggesting adding "time unxz" into devstack codebase?15:52
*** yamamoto has joined #openstack-qa15:54
yoctozeptoand time for upload15:58
brtknryoctozepto: ubuntu@devstack-master:~/magnum-terraform$ time unxz -vkfT0 fedora-coreos-31.20200323.3.2-openstack.x86_64.qcow2.xz15:59
brtknrfedora-coreos-31.20200323.3.2-openstack.x86_64.qcow2.xz (1/1)15:59
brtknr  100 %      459.2 MiB / 1657.1 MiB = 0.277    55 MiB/s       0:3015:59
brtknrreal 0m30.363s15:59
brtknruser 0m28.679s15:59
brtknrsys 0m1.531s15:59
brtknrthats my local result15:59
*** gcheresh has quit IRC15:59
brtknrnot sure why the CI takes 16 mins16:00
brtknrupload doesnt take very long16:00
brtknrthis is in the lgs16:01
brtknrthere^16:02
openstackgerritBharat Kunwar proposed openstack/devstack master: Support upload of qcow2.xz image format  https://review.opendev.org/72121316:02
brtknrg2g now, childcare duties but i will be back tomorrow16:03
*** lucasagomes has quit IRC16:07
*** kklimonda has quit IRC16:28
*** kklimonda has joined #openstack-qa16:30
*** evrardjp has quit IRC16:35
*** evrardjp has joined #openstack-qa16:35
brtknryoctozepto: do you want it there permanently or just for one off check?16:36
*** kklimonda has quit IRC16:38
*** lseki has quit IRC16:38
*** dviroel has quit IRC16:38
*** rpittau is now known as rpittau|afk16:39
*** jberg-dev has quit IRC16:39
*** masayukig has quit IRC16:39
*** kklimonda has joined #openstack-qa16:40
*** simondodsley has quit IRC16:40
*** jamespage has quit IRC16:40
*** dviroel has joined #openstack-qa16:40
*** nightmare_unreal has quit IRC16:40
*** simondodsley has joined #openstack-qa16:41
*** mnaser has quit IRC16:41
*** lseki has joined #openstack-qa16:42
*** jamespage has joined #openstack-qa16:42
*** TheJulia has quit IRC16:42
*** csatari has quit IRC16:43
*** masayukig has joined #openstack-qa16:43
*** jberg-dev has joined #openstack-qa16:43
*** nightmare_unreal has joined #openstack-qa16:44
*** TheJulia has joined #openstack-qa16:44
*** mnaser has joined #openstack-qa16:44
*** csatari has joined #openstack-qa16:45
*** vdrok has quit IRC16:45
*** mnaser has quit IRC16:46
*** vdrok has joined #openstack-qa16:47
*** mnaser has joined #openstack-qa16:47
*** mnaser has quit IRC16:49
*** mnaser has joined #openstack-qa16:50
*** dtantsur is now known as dtantsur|afk16:59
yoctozeptobrtknr: perma is fine17:03
yoctozeptoI wonder is your machine single-threaded? as it looks like it used just one core; still it's much much faster than in CI so maybe it was glance/swift doing it mega ineffectively17:05
AJaegerpatrole fails the admin,member, reader tests for me on https://review.opendev.org/#/c/721525/ - that should be a simple py27 cleanup. If anybody can give me a pointer, i would appreciate it.17:09
gmannAJaeger: it is failing due to glance change. all the glance tests are failing. it is hard to debug and also blocking the release.17:10
gmannI need to check actual issue from patrole or glance side17:10
AJaegergmann: thanks for confirmation - then I'll wait.17:10
gmanndefault policy which is what tested by patrole should keep working as it is but somehow they are failing17:10
gmannfixing all the nova tests is already up but that is blocked by glance failure- https://review.opendev.org/#/c/720601/17:11
AJaegerack17:12
*** jpena is now known as jpena|off17:13
*** nightmare_unreal has quit IRC17:13
*** ajitha has joined #openstack-qa17:41
ajithahi all, we have been running a openstack CI for cinder driver.. with ubuntu 18.04 and py3.6... After this commit https://opendev.org/openstack/nova/commit/f1e448d6729f674101b34b08e3c5e95fd8f75770 , our CI/CD pipeline is getting break in devstack with following error "pip._vendor.pkg_resources.ContextualVersionConflict: (oslo.policy 3.0.3 (/usr/local/lib/python3.6/dist-packages), Requirement.parse('oslo.policy>=3.1.0'), {'nova'}).."17:42
ajithahttp://paste.openstack.org/show/792492/  -- detailed log..manual devstack execution works fine with an error throwing as ERROR: nova 20.1.0.dev1681 has requirement oslo.policy>=3.1.0, you'll have oslo-policy 3.0.3 which is incompatible... but it skips that and devstack gets completed.   and while executing devstack-gate jenkins job, devstack gets error at the above point17:42
ajithaThe error is throwing in the manual devstack execution(./stack.sh) but it skips and complete the devstack.. In case of devstack-gate, it just stops at that point17:42
openstackgerritRadosÅ‚aw Piliszek proposed openstack/devstack master: Support upload of qcow2.xz image format  https://review.opendev.org/72121317:43
openstackgerritAndreas Jaeger proposed openstack/tempest master: Set TOX_CONSTRAINTS_FILE  https://review.opendev.org/72160617:43
gmannajitha: which job is this ? on master and py3 ?17:44
ajithayes17:45
ajithapy3.6 and master17:45
clarkblinks to the job logs are helpful17:45
clarkbhttps://opendev.org/openstack/requirements/src/branch/master/upper-constraints.txt#L824 py3.8 is the only one I would expect to try and install the old version17:46
gmannajitha: nova need oslo.policy >3.1.0 now as i am using the new flag introduced in oslo policy 3.1.0 which should be available in your CI also.17:46
gmannyeha more log is needed here to check17:46
gmannyeah17:47
ajithasure17:47
ajithamore log of devstack right?17:47
clarkblooks like that was updated recently https://review.opendev.org/#/c/719594/17:47
gmannyeah17:47
clarkbajitha: specifically the link to your zuul jobs17:47
clarkbor I guess it doesn't have to be zuul17:48
clarkbbut third party ci are supposed to publish logs (maybe this isn't third party ci?)17:48
ajithaactually we wont populate logs if it failed. i shall send the recent success link.. and current devstack log17:49
ajithaits thirdparty nimble CI17:49
gmannajitha: devstack log should give more info on what constrained are used and installed17:50
ajithasure will paste in paste.openstack.org17:51
clarkbajitha: note there is a size limite on paste.openstack.org and your devstack logs are likely to go over it17:51
ajithayes.. what other options?17:51
clarkbajitha: I think gist on github may not have size limits. Not sure about other paste bins. You could also run the job and publish the logs17:52
clarkbyou are supposed to do that anyway aiui17:52
ajithasure.. thanks17:52
gmanntry to paste where you find 'oslo.policy ' but you said error is skipped in devstack ?17:53
gmannajitha: note its all working in upstream CI17:54
ajithayes error is skipped in devstack(./stack.sh).. But stopped while running gate18:00
*** gfidente is now known as gfidente|afk18:00
ajithaRequirement already satisfied: pyperclip===1.8.0 in /usr/local/lib/python3.6/dist-packages (from -c /opt/stack/new/requirements/upper-constraints.txt (line 536)) (1.8.0)18:00
ajithaERROR: nova 20.1.0.dev1681 has requirement oslo.policy>=3.1.0, but you'll have oslo-policy 3.0.3 which is incompatible.18:00
ajithaInstalling collected packages: nova18:00
ajitha  Attempting uninstall: nova18:00
ajithaabove is the skipped one18:01
ajithashall send you the devstack log file clarkb and gamn ?18:01
gmannajitha: this is not skipped, this show it failed- http://paste.openstack.org/show/792492/18:01
ajithathis is devstack-early.txt18:02
clarkbajitha: are you reusing test nodes?18:02
gmannajitha: not the success one but the one failing. if you can paste the 'oslo.policy' logs so that i can check on what version it was installed and what constrained was used18:02
ajithaskipped is when i execute devstack alone18:02
clarkbI wonder if you've got an older package installed and pip isn't wanting to upgrade it for some reason18:02
gmanni am suspecting you are using old constraint from old requirement repo not master18:02
clarkbgmann: oh ya that could do it too18:03
ajithayes i reused first.. even in fresh machine i got the same error..18:03
ajithai doubt whether it will work with py3.6?18:05
ajithaand 18.04?18:06
gmanncheck what constraint used for oslo.policy. there should be this log - "Collecting oslo.policy===3.1.0"18:07
gmannor other version if old constraint18:07
gmannif it is 3.1.0 then we can go to next step like clarkb mentioned on pip did upgrade/installed or not ?18:08
ajithano its 3.0.318:11
ajithahttp://paste.openstack.org/show/792497/18:11
gmannajitha: ok then your requirement repo is not up to date where constraint has been updated18:12
ajitharoot@openstack-ubuntu-iscsi-backup:/opt/stack/new# ls -alht requirements/18:12
ajithatotal 160K18:12
ajithadrwxr-xr-x 43 stack stack 4.0K Apr 21 08:13 ..18:12
ajithadrwxr-xr-x 10 stack stack 4.0K Apr 21 07:44 .18:12
ajitha-rw-r--r--  1 stack stack  26K Apr 21 07:44 upper-constraints.txt18:12
ajithaoslo.policy===3.0.3;python_version=='3.7'18:14
ajithathey have given18:14
gmannyeah these are old constraint and they got updated ~7 days ago. is /opt/stack/new/requirements latest ?18:15
*** ralonsoh has quit IRC18:16
ajithais18:17
ajithayes18:17
ajithaeven in other CI  logs i have seen as collecting 3.0.318:17
ajithahttp://openstack-logs.purestorage.com/26/721626/1/check/PureISCSIDriver-tempest-dsvm-bionic-aio-multipath-chap/a6fa41d/logs/18:18
gmannajitha: humm. this should be in if latest requirements repo https://review.opendev.org/#/c/719594/118:18
ajithaok18:18
ajithafor every gate execution it will get a fresh clone right?18:19
ajithaof devstack18:19
gmannhttp://openstack-logs.purestorage.com/26/721626/1/check/PureISCSIDriver-tempest-dsvm-bionic-aio-multipath-chap/a6fa41d/logs/devstacklog.txt.gz#_2020-04-21_14_14_47_28318:20
gmannit checkout the old one, older than oslo.policy constarint update18:21
ajithaok18:21
gmanndevstack is not cloning the fresh because /opt/stack/new/requirements already exists18:23
gmannbut you said it is fresh node/installation with no /opt/stack/new/requirements ?18:24
ajithayes.. i do remove /opt/stack/new/*18:25
ajithafor every job18:26
ajithawhen this oslo.policy constarint update happened today right?18:27
gmannnot today, 8 days ago - https://review.opendev.org/#/c/719594/118:28
ajithaok i will check once, after removing /opt/stack18:28
gmanneven pre cloned requirement repo should be latest one which devstack detected and did not clone it again18:28
gmanngoing for lunch, will be back18:29
clarkbajitha: gmann if ERROR_ON_CLONE is true then it won't update the repos18:29
clarkbI would double check that isn't set18:29
clarkbif it is set then your ci system is expected to provide the correct repo state18:29
ajithasure.. that is not set18:29
gmannyeah, that is true18:29
gmannajitha: is it? - http://openstack-logs.purestorage.com/26/721626/1/check/PureISCSIDriver-tempest-dsvm-bionic-aio-multipath-chap/a6fa41d/console.html18:30
gmannif you keep the latest requirement repo or let devstack clone it fresh will work18:30
*** gmann is now known as gmann_lunch18:31
ajithaclarkb: should i set that flag ERROR_ON_CLONE?18:33
clarkbajitha: no, not necessarily. Its just common in CI systems so wanted to rule it out18:34
clarkbdo you have a specific ref set? also where are you cloning from?18:34
clarkbwould be good to confirm those values even if using the defaults18:34
ajithaclarkb https://ftp.nimblestorage.com/openstack_ci/iscsi/58/718758/2/check/nimble-iscsi-driver-dsvm-volume/e602519/logs/local.conf18:39
clarkberror on clone is set there18:40
clarkbso devstack won't update your git repos18:40
ajithayes sorry..18:41
ajithai should remove and execute?18:41
ajithaclarkb i should remove and execute?18:42
clarkbnot necessarily18:42
clarkbwhat that means is your CI system is currently setting up the repo state18:42
clarkband that is where you need to look for why requriements isn't updated18:43
clarkbare you using zuul? if so which version?18:43
ajithayes zuul 218:43
clarkbok with zuulv2 devstack-gate was responsible for updating the repos to the correct version. Are you using devstack-gate?18:44
ajithayes18:45
ajithadevstack-gate18:45
clarkbok so now what you need to do is look at devstack-gate logs and see how it is updating openstack/requirements18:45
clarkband work from there to find out why it isn't pulling the latest version18:45
ajithahttps://ftp.nimblestorage.com/openstack_ci/iscsi/58/718758/2/check/nimble-iscsi-driver-dsvm-volume/e602519/18:46
ajithathis is like the logs will be18:46
clarkbajitha: that shows that particular job was for stable/train (whcih won't be as up to date as master18:47
ajithathis is 10 days older.. we have some issues with ftp.. thatsy couldnt update the logs after that18:47
clarkbbut also it uses review.openstack.org/p/ which ended up out of sync for a bit18:48
clarkbI think we thoguht that was fixed yesterday18:48
clarkbcan you rerun the job today and see if it still fails with the oslo.policy problem18:48
*** gmann_lunch is now known as gmann18:51
ajithasorry clarkb.. that is a train commit18:52
ajithahttps://ftp.nimblestorage.com/openstack_ci/iscsi/58/721058/1/check/nimble-iscsi-driver-dsvm-volume/f6c5929/18:52
ajithasure.. i will rerun it now18:53
ajithaclarkb oslo.policy===2.4.1;python_version=='2.7'19:03
ajithaoslo.policy===3.0.3;python_version=='3.6'19:03
ajithaoslo.policy===3.0.3;python_version=='3.7'19:03
ajitha in requirements.txt.. may be is it like this for ubuntu 18.04??19:03
clarkbajitha: no it isn't distro specific its global19:03
ajithasorry i am new to this.. thats y the trouble19:04
ajithaok19:04
clarkbI have meetings now but I think the next step is for someone to clone from review.openstack.org/p/openstack/requirements and check it outside of your ci system19:04
clarkbgmann: ^ fyi19:04
gmannok19:04
clarkbif that is still otu of date mordred was the person debugging it19:05
clarkbI've just cloned it and it is out of date19:10
clarkbso I think we still haven't solved that entirely19:11
clarkbI think I may know why19:11
clarkbgoing to try a thing19:11
gmannyou mean this  - review.openstack.org/p  ?19:11
clarkbyes19:11
gmannahh19:11
ajithaclarkb you are saying about my issue?19:12
clarkbajitha: yes, I'm testing something really quick19:13
ajithaclarkb: thanks19:13
clarkbok that didn't fix it. I'll bring it up with mordred as he was driving this19:13
clarkbgmann: we should have d-g stop cloning from review.openstack.org/p/19:14
*** slaweq has quit IRC19:14
clarkbmaybe lets see what mordred says19:14
ajithaSo it will be oslo.policy==3.0.3 for everyone right?.. i spend hours on analyzing19:15
gmannthat whats i was thinking whether to fix d-g or wait for users to move to zuulv3 in V cycle. even we move all upstream CI to zuulv3 but still third party CI need it ?19:15
clarkbgmann: at some point we have to retire d-g19:16
clarkbit isn't being maintained properly anymore19:16
gmanntrue19:16
clarkbajitha: no, the issue is specific to devstack-gate19:16
clarkbajitha: and very little uses devstack-gate anymore as it hasn't been maintained for a few years19:16
ajithaok19:16
gmannajitha: you are not planning to move to zuulv3 ? just making sure that devstack-gate is not you are expecting to be maintained for ling term.19:17
gmannlong19:18
*** slaweq has joined #openstack-qa19:20
ajithayes.. we thought to move recently.. but it was working fine.. so didnt think off later.. will plan19:22
gmannthanks.19:26
ajithawill the devstack error will be solved today?19:26
clarkbajitha: I don't know19:28
ajithaclarkb19:30
ajithaok19:30
AJaegergmann: could you review https://review.opendev.org/721606 later, please? I just noticed that we might need this...19:30
ajithaclarkb and gmann: Thanks for the help in figuring out the issue19:32
gmannajitha: np! sorry for not solving it for you.19:37
gmannAJaeger: commented.19:37
AJaegergmann: if we call tox, we need both since both are used currently. If we use it internally only, we can use TOX_CONSTRAINTS_FILE directly.19:40
AJaegertools/tempest-plugin-sanity.sh looks like internal use - but please confirm19:40
AJaegerwhile roles/run-tempest/tasks/main.yaml is calling out-of-repo files, so needs both19:40
gmannAJaeger: yeah, almost all tox.ini use UPPER_CONSTRAINTS_FILE not sure what all moved to TOX_CONSTRAINTS_FILE19:43
AJaegergmann: it's a slow move, I think...19:43
gmannyeah, and for tempest tox, i remember it is set from different places too devstack, grenade, d-g, tempest plugins etc19:44
AJaegerdevstack does not set UPPER_CONSTRAINT, I checked - or what is set?19:45
gmannit is set on stable branch. on those using master tempest also but let me check19:46
AJaegerlet me check other repos...19:46
AJaegerwe should always set both19:46
gmannits on devstack rocky which use master run-tempest role19:48
AJaegerwill check, thanks19:48
gmannbut my concern is of tox.ini still use UPPER_CONSTRAINTS_FILE then why to set both. or we should plan for complete move soem time ?/19:49
gmannsometime19:49
openstackgerritAndreas Jaeger proposed openstack/devstack-gate master: Set TOX_CONSTRAINTS_FILE  https://review.opendev.org/72171819:52
AJaegerwe need to plan for a move, first repos use TOX_CONSTRAINTS_FILE...19:55
openstackgerritAndreas Jaeger proposed openstack/tempest master: Set TOX_CONSTRAINTS_FILE  https://review.opendev.org/72160620:00
*** ajitha has quit IRC20:02
openstackgerritGhanshyam Mann proposed openstack/tempest master: Use stable constraint in tox to release new tag for Ussuri  https://review.opendev.org/72057820:08
clarkbajitha is gone now?20:09
clarkbfwiw I think the thing I did earlier may have actually addressed this for requirements20:09
clarkbit seems up to date now20:09
gmannkopecmartin: masayukig let's do this also before tempest release so that we can keep the tox constraint compatible with the source code of tag -https://review.opendev.org/#/c/720578/20:09
clarkbso I think rerunning the jobs at this point might work as long as no other stale repos cause it problems20:09
clarkbgmann: ^ fyi20:09
gmannkopecmartin: masayukig and as soon as release is done we will revert it to master constraint20:10
gmannclarkb: i think ajitha did re-run ?20:10
gmannor no ?20:10
kopecmartingmann: ok20:12
gmannkopecmartin: masayukig this can avoid setting the env var for constraint which i hacked during rocky testing on lot of places, devstack, grenade, d-g, heat plugin etc20:12
*** paras333 has quit IRC20:14
openstackgerritGhanshyam Mann proposed openstack/tempest master: Use the master constraint again in tox.ini  https://review.opendev.org/72172420:17
openstackgerritVictoria Martinez de la Cruz proposed openstack/devstack-plugin-ceph master: Updates script to use latest version of Ceph  https://review.opendev.org/67672220:17
gmannkopecmartin: masayukig FYI. this is kind of revert of that once Tempest 24.0.0 is released - https://review.opendev.org/#/c/721724/120:18
clarkbgmann: rerun again20:19
gmannok.20:19
AJaegergmann: I answered your comment on 721606  - I don't know what syntax you propose ;( Could you help, me please?20:29
gmannAJaeger: ah, I have not tried that actually or do not know if that is possible :). I was thinking if you know some hacking....20:31
AJaegergmann: I don't - sorry ;(20:32
*** paras333 has joined #openstack-qa20:37
*** nweinber has quit IRC20:39
openstackgerritVictoria Martinez de la Cruz proposed openstack/devstack-plugin-ceph master: Updates script to use latest version of Ceph  https://review.opendev.org/67672220:43
*** paras333 has quit IRC21:38
openstackgerritGhanshyam Mann proposed openstack/patrole master: Update compute tests to adopt new policies  https://review.opendev.org/72060121:41
*** slaweq has quit IRC21:42
*** paras333 has joined #openstack-qa21:52
*** raildo has quit IRC22:15
*** rcernin has joined #openstack-qa22:17
*** paras333 has joined #openstack-qa22:25
openstackgerritMerged openstack/devstack-plugin-cookiecutter master: [ussuri][goal] Update contributor documentation  https://review.opendev.org/72137522:41
openstackgerritGhanshyam Mann proposed openstack/qa-specs master: [ussuri][goal] Update contributor documentation  https://review.opendev.org/72137322:45
openstackgerritMerged openstack/tempest-plugin-cookiecutter master: [ussuri][goal] Update contributor documentation  https://review.opendev.org/72137222:46
openstackgerritGhanshyam Mann proposed openstack/os-testr master: [ussuri][goal] Update contributor documentation  https://review.opendev.org/72111222:47
openstackgerritMerged openstack/karma-subunit-reporter master: [ussuri][goal] Update contributor documentation  https://review.opendev.org/72137422:52
*** paras333 has quit IRC22:55
openstackgerritMerged openstack/openstack-health master: [ussuri][goal] Update contributor documentation  https://review.opendev.org/72111823:01
openstackgerritGhanshyam Mann proposed openstack/tempest-stress master: [ussuri][goal] Update contributor documentation  https://review.opendev.org/72112023:02
*** tosky has quit IRC23:03
masayukiggmann: +A for https://review.opendev.org/#/c/720578/ .23:12
gmannmasayukig: thanks23:27
openstackgerritGhanshyam Mann proposed openstack/patrole master: Update compute tests to adopt new policies  https://review.opendev.org/72060123:34
gmannmasayukig: can you review these also - https://review.opendev.org/#/q/topic:project-ptl-and-contrib-docs+status:open+owner:self23:34
gmannhttps://review.opendev.org/#/q/topic:project-ptl-and-contrib-docs+status:open23:35
masayukiggmann: sure, will do23:35
masayukiggmann: And, I'm now filling the form for the PTG registration, https://openstackfoundation.formstack.com/forms/june2020_virtual_ptg_survey And, I'm wondering the number of attendees, and "Are there other groups we need to avoid scheduling conflicts with?"23:36
gmannmasayukig: as per last counted I think we are around 7-8 people but we can consider 10 or 15 max23:37
gmannmasayukig: for me, I would like to avoid conflcit with nova, TC23:38
masayukiggmann: thanks! OK, I'll put 10 as attendees, and Nova and TC to avoid conflict23:40
gmannthanks.23:40
gmannmasayukig: also sending that etherpad again to ML to ask for topic to discuss will be good. Previously it was with physical  PTG so people might not have added the topic.23:41
gmannconsidering their absent for physical PTG23:42
openstackgerritGhanshyam Mann proposed openstack/patrole master: Add releasenote to tag the Patrole for Ussuri release  https://review.opendev.org/72130523:43
*** paras333 has joined #openstack-qa23:46
*** paras333 has quit IRC23:51
*** paras333 has joined #openstack-qa23:52
*** paras333 has quit IRC23:56

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!