14:00:59 #startmeeting sahara 14:01:00 Meeting started Thu May 30 14:00:59 2019 UTC and is due to finish in 60 minutes. The chair is jeremyfreudberg. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:03 The meeting name has been set to 'sahara' 14:01:47 o/ 14:01:49 o/ 14:01:58 #topic news/updates 14:02:20 unfortunately i don't have anything much to report this time 14:03:01 starting new position next week, so once there is some organization to my daily routine again i'll probably become more active 14:03:04 I have a bit of updates, and also I don't remember if I already explained why our gates are failing 14:05:17 nothing from me eiter 14:05:18 either 14:05:48 #topic open discussion 14:06:01 tosky, you can remind us about the gate, or give any other updates 14:07:00 sure 14:07:09 there are two issues: bandit and stestr 14:07:29 both may be fixed by an update of the said softwares, but! 14:07:35 in the right order: 14:08:51 - bandit is the easier one; a regression in bandit 1.6.0 break the way bandit understand the paths, it could be fixed by either excluding bandit 1.6.0 or by using wildcards 14:09:24 - stestr 2.3.1 which was finally set as the upper-constraints few weeks ago fixes various issues with python3 but apparently not a specific issue which makes us fail 14:09:40 I tried to workaround it, but it didn't work; I tried to upgrade stestr and it seems to work 14:09:50 to be more precise... 14:11:21 https://review.opendev.org/#/c/660192/ -> the fix for bandit is always fine; revision 4 is my last test with stestr and it didn't work; revision 3 is a crude solution for upgrading stestr to the last master 14:11:55 I pinged the maintainers, they are waiting to merge a specific change; I will try to find a better workaround in the meantime 14:12:18 of course if a new version of bandit is released in the meantime, the bandit fix won't be needed anymore 14:12:24 got it 14:12:42 and that's it for the gates; I have found an minor issue with python-saharaclient 14:13:03 and also I realized that while we run scenario tests with Python 3, we should probably also run the tempest tests with Python 3 14:13:28 I'd suggest to unconditionally run all APIv2 tests with Python 3 only, as APIv2 has been added together with the proper Python 3 support 14:13:43 suggestion sounds good to me 14:13:53 #link https://review.opendev.org/#/c/661857 14:13:55 ^ for the logs 14:14:03 the meeting logs, that is 14:14:24 and then add a Python 3 test for APIv1; or better, switch the current tempest job to py3 in master and stein too and add a py2 job for stein and master 14:14:55 I tried to fix the saharaclient issue with https://review.opendev.org/#/c/661857/, which worked locally, but for some reasons is failing 14:15:21 I tested it with https://review.opendev.org/#/c/661744/, which also uses https://review.opendev.org/#/c/661771/ (py3 fixes for sahara-tests) 14:16:51 and that's basically it 14:17:07 i like the idea of changing the current job to py3 and adding explicit extra py2 jobs where needed 14:17:30 I was busy with a presentation for my university until this morning, I will be more active with debugging and fixing in the rest of today and tomorrow 14:17:41 sure 14:17:47 thanks for looking into it :) 14:17:57 :) 14:19:13 alright, i guess we can close, unless there is anything else 14:20:10 nothing else from me 14:22:04 ok let's close 14:22:07 thanks all 14:22:11 thanks 14:22:34 #endmeeting