Wednesday, 2022-03-09

opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: haproxy: support single external frontend  https://review.opendev.org/c/openstack/kolla-ansible/+/82339508:00
SvenKieskemorning08:29
opendevreviewMichal Nasiadka proposed openstack/kayobe master: Add support for Rocky Linux 8  https://review.opendev.org/c/openstack/kayobe/+/83165208:38
opendevreviewMichal Nasiadka proposed openstack/kayobe master: Add support for Rocky Linux 8  https://review.opendev.org/c/openstack/kayobe/+/83165208:44
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: haproxy: support single external frontend  https://review.opendev.org/c/openstack/kolla-ansible/+/82339509:00
opendevreviewyangjianfeng proposed openstack/ansible-collection-kolla master: Add support for git http/https proxy setup  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/83277009:39
opendevreviewyangjianfeng proposed openstack/ansible-collection-kolla master: baremetal: Add support for git http/https proxy setup  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/83277009:41
sri_Hi Team, quick question, I am using two different interface exp:(octavia_network_interface: "enp9s0", neutron_external_interface: "enp7s0"):  if that is case physnet1 can only used by one of this two networks right ? 09:50
sri_this is my globals.yml  config: https://paste.openstack.org/show/b9609hfvztqClMa6fwAw/, in this example I am using physnet1 in lb-mgmt-net, because of that I am not able to create a external network using physnet1 , how to I map these two interfaces to physnet1, physnet2 ! 09:56
wuchunya_octavia_network_interface don't need to bind to bridge,  we use this interface is to use it's ip for generating octavia.conf10:10
sri_wuchunya_:  But when creating a octavia_amp_network it require  provider_physical_network right ! exp: https://docs.openstack.org/kolla-ansible/latest/reference/networking/octavia.html10:14
wuchunya_octavia can also use a tenant network as octavia manage network, does your deployment used for production ?10:17
sri_wuchunya_:  i've used tenant network in octavia everything works fine, and no this not a production deployment I was just trying to simulate production deployment to understand octavia networking.    10:20
wuchunya_sri_:  how to setup two external network,? FYI: neutron_external_interface: eth1,eth2   neutron_bridge_name: br-ex, br-phy  and configure ml2.conf finally, 10:22
wuchunya_[ml2_type_flat]  flat_networks = public,lb   and [ovs] section: bridge_mappings: physnet2:br-phy10:24
wuchunya_sorry, flat_networks should be physnet1, physnet210:24
sri_wuchunya_:  I think this is what I am missing, I was not sure whether I can neutron_external_interface: "eth1,eth2" for octavia10:27
sri_wuchunya_: Thanks for the tip, 👍10:28
wuchunya_After I look at the code, you don't need to configure ml2.conf, kolla will do it automatically. 10:33
wuchunya_you are welcome.10:34
*** brinzhang_ is now known as brinzhang10:39
opendevreviewMark Goddard proposed openstack/kolla stable/train: CentOS Stream 8: drop CentOS RabbitMQ 3.8 repo  https://review.opendev.org/c/openstack/kolla/+/83265010:51
opendevreviewMichal Nasiadka proposed openstack/kayobe master: Add support for Rocky Linux 8  https://review.opendev.org/c/openstack/kayobe/+/83165210:54
chooozeHello guys.11:12
chooozeWe're trying to find out now is there a possibility to separate ELK-services to different nodes. Including new VIP for ELK and so on?11:13
mgoddardchoooze: different nodes - yes. Change the hosts in the relevant groups in the inventory11:14
mgoddardchoooze: new VIP - not currently11:14
chooozeThanks.11:15
chooozeIf we will try to add that possibility in your playbooks is there a chance that you will include our changes in upstream?11:15
mgoddardchoooze: it would probably be a fairly difficult change to make. I expect we'd be open to it though11:19
chooozemgoddard: thank you! We will try then. 11:19
mgoddardchoooze: I would suggest discussing the design with the upstream maintainers, before putting too much effort into it.11:20
mgoddardchoooze: weekly meetings would be a good place to start11:20
chooozemgoddard: got it11:20
opendevreviewMichal Nasiadka proposed openstack/kayobe master: Add support for Rocky Linux 8  https://review.opendev.org/c/openstack/kayobe/+/83165211:27
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: WIP: Run testssl.sh against HAProxy  https://review.opendev.org/c/openstack/kolla-ansible/+/82349911:35
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: WIP: Run testssl.sh against HAProxy  https://review.opendev.org/c/openstack/kolla-ansible/+/82349911:35
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: WIP: Run testssl.sh against HAProxy  https://review.opendev.org/c/openstack/kolla-ansible/+/82349913:06
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: WIP: Run testssl.sh against HAProxy  https://review.opendev.org/c/openstack/kolla-ansible/+/82349914:22
opendevreviewIvan Halomi proposed openstack/kolla-ansible master: Adding support of podman deployment  https://review.opendev.org/c/openstack/kolla-ansible/+/79922914:24
kevko_some already existing tool to migrate oooold kolla-ansible ceph to "external" ceph 14:35
opendevreviewMark Goddard proposed openstack/kayobe master: Revert "Add the bonding 802.3ad aggregation selection option"  https://review.opendev.org/c/openstack/kayobe/+/83272914:35
kevko_or let's say transfer kolla-ansible depend ceph to cephadm ? 14:35
kevko_or i will need to do it manually ? 14:35
mnasiadkamanually, you're on your own14:36
mnasiadka(if it's kolla-ansible deployed Ceph that we dropped long time ago)14:36
kevko_yes it is :D 14:37
mnasiadkahave fun :)14:40
kevko_:D 14:46
mnasiadkamgoddard mnasiadka hrw egonzalez yoctozepto rafaelweingartne cosmicsound osmanlicilegi bbezak parallax Fl1nt frickler adrian-a - meeting in 1014:50
mgoddardmnasiadka: unfortunately I can't make it today14:50
mnasiadkamgoddard: we'll miss you14:50
mnasiadka#startmeeting kolla15:00
opendevmeetMeeting started Wed Mar  9 15:00:00 2022 UTC and is due to finish in 60 minutes.  The chair is mnasiadka. 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 'kolla'15:00
mnasiadka#topic rollcall15:00
mnasiadkao/15:00
kevko_#help15:00
halomiva\o15:01
hinermaro/15:01
kevko\o/15:01
yoctozeptoo/15:01
ohorecny2o/15:01
yarovkono/15:01
mnasiadka#topic agenda15:03
mnasiadka* Review action items from the last meeting15:03
mnasiadka* CI status15:03
mnasiadka* Release tasks15:03
mnasiadka* Current cycle planning15:03
mnasiadka* Additional agenda (from whiteboard)15:03
mnasiadka* Open discussion15:03
mnasiadka#topic Review action items from the last meeting15:03
mnasiadkamnasiadka to triage security bugs and update them with resolution plan (if needed)15:03
mnasiadkaEnable osbpo in Debian APT sources, abandon extrepo command use then?15:03
mnasiadkamnasiadka to update kolla review dashboard with kolla collection15:03
mnasiadkaI triaged security bugs, but mgoddard created a new one :)15:04
mnasiadkaDashboard not updated.15:04
mnasiadkathe osbpo task was on hrw15:04
mnasiadkadoes anybody know if he has done it?15:04
yoctozeptoI've seen something15:04
yoctozeptoabandoned15:04
yoctozeptohttps://review.opendev.org/c/openstack/kolla/+/83154815:05
yoctozeptoshift of approach15:05
mnasiadkaso extrepo will have offline config, ok15:05
mnasiadkaso then it's still sort of in progress15:05
yoctozeptoyup15:06
mnasiadka#action mnasiadka to triage security bugs and update them with resolution plan (if needed)15:06
mnasiadka#action mnasiadka to update kolla review dashboard with kolla collection15:06
mnasiadka#action hrw Enable osbpo in Debian APT sources, abandon extrepo command use then?15:06
mnasiadka#topic CI Status15:06
mnasiadkaHow's our CI yoctozepto ?15:07
yoctozeptomnasiadka: happy15:07
mnasiadkagoodie15:07
yoctozeptono idea about kayobe though15:07
mnasiadkaI've seen an occasional OOM on TLS job, but nothing very concerning.15:08
mnasiadka#topic Release tasks15:08
mnasiadkaNone this week.15:08
mnasiadka#topic Current cycle planning15:08
mnasiadkaMost of the leftovers have been postponed to Z, but let's get anything we can in Y.15:09
mnasiadkayoctozepto: some more changes from mgoddard on baremetal role split15:09
yoctozeptomnasiadka: where?15:10
mnasiadkawhiteboard L42815:10
yoctozeptooh my15:12
yoctozeptodoes not seem look like a priority to me, to be honest, add me as a reviewer and I will get to it15:12
mnasiadkaok15:12
mnasiadkaI think it's important for Kayobe to reach the last patch on the list to be merged15:13
mnasiadka#topic Additional agenda (from whiteboard)15:13
mnasiadka(yoctozepto) Having both PXE and iPXE working at the same time https://review.opendev.org/c/openstack/kolla-ansible/+/832159/15:13
yoctozeptoyes, I think that's something sensible to do15:14
yoctozeptoespecially for people having existing pxe deployments15:15
yoctozeptoand wanting to progressively move to ipxe15:15
yoctozeptothe downside is we need to touch the volumes15:15
mnasiadkaas long as it works and doesn't break anything15:15
yoctozeptoyeah15:15
yoctozeptothe question is whether there is some state that we should preserve15:16
yoctozeptoin tftpboot and httpboot15:16
yoctozeptoto me it looks easy/not-expensive to regenerate15:16
mnasiadkaI'm not an Ironic expert15:16
yoctozeptobut I would like to know your opinions15:16
yoctozeptoyeah15:16
yoctozeptosadly mgoddard is not around15:16
mnasiadkaso ideally we would need mgoddard to look into this15:16
yoctozeptothat was the point15:17
mnasiadkaok then, I guess he'll try, given the notifications he already did get ;-)15:17
*** hrww is now known as hrw15:17
yoctozeptomnasiadka: yeah ;-) 15:18
mnasiadka(yarovkon) Migration path for kolla-ansible from docker to podman (https://etherpad.opendev.org/p/Kolla-ansible_migration_plan_docker-podman)15:18
mnasiadkathat's next15:18
yarovkonWanted to ask if that path looks fine for you15:19
mnasiadkaI think we need to automate those first two steps, you don't expect people to do it manually on let's say - 300 servers?15:20
ohorecny2of course that it will be automated in ansible15:20
ohorecny2we even have it already (not in gerrit yet)15:21
kevkoohorecny2: post to gerrit ..i'm curious 15:21
mnasiadkayes, post it to gerrit and let's review15:22
mnasiadkabut I doubt we will get to podman in Y15:22
yoctozeptouninstalling docker cannot be the first step15:23
yoctozeptoas it will down containers15:23
yoctozeptowe should be able to migrate container by container15:23
kevkoit doesn't matter i think15:23
yoctozeptokevko: how so?15:24
mnasiadkayoctozepto: installing both podman and docker on the same host (at least in CentOS world) is problematic15:24
kevkoit was reply to mnasiadka that it will be not in Y 15:24
yoctozeptokevko: ack15:24
ohorecny2yes, it doesn't matter we tested it with active VMs (instances) and they were still alive, during whole migration process15:24
yoctozeptomnasiadka: hmm, that's sad - what's the issue?15:24
mnasiadkayoctozepto: containerd mumbo jumbo15:24
kevkohaha, kolla will be tested directly from kolla itself :D ...so we will see how HA works :D :D :D 15:25
mnasiadkahere is some writeup, it's a bit problematic: https://faun.pub/how-to-install-simultaneously-docker-and-podman-on-rhel-8-centos-8-cb67412f321e15:25
yoctozeptoohorecny2: well, vms yes but not all other processes ;-)15:25
yoctozeptomnasiadka: ack, sad15:25
yoctozeptokevko: where?15:25
kevkowell, problem will be with rabbitmq, mysql and haproxy 15:25
kevkoand definitively has to be run with limit to one host 15:26
ohorecny2yes, but small outage during migration process is ok, I think15:26
mnasiadkaas long as everything works afterwards, with rabbitmq it's not granted ;-)15:27
kevkoi'm just trying to say that on the end of process there should be tasks which will check everything is working well15:27
kevkoand when i am thinking about it ..same tests should run before these actions are going happen 15:27
mnasiadkawe need to start with something, post the patch to gerrit and let's work on it collectively15:27
kevkomnasiadka: for example I know that kolla-ansible changed autoheal politics (sorry i don't know the exact keyword in config) to something different 15:28
ohorecny2yes, it is ok to do some healthchecks before and after migration15:28
kevko(for rabbitmq)15:28
mnasiadkaautoheal? it's not Kubernetes15:28
mnasiadkaah, for rmq15:28
kevkoso on deployments with three rabbitmqs (small ones) rabbit will stop working immediately15:28
kevkofor rabbitmq15:29
kevkomnasiadka: rabbitmq_cluster_partition_handling: "pause_minority" << this 15:30
opendevreviewMerged openstack/kolla stable/train: CentOS Stream 8: drop CentOS RabbitMQ 3.8 repo  https://review.opendev.org/c/openstack/kolla/+/83265015:30
kevkoin moment where rabbitmq will not see a node ..rabbitmq will be unresponsive .. 15:30
mnasiadkakevko: pause_minority is partition handling, there's no partition if you stop one node.15:30
mnasiadkait should only cause havoc on network issues15:31
mnasiadkabut we've diverted the topic15:31
ohorecny2yes, there can be some errors, because it will be for some time down, but after migration it is going up again15:32
mnasiadkaas long as we have some CI that is testing the move - we can work out the quirks I guess15:32
mnasiadkaso, post a patch - and let's discuss in the review (and probably on next meetings)15:33
kevkohmm ok 15:33
mnasiadkaThere's another podman-ish topic 15:34
mnasiadka(halomiva,hinermar) structure of podman testing and moving baremetal role to openstack collection15:34
mnasiadkawhat about this one?15:34
halomivai think we should talk about systemd first15:34
halomivabecause podman depends on it15:35
mnasiadkayes, systemd is something we should be able to land in Y15:35
mnasiadkaso what's the status of systemd implementation?15:36
halomivatests are passing but reviews are not coming so we would really appreciate some reviews 15:36
halomivabecause we implemented everything you asked for 15:36
mnasiadkahttps://review.opendev.org/c/openstack/kolla-ansible/+/816724 - this one?15:37
halomivayes15:37
mnasiadkayoctozepto: have cycles to look there again?15:38
yoctozeptomnasiadka: currently not15:40
opendevreviewMerged openstack/kolla-ansible master: Explicitly unset net.ipv4.ip_forward sysctl  https://review.opendev.org/c/openstack/kolla-ansible/+/83208715:40
mnasiadkaok, I'll do some testing and review that until end of the week.15:40
mnasiadkaand ask mgoddard to do the same15:41
hinermarThank you15:41
hinermarAnd regarding the testing of podman patch, since the single file for kolla_docker would be too large I have split up the specific test parts and put them in directory /tests/kolla_docker_tests/15:41
hinermarI just want check with you if that's alright15:41
mnasiadkasure, who likes big files15:42
hinermarGreat, thank you15:43
halomivasince baremetal role was move to collection and is under refactor, does it make sense to try push our patch to it for installing podman?15:43
halomivaor should we keep baremetal role in kolla-ansible for testing purposes?15:44
mnasiadkabaremetal role is already out, removed15:45
mnasiadkaso you need to add podman installation to kolla Ansible collection15:45
mnasiadkaand without that, you won't be able to test the podman patch ;-)15:45
halomivayea but there are some changes coming to that role no?15:45
halomivaso should I wait for the changes to come or push it now15:46
mnasiadkayes, look if there are any patches conflicting with your work, and adapt to that direction?15:46
mnasiadkaI don't think mgoddard is planning a lot more work with the collection this cycle15:47
mnasiadkahttps://review.opendev.org/q/project:openstack/ansible-collection-kolla15:47
mnasiadkahalomiva: probably best would be to create new role(s) for podman in the collection15:50
mnasiadkaok then15:50
mnasiadka#topic Open discussion15:51
mnasiadkaAnybody? Anything?15:51
ohorecny2yes, just ask for review15:51
ohorecny2beside these podman changes to kolla-ansible15:51
ohorecny2we have additional to kolla15:51
ohorecny2for image building by podman15:51
ohorecny2from our point of view they are ready, is there possibility to merge them to Y release?15:52
mnasiadkaurl?15:52
ohorecny2I think it is quite independent thing15:52
ohorecny2mnasiadka: https://review.opendev.org/q/owner:konstantin.yarovoy%2540tietoevry.com15:52
mnasiadkaok, I see them - will try to review before next meeting15:54
ohorecny2thank you very much15:54
mnasiadkayoctozepto: I'm nearly finished with the fqdn based single external frontend on HAProxy (https://review.opendev.org/c/openstack/kolla-ansible/+/823395) - would be nice if you could look into that15:55
mnasiadkaI'll add a CI job as well, guess without that it's going to be hard to merge ;)15:56
mnasiadkapath based should be easy to add, probably I'll do that when adding CI job15:56
mnasiadkaok, let's finish for today15:57
mnasiadkathanks for coming!15:57
mnasiadka#endmeeting15:57
opendevmeetMeeting ended Wed Mar  9 15:57:53 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:57
opendevmeetMinutes:        https://meetings.opendev.org/meetings/kolla/2022/kolla.2022-03-09-15.00.html15:57
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/kolla/2022/kolla.2022-03-09-15.00.txt15:57
opendevmeetLog:            https://meetings.opendev.org/meetings/kolla/2022/kolla.2022-03-09-15.00.log.html15:57
yoctozeptomnasiadka: thanks16:01
yoctozeptoand would be nice indeed16:01
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible stable/xena: Explicitly unset net.ipv4.ip_forward sysctl  https://review.opendev.org/c/openstack/kolla-ansible/+/83281316:14
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible stable/wallaby: Explicitly unset net.ipv4.ip_forward sysctl  https://review.opendev.org/c/openstack/kolla-ansible/+/83281416:15
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible stable/wallaby: Explicitly unset net.ipv4.ip_forward sysctl  https://review.opendev.org/c/openstack/kolla-ansible/+/83281416:16
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible stable/victoria: Explicitly unset net.ipv4.ip_forward sysctl  https://review.opendev.org/c/openstack/kolla-ansible/+/83281516:16
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible stable/ussuri: Explicitly unset net.ipv4.ip_forward sysctl  https://review.opendev.org/c/openstack/kolla-ansible/+/83281616:16
opendevreviewRafael Weingartner proposed openstack/kolla-ansible master: Customize the authentication error timeout page in modOIDC  https://review.opendev.org/c/openstack/kolla-ansible/+/83280616:17
opendevreviewRafael Weingartner proposed openstack/kolla-ansible master: Customize the authentication error timeout page in modOIDC  https://review.opendev.org/c/openstack/kolla-ansible/+/83280616:19
opendevreviewRafael Weingartner proposed openstack/kolla-ansible master: Customize the authentication error timeout page in modOIDC  https://review.opendev.org/c/openstack/kolla-ansible/+/83280616:21
opendevreviewRafael Weingartner proposed openstack/kolla-ansible master: Customize the authentication error timeout page in modOIDC  https://review.opendev.org/c/openstack/kolla-ansible/+/83280616:22
opendevreviewRafael Weingartner proposed openstack/kolla-ansible master: Customize the authentication error timeout page in modOIDC  https://review.opendev.org/c/openstack/kolla-ansible/+/83280616:23
jamesbensonGood morning all, just wondering if anyone has issues using the TLS options: kolla_enable_tls_internal/external/backend.  And which ones do you typically use?  And do you use it with a FQDN or just the IP addr for testing purposes....17:08
opendevreviewMark Goddard proposed openstack/kolla stable/train: CentOS Stream 8: drop build deps repo  https://review.opendev.org/c/openstack/kolla/+/83283317:24
jingvarjamesbenson: tls/internal/external with ip or fqdn - no issues / xena/waalaby18:37
opendevreviewRafael Weingartner proposed openstack/kolla-ansible master: Customize the authentication error timeout page in modOIDC  https://review.opendev.org/c/openstack/kolla-ansible/+/83280618:53
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible stable/xena: [CI] Test Ironic on Debian  https://review.opendev.org/c/openstack/kolla-ansible/+/83281720:00
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible stable/wallaby: [CI] Test Ironic on Debian  https://review.opendev.org/c/openstack/kolla-ansible/+/83281820:01
opendevreviewRadosław Piliszek proposed openstack/kolla stable/xena: [CI] Test Ironic on Debian  https://review.opendev.org/c/openstack/kolla/+/83281920:01
opendevreviewRadosław Piliszek proposed openstack/kolla stable/wallaby: [CI] Test Ironic on Debian  https://review.opendev.org/c/openstack/kolla/+/83282020:01
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible stable/xena: [CI] Test Ironic when touching Neutron  https://review.opendev.org/c/openstack/kolla-ansible/+/83282120:17
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible stable/wallaby: [CI] Test Ironic when touching Neutron  https://review.opendev.org/c/openstack/kolla-ansible/+/83282220:17
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible stable/xena: [CI] Use Tenks in Ironic job  https://review.opendev.org/c/openstack/kolla-ansible/+/83284920:22
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible stable/wallaby: [CI] Use Tenks in Ironic job  https://review.opendev.org/c/openstack/kolla-ansible/+/83282320:24
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible stable/xena: [CI] Test Ironic when touching Neutron  https://review.opendev.org/c/openstack/kolla-ansible/+/83282120:25
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible stable/xena: [CI] Use Tenks in Ironic job  https://review.opendev.org/c/openstack/kolla-ansible/+/83284920:25
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible stable/wallaby: [CI] Test Ironic when touching Neutron  https://review.opendev.org/c/openstack/kolla-ansible/+/83282220:25
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible stable/wallaby: [CI] Use Tenks in Ironic job  https://review.opendev.org/c/openstack/kolla-ansible/+/83282320:26
opendevreviewMark Goddard proposed openstack/kolla-ansible stable/xena: Explicitly unset net.ipv4.ip_forward sysctl  https://review.opendev.org/c/openstack/kolla-ansible/+/83281320:30
opendevreviewMerged openstack/kolla-ansible stable/xena: Explicitly unset net.ipv4.ip_forward sysctl  https://review.opendev.org/c/openstack/kolla-ansible/+/83281321:44
opendevreviewMerged openstack/kolla-ansible stable/wallaby: Explicitly unset net.ipv4.ip_forward sysctl  https://review.opendev.org/c/openstack/kolla-ansible/+/83281421:44
opendevreviewMerged openstack/kolla-ansible stable/victoria: Explicitly unset net.ipv4.ip_forward sysctl  https://review.opendev.org/c/openstack/kolla-ansible/+/83281521:44
opendevreviewMerged openstack/kolla-ansible stable/ussuri: Explicitly unset net.ipv4.ip_forward sysctl  https://review.opendev.org/c/openstack/kolla-ansible/+/83281621:44
opendevreviewVerification of a change to openstack/kayobe master failed: CI: Move to pytest-testinfra  https://review.opendev.org/c/openstack/kayobe/+/83222522:53

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