Tuesday, 2021-06-08

opendevreviewMerged openstack/openstack-ansible-os_heat master: Fix _service_users for multi-domain deployments  https://review.opendev.org/c/openstack/openstack-ansible-os_heat/+/79477000:06
*** spatel has joined #openstack-ansible01:31
*** spatel has joined #openstack-ansible03:00
*** spatel has quit IRC03:19
*** spatel has joined #openstack-ansible03:22
opendevreviewSatish Patel proposed openstack/openstack-ansible-os_neutron master: Add ovn clustering support  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/79426604:10
opendevreviewSatish Patel proposed openstack/openstack-ansible-os_neutron master: Add ovn clustering support  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/79426604:11
*** spatel has quit IRC04:26
*** opendevreview has quit IRC04:26
noonedeadpunkmornings06:09
noonedeadpunkwould be awesome to land https://review.opendev.org/c/openstack/openstack-ansible-lxc_hosts/+/795102 (or some alternative?) along with https://review.opendev.org/c/openstack/openstack-ansible/+/79479506:10
noonedeadpunkto be able to recheck and merge all stuck from friday stuff06:10
*** Adri2000 has joined #openstack-ansible06:48
*** odyssey4me has joined #openstack-ansible06:59
*** odyssey4me has quit IRC07:00
*** odyssey4me has joined #openstack-ansible07:01
*** andrewbonney has joined #openstack-ansible07:29
*** rpittau|afk is now known as rpittau07:30
jnamdarhi noonedeadpunk07:54
jnamdarI'm trying to set up mistral and tacker on my aio, but I'm getting the regular error `Failed to set up vim monitoring: requests.exceptions.SSLError: HTTPSConnectionPool(host='10.0.2.15', port=8989): Max retries exceeded with url: /v2/workflow?scope=private&namespace= (Caused by SSLError(SSLError("bad handshake: Error([('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')`07:55
jnamdarthat seems to be tacker trying to contact mistral07:55
jnamdarI think I should put mistral_endpoint_type = internal somewhere but I'm not sure where ? I can't find it in the docs07:56
*** miloa has joined #openstack-ansible08:13
miloaMorning :)08:13
*** luksky has joined #openstack-ansible08:14
jrossermorning08:16
miloaI've got a question on os_nova in nova.conf.j2 in train version in the [neutron] section there is no "region_name" and username is nova_service_user_name and before (rocky version) it was neutron_service_user_name. We are trying to deploy on multiple region and we've got some issue like default security group not found when we try to deploy an instance. Could it be related with these08:18
miloachanges ?08:18
*** tosky has joined #openstack-ansible08:39
*** opendevreview has joined #openstack-ansible09:44
opendevreviewArx Cruz proposed openstack/openstack-ansible-os_tempest master: Generate list of failing tests  https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/79526409:44
*** ioni has joined #openstack-ansible10:56
*** odyssey4me has quit IRC11:16
noonedeadpunkmiloa: regarding `region_name` it might be related, but neutron_service_user_name vs nova_service_user_name doesn't really matter11:22
noonedeadpunkjnamdar: I think we're missing `interface` inside `keystone_authtoken` section at least11:27
*** ebbex has quit IRC11:27
noonedeadpunkbut I guess it's more then that actually11:27
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_tacker master: Update tacker config  https://review.opendev.org/c/openstack/openstack-ansible-os_tacker/+/79530311:44
*** odyssey4me has joined #openstack-ansible12:01
jnamdarnoonedeadpunk: i'll try your changes on tacker.conf12:02
jnamdarbut it looks related to the the mistral connection to me, not keystone12:03
noonedeadpunkI think iterface in `keystone_authtoken` might be used for retrieving endpoints from catalog as well12:04
noonedeadpunkas eventually you get mistral endpoint from keystone anyway12:04
jnamdaroh I see12:04
jnamdarnoonedeadpunk: meh unfortunately it's still using the public endpoint or mistral12:20
noonedeadpunkhm....12:20
jnamdarfor* mistral12:21
noonedeadpunkBut I think that connection should be made in other way isn't it? That it's mistral who should reach tacker? I actually no idea about this part as never used neither of these services...12:23
noonedeadpunkit's just what I see in https://docs.openstack.org/tacker/latest/reference/mistral_workflows_usage_guide.html12:23
jnamdarit seems like when I register a VIM, it's trying to create a workflow on mistral12:23
noonedeadpunkaha12:24
jnamdaralso mistral is listed as a dependency of tacker IIRC12:24
noonedeadpunkyeah might be12:24
noonedeadpunkand have you catched stack trace of the error in logs?12:25
noonedeadpunkI think it also depends pretty much on barbican...12:25
jnamdaryeah12:25
jnamdarSeems like barbican can be turned off12:25
jnamdarit is by default in tacker.conf at least12:25
jnamdaruse_barbican = False12:26
noonedeadpunkbut log stack trace with error would be really hepfull as give a clue where start reading tacker code12:26
jnamdari'll link my stack trace in a pastebin12:26
noonedeadpunksounds good12:26
noonedeadpunkjnamdar: well, feels like mistral endpoint is not configurable for tacker....12:32
noonedeadpunkhttps://opendev.org/openstack/tacker/src/branch/master/tacker/mistral/mistral_client.py#L20-L2112:32
*** spatel has joined #openstack-ansible12:32
noonedeadpunkor it really should be addressed with `keystone_authtoken`...12:33
jnamdarhere is the paste https://pastebin.com/raw/x56VpEzC12:33
jnamdarthere are a bunch of openstack vim delete/register in there12:34
jnamdarnoonedeadpunk: yeah I was afraid of that12:34
jnamdarwhat if I just updated the public endpoint of mistral with the internal url ? :|12:35
jnamdarnasty patch12:35
noonedeadpunkwell, you can do that for testing at least...12:35
noonedeadpunkor you can disable ssl for public:)12:35
jnamdarmmh how can I do that?12:35
jnamdarin keystone conf?12:36
spateljrosser i have solve my yesterday LXC issue after adding this - https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/794266/8/tasks/providers/setup_ovs_ovn.yml#9412:36
spatelLXC aio works but metal is failing so looking into12:36
noonedeadpunkfirst of all set `mistral_service_publicuri_proto: http`12:37
noonedeadpunkand you will also need to override `haproxy_mistral_service` (if you're on master or V) to disable `haproxy_ssl` specifcily for it https://opendev.org/openstack/openstack-ansible/src/branch/master/inventory/group_vars/haproxy/haproxy.yml#L281-L29012:38
jnamdarok thx, I'm on ussuri so I don't need to modify haproxy's conf?12:39
jnamdaralso is mistral_service_publicuri_proto is in mistral.conf ?12:39
noonedeadpunkit's https://opendev.org/openstack/openstack-ansible-os_mistral/src/branch/master/defaults/main.yml#L15212:40
noonedeadpunkbut you need to set it in user_variables.yml12:40
noonedeadpunkon U things even more nasty unfortunatelly :(12:40
jnamdaroh, I would need to rerun the playbook os-install-mistral then right?12:41
noonedeadpunkit's probably easier just to edit /opt/openstack-ansible/inventory/group_vars/haproxy/haproxy.yml12:41
noonedeadpunkyep12:41
noonedeadpunkand probably to remove public endpoint from keystone as well12:42
opendevreviewMerged openstack/openstack-ansible-lxc_hosts master: Add CentOS 8.4 support  https://review.opendev.org/c/openstack/openstack-ansible-lxc_hosts/+/79510212:53
miloathanks noonedeadpunk, we will try to add region_name in the neutron section of nova.conf.12:58
jnamdarnoonedeadpunk: i think connection with mistral is good now, thanks. I think there are some actions missing for tacker though, my openstack vim register is still failing14:01
jnamdar`Failed to run task [error=Failed to find action [action_name=tacker.vim_ping_action] in [namespace=], wf=vim_id_f7721da8-288a-44c2-8c39-aeff531d5194, task=monitor_ping_vimPingVIMTASK]`14:01
jnamdarI probably need to setup those actions in mistral, I hope they're in the docs somewhere lol14:01
noonedeadpunkyeah. might be.14:08
noonedeadpunkwe indeed didn't payed enough attention to these services, but would be great if you could suggest improvements for config or roles14:08
jnamdarso far I met a lot of the same errors regarding certificate verification14:09
jnamdaracross services14:09
jnamdarand those were usually fixed by setting the endpoint interface to internal like you suggested. on an AIO I guess those should be put to internal by default14:10
jnamdarotherwise I'm working on ussuri right now, so sometimes it's hard to tell whether something's already been fixed or not14:11
jrosserin general the services should communicate with each other on the internal endpoint14:11
jrosserso if they're not doing that and we can patch it to do so it would be good14:11
jrosserthe AIO has both internal and external endpoints and ought to be as representative of a real deployment as is practical14:12
jnamdarmmh seems like it's still in development https://docs.openstack.org/tacker/latest/contributor/tacker_vim_monitoring.html14:21
jnamdarthat's weird then, not sure why I'm getting this error if the feature's not done yet14:21
jnamdari'll try to look at the #openstack-tacker chat for more info14:22
noonedeadpunkjnamdar: why do you think it's still in development?14:42
noonedeadpunkI think it's just link to the latest version?14:42
jnamdarnoonedeadpunk: yeah you're right I misread that14:43
jrosserthats an interesting side effect of the OFTC move14:43
jnamdarI think the feature is up, but it does link to the latest version, not ussuri14:44
jrosserany stable branch of /contributor/ redirects to latest14:44
noonedeadpunkyeah....14:44
noonedeadpunkalso noticed that14:44
noonedeadpunk#startmeeting openstack_ansible_meeting15:00
opendevmeetMeeting started Tue Jun  8 15:00:18 2021 UTC and is due to finish in 60 minutes.  The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'openstack_ansible_meeting'15:00
noonedeadpunk#topic rollcall15:00
noonedeadpunk\o/15:00
noonedeadpunkhm, btw topic is not actually changed with meetingbot :(15:00
jrosserhello15:04
noonedeadpunk#topic office hours15:05
noonedeadpunkCentOS 8.4 <- this has been solved right now I think. CI is passing again, which is awesome. But timing as usual was awful15:05
noonedeadpunkbut we also need to backport to V and I think also to U?15:06
jrosseroh yes i expect so15:06
jrosserthankfully they changes are small15:06
noonedeadpunkyeah, just one symlink:)15:07
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-lxc_hosts stable/victoria: Add CentOS 8.4 support  https://review.opendev.org/c/openstack/openstack-ansible-lxc_hosts/+/79528215:07
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-lxc_hosts stable/ussuri: Add CentOS 8.4 support  https://review.opendev.org/c/openstack/openstack-ansible-lxc_hosts/+/79528315:07
noonedeadpunkand thankfully 8.4 does not fail on libvirt firmware like stream still does15:07
noonedeadpunkas https://review.opendev.org/c/openstack/openstack-ansible-os_nova/+/793007 still failing....15:08
noonedeadpunkSo next we have 2 topics, that I expect to be merged by the end of the day15:09
noonedeadpunk#link https://review.opendev.org/q/topic:%22osa%252Fpki%22+(status:open%20OR%20status:merged)15:09
noonedeadpunk#link https://review.opendev.org/q/topic:%22osa%252Fbullseye%22+(status:open%20OR%20status:merged)15:09
noonedeadpunkOnce this is done, we do RC1. And probably we can branch as well, but I'd wait till next week with branching roles at least15:11
jrosseryes - feels like all the major things are done now15:11
noonedeadpunkwe also should do bunch of rechecks...15:11
noonedeadpunkas our gates were not really stable lately15:13
noonedeadpunkok, then regarding https://bugs.launchpad.net/openstack-ansible/+bug/193027615:14
opendevmeetLaunchpad bug 1930276 in openstack-ansible "Nova API not restarted when nova policy is updated" [Undecided,Triaged] - Assigned to Dmitriy Rabotyagov (noonedeadpunk)15:14
noonedeadpunkI'd say that it's really oslo bug. But I'm not sure if we should workaround it with triggering handlers on older branches15:15
noonedeadpunkas it can be reproduced only with json15:15
noonedeadpunkbut it's also pretty much work I'd say..15:15
noonedeadpunkI wasn't able to look into oslo.policy code yet :( But will try to this week15:16
noonedeadpunkI hope that just catching exception in correct place will do job15:16
noonedeadpunkas otherwise we should also trigger service restart when we're removing policy.yaml15:17
spatelnoonedeadpunk jrosser i have installed aio_ovn_metal senario and seeing this - http://paste.openstack.org/show/806463/15:18
noonedeadpunkBut I a bit doubt regarding possibility of fixing json file, since they're deprecated for a while15:18
spatelinventory is totally empty is that ok ?15:18
spatelsorry we are in middle of meeting.15:18
jrossereven though the json is deprecated it's still supported in a lot of stable branchs15:20
jrosseri'd expect there to be an interest in fixing it if we can get a good bug report15:20
noonedeadpunkI missed oslo meeting yestarday to raise this :(15:20
noonedeadpunkfair ppint15:22
noonedeadpunk*point15:22
jrosserlets ask them about our bug15:22
noonedeadpunkI was asking but haven't pinged hberaud so get no answer:)15:23
jrosserah well i just did, lets see if anything happens15:24
noonedeadpunkI guess they mostly following on channel during meetings15:25
noonedeadpunkregarding https://specs.openstack.org/openstack/openstack-ansible-specs/specs/xena/protecting-plaintext-configs.html - I think it's worth creating new repo for vault only after branching15:26
noonedeadpunkI saw folks have been asking here about backporting this work to previous branches, which is kind of important point for them. But I'd say that's not possible considering amount of work and requirement of vault role15:27
jrosseryes it looks awkward15:29
noonedeadpunkOh! And regarding DDoS! What I think we can do - in python_venv_build, check for amount of hosts in the play and fail, in case there're more then let's say 5 hosts, and wheels won't be built for $reasons15:29
jrosseryes like safety net of some sort15:29
noonedeadpunkand maybe link to some doc about troubleshooting this? And suggest workaround of setting osa_serial to lower then 5 if it can't be fixed for any reason15:31
jrosserwe can probably print out useful stuff in a fail: message about number of hosts, number of repo servers and stuff15:31
noonedeadpunkyeah, totally15:31
jrosserOS releases / architecture etc, to show why it's not worked15:31
noonedeadpunkyeah, really good idea. it would be easier to understand for deployer what he does wrong15:32
noonedeadpunkAlso I was thinking of moving https://docs.openstack.org/openstack-ansible/rocky/admin/upgrades/distribution-upgrades.html to master as well in regards to focal upgrade?15:32
noonedeadpunkand do some critical note about that you can't just upgrade computes without having repo container15:33
noonedeadpunkbut yeah, having repo container might be really tricky. Smth we probably should figure out in terms of the best way to sort this out15:33
jrosserah - does that page not appear in all branches15:33
noonedeadpunknope15:33
noonedeadpunkit's only for rocky15:34
noonedeadpunkit has been merged directly there15:34
jrosserright - rocky was xenial->bionic, but i guess that W is a really huge transition release for all OS15:34
noonedeadpunkyep15:34
noonedeadpunkwell, for centos it would be relatively easy migration, but debian and ubuntu...15:35
jrossertheres a similar thing to bring arm nodes into an existing x86_64 cloud15:35
jrossernothing prevents that other than missing a repo server15:35
noonedeadpunkeventually we have planned bionic->focal upgrade for autumn, so it will be adjusted anyway, but would be good to look into it in advance15:36
noonedeadpunkand the biggest thing here is actually lsync15:36
jrosseri feel like we maybe miss something here to bring in temporary / alternative repo hosts for specific cases15:36
noonedeadpunkyou mean for being standalone (ie under proxy)?15:37
jrosserright, it's easy to point the build host at something else for an ansible group15:38
jrosserbut not so easy to get the build results to appear at the LB15:38
noonedeadpunkah15:38
noonedeadpunkI think we can leverage ACLs or smth like that15:39
noonedeadpunkan be a bit smarter here...15:39
noonedeadpunkactually nothing stopps us from having several group of backends15:39
jrosseroh well actually i wonder if overriding openstack_repo_url for a host group would work15:40
noonedeadpunkit probably should... but it's not that neat.. As you need to set it manually and define extra group for new OS15:41
noonedeadpunkand well, if you have more then 1 repo container per specific case...15:41
noonedeadpunkthat would be not handy really15:42
noonedeadpunkoh, btw. I saw really weird failures during facts gathering after switching to min15:44
jrosseroh dear - anything specific?15:45
noonedeadpunkhttps://700a7e3ec90813bffe3e-a140c73e010d1e58296165dc52d0a2c3.ssl.cf2.rackcdn.com/788031/11/check/openstack-ansible-deploy-aio_lxc-debian-buster/c9ca1d5/logs/ara-report/results/3366.html15:45
noonedeadpunkAnd I saw it periodicly on different patches15:45
noonedeadpunkno details in stdout either15:46
noonedeadpunkso have literally no idea wtf is going on...15:47
dmsimardthose are the worst15:48
dmsimardsometimes you can get the actual traceback by adding -vvv15:49
noonedeadpunkdmsimard: have you seen smth like that in other places?15:49
dmsimardansible eats tracebacks unless it's -vvv15:49
noonedeadpunkyeah... but you need to catch it first... and until it's random and not really reproducable...15:49
noonedeadpunkat least I couldn't reproduce that relatively easily...15:50
dmsimardit's delegating the setup task that fails ? maybe one of the item from the list doesn't work for some reason15:50
noonedeadpunkwell, it's a container on the same host... and in case of CI item consist of single element15:51
noonedeadpunkbut that's actually what I also thought about15:52
noonedeadpunkI could imagine this happening in case of OOM but haven't found any proof in the log15:54
jrossernot found anything suspicious at all here15:57
noonedeadpunkbut I also don't see it happening today...15:59
noonedeadpunk#endmeeting16:01
opendevmeetMeeting ended Tue Jun  8 16:01:01 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
opendevmeetMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2021/openstack_ansible_meeting.2021-06-08-15.00.html16:01
opendevmeetMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2021/openstack_ansible_meeting.2021-06-08-15.00.txt16:01
opendevmeetLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2021/openstack_ansible_meeting.2021-06-08-15.00.log.html16:01
*** rpittau is now known as rpittau|afk16:31
*** miloa has quit IRC16:36
opendevreviewMerged openstack/openstack-ansible master: Gather extra facts for healthcheck playbooks  https://review.opendev.org/c/openstack/openstack-ansible/+/79479516:42
opendevreviewMerged openstack/openstack-ansible-rsyslog_client master: Replace linters test with integarted one  https://review.opendev.org/c/openstack/openstack-ansible-rsyslog_client/+/79425417:03
opendevreviewMerged openstack/openstack-ansible-rsyslog_client master: Add support for debian bullseye  https://review.opendev.org/c/openstack/openstack-ansible-rsyslog_client/+/79128817:03
*** b1tsh1ft3r has joined #openstack-ansible17:32
*** andrewbonney has quit IRC17:32
spateljrosser could you use your ninja skill to find out why this one failed? - https://zuul.opendev.org/t/openstack/build/b2a88bd86c6849dea5921a3fa373652d18:09
jrosserthe OVN router is not accessible18:12
jrosserand i guess i'm wondering where teh ovn service logs are18:14
spatelteach me how do you finding error in logs, i did search RUN END etc.. but not seeing any good way to find error block18:15
spatelhmm i can see it now, tempest task failed18:17
jrosseroh i found them, they don't seem to be journal logs18:17
jrosseryou have to repeatedly search for RUN END, there are 7 occurrences of that in each job18:18
jrosserso i think that something to look at (unrelated to the error) is if the ovn things make useful systemd journals18:20
jrosserand if they do we should be collecting them in the CI jobs18:20
jrossertheres not really anything useful in the ovn controller log from the host https://zuul.opendev.org/t/openstack/build/b2a88bd86c6849dea5921a3fa373652d/log/logs/host/ovn/ovn-controller.log.txt18:21
spatelagreed, these logs are general logs, may need to set debug for AIO so we have more logs data18:22
spateli am trying to build AIO metal in my lab to experiment18:23
spatelyesterday i fixed OVN_LXC issue not getting metal issue18:24
jrosserthese should have debug anyway18:26
jrosserwhat you need to do is see if there is anything better in journalctl -i ovn_northd18:26
jrosserand if there is we need to update the AIO log collection to grab those too18:27
jrosserhere is where your router is created https://zuul.opendev.org/t/openstack/build/b2a88bd86c6849dea5921a3fa373652d/log/logs/host/neutron-server.service.journal-16-56-52.log.txt#5377-541218:27
mgariepyhttps://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_b2a/794266/8/check/openstack-ansible-deploy-aio_metal_ovn-ubuntu-focal2/b2a88bd/logs/host/neutron-ovn-metadata-agent.service.journal-16-56-52.log.txt18:41
mgariepythat seems interesting Unable to open stream to unix:/var/run/openvswitch/db.sock to retrieve schema: No such file or directory18:42
opendevreviewMerged openstack/openstack-ansible-os_tacker master: Update tacker config  https://review.opendev.org/c/openstack/openstack-ansible-os_tacker/+/79530318:46
spatelmgariepy i am building AIO metal in my lab to understand issue18:47
opendevreviewMerged openstack/openstack-ansible-openstack_hosts master: Add CentOS 8.4 support  https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/79510318:47
spatelin metal case northd and ovn-controller both use ovsdb and may be something going on between them18:50
mgariepyspatel, what the right invocation to run the test locally ?19:00
spatelwhat do you mean by locally?19:01
mgariepyto run the test via run_tests.sh19:01
mgariepyin a vm19:01
spateli am not following you.. what do you trying to do here?19:04
spatelwhat is run_tests.sh (sorry my CI knowledge is limited here)19:04
mgariepyjrosser, noonedeadpunk if i want to run the openstack-ansible-deploy-aio_metal_ovn-ubuntu-focal2  is there some args i can pass to run_test.sh to run it locally ?19:06
spatelmgariepy i am installing aio-ovn normal way using export SENARIO='aio_ovn_metal'19:12
spatelif you want to play in your PC19:13
jrosserrun_test.sh is a bit awkward if you want to apply patches to roles, I generally just run the bootstrap / playbooks manually19:17
mgariepyok19:19
mgariepyi tought that it was possible.19:20
opendevreviewMerged openstack/openstack-ansible master: Add PKI role to integrated repo  https://review.opendev.org/c/openstack/openstack-ansible/+/78803119:41
spateljrosser mgariepy something odd going on here - http://paste.openstack.org/show/806468/19:49
spateli will debug later tonight19:50
spatelits trying to start ovsdb 6640 on all interface 0.0.0.0:6640 but HAproxy already listening on it..19:51
spateli don't think we need HAProxy stanza for 664019:52
jrosserwe do19:52
*** b1tsh1ft_ has joined #openstack-ansible19:52
jrosserthe services should bind to their port on br-mgmt19:52
jrosserwhich is the .100 address19:52
*** b1tsh1ft3r has quit IRC19:53
jrosserand the vip bonds to .10119:53
jrosser*binds19:53
jrosserlooks like OVN has not had the “bind-to-mgmt” treatment19:53
spatelhmmm19:54
jrosserall of these things will have some settings in their config file setting the bind address19:54
jrosserwhich maybe we don’t configure yet?19:54
spateli will take a look tonight.. i have to leave now :(19:55
*** spatel has quit IRC19:58
mgariepylooks like the ovsdb server is configured with 2 managers one on 127.0.0.1:6640 and the other on 6640 directly20:24
opendevreviewMerged openstack/openstack-ansible stable/ussuri: Fix sahara backend URL  https://review.opendev.org/c/openstack/openstack-ansible/+/79444520:32
*** gilou__ has joined #openstack-ansible20:33
jrosserfeels like we need to change some port numbers?20:36
*** gilou_ has quit IRC20:40
*** b1tsh1ft_ has quit IRC21:28
*** b1tsh1ft3r has joined #openstack-ansible21:58
*** b1tsh1ft3r has quit IRC22:06
*** luksky has quit IRC22:10
*** fresta has joined #openstack-ansible22:43
*** tosky has quit IRC23:03

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