Wednesday, 2022-06-08

opendevreviewMasayuki Igawa proposed openstack/cinder master: Doc: Fix way to update default quota value for a new project  https://review.opendev.org/c/openstack/cinder/+/84506901:07
opendevreviewKeigo Noha proposed openstack/os-brick stable/train: multipath/iscsi: iSCSI connections are not reinitiated after reboot  https://review.opendev.org/c/openstack/os-brick/+/82904704:22
*** abhishekk is now known as akekane|home05:01
*** akekane|home is now known as abhishekk05:01
whoami-rajatrosmaita, hey, i think you missed out this patch in the DB series https://review.opendev.org/c/openstack/cinder/+/837538/09:15
opendevreviewMerged openstack/cinder-tempest-plugin master: Remove stable/victoria job and fixing job description  https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/84368510:11
opendevreviewMerged openstack/cinder master: Remove redundant line from host_manager.py  https://review.opendev.org/c/openstack/cinder/+/84492010:11
stephenfinrosmaita: Can you revisit https://review.opendev.org/c/openstack/cinder/+/837538/ please?10:16
stephenfinrosmaita: I also suspect this can be bumped to a +2 now as I've addressed the concern in a follow-up https://review.opendev.org/c/openstack/cinder/+/83754010:17
opendevreviewMerged openstack/cinder master: db: Migrate online upgrade helpers to enginefacade  https://review.opendev.org/c/openstack/cinder/+/83753710:43
opendevreviewBrian Rosmaita proposed openstack/cinderlib master: Add requirements-check job  https://review.opendev.org/c/openstack/cinderlib/+/84502610:50
*** dviroel|afk is now known as dviroel11:19
opendevreviewJean Pierre Roquesalane proposed openstack/cinder master: WIP: Add Cinder NFS driver for Dell EMC PowerStore  https://review.opendev.org/c/openstack/cinder/+/79760811:20
opendevreviewArun KV proposed openstack/cinder master: Reintroduce DataCore driver  https://review.opendev.org/c/openstack/cinder/+/83699612:12
opendevreviewBrian Rosmaita proposed openstack/cinderlib master: Add requirements-check job  https://review.opendev.org/c/openstack/cinderlib/+/84502612:44
opendevreviewJean Pierre Roquesalane proposed openstack/cinder master: Add NVMe/TCP support to Dell EMC PowerStore driver  https://review.opendev.org/c/openstack/cinder/+/81914912:44
opendevreviewVlad Gusev proposed openstack/cinder stable/yoga: RBD: Don't flatten temporary resources  https://review.opendev.org/c/openstack/cinder/+/84503912:53
opendevreviewBrian Rosmaita proposed openstack/cinderlib master: Update doc/requirements.txt  https://review.opendev.org/c/openstack/cinderlib/+/84512612:55
opendevreviewBrian Rosmaita proposed openstack/cinderlib master: Add requirements-check job  https://review.opendev.org/c/openstack/cinderlib/+/84502612:59
opendevreviewVlad Gusev proposed openstack/cinder stable/xena: RBD: Don't flatten temporary resources  https://review.opendev.org/c/openstack/cinder/+/84513013:04
whoami-rajatCinder meeting in #openstack-meeting-alt at 1400 UTC13:59
whoami-rajatjungleboyj rosmaita smcginnis tosky whoami-rajat m5z e0ne geguileo eharney walshh_ jbernard sfernand enriquetaso hemna fabiooliveira yuval tobias-urdin13:59
*** enriquetaso_ is now known as enriquetaso14:02
*** whoami-rajat__ is now known as whoami-rajat14:16
whoami-rajatrosmaita, i might have done a bad copy paste, can you please check the indentation of your topics if they're correctly aligned14:27
rosmaitawhoami-rajat: ack14:28
whoami-rajatsorry about that14:28
rosmaitanp, looks fine14:30
*** dviroel is now known as dviroel|lunch14:47
enriquetaso#startmeeting cinder_bs15:02
opendevmeetMeeting started Wed Jun  8 15:02:01 2022 UTC and is due to finish in 60 minutes.  The chair is enriquetaso. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
opendevmeetThe meeting name has been set to 'cinder_bs'15:02
enriquetasoFull list of bugs15:02
enriquetaso#link http://lists.openstack.org/pipermail/openstack-discuss/2022-June/028887.html15:02
rosmaitanothing like the old cinder BS15:02
enriquetaso:P today's a small one15:02
enriquetaso#topic [IBM Storwize] lsfcportsetmember is being called in the wrong SVC code level15:02
enriquetaso#link https://bugs.launchpad.net/cinder/+bug/197649915:02
enriquetasoFix proposed to master already, i've already reviewed, feel free to check it15:02
rosmaitasounds like a pure storwize problem15:03
enriquetasoit is15:03
enriquetaso#topic When creating volume from an image, the image is fetched twice15:03
enriquetaso#link https://bugs.launchpad.net/cinder/+bug/197786815:03
enriquetasoI know it's not the best idea to download the same image twice, but that's how we currently do it. However, I am not quite sure how to respond to this bug report. I wonder if whoami-rajat or another interested fellow could help me with this.15:03
whoami-rajatdon't think that's true but need to check ...15:03
rosmaitalaunchpad is really slow for me today15:03
eharneyyeah i can't even load the bugs15:03
rosmaitaenriquetaso: you broke the bug tracker!!!15:04
eharneyi think it is true that it can happen twice, but we do limit it w/ locking15:04
enriquetasotrue.. was working half an hour before ..15:04
enriquetasohahaha15:04
enriquetasoeharney, good question, i'm not sure15:05
enriquetasoi have to check 15:05
rosmaitalaunchpad is apparently in the middle of an update15:05
enriquetasooh15:05
enriquetasowell, that was the last bug for todays meeting anyway15:05
geguileobtw we kind of have 6 broken os-brick unit tests15:05
eharneyonly 6?15:06
geguileoit doesn't affect the gate since they use an old OS15:06
whoami-rajatI can take a look (if i get time from the pile of pending reviews)15:06
geguileowhoami-rajat: I have a local patch15:06
geguileowhoami-rajat: I'll submit it shortly15:06
enriquetaso#action (enriquetaso): check when happen twice and if we limit it with locking15:06
whoami-rajatgeguileo, no, it was for the previous bug ... sorry15:06
enriquetasowhoami-rajat, thanks!15:06
geguileolol15:06
enriquetasolol15:06
* geguileo realizing the world doesn't revolve around him15:07
enriquetasodo we have patches for the os-brick unit test failures? geguileo 15:07
rosmaitageguileo: we always assume that if you file a bug, you already have a fix15:07
rosmaita:D15:07
whoami-rajat:D thanks geguileo for finding and fixing it15:07
geguileoenriquetaso: I have it locally, but it's the first one of the new rebased nvmeof series, so will send it in an hour or so15:07
eharneyenriquetaso: here's a starting point re: locking... https://review.opendev.org/c/openstack/cinder/+/55660715:07
geguileorosmaita: lol15:07
whoami-rajatwhat rosmaita said is true!15:08
enriquetasothank eharney 15:09
enriquetaso#topic open discussion15:09
enriquetasodo we have more bugs to keep an eye on geguileo ?15:09
geguileoenriquetaso: not that I have filed15:10
enriquetasocinder team: feel free to proposed bugs now 15:11
opendevreviewGorka Eguileor proposed openstack/os-brick master: Support extending encrypted volumes  https://review.opendev.org/c/openstack/os-brick/+/83605915:13
opendevreviewGorka Eguileor proposed openstack/os-brick master: NVMe-oF: Consolidate code paths  https://review.opendev.org/c/openstack/os-brick/+/83606015:13
opendevreviewGorka Eguileor proposed openstack/os-brick master: NVMe-oF: Disconnect subsystems  https://review.opendev.org/c/openstack/os-brick/+/83606215:13
opendevreviewGorka Eguileor proposed openstack/os-brick master: Support shared_targets tristate value  https://review.opendev.org/c/openstack/os-brick/+/83606315:13
opendevreviewGorka Eguileor proposed openstack/os-brick master: Fix Unit Test failures due to host's ANA support  https://review.opendev.org/c/openstack/os-brick/+/84514915:13
enriquetasocool15:13
enriquetasoguess that was all for today!15:13
geguileoenriquetaso: rosmaita whoami-rajat ^ that last one is the fix for unit tests15:13
enriquetasogeguileo++15:13
rosmaitageguileo: ack15:13
whoami-rajatack15:13
enriquetasothank you for attending!15:13
geguileoit's a oneliner, so easy review15:13
enriquetaso#endmeeting15:14
opendevmeetMeeting ended Wed Jun  8 15:14:31 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:14
opendevmeetMinutes:        https://meetings.opendev.org/meetings/cinder_bs/2022/cinder_bs.2022-06-08-15.02.html15:14
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/cinder_bs/2022/cinder_bs.2022-06-08-15.02.txt15:14
opendevmeetLog:            https://meetings.opendev.org/meetings/cinder_bs/2022/cinder_bs.2022-06-08-15.02.log.html15:14
whoami-rajatthanks enriquetaso !15:14
eharneycinder-tempest-plugin?15:14
enriquetasooh true, let's wait for gmann 15:15
gmanno/15:15
enriquetasohello gmann 15:16
enriquetasoit's not clear what the correct process is when we are adding tests to cinder-tempest-plugin that require newly landed changes in tempest15:16
enriquetasojust saying "assume it's all running master" means that people who want to install tempest and our plugin themselves from pip will just break15:16
gmannabout compatibility of tempest and tempest plugins are 1. we test all supported stable branch (Wallaby -> yoga) with tempest master and all tempest plugin master so we can 100% confirm the compatibility of both with that time period. 15:16
* enriquetaso copy-paste from the cinder meeting15:17
eharneymy concern isn't really about stable branches necessarily15:17
eharneycinder-tempest-plugin says in requirements.txt that it requires tempest>=27.0.0 currently15:17
gmannif there is old tempest is pinned in stable brnach like stable/victoria then yes cinder-tempest-plugin master and Tempest old pin in stable/victotria cannot be guaranteed as compatible 15:17
gmanneharney: tempest in requirements.txt is not sure how well that is maintained.15:18
eharneyif you add new functionality to tempest and then write new test code in cinder-tempest-plugin that needs that functionality, don't you need to bump that version?15:18
eharneyi'm just asking how it should be done.15:18
eharneybecause what we are doing now seems incorrect15:18
eharneyand will break people consuming cinder-tempest-plugin outside of the gate15:18
gmannbut we can say anyone that current tempest or plugins master are all good to use for stable/wallaby-> master as we test them in upstream15:18
gmanneharney: we can bump but in our upstream testing we use master version only. tempest is not in requirements repo upper constraints15:19
gmannso we can keep up to date version in requirements.txt on plugin side but that needs to be best effort.15:20
eharneyi'm not talking about upstream testing, i'm talking about the fact that we cut releases of cinder-tempest-plugin, and presumably somebody is expecting those to work15:20
gmanneharney: yes you can do that for that reason.15:20
gmannor best way to find the compatible version of both is from release page too https://releases.openstack.org/yoga/index.html#tempest-plugins15:21
gmanneharney: enriquetaso ^^ that page is best effort to tell production testing also what is compatible version of plugin and tempest for that release15:22
gmannbut again I will say master are always compatible as we test them and guarantee. 15:22
gmannfor example new cinder-tempest-plugin is released 1.7.0 today. so we can say it is compatible with latest tempest released version 31.0.0 15:23
gmanneither through release page or via requirement.txt15:23
enriquetasoso we need to update the tempest version in the cinder plugin 15:23
rosmaitagmann: ok, and if we need some tempest changes for something we have in cinder-tempest-plugin, do we ask for a tempest release?15:24
rosmaita(so we can coordinate cinder-tempest-plugin and tempest?)15:24
gmannwe can for record but remember that will be best effort and need to be done carefully as we do not use requirement.txt file in our upstream tresting15:24
enriquetasoi.e https://review.opendev.org/c/openstack/tempest/+/843542 15:24
gmannrosmaita: yes, that we can do always, any time in between of release or so15:25
gmannenriquetaso: yes, we can cut a tempest release for that and mention in requirement.txt file too as we know by knowing the changes15:25
rosmaitaok, so it sounds like whenever we release a new version of cinder-tempest-plugin, we should make sure it works with the most recent tempest release15:25
rosmaitaand if it doesn't ask for a new release15:26
gmannrosmaita: yes. that is true15:26
rosmaita(i guess we should check *before* we release cinder-tempest-plugin, though)15:26
gmannthat way release page also will be up to date and also yoou can keep up to date in cinder-temepst-plugin requiremnts.txt file15:27
enriquetasothat would be nice, i think we need a new tempest release for  https://review.opendev.org/c/openstack/tempest/+/843542 15:27
gmannrosmaita: enriquetaso eharney yes, like we want to release plugin as it has good amount of changes and need tempest to be released and we will do both release15:27
rosmaitaok, cool15:28
gmannenriquetaso: right, tempest.scenario.manager is a stable interface for plugins and any change in that is all good to be released15:28
gmannso in current case we can release tempest now or can wait for more time if you want to wait for more things in cinder-temepst-plugin to be released together 15:29
gmannjust ping us in qa whenever you want to do and we release tempest first and them you can update requiremnts.txt and release cinder-temepst-plugin15:29
enriquetasoi think we could wait for some cinder-tempest-plugin so we could release them together, what do you think eharney ?15:29
enriquetasogmann++15:30
enriquetasosounds good to me15:30
rosmaitagmann: thanks, this sounds good15:30
eharneywell you have to release tempest first, not together, but yes15:30
enriquetasoack15:30
enriquetasothanks gmann 15:30
gmanneharney: yes, whenever you are ready for cinder-tempst-plugin release ping me in qa chanel and will do tempest release15:31
gmannand after that you can do plugin release15:31
eharneyi may not be me, but yes, sounds good15:32
gmannenriquetaso: as eharney mentioned requirement.txt file needs to have latest release tempest so order can be 1. release tempest 2. update requiremnts.txt file with new released tempest version 2. release cinder-tempest-plugin15:32
eharneyit may not*15:32
eharneythanks!15:32
gmannsure15:33
enriquetaso\o/15:33
gmannrosmaita: enriquetaso eharney whoami-rajat__ I will documents the process in tempest doc also and you can also refer that in your doc. it will be helpful for other plugins also15:34
enriquetasogmann, that would be fantastic 15:34
rosmaitagmann: thanks, that will be helpful ... it is good to know that instead of waiting for a tempest release, we can ask for one when it's needed15:34
gmannsure I will do in next hr or so otherwise we keep forgetting :)15:34
gmannrosmaita: yes. even we end up doing tempest release every week it is all good.15:35
rosmaitayeah, releases are cheap!15:35
whoami-rajat__gmann++ thanks15:37
whoami-rajat__and I've a bunch of cinder tempest plugin patches, would like to get them before the release :)15:37
whoami-rajat__this one had a lot of reviews at one point but got stuck, would be good to get some reviews on this https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/79575315:38
*** whoami-rajat__ is now known as whoami-rajat15:38
gmannand feel free to add me in cinder-tempest-plugin changes review if any question from tempest side or best practice on plugins using tempest interface15:38
whoami-rajatsure, that would be great help15:39
gmannour best effort is to avoid breaking plugins due to tempest future change and we have improved a lot now which was really bad in past. so using tempest interface in right way if the key15:39
gmann* is the key15:39
whoami-rajatwould be helpful to have tempest stable interface for API as well although i don't have many things that depend on it atm15:41
gmannand also as I talked to whoami-rajat, anytime you think this tempest plugin code is good to use in plugins but we need to make tempest a stable interface feel free to reachout to us and we can do that in best possible wa,y. and add that in plugin stable interface - https://docs.openstack.org/tempest/latest/plugins/plugin.html#stable-tempest-apis-plugins-may-use 15:41
gmannwhoami-rajat: right ^^ we both were thinking same for that15:42
gmannwhoami-rajat: we can judge the amount of benefits it will give or so. for example if there is large amount of duplicate code in tempest.volume.base and cinder-tempest-plugin then we can think of making that code as stable interface in tempest15:43
whoami-rajatgmann, yes, I understand it's going to take some amount of work and resources from tempest team so better to do it if we have enough benefits15:44
whoami-rajatwe can retrospect it sometime15:44
gmannyeah15:50
*** dviroel|lunch is now known as dviroel16:05
Roamer`Hi, here's a possibly dumb question. We have Glance configured to use Cinder as a backend, and we have specified in the glance-api.conf file that it should use a specific project to keep its images in. If we create a Glance image via a file upload, everything is fine and good, it is created in the correct project. If, however, we try to create a Glance image from a Cinder volume in another 16:38
Roamer`project, openstackclient issues a os-volume_upload_image API call (as it should) and... the new volume is cloned correctly *into the same project as the original Cinder volume*... so then Cinder tries to tell Glance "here's the location for your new image", Glance says "let me just do a quick check, give me the volume details for this volume *in my project*" and Cinder goes "nah, there is no 16:39
Roamer`such volume in your project"16:39
Roamer`from what I can see in the os-volume_upload_image API call's parameters, there does not seem to be a way to tell it to create the volume in another project16:39
Roamer`so..... how can we create a Glance image from a Cinder volume in a different project?16:39
Roamer`this is all on Xena, BTW16:40
Roamer`when I said "is cloned correctly" above, I meant "the clone operation completes successfully with the parameters it was given"16:40
Roamer`...into the wrong project.16:40
Roamer`so yeah, what happens later is that Cinder says "okay, this operation failed, let's do the full attach-and-run-dd dance" and that works correctly16:43
opendevreviewGorka Eguileor proposed openstack/os-brick master: NVMe-oF: Consolidate code paths  https://review.opendev.org/c/openstack/os-brick/+/83606016:49
opendevreviewGorka Eguileor proposed openstack/os-brick master: NVMe-oF: Disconnect subsystems  https://review.opendev.org/c/openstack/os-brick/+/83606216:49
opendevreviewGorka Eguileor proposed openstack/os-brick master: Support shared_targets tristate value  https://review.opendev.org/c/openstack/os-brick/+/83606316:49
Roamer`hmmmm, okay, so I just found the image_upload_use_internal_tenant config option16:49
Roamer`...is that the way to go? should we configure Glance to use the Cinder internal tenant instead of its own project?16:50
Roamer`so, yeah, ignore all this17:13
Roamer`it turned out to be a misconfiguration on our part: a coworker clearly meant to use the internal tenant, but forgot to configure it17:14
Roamer`now everything seems to work17:14
Roamer`actually... everything almost works, I'd forgotten that I'd made a small change a while ago: I think there is another bug related to the URLs that Glance uses to reference Cinder-volume-backed images: when cinder.volume.manager.VolumeManager._clone_image_volume_and_add_location() tries to give cinder://<volume-id> to Glance, Glance does not accept it, since it does not contain a Glance store 17:42
Roamer`name (e.g. "main", something like cinder://main/<volume-id>)... and, TBH, I don't know what to do about that, because I'm not sure that Cinder has a way to know the name of the Glance backend to specify :(17:42
Roamer`...I wonder if it could be made into a configuration option17:42
Roamer`right now, I will modify cinder/volume/manager.py and hardcode cinder://main/<volume-id>, but that doesn't really seem like a viable solution :)17:43
Roamer`maybe I snould file a bug about that, because Glance API v2 certainly does not want to work with cinder://<volume-id> URLs17:48
Roamer`of course, making it into a configuration option would imply that people only want to use a single Cinder-volume-backed Glance backend, which might not be the case - there might be two Glance backends with different settings... and I have no idea how that could possibly work when uploading a volume to a Glance image.17:50
whoami-rajatRoamer`, hey, thanks for finding this issue, it is indeed a valid issue18:02
whoami-rajatRoamer`, we added support for multiple cinder stores in i guess victoria and there have been a bunch of code paths that were not updated to take into account the new location format18:02
whoami-rajatRoamer`, we added a volume type extra specs parameter 'image_service:store_id' but unfortunately it only updates the location metadata and not the URL18:03
whoami-rajatRoamer`, if you can file a bug, i can work on a fix for your issue :)18:04
Roamer`whoami-rajat, okay, I will, thanks a lot!18:04
whoami-rajatRoamer`, np, may i know which cinder backend are you using in your deployment? and are you using multiple glance cinder stores?18:06
Roamer`whoami-rajat, glance-api.conf says enabled_backends = basic:file, readonly:http, main:cinder  and in Cinder we use the storpool backend18:07
Roamer`whoami-rajat, so, if I understand you right, we should now add the image_service:store_id=main extra spec to all our volume types18:07
whoami-rajatack so it's a mix of multiple stores with only one single store18:07
Roamer`and then fix cinder/volume/manager.py to honor that18:07
whoami-rajatRoamer`, yes, that seems to be the right approach18:08
whoami-rajats/single/cinder18:08
Roamer`(of course, I could also whip up a quick Glance fix to check whether there is only a single :cinder backend defined in the config, but that seems less than ideal :))18:08
whoami-rajatI think glance is moving towards defaulting multiple stores only so even if you want to configure a single store, it will be in the multiple stores format18:10
Roamer`yeah, I meant something like patch glance_store.multi_backend.get_store_from_store_identifier() to check for store_identifier=None and, if so, go through all the defined backends and see if there is only one that handles that specific scheme... but that seems much, much, much worse than fixing Cinder to fully honor image_service:store_id :)18:12
Roamer`whoami-rajat, thanks for letting me know about that extra spec, I had somehow managed to completely miss it!18:13
whoami-rajatRoamer`, np, thanks for reporting the issue, you found a bug in the original implementation which was targeted to address your usecase, see commit message here: https://github.com/openstack/cinder/commit/350973f3dddd8e3b1d521238c69a5bd8c8df3fec18:15
whoami-rajatRoamer`, will you be proposing an upstream fix or just patch it in your deployment?18:16
Roamer`whoami-rajat, I think I can propose a simple upstream fix, if you'd be okay with that18:18
whoami-rajatRoamer`, sure, let me know and i will review it18:19
Roamer`thanks!18:19
Roamer`I think I can do that a bit later tonight or early tomorrow, I really need to go grab something to eat now18:19
whoami-rajatsure anytime18:20
geguileorosmaita: the cinderlib gate failure is weird... I can't reproduce it locally with the same dependencies, same python hash seed, and same execution order...18:21
Roamer`whoami-rajat, just one more thing: should I make it so that if the volume type's extra specs do *not* have this setting, then assume that Glance does not use multiple backends and send an old-style cinder://<volume-id> URL, otherwise send a cinder://<store-name>/<volume-id> one?18:22
Roamer`<store-id>, of course18:22
whoami-rajatRoamer`, yes, correct18:22
Roamer`okay, thanks again!18:22
rosmaitageguileo: i don't understand it either18:23
whoami-rajatnp18:24
rosmaitageguileo: we haven't had a lot of patches posted to cinderlib, so it's hare to tell when it started: https://zuul.opendev.org/t/openstack/builds?job_name=cinderlib-tox-py39&project=openstack/cinderlib18:25
geguileorosmaita: what I don't understand is how I can't reproduce the issue18:26
geguileoI've reproduced dozens of gate issues with this same procedure...18:27
geguileomostly for flaky gate failures...18:27
geguileoand this is no longer intermitent, this is always failing...18:27
geguileoI can only think that it's the Python version, mine is 3.9.12 running on Fedora and that one is 3.9.5 running on Ubuntu18:29
rosmaitai'm running 3.9.518:31
rosmaitaon Fedora, though18:32
geguileorosmaita: this is kind of crazy  :-(18:44
geguileorosmaita: I was trying to run it in Ubuntu, but ubuntu focal doesn't seem to have python 3.9 as a standar package from the normal repos18:45
rosmaitamaybe it is some kind of packaging problem, then18:45
rosmaitai wonder if we try centos nodes for that job18:45
rosmaitagimme a minute to find the nodeset name18:45
rosmaitai will put up a test patch real quick18:46
opendevreviewBrian Rosmaita proposed openstack/cinderlib master: DNM: use centos-9-stream node for py39  https://review.opendev.org/c/openstack/cinderlib/+/84516718:49
rosmaitageguileo: failure: https://zuul.opendev.org/t/openstack/build/7453076e4bb34676a586d89aecd1294d19:06
geguileorosmaita: is it me, or those are even more failures?19:10
rosmaitai think one more?19:10
rosmaitathere are usually 1419:10
rosmaitai have seen one with 2219:10
geguileorosmaita: nothing, can't make it fail runing on stream-9 either19:16
rosmaitathis is very frustrating19:16
geguileorosmaita: Since I can't reproduce it, I'll try reading the tests and the code tomorrow19:21
rosmaitasounds good19:22
rosmaitai think i figured out the problem with the py36 job, it wants to use the latest importlib-metadata (4.11.4) and that requires python >= 3.7 ... i think it's the same problem i was having yesterday with the requirements job, cinderlib master != zed development19:37
toskyrosmaita: I hit that issue somewhere else (internal stuff) but is there a reason why you need 4.11.4? IIRC the version of py36 is 4.8.something19:38
rosmaitatosky: i don't want 4.11.4 at all, but see the bottom of https://zuul.opendev.org/t/openstack/build/430adc04b01145b3bc6b63837e915386/console#4/0/10/ubuntu-bionic19:40
rosmaitai think i need to override checkout openstack/requirements to stable/yoga so it uses the correct constraints file19:43
opendevreviewBrian Rosmaita proposed openstack/cinderlib master: DNM: use stable/yoga requirements for unit test jobs  https://review.opendev.org/c/openstack/cinderlib/+/84517019:47
opendevreviewWalt proposed openstack/cinder master: Fix and unify capacity calculations  https://review.opendev.org/c/openstack/cinder/+/83124719:50
*** dviroel is now known as dviroel|afk20:27
opendevreviewWalt proposed openstack/cinder-specs master: WIP: Add new volume transaction tracking  https://review.opendev.org/c/openstack/cinder-specs/+/84517621:05
hemnageguileo ^^ I did a rough initial draft of the spec for the idea of volume transaction tracking.   Feel free to read/modify/discuss.21:05
hemnaultimately I want to be able to run 'cinder top'21:06
hemnaand see a live view of what cinder is doing right now.21:06
hemnafirst step towards graceful shutdown and restart of transactions as well.21:06
hemnaI haven't thought everything out, but wanted to have a WIP spec up for review so we can all have a starting point.21:07
hemnarosmaita as well ^^21:07
rosmaitahemna: nice21:08
hemnaIt would be kinda cool to have an external project for transaction tracking, then nova and others could use it as well and one could run 'openstack top'21:09
hemnaand see what all the services are doing at any moment.21:09
opendevreviewBrian Rosmaita proposed openstack/cinderlib master: DNM: use stable/yoga requirements for CI jobs  https://review.opendev.org/c/openstack/cinderlib/+/84517021:11
opendevreviewJean Pierre Roquesalane proposed openstack/cinder master: WIP: Add Cinder NFS driver for Dell EMC PowerStore  https://review.opendev.org/c/openstack/cinder/+/79760821:14
opendevreviewPeter Penchev proposed openstack/cinder master: Send the correct location URI to the Glance v2 API  https://review.opendev.org/c/openstack/cinder/+/84517822:55
opendevreviewPeter Penchev proposed openstack/cinder master: Send the correct location URI to the Glance v2 API  https://review.opendev.org/c/openstack/cinder/+/84517822:55
Roamer`(of *course* I will notice a stray blank line immediately *after* pushing to Gerrit... some things never change)22:56
opendevreviewPeter Penchev proposed openstack/cinder master: Send the correct location URI to the Glance v2 API  https://review.opendev.org/c/openstack/cinder/+/84517823:10
opendevreviewBrian Rosmaita proposed openstack/cinderlib master: Use stable/yoga override for CI jobs  https://review.opendev.org/c/openstack/cinderlib/+/84517023:21

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