15:03:05 <evrardjp> #startmeeting openstack_ansible_meeting
15:03:06 <openstack> Meeting started Tue Mar 27 15:03:05 2018 UTC and is due to finish in 60 minutes.  The chair is evrardjp. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:03:07 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:03:10 <openstack> The meeting name has been set to 'openstack_ansible_meeting'
15:03:30 <evrardjp> #topic What happened since last meeting
15:03:32 <hwoarang> o/
15:03:38 <mattt> o/
15:03:39 <evrardjp> odyssey4me and others agreed on the "DRY" approach for the python build simplification: a role to do ptyhon venv building only, and the user management that can be not repeated would go into the systemd_service role. (https://etherpad.openstack.org/p/osa-source-deploy-role-planning)
15:03:47 <evrardjp> tonyb is still working on EOL-ing newton. Not yet done.
15:03:54 <evrardjp> we have new repos: the openstack/ansible-config_template, openstack/ansible-role-python_venv_build, openstack/ansible-role-systemd_mount, openstack/ansible-role-systemd_networkd, openstack/ansible-role-systemd_service. We'll work for their inclusion into roles and integrated repo this cycle, in order to simplify the roles (DRY)
15:03:55 <prometheanfire> o/
15:04:01 <evrardjp> evrardjp remembered on the ML the brainstorming etherpad for vancouver https://etherpad.openstack.org/p/YVR-openstack-ansible-brainstorming
15:04:07 <evrardjp> hwoarang found a major bug during the cinder deployment in master/queens and the fix provided by odyssey4me is on its way back.
15:04:07 <hwoarang> (what is DRY?)
15:04:12 <evrardjp> evrardjp said he will do the usual release at the end of the week for all branches, including newton, and bump master.
15:04:23 <evrardjp> hwoarang: Don't repeat yourself
15:04:27 <hwoarang> ok
15:04:38 <evrardjp> anything else?
15:05:07 <openstackgerrit> Kevin Carter (cloudnull) proposed openstack/openstack-ansible-os_neutron master: Fix post up checksum script  https://review.openstack.org/556875
15:05:09 <evrardjp> if you think about something missing, add it to the agenda for next week, please :)
15:05:21 <evrardjp> #topic Bug triage
15:05:34 <evrardjp> #link https://bugs.launchpad.net/openstack-ansible/+bug/1758351
15:05:35 <openstack> Launchpad bug 1758351 in openstack-ansible "iornic is using old things" [Undecided,New]
15:05:39 <andymccr> o/
15:05:49 <evrardjp> ofc that is ironic, not iornic
15:06:01 <andymccr> invalid since its mispelled next!
15:06:02 <evrardjp> updated
15:06:08 <evrardjp> na!
15:06:23 <odyssey4me> brb, need to just take a 5 min break
15:06:28 <evrardjp> prometheanfire: will you have a look?
15:06:32 <evrardjp> odyssey4me: no worries
15:06:34 <andymccr> evrardjp: that is valid - tbh that role hasnt been kept up to date at all
15:06:46 <andymccr> would be nice if ppl who plan on using it could do that
15:06:47 <evrardjp> yep I'd like someone to step up on this
15:06:55 <evrardjp> yeah my point precisely
15:07:01 <evrardjp> I think Rackspace has some interest in it
15:07:19 <evrardjp> I'll mark it as high and assign that to d34dh0r53
15:07:20 <openstackgerrit> Kevin Carter (cloudnull) proposed openstack/openstack-ansible-os_neutron master: Fix post up checksum script  https://review.openstack.org/556875
15:07:24 <prometheanfire> in 2 meetings at once
15:07:34 <prometheanfire> ya, I'll look
15:07:43 <prometheanfire> assigned https://bugs.launchpad.net/openstack-ansible/+bug/1758351 to me
15:07:44 <openstack> Launchpad bug 1758351 in openstack-ansible "ironic is using old things" [High,Confirmed] - Assigned to Matthew Thode (prometheanfire)
15:07:54 <evrardjp> next
15:08:05 <evrardjp> oh ok sorry
15:08:23 <evrardjp> reassigning we did it at the same time
15:08:36 <evrardjp> next
15:08:38 <evrardjp> #link https://bugs.launchpad.net/openstack-ansible/+bug/1758144
15:08:38 <openstack> Launchpad bug 1758144 in openstack-ansible "resolv.conf in containers set too late" [Undecided,New]
15:09:24 <spotz> o/
15:10:20 <evrardjp> resolv conf isn't linked to the repo-use
15:10:27 <hwoarang> hmm
15:11:21 <evrardjp> the setup hosts run first, so you should have all the things to run on ready
15:11:29 <evrardjp> then you run the resolvconf
15:11:37 <evrardjp> I mean unbound here
15:11:50 <evrardjp> repo-use isn't linked to resolving
15:12:27 <evrardjp> opinion?
15:12:40 <evrardjp> I mean -- what do you guys think?
15:12:50 <evrardjp> should we go on the next one?
15:13:33 <hwoarang> i dont quite understand yet so i can't comment
15:13:39 <hwoarang> *understand the bug
15:14:15 <odyssey4me> back
15:14:18 <evrardjp> yeah me neither.
15:14:24 <evrardjp> I am not sure.
15:14:38 <evrardjp> but for me it makes 0 sense that repo-use is doing resolving things :p
15:14:48 <logan-> ill look into it, its probably a race condition with how the resolv stuff got reorganized for JIT container builds
15:14:55 <evrardjp> I think resolv.conf should move to setup-hosts now
15:15:06 <odyssey4me> possibly
15:15:10 <evrardjp> yeah
15:15:16 <evrardjp> but the patch is like last year
15:15:19 <logan-> evrardjp: can't do that until the unbound containers are built
15:15:37 <evrardjp> that's true but setup hosts build containers
15:15:45 <evrardjp> at the end of it would make sense
15:16:34 <evrardjp> you prep your hosts for the rest, so preparing the networking and preparing the dns doesn't seem so far distant
15:16:39 <evrardjp> but yes, I trust you logan
15:16:56 <evrardjp> I leave it open, but with you assigned
15:17:17 <jamespo> Hey, just wondering what we need to back up if we were to rebuild our deployment host for OSA, it looks like we need.. user_secrets.yml, openstack_user_config.yml, user_variables*.yml and probably openstack_inventory.json. Do we need to keep openstack_hostnames_ips.yml as well?
15:17:27 <spotz> ask for clarification if no one understands it?
15:17:35 <evrardjp> next
15:17:37 <evrardjp> #link https://bugs.launchpad.net/openstack-ansible/+bug/1757453
15:17:37 <openstack> Launchpad bug 1757453 in openstack-ansible "os_heat: missing database configuration options" [Undecided,New]
15:18:09 <evrardjp> jamespo: keep it, and also env.d/conf.d
15:18:39 <jamespo> OK thanks!
15:20:18 <evrardjp> I don't understand this bug
15:20:40 <evrardjp> why would you need more variables if you can already override them?
15:22:05 <cloudnull> evrardjp: i think this is just a doc / education issue.
15:22:14 <evrardjp> cloudnull: ok so won't fix?
15:22:33 <cloudnull> if the defaults are ok, config_template can be used to add "insert your favorite option here".
15:22:42 <cloudnull> ++
15:22:52 <evrardjp> yeah
15:22:57 <evrardjp> Will add what you said in the bug
15:23:34 <cloudnull> will do
15:23:48 <evrardjp> no I do it, don't worry :)
15:24:03 <cloudnull> oh you already did it :)
15:24:07 <evrardjp> #link #link https://bugs.launchpad.net/openstack-ansible/+bug/1755821
15:24:08 <openstack> Launchpad bug 1755821 in openstack-ansible "config_template fails to parse template if it contains a comment with leading spaces" [High,New] - Assigned to Kevin Carter (kevin-carter)
15:24:08 <evrardjp> #link https://bugs.launchpad.net/openstack-ansible/+bug/1755821
15:24:27 <cloudnull> ive not spent anytime on that. still a bug
15:25:04 <evrardjp> ok
15:25:08 <evrardjp> let's move on
15:25:15 <cloudnull> I think we partially tackled that with the retained ordering, however we need to do more on that.
15:25:38 <evrardjp> I guess, including testing would be nice too. We should maybe add this into the new repo now
15:25:46 <evrardjp> but that's another discussion
15:25:51 <cloudnull> is there a new repo now ?
15:25:54 <evrardjp> we can leave it there until next week
15:25:59 <cloudnull> oh ok.
15:26:01 <evrardjp> cloudnull: see highlights of the week :)
15:26:09 <evrardjp> next!
15:26:11 <evrardjp> #link https://bugs.launchpad.net/openstack-ansible/+bug/1754139
15:26:12 <openstack> Launchpad bug 1754139 in openstack-ansible "openvswitch does not start on new AIO deployment" [Undecided,New]
15:26:40 <evrardjp> hwoarang: do you know if mbuil could have a look at it?
15:26:47 <evrardjp> he doesn't seem to be on irc
15:27:02 <hwoarang> yes he is away this week but he should be able to look at it
15:27:03 <andymccr> ahh ovs
15:27:07 <andymccr> the gift that keeps on giving :D
15:27:24 <evrardjp> andymccr: haha
15:27:40 <evrardjp> I'd like to spend some cycles on it, but there are more urgent things. Always.
15:27:40 <hwoarang> doesn't seem too complicated i will talk to him
15:27:42 <evrardjp> :)
15:27:46 <evrardjp> great.
15:27:49 <hwoarang> evrardjp: assign it to manuel and if he can't look at it i iwll
15:27:50 <evrardjp> Will add him
15:27:56 <evrardjp> yup!
15:28:27 <cloudnull> I think that ovs issue might be related to https://review.openstack.org/#/c/550609/
15:28:29 <evrardjp> there are two manuel buil!
15:28:52 <evrardjp> cloudnull: I will add that to the bug.
15:29:09 <cloudnull> IDK if it is, could be a new gift from the ovs gods
15:29:30 <evrardjp> I'll mark it as incomplete.
15:29:31 <openstackgerrit> Markos Chandras (hwoarang) proposed openstack/openstack-ansible-os_neutron master: Testing neutron jobs  https://review.openstack.org/528692
15:29:36 <evrardjp> this was for 17.0.0rc1
15:29:44 <evrardjp> so we need more input with latest master
15:29:48 <evrardjp> ok let's move to the next bug
15:29:55 <evrardjp> #link https://bugs.launchpad.net/openstack-ansible/+bug/1753801
15:29:57 <openstack> Launchpad bug 1753801 in openstack-ansible "Galera connection contention on full base deployment on Xeon E3 " [Undecided,New]
15:30:48 <evrardjp> logan-: what's the outcome of your testing? Sorry if I am not sure to understand what you mean with your new results?
15:30:58 <evrardjp> do we need to adapt our defaults?
15:31:19 <odyssey4me> it sounds like we should probably do some sort of playbook/group_var calculations based on number of hosts, number of services, etc
15:31:20 <openstackgerrit> Kevin Carter (cloudnull) proposed openstack/openstack-ansible-os_neutron stable/queens: Create ovs temp directories when using ovs  https://review.openstack.org/556890
15:31:29 <odyssey4me> or perhaps our worker/process/threads defaults are too high?
15:32:08 <evrardjp> that's exactly what I am asking :) which one do we need to setup ?
15:33:25 <logan-> still getting load on the cloud and stuff. but mysql max connections does need a lower floor imo, i saw it level off just over 800 with a base deploy
15:34:16 <odyssey4me> I'm not sure what a good approach would be here - maybe we could spec up some way to solve this, maybe have some sort of small/medium/large cloud thresholds for all these settings - then we have a playbook which determines the best set to use.
15:34:48 <logan-> the thing on the workers... the counts were fine 2 cycles ago before we added services like placement etc
15:34:49 <odyssey4me> Right now we offer all the tunables in the world, but ask our deployers to figure it out on their own. Perhaps we could make that a little easier.
15:35:10 <odyssey4me> Yeah, I don't think it's just placement - I think uwsgi has changed things up considerably.
15:35:13 <logan-> yup ^
15:35:24 <evrardjp> probably indeed
15:35:29 <logan-> and keystone workers could be improved by running unequal numbers for :35357 vs :5000
15:35:45 <logan-> (like very few for :35357 because hardly anything uses it)
15:36:05 <evrardjp> I think this should end up with a spec more than a bug
15:36:12 <jrosser> a tool to report numbers vs. inventory would be useful as service layouts across hosts might be different for everyone
15:36:25 <odyssey4me> logan- I wonder if we could get a tigkstack implemented in your nodepool cloud and implement some metrics monitoring on API response and stuff so that we can try to find a good balance between performance and responsiveness?
15:36:26 <evrardjp> giving the ideas of what to improve, with work items for their implementation
15:37:36 <odyssey4me> Yeah, the hard part with doing work like this is that we need multiple sized clouds to try various settings against to see what works right.
15:37:38 <evrardjp> I think this can indeed be brought inside a cli tool, but let's think about getting data first, before trying to implement something
15:37:38 <logan-> yeah odyssey4me I think that would help guide it some
15:37:53 <logan-> evrardjp: yeah a spec would help work out the formulaic approach to how we determine these
15:38:10 <evrardjp> ok great.
15:38:21 <evrardjp> Will mark it as confirmed and wishlist for now
15:38:22 <logan-> i think the current approach is not too bad, just needs some tuning, like they keystone thing I mentioned
15:38:58 <odyssey4me> logan- yeah, makes sense
15:39:08 <mattt> i almost feel this is best to leave to the deployer to figure out
15:39:14 <odyssey4me> the admin endpoint is eventually going to go away, but it's only really used for bootstrapping
15:39:39 <evrardjp> mattt: I also agree with you, and should maybe be a documentation thing
15:39:42 <mattt> because you can invest a boat load of time trying to optimize for scenarios but unless we're able to constantly re-test for performance regressions then it feels like a waste of time
15:39:48 <logan-> mattt: that's fine but in that case I would expect to see defaults on the conservative side, and right now they are quite aggressive in some cases
15:39:59 <mattt> logan-: yes, totally agree with that
15:40:08 <evrardjp> I think we agree then
15:40:12 <evrardjp> let's move on
15:40:14 <evrardjp> next
15:40:16 <evrardjp> #link https://bugs.launchpad.net/openstack-ansible/+bug/1753790
15:40:17 <openstack> Launchpad bug 1753790 in openstack-ansible "spurious 'no space left on device' errors during venv build" [Undecided,New]
15:40:18 <openstackgerrit> Merged openstack/openstack-ansible-tests master: Have run_tests clone the test repo  https://review.openstack.org/556518
15:40:30 <evrardjp> I have seen a few ones today
15:40:41 <evrardjp> I didn't get the chance to investigate on that
15:41:00 <odyssey4me> evrardjp yeah, as we discussed last week - that is still happening on rax nodes, but it's not consistent so it's impossible to figure out right now
15:41:02 <evrardjp> I will focus on the nova issue right now so if someone could have a look that would be great
15:41:16 <odyssey4me> we've not been able to replicate it outside the gate
15:41:31 <odyssey4me> but it only happens on the rax two-disk instances
15:41:45 <odyssey4me> also, it's only happening for master & queens
15:41:47 <evrardjp> let's leave it as new then
15:42:02 <evrardjp> yes, the only ones with btrfs
15:42:15 <odyssey4me> well, we can confirm - I'll add some notes on what we figured out last week
15:42:35 <evrardjp> yeah okay, so let's mark it critical if it's confirmed -- it's blocking gates
15:42:38 <evrardjp> if not critical, high
15:43:45 <MikeW> Hey guys has anyone nested an aio on top of kvm to test different network topologies?
15:43:54 <evrardjp> odyssey4me: I will wait for your notes on the bug
15:43:58 <evrardjp> next
15:44:04 <evrardjp> #link https://bugs.launchpad.net/openstack-ansible/+bug/1752073
15:44:05 <openstack> Launchpad bug 1752073 in openstack-ansible "Neutron firewall_v2 driver missing" [Undecided,New] - Assigned to Markos Chandras (hwoarang)
15:44:18 <evrardjp> MikeW: we are doing triage, can you come back after the meeting?
15:44:27 <hwoarang> i asked Peri to had a look at it so I will follow up with him
15:44:30 <evrardjp> MikeW: but multi-node AIO is kvm
15:44:38 <evrardjp> hwoarang: thanks!
15:44:44 <evrardjp> let's move to next bug then
15:44:49 <evrardjp> #link https://bugs.launchpad.net/openstack-ansible/+bug/1750836
15:44:50 <openstack> Launchpad bug 1750836 in openstack-ansible "Cloudwatch configuration still present in heat containers" [Undecided,New]
15:45:14 <evrardjp> oh yes. that's cleanup required there
15:45:26 <spotz> oooh ripping stuff out?:)
15:45:29 <evrardjp> cloudnull: do you think your systemd role can cleanup things too?
15:45:36 <evrardjp> spotz: heat did that for us
15:45:47 <cloudnull> evrardjp: yes.
15:45:51 <spotz> bah I like ripping stuff out!
15:45:54 <cloudnull> we had state absent
15:46:02 <MikeW> evrardjp Yep sorry
15:46:24 <cloudnull> s/had/have/ it might need a little tweaking but it for sure can clean things up
15:46:29 <openstackgerrit> Markos Chandras (hwoarang) proposed openstack/openstack-ansible-os_neutron stable/pike: tasks: Ensure Open vSwitch is started for all providers that need it  https://review.openstack.org/556892
15:46:36 <evrardjp> cloudnull: good
15:46:43 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-apt_package_pinning master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556893
15:46:46 <evrardjp> confirmed and medium?
15:46:57 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-ceph_client master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556895
15:47:10 <evrardjp> not sure it's really problematic
15:47:12 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-galera_client master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556896
15:47:28 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-galera_server master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556897
15:47:43 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-haproxy_server master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556898
15:47:46 <odyssey4me> uh oh -sorry, patch storm incoming
15:47:53 <evrardjp> odyssey4me: come on!
15:47:58 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-lxc_container_create master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556899
15:48:10 <evrardjp> so confirmed medium?
15:48:13 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-lxc_hosts master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556901
15:48:20 <odyssey4me> I blame hwoarang - he pressed +w!
15:48:21 <odyssey4me> ;)
15:48:27 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-memcached_server master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556902
15:48:33 <hwoarang> oh noes
15:48:34 <evrardjp> I assume that's a yes?
15:48:40 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-nspawn_container_create master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556903
15:48:54 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-nspawn_hosts master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556904
15:49:09 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-openstack_hosts master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556905
15:49:23 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-openstack_openrc master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556906
15:49:26 <evrardjp> ok let's move to the next bug please
15:49:38 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-ops master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556907
15:49:38 <evrardjp> #link https://bugs.launchpad.net/openstack-ansible/+bug/1750789
15:49:39 <openstack> Launchpad bug 1750789 in openstack-ansible "VPNaaS dashboard not copied to horizon container" [Undecided,New]
15:49:51 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_almanach master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556908
15:50:05 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_aodh master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556909
15:50:19 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_barbican master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556910
15:50:34 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_ceilometer master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556911
15:50:43 <evrardjp> I'd say confirmed and low
15:50:45 <odyssey4me> evrardjp I'm not seeing any vpnaas dashboard enablement in the horizon role, so that's ilkely why.
15:50:50 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_cinder master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556912
15:50:53 <hwoarang> ok
15:51:03 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_cloudkitty master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556913
15:51:03 <evrardjp> yeah on the link he gives, vpnaas isn't listed
15:51:16 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_congress master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556914
15:51:28 <odyssey4me> so this would be a new feature addition, really - not a bug
15:51:31 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_designate master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556915
15:51:38 <evrardjp> but we've never did that I see
15:51:40 <evrardjp> yeah
15:51:46 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_glance master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556916
15:51:51 <odyssey4me> confirmed, wishlist
15:52:00 <evrardjp> yup
15:52:01 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_gnocchi master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556917
15:52:15 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_heat master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556918
15:52:31 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_horizon master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556919
15:52:46 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_ironic master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556920
15:53:01 <evrardjp> next
15:53:03 <evrardjp> #link https://bugs.launchpad.net/openstack-ansible/+bug/1750582
15:53:04 <openstack> Launchpad bug 1750582 in openstack-ansible "monitoring user in rabbitmq" [Undecided,New]
15:53:10 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_keystone master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556921
15:53:25 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_magnum master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556922
15:53:39 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_molteniron master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556924
15:53:53 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_monasca master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556925
15:53:54 <odyssey4me> ah, is that why it doesn't work - I remember discussing this with someone who was trying to figure it out
15:54:06 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_monasca-agent master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556926
15:54:17 <odyssey4me> looks like it should be a pretty simple fix
15:54:19 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_monasca-ui master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556927
15:54:20 <odyssey4me> I'd say confirmed, because I discussed this issue with another person.
15:54:30 <evrardjp> ok
15:54:35 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_neutron master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556929
15:54:52 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_nova master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556930
15:54:58 <odyssey4me> maybe low, not sure how urgent it is
15:55:05 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_octavia master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556932
15:55:17 <evrardjp> confirmed and low seems ok
15:55:18 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_panko master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556933
15:55:29 <evrardjp> and low-hanging-fruit
15:55:32 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_rally master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556934
15:55:36 <odyssey4me> yep
15:55:45 <evrardjp> next
15:55:47 <evrardjp> #link https://bugs.launchpad.net/openstack-ansible/+bug/1750236
15:55:48 <openstack> Launchpad bug 1750236 in openstack-ansible "os::aodh::alarm via heat stable/pike ubuntu & centos http 503" [Undecided,New]
15:55:48 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_sahara master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556935
15:56:01 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_searchlight master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556936
15:56:17 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_swift master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556937
15:56:30 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_tacker master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556938
15:56:45 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_tempest master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556939
15:56:49 <odyssey4me> dunno, I defer to gokhan_ and mnaser
15:56:55 <evrardjp> I have 0 knowledge of this
15:56:59 <evrardjp> hahah yes
15:56:59 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_trove master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556940
15:57:05 <odyssey4me> to me that's all gibberish
15:57:09 <evrardjp> :)
15:57:13 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_watcher master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556941
15:57:13 <evrardjp> like me speaking!
15:57:16 <evrardjp> hahaha
15:57:17 <openstackgerrit> German Eichberger proposed openstack/openstack-ansible master: Fixes typo to enable log rotate for Octavia  https://review.openstack.org/555631
15:57:21 <odyssey4me> lol
15:57:26 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-os_zaqar master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556942
15:57:35 <evrardjp> Imagine if I was speaking with gnocchis and autoscalings in my sentences!
15:57:41 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-pip_install master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556943
15:57:41 <evrardjp> anyway
15:57:43 <openstackgerrit> German Eichberger proposed openstack/openstack-ansible master: Moves Octavia gate from experimental to required  https://review.openstack.org/545020
15:57:45 <evrardjp> last one
15:57:46 <prometheanfire> evrardjp: we going over specs/blueprints today?
15:57:55 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-plugins master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556944
15:58:00 <evrardjp> prometheanfire: nope should we?
15:58:03 <evrardjp> It was not on the agenda
15:58:10 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-rabbitmq_server master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556945
15:58:15 <evrardjp> let's discuss after the meeting
15:58:17 <odyssey4me> xgerman_ rebasing should not be necessary, just recheckiing is all that's required - zuul rebases automatically when it prepares the checkout
15:58:18 <evrardjp> last bug for today
15:58:25 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-repo_build master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556946
15:58:27 <evrardjp> #link https://bugs.launchpad.net/openstack-ansible/+bug/1743032
15:58:28 <openstack> Launchpad bug 1743032 in openstack-ansible "Galera cluster maintenance in OpenStack-Ansible" [Undecided,New] - Assigned to Kevin Carter (kevin-carter)
15:58:39 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-repo_server master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556947
15:58:47 <xgerman_> ok, will recheck then more often
15:58:53 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-rsyslog_client master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556948
15:59:07 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-rsyslog_server master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556949
15:59:21 <openstackgerrit> OpenStack Proposal Bot proposed openstack/openstack-ansible-specs master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556950
15:59:27 <evrardjp> cloudnull: what should we do?
15:59:36 <openstackgerrit> OpenStack Proposal Bot proposed openstack/ansible-hardening master: Updated from OpenStack Ansible Tests  https://review.openstack.org/556951
15:59:47 <evrardjp> xgerman_: not rechecking, finding the root cause and fixing if required, that's what should be done :)
16:00:01 <openstackgerrit> Kevin Carter (cloudnull) proposed openstack/openstack-ansible-os_neutron master: Convert role to use a common systemd service role  https://review.openstack.org/556952
16:00:02 <evrardjp> cloudnull: should we unassign this from you?
16:00:15 <evrardjp> this is impossible to read, thanks odyssey4me .
16:00:22 <evrardjp> and hwoarang
16:00:23 <evrardjp> :/
16:00:25 <cloudnull> hahaha
16:00:49 <xgerman_> well, I usually chase the os_octavia stuff but might need to expand then…
16:00:53 <evrardjp> cloudnull: opinion?
16:01:14 <evrardjp> I don't know why you assigned yourself on this
16:01:14 <cloudnull> you can keep me assigned, or someone else can take it.
16:01:19 <cloudnull> either way.
16:01:30 <evrardjp> depends on your time, if you don't, I'd rather have it unassigned
16:01:42 <cloudnull> ok
16:01:51 <evrardjp> that doesn't answer my question :)
16:02:36 <evrardjp> looks like a logician joke.
16:02:39 <cloudnull> indeed :)
16:02:57 <evrardjp> so do you have time?
16:03:22 <cloudnull> i hope so .
16:03:25 <evrardjp> ok
16:03:30 <evrardjp> leaving it assigned to you
16:03:35 <evrardjp> let's stop for today
16:03:36 <cloudnull> yay!
16:03:38 <evrardjp> #endmeeting