15:00:59 <jpena> #startmeeting RDO meeting 2018-06-27
15:00:59 <openstack> Meeting started Wed Jun 27 15:00:59 2018 UTC and is due to finish in 60 minutes.  The chair is jpena. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:01 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:03 <openstack> The meeting name has been set to 'rdo_meeting_2018_06_27'
15:01:06 <jpena> #topic roll call
15:01:11 <mwhahaha> pffft meetings
15:01:23 <leanderthal> o/
15:01:26 <leanderthal> lolz mwhahaha
15:01:29 <jpena> #chair leanderthal mwhahaha
15:01:33 <openstack> Current chairs: jpena leanderthal mwhahaha
15:01:35 <mwhahaha> upgrade
15:01:53 <jpena> btw, you can add more topics to the agenda at https://etherpad.openstack.org/p/RDO-Meeting
15:01:59 <sshnaidm> pabelanger, hi, can you please elaborate what happens in this patch? https://review.rdoproject.org/r/#/c/14496  I have a trouble to connect commit message and code..
15:02:27 <pabelanger> sshnaidm: jobs will stop running in jenkins and be moved to zuulv3 for those projects
15:02:42 <pabelanger> sshnaidm: which are non-OVB jobs
15:03:00 <jpena> let's move to the agenda
15:03:06 <jpena> #topic p-o-i failures in RDO master
15:03:36 <jpena> so there must be something failing in the Puppet promotion. amoralej, ykarel, do you know what it is?
15:03:38 <mwhahaha> so i'm looking at the logs and it appears that older versions of the modules are being used
15:03:43 <amoralej> let me check
15:03:46 <mwhahaha> ie missing params in puppet-tempest
15:04:47 <amoralej> last run
15:05:01 <amoralej> in puppet promotion failed because infra issue we are troubleshooting
15:05:09 <amoralej> i mean https://ci.centos.org/view/rdo/view/weirdo-pipelines/view/weirdo-promote-puppet/
15:05:18 <amoralej> that's promotion for p-o-i
15:05:27 <mwhahaha> ok i'll poke at those then
15:05:59 <jpena> amoralej: is that the nested virt issue?
15:06:02 <mwhahaha> just want to make sure we don't have any outstanding code related issues
15:06:03 <amoralej> yes
15:06:09 <amoralej> https://centos.logs.rdoproject.org/weirdo-generic-puppet-openstack-scenario001/5662/weirdo-project/logs/libvirt/qemu/instance-00000001.txt.gz
15:08:44 <amoralej> to be clear, for https://ci.centos.org/view/rdo/view/promotion-pipeline/job/rdo_trunk-promote-master-current-tripleo/ we need to get a new promotion in puppet-tripleo
15:09:21 <pabelanger> why do jobs need nested virt?
15:10:42 <dmsimard> pabelanger: we test with nested virt because it's not tested anywhere else and getting some real kvm coverage is nice every now and then
15:11:10 <dmsimard> there's no production clouds running qemu :p
15:12:03 <pabelanger> okay, this is part of the reason why we don't run it upstream in openstack-infra, tend to find random issue, then need to shutdown capacity to debug
15:12:17 <pabelanger> but it is good we are debugging it
15:13:20 <jpena> ok, moving on to the next topic?
15:13:36 <mwhahaha> works for me
15:13:42 <jpena> #topic anything for the july newsletter?
15:13:54 <jpena> leanderthal: the stage is yours
15:15:37 <leanderthal> the july rdo newsletter is coming out on tuesday; wondering if anyone has anything they'd like to add to our readers?
15:15:49 <leanderthal> i'm thinking something about the openstack birthday, PagliaccisCloud
15:15:56 <leanderthal> and the august test days
15:16:05 <leanderthal> but anyone have anything else they'd like to say?
15:16:17 <jpena> maybe pabelanger would like to add something about the migration to zuul v3
15:16:25 <leanderthal> #YESSS
15:16:38 <pabelanger> jpena: when does it go out?
15:16:47 <pabelanger> tuesday
15:16:55 <pabelanger> if we finish the migration by then, sure
15:18:59 <leanderthal> pabelanger, actually monday night, but the email is sent tuesday
15:19:06 <leanderthal> pabelanger, i'll follow up with you on monday :-)
15:19:12 <pabelanger> sure
15:19:19 <leanderthal> no worries either way
15:19:38 <leanderthal> jpena, that's it for me for today
15:20:01 <jpena> #topic next week's chair
15:20:08 <jpena> who would like to volunteer?
15:21:19 <amoralej> i will do it
15:21:28 <jpena> #action amoralej to chair the next meeting
15:21:28 <leanderthal> yay amoralej !! !
15:21:30 <jpena> thanks amoralej :D
15:21:36 <jpena> #topic open floor
15:22:39 <tosky> the dev (and the users) mailing list receive two identical reminders for this meeting, would it be possible to remove the duplicate?
15:22:53 <tosky> see for example https://lists.rdoproject.org/pipermail/dev/2018-June/008788.html and https://lists.rdoproject.org/pipermail/dev/2018-June/008787.html
15:23:09 <jpena> each list has a potential different audience, so I guess it's ok to duplicate
15:23:30 <tosky> yeah, and that's not the problem, I didn't write it properly
15:23:35 <tosky> each list receives it twice
15:23:44 <jpena> ahh
15:23:49 <tosky> see the links above; https://apps.fedoraproject.org/calendar/meeting/8759/ is a duplicate of https://apps.fedoraproject.org/calendar/meeting/2017/
15:24:16 <leanderthal> number80, do you have that on cron or something?
15:24:32 <tosky> it's a reminder on fedoraproject calendar apparently
15:24:45 <leanderthal> sneaky
15:24:47 <tosky> and few people should have access to it, according that page above
15:25:07 <tosky> ok, sorry, minor thing but it has been bothering me for a while :)
15:25:24 <jpena> it looks like I have access, let me check
15:25:30 <leanderthal> it's a great point; easily fixed! (maybe)
15:26:41 <jpena> ok, I removed the instance with id 2017
15:26:46 <jpena> I hope I didn't break anything
15:26:52 <tosky> the older one, poor it
15:26:54 <tosky> thanks!
15:27:31 <leanderthal> thx jpena
15:30:23 <jpena> if there's no other topic, we can get half an hour back
15:32:59 <leanderthal> sounds like a plan, jpena
15:33:02 <jpena> ok then, let's enjoy the extra time!
15:33:05 <jpena> #endmeeting