15:01:53 #startmeeting RDO meeting - 2019-08-21 15:01:53 Meeting started Wed Aug 21 15:01:53 2019 UTC. 15:01:53 This meeting is logged and archived in a public location. 15:01:53 The chair is jpena. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:53 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:01:53 The meeting name has been set to 'rdo_meeting_-_2019-08-21' 15:01:53 Meeting started Wed Aug 21 15:01:53 2019 UTC and is due to finish in 60 minutes. The chair is jpena. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:54 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:56 The meeting name has been set to 'rdo_meeting___2019_08_21' 15:02:08 Please add any last-minute topic to the agenda at https://etherpad.openstack.org/p/RDO-Meeting 15:02:10 jpena: o/ 15:02:12 #topic roll call 15:02:16 #chair jcapitao 15:02:16 Current chairs: jcapitao jpena 15:02:17 Current chairs: jcapitao jpena 15:02:18 o/ 15:02:27 #chair zbr 15:02:27 Current chairs: jcapitao jpena zbr 15:02:29 Current chairs: jcapitao jpena zbr 15:02:42 o/ 15:02:54 #chair ykarel 15:02:54 Current chairs: jcapitao jpena ykarel zbr 15:02:55 Current chairs: jcapitao jpena ykarel zbr 15:03:34 o/ 15:03:48 #chair amoralej 15:03:48 Current chairs: amoralej jcapitao jpena ykarel zbr 15:03:49 Current chairs: amoralej jcapitao jpena ykarel zbr 15:05:29 so.. there's not a lot in the agenda :) 15:05:32 #topic open floor 15:05:38 Anything to be discussed? 15:07:35 just one update about centos8 15:07:39 according to https://wiki.centos.org/About/Building_8 15:07:50 it's very close to be ready 15:08:38 #info CentOS 8 is coming soon: https://wiki.centos.org/About/Building_8 15:08:44 nice, but no ETA available for release there 15:08:53 nop 15:09:19 ah, and about 7.7 15:09:36 i've requested to remove ocata and pike 15:10:01 as it's not supported anymore 15:10:02 amoralej, remove buildsys-tags? 15:10:05 no 15:10:06 i mean 15:10:09 removing the repos 15:10:22 when a new minor release is created in centos 15:10:43 it's the time when repos can be removed 15:10:53 ack 15:11:00 from http://mirror.centos.org/centos/7/cloud/x86_64/ 15:11:01 \o 15:11:08 #chair PagliaccisCloud 15:11:08 Current chairs: PagliaccisCloud amoralej jcapitao jpena ykarel zbr 15:11:10 Current chairs: PagliaccisCloud amoralej jcapitao jpena ykarel zbr 15:11:28 as, actualy /7 is a link to the last minor 15:11:40 now is http://mirror.centos.org/centos/7.6.1810/ 15:11:56 when 7.7 is released, there is a new directory and content is copied 15:11:58 from sigs 15:12:25 so i requested to remove EOL releases 15:12:32 ack 15:12:50 amoralej, do you know when packages get available in cr repo 15:13:15 i remember it's before new update is released 15:13:23 yes 15:13:24 http://mirror.centos.org/centos/7/cr/x86_64/Packages/ 15:13:31 they send a mail to centos-devel 15:13:45 i'd say one week before or so 15:13:49 ohhk 15:15:01 amoralej, and regarding, CentOS8, once it's released, we need to request train centos8 tags, right 15:15:10 i see there is new koji instance https://koji.mbox.centos.org/koji/tags 15:15:17 #info CloudSIG repo for ocata and pike will be removed with CentOS 7.7 GA 15:15:37 ykarel, yes, that's the one used for CentOS8 15:15:51 not sure if there will be the same for CBS or a new one 15:16:01 but i think they will move from existing one 15:16:07 we need to stay tuned 15:16:35 yup 15:17:05 one last thing, fedora is bootstraping f32 on python3.8 15:17:31 we may need to fix things and enable bootstrap macros for some packages 15:17:53 i did yesterday for oslotest, but need to keep an eye on it 15:18:30 amoralej, where are u tracking all this, u said u creating etherpad yesterday 15:19:02 dunno, the problem is that i don't find a way to list other that checking my mail 15:19:17 ohhk np 15:20:33 they are creating ftbfs in bz https://bugzilla.redhat.com/show_bug.cgi?id=1743899 15:20:34 bugzilla.redhat.com bug 1743899 in python-oslo-utils "python-oslo-utils fails to build with Python 3.8" [High,New] - Assigned to apevec 15:21:23 they are opening them for real issues that are blocking 15:21:26 which is good 15:21:51 and blocking https://bugzilla.redhat.com/show_bug.cgi?id=1686977 15:21:53 bugzilla.redhat.com bug 1686977 in Changes Tracking "Python 3.8" [Unspecified,Modified] - Assigned to mhroncok 15:22:11 so we may look for bz blocking that and list by package 15:22:14 i'll check 15:22:27 ack 15:23:35 you want to proactively update the package before having a bz ticket ? 15:23:42 hmm too many failures https://koji.fedoraproject.org/koji/builds?prefix=p&userID=churchyard&order=-build_id&state=3 15:24:56 we can start fixing the ones with bz 15:25:42 we can also check all packages and there f32 builds https://src.fedoraproject.org/group/openstack-sig 15:25:55 and try build in order 15:28:43 https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__&bug_status=NEW&bug_status=ASSIGNED&f1=blocked&f2=assigned_to&list_id=10432013&o1=substring&o2=anywords&query_format=advanced&v1=1686977&v2=apevec%20jpena%20amoralej%20ykarel%20hguemar 15:28:47 ykarel, ^ 15:28:51 may be good 15:28:58 in fact you have one :) 15:29:11 need to start by fixing oslo-utils 15:29:16 that will probably unblock others 15:30:05 hmm i filed issue upstream for the one i had, need to followup 15:30:12 that's not openstack one though 15:30:38 ups https://bugs.python.org/issue37218 15:30:58 probably needs fix upstream too 15:31:51 yes, the one i saw was also python3.8 issue, related to ast 15:32:30 amoralej: that definitely needs an upstream fix 15:32:39 if it's only affecting tests we may be able to trick 15:33:26 let me expend some time on it 15:33:30 yes only tests should be affected 15:34:18 getting upstream fixes, will also need tag released and so on, else we need patches 15:34:36 if we get the upstream fix, we can carry a .patch for a while 15:34:58 yes 15:34:59 yes 15:35:09 we'll need to fix patch in distgit 15:35:36 in fact merging a patch in a stable branch for a python version which is not supported is weird 15:35:46 let's send it to master and put the .patch 15:36:19 ack 15:36:32 amoralej: well, it's a deprecated parameter since 3.4, maybe it would be accepted 15:36:34 but anyway 15:36:46 that's also true 15:36:59 and convincing 15:39:32 anything else to discuss? Else we can get ~20 minutes back 15:41:54 going once, going twice... 15:42:06 oh, I forgot! 15:42:15 any volunteer to chair the next meeting? 15:42:27 I can take it 15:42:37 #action ykarel to chair the next meeting 15:42:39 thanks ykarel 15:42:45 ok, let's close it 15:42:48 #endmeeting