Wednesday, 2021-11-24

*** amoralej|off is now known as amoralej08:08
DK4when doing the quickstart in kolla i get an error at the pip3 install of kola itself: ERROR: Command errored out with exit status 128: git clone -q https://opendev.org/openstack/kolla-ansible /tmp/pip-req-build-qtdndaab Check the logs for full command output.08:11
opendevreviewMark Goddard proposed openstack/kolla-ansible stable/xena: Specify log file name for Nova API  https://review.opendev.org/c/openstack/kolla-ansible/+/81890508:52
opendevreviewMark Goddard proposed openstack/kolla-ansible stable/victoria: Specify log file name for Nova API  https://review.opendev.org/c/openstack/kolla-ansible/+/81890608:53
mnasiadkamgoddard, yoctozepto, hrw: https://review.opendev.org/c/openstack/releases/+/818882 - seems monasca-grafana build has failed on the publish job - but all the other images have been pushed.10:38
mgoddardmnasiadka: ack10:41
mnasiadkaI guess we don't really care?10:41
ijustrhello, wondering if this is the right place to ask a kayobe question to the community :) i'm able to deploy openstack with controllers, compute and storage nodes but as soon as we try to deploy 2 separate network hosts it fails with "msg": "Required network 'internal' (Default network) is not mapped to this host; Required network 'internal' (API network) is not mapped to this host; Required network 'public' (External 10:47
ijustrnetwork) is not mapped to this host; Required external network 'external' is not mapped to this host". Followed https://docs.openstack.org/kayobe/wallaby/control-plane-service-placement.html#control-plane-service-placement-network-hosts, as we playing around with Wallaby at the moment.10:47
jingvarYou should  walk thoght the network model10:56
ijustrfrom this page? https://docs.openstack.org/kayobe/wallaby/configuration/reference/network.html10:56
hrwmnasiadka: we dropped monasca-grafana in April...10:57
jingvarjust write out wich network, host , interface 10:57
ijustrhere on irc?10:58
jingvarijustr: start from the end :)10:58
ijustrin etc/kayobe/inventory/controllers/network-interfaces11:00
ijustrbr_interface: "{{ controller_extra_network_interfaces[0] }}{{ br_bridge_ports[0] }}"11:01
ijustrbr_bridge_ports:11:01
ijustr  - eth111:01
ijustrprovision_oc_interface: eth011:01
ijustroob_oc_interface: "{{ br_interface }}.{{ oob_vlan }}"11:01
ijustrinternal_interface: "{{ br_interface }}.{{ internal_vlan }}"11:01
ijustrstorage_interface: "{{ br_interface }}.{{ storage_vlan }}"11:01
opendevreviewPierre Riteau proposed openstack/kolla-ansible stable/xena: Fix wrong opts in cyborg.conf  https://review.opendev.org/c/openstack/kolla-ansible/+/81890711:01
ijustrpublic_interface: "{{ br_interface }}.{{ public_vlan }}"11:01
ijustrexternal_interface: "{{ br_interface }}.{{ external_vlan }}"11:01
ijustrtunnel_interface: "{{ br_interface }}.{{ external_vlan }}"11:01
ijustrnah that's not good :P11:01
opendevreviewPierre Riteau proposed openstack/kolla-ansible stable/wallaby: Replace auth_uri with www_authenticate_uri  https://review.opendev.org/c/openstack/kolla-ansible/+/81890811:03
opendevreviewPierre Riteau proposed openstack/kolla-ansible stable/victoria: Replace auth_uri with www_authenticate_uri  https://review.opendev.org/c/openstack/kolla-ansible/+/81890911:04
ijustrI'll fork the config repo and send a compare link instead for overview of our config might be a good idea11:06
mnasiadkahrw: in Ussuri?11:10
hrwah. sorry11:10
hrw(kolla) 12:23 (s) marcin@puchatek:kolla$ for branch in ussuri victoria wallaby xena;do git switch stable/$branch;git up;kolla-build-images.sh centos source monasca-grafana test-monasca-grafana-$branch;done11:23
hrwlet me check does it work at all in any branch11:23
mnasiadkait seems it fails on c entos11:28
hrwbuilt in victoria11:33
hrwno idea what goes wrong11:43
ijustrhttps://github.com/openstack/kayobe-config/compare/stable/wallaby...ist-international:stable/wallaby with this config we get the error pasted before (is not mapped to this host)11:54
jingvarI'm not sure that {{ br_bridge_ports[0] }}" sould works12:10
jingvarI think etc/kayobe/inventory/group_vars/controllers/network-interfaces rendered as jinja template, and  {{ br_bridge_ports[0] }}" is undefined for the render, because  br_bridge_ports is in template body12:13
ijustrit seems to render just fine for kayobe-config/etc/kolla/inventory/overcloud/host_vars/controller0, there's data rendered from template, and it works correctly if not trying to separate the network nodes, but I can hard code it and run again12:14
jingvarif you want to use a variable in template yuo should define it in level up, I mean as hostvariable12:14
jingvarI don't like use variables which  are defined somewhere later12:16
ijustrupdated conf and running again12:16
jingvarjust add  ansible debug and check varibales for the host12:17
jingvarexternal networks etc12:17
ijustrthe -vvvv to the command?12:17
ijustrsame error hardcoded 12:18
jingvarno, insert debug code into failed playbook12:18
ijustrI'm not that familiar with ansible to to translate that into what to write and where :)12:19
ijustrI'm guessing where is in this file venvs/kayobe/share/kayobe/ansible/kolla-ansible.yml the the task that fails, in this case 'Set Kolla Ansible host variables'12:22
*** hrww is now known as hrw13:00
opendevreviewMartin Hiner proposed openstack/kolla-ansible master: Refactor of kolla_docker into module_utils  https://review.opendev.org/c/openstack/kolla-ansible/+/81795413:01
DK4is there something wrong with the mariadb backup enable? FAILED! => {"action": "mysql_user", "changed": false, "msg": "(1064, \"You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'BINLOG MONITOR ON *.* TO 'backup'@'%'' at line 1\")"}14:14
mnasiadkamgoddard mnasiadka hrw egonzalez yoctozepto rafaelweingartne cosmicsound osmanlicilegi bbezak parallax Fl1nt frickler adrian-a - Kolla meeting in 1014:50
mnasiadka#startmeeting kolla15:01
opendevmeetMeeting started Wed Nov 24 15:01:04 2021 UTC and is due to finish in 60 minutes.  The chair is mnasiadka. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
opendevmeetThe meeting name has been set to 'kolla'15:01
mnasiadka#topic rollcall15:01
fricklero/15:01
adrian-a\o15:02
mgoddard\o15:02
mgoddardmnasiadka: where is that ping list from?15:03
mnasiadkamgoddard: from the wiki, we still haven't merged the docs change I think15:03
mnasiadkao/15:03
headphoneJameso/15:05
adrian-ahttps://wiki.openstack.org/wiki/Meetings/Kolla#10_minute_warning15:06
mnasiadka#topic agenda15:06
mnasiadka* Review action items from the last meeting15:06
mnasiadka* CI status15:06
mnasiadka* Release tasks15:06
mnasiadka* Yoga cycle planning15:06
mnasiadka* Bootstrap servers in Kayobe (mgoddard)15:06
mnasiadka* Open discussion15:06
mnasiadka#topic Review action items from the last meeting15:06
mnasiadkamnasiadka to triage security bugs and update them with resolution plan (if needed)15:07
mnasiadkayoctozepto hide properly init-runonce15:07
mnasiadkanot forget to go through backports for stable branches (L248 on Whiteboard) and do stable releases afterwards.15:07
mnasiadkamnasiadka to EOL rocky and stein for both kolla and kolla-ansible15:07
mnasiadkaI didn't triage sec bugs15:07
mnasiadkaI have raised the EOL change and sent a mail to ML15:07
mnasiadkayoctozepto is not here, but I don't think he did his15:07
mnasiadkaHas anybody gone through backports? I guess not...15:08
mgoddardnot I15:09
mnasiadkaThen not15:09
mnasiadka#action mnasiadka to triage security bugs and update them with resolution plan (if needed)15:09
mnasiadka#action yoctozepto hide properly init-runonce15:09
mnasiadka#action not forget to go through backports for stable branches (L248 on Whiteboard) and do stable releases afterwards.15:09
mnasiadka#topic CI Status15:09
mnasiadkaWe've had a fail on publish jobs for centos in Ussuri (monasca-grafana failed)15:10
mnasiadkahrw was looking at rebuilding it, but I think it suceeded on his end15:11
mnasiadkaI'll check as well, and if it works, then it was just a one off... (and Ussuri is EM anyway)15:12
mnasiadkaCI Status on the whiteboard looks green as grass15:12
mnasiadka#topic Release tasks15:13
mnasiadkait's R-18 now15:13
mnasiadkaR-17 was Switch source images to current release15:14
mnasiadkamgoddard: are those changes merged? I remember you raised those?15:14
mgoddardR-17 is next week :)15:14
mgoddardthey didn't get merged IIRC15:15
mnasiadkaAh, right15:15
mnasiadkaCan we get them marked as priority changes?15:16
mgoddardWe may as well wait for next week now15:16
mnasiadkaSure15:17
mnasiadkaSo let's move on15:17
mnasiadka#topic Yoga cycle planning15:17
mnasiadkaI've sent out the email regarding Kolla plans for next cycle, let's wait a bit more for replies - I know Fl1nt promised one (and some others promised to send replies)15:18
mnasiadkaIs there any particular feature we'd like to discuss today?15:19
mgoddardHow is the yoga feature list looking?15:19
mnasiadkaI started tidying it up and will populate it in the whiteboard, so that's a valid question mgoddard ;-)15:21
mgoddardyeah, would be nice to have something to iterate on15:22
mnasiadkaOk, I'll make that my priority for this week.15:22
mgoddardshould we formalise the process of updating/maintaining versions?15:22
adrian-aI assume this can be dropped as CentOS will be deprecated: https://bugs.launchpad.net/kolla/+bug/1946801 15:23
mnasiadkamgoddard: do you mean stable minor releases?15:24
mgoddardI think we don't have a very standard way of deciding when we should update things like OS distros, core component versions (mariadb, rabbitmq) and tooling (ansible)15:24
mnasiadkaadrian-a: no, that is for both binary and source - but we may fix it by not using RDO packages.15:24
adrian-aok15:25
mgoddardadrian-a: let's not make any assumptions until we have a final decision on the future of images15:25
mnasiadkamgoddard: that's correct, we could think of having some rules15:25
hrwmnasiadka: monasca-grafana failed in ussuri, worked in victoria15:25
mgoddardI suppose rules might help, e.g. can't update things after R-X15:26
mnasiadkaEspecially after deprecating/dropping binary - we would not be so tied to upgrading OS distros as we currently are with CentOS15:26
mnasiadkatrue15:26
mgoddardI was thinking more about encouraging conversations at certain points in a release cycle about what we might need to update15:27
* hrw off, sorry15:27
yoctozeptoo/ (sorry, I got lost in some analysis and forgot the meeting)15:27
yoctozepto(oh my, two sorries at once)15:28
mnasiadkaOk then, one thing is updating Ansible - this can be more or less predicted even at PTG level15:28
mgoddardhrw tags in yoctozepto 15:29
mnasiadkaProbably OS distro upgrade is similar15:29
mgoddardhopefully, yes15:29
yoctozeptomgoddard: :D15:29
yoctozeptook, so we have upgrade to mariadb 10.6 as we planned15:30
yoctozeptobut the change just landed randomly15:30
yoctozeptoupgraded*15:30
mgoddardright, that's what I'm saying15:30
mnasiadkaAnd then new RabbitMQ/MariaDB/infrastructure_software releases should not be done late in the cycle, often OS distro upgrade dictates those versions15:30
mnasiadkaAnd especially MariaDB/RabbitMQ upgrades should be done early in the cycle to see what issues will we get in CI for the next couple of months15:31
mgoddardso maybe we need a standard PTG topic for this, and then a release process point mid-cycle to discuss again15:31
mnasiadkaBut RabbitMQ and MariaDB are now from their own repositories, so we have more control over them.15:31
yoctozeptoyeah15:32
yoctozeptois rabbitmq upgradable btw?15:32
mnasiadkaYou ask me :)15:32
yoctozeptoI think they have been on 3.8 for a long time15:32
yoctozeptoyeah, there seems to be 3.9 already15:32
adrian-awe have a rule in another project where we update 3rd parties as first task after a stable release (or as early as possible), this way we have a full cycle to discover issues15:32
yoctozeptodo we want to touch it?15:32
mnasiadkaDo we need some part of the Kolla contributor docs with standard topics that should be discussed over PTG and then revisited in mid-cycle?15:32
yoctozeptowe could use that15:33
yoctozepto(re: docs)15:33
mgoddard+115:34
mnasiadkaOk, any volunteer to start the docs change?15:34
yoctozeptonow that's a harder question15:35
mnasiadkaWell, I need to update the weekly meetings docs change, so I can start that one15:36
mnasiadka#action mnasiadka post a patch for docs - standard topics that should be discussed over PTG and then revisited in mid-cycle15:36
* yoctozepto cheering mnasiadka on15:36
mnasiadkaWhile we're at tooling - ansible-core 2.11 is out, Ansible 5 (the collection of collections and so on) will be out somewhere mid December - are we bumping this cycle?15:38
mnasiadkaups, I mean ansible-core 2.1215:39
yoctozeptoif it works with core 2.12, then I'm all in15:39
yoctozeptoor otherwise15:39
mnasiadkaWell, Python 3.8 is a hard requirement ;-)15:39
yoctozeptoif we can keep the compats sane15:39
yoctozeptoah well15:39
mgoddardah, difficult for centos 815:40
yoctozeptofor sure we don't want to make it a minimum15:40
mnasiadkaYes, even for Stream15:40
mnasiadkaBut we could set it as maximum15:40
yoctozeptobut let's test it15:40
yoctozeptoindeed15:40
mnasiadkaOk, I'll add it to the list of priorities for Yoga15:41
mnasiadka#action mnasiadka Add ansible-core 2.12 to the list of Yoga priorities15:41
mnasiadkaok, any other Yoga topics?15:41
yoctozeptoyeah, rabbitmq15:42
yoctozeptodo we want to bump it since we can?15:42
mgoddardhow new is it?15:42
yoctozepto3.9.023 July 202115:42
mnasiadka3.8 End of General Support is 31 January 202215:42
mnasiadkaso do we have any option not to?15:42
yoctozepto3.9.1020 November 202115:42
mgoddardok, let's go15:42
mgoddardit can't get much worse :D15:43
mnasiadka#action mnasiadka Add rabbitmq 3.9 to the list of Yoga priorities15:43
mnasiadka;)15:43
mnasiadkaanything else?15:43
yoctozepto1 General Support means patch releases that are produced regularly based on feedback from all users.15:43
yoctozepto2 Extended Support means security patches and high-severity issues reported by users with a commercial license.15:43
yoctozeptojust a note it's not THAT BAD ;-)15:43
mnasiadkaI don't have a commercial license ;-)15:43
yoctozeptonothing else from me15:43
yoctozeptomnasiadka: yeah, but utterly broken releases will still get fixed as well as sec issues15:44
yoctozeptoanyhow, let's bump since it's sensible15:44
mnasiadkayoctozepto: I don't want to count how many times did I do full RabbitMQ wipe to get it back to working state, and couldn't find a bug that caused that ;-)15:45
mnasiadka#topic Bootstrap servers in Kayobe (mgoddard)15:45
yoctozeptomnasiadka: precisely, so what are you worrying about even? :D15:45
mnasiadkamgoddard: stage is yours15:46
mgoddardthank you15:46
mgoddardtl;dr: I'm working on copying the baremetal role from kolla-ansible into kayobe15:47
mgoddardsome background15:47
mgoddardAnsible error handling is tricky15:47
mgoddard#link https://github.com/markgoddard/ansible-experiments/tree/master/14-error-handling15:47
mgoddardThe use case is: allow a 'kayobe overcloud host configure' command to execute to completion in the face of some host failures, or even missing hosts15:48
mgoddardThe relevant part of the problem here is that kayobe mixes its own playbooks and kolla-ansible bootstrap-servers in that command15:49
mgoddardso if any hosts fail during the kayobe playbooks, we don't run bootstrap-servers15:49
mgoddardsome less important reasons for doing this:15:50
yoctozepto( mgoddard: on the linked github page some "echo $?" are missing return value )15:50
mgoddardit can be a bit clunky/hairy to specify tags/limit to this command, since it mixes kayobe & kolla playbooks15:51
mgoddardand some parts of bootstrap-servers are duplicated in kayobe already15:51
mgoddardfinally, some of this code could use a clean up15:51
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible master: [WIP] Add Ansible 5 aka core 2.12 support  https://review.opendev.org/c/openstack/kolla-ansible/+/81913515:52
* yoctozepto does not use kayobe but mgoddard's monologue is sensible15:52
mnasiadkamgoddard: I remember we spoke about moving some tasks to separate role than baremetal (e.g. docker)15:53
mgoddardthe reason I bring this here today is to find out whether there is interest in sharing this code between kolla-ansible and kayobe15:53
mnasiadkaBut I'm worried about copy'ing - e.g. maintaining it in both places - maybe we should create a ,,Kolla'' Galaxy collection?15:53
mgoddardor should I just copypasta 15:53
yoctozeptomgoddard: copypasta sounds bad15:53
mgoddardI think a kolla collection would be ideal, it's just whether we want to create and maintain that thing15:54
yoctozeptowhat is your plan about sharing the code? could we standardise something?15:54
psuedoo/15:54
mgoddardit would also be a bit more effort to make the code work in both codebases15:54
yoctozeptohmm, but then again; what does a collection bring over being in kolla-ansible?15:54
yoctozeptoI mean, except for distribution :D15:55
mgoddardwell, what it brings to k-a is benefitting from me spending some time on it15:55
mnasiadkaWell, I think we can't just leave it in kolla-ansible repo and distribute it to kayobe in the same time? ;-)15:56
mgoddardI probably wouldn't keep the two in sync if each had a copy15:56
yoctozeptomnasiadka: does not kayobe install kolla-ansible?15:56
mnasiadkayoctozepto: in a kolla-ansible venv15:56
mnasiadka(separate from kayobe venv)15:56
yoctozeptoyeah, but, as I said, what's the difference except for distribution means?15:57
mgoddardI see your point, yoctozepto 15:57
mgoddardit could probably be made to work by fudging the role path15:57
mgoddardI would be a bit concerned about changes to the role breaking kayobe15:58
fricklercould add a cross-project job for that?15:59
yoctozepto^ precisely15:59
mgoddardwe could, and only trigger it on changes to the role15:59
yoctozeptoI mean, best to integrate closely15:59
yoctozeptocollection could be trickier in fact15:59
mgoddardwhat'why the resistance to the collection?15:59
mnasiadkatricker for kolla-ansible (we would need to add support for that)15:59
mgoddards/what'//15:59
mnasiadkain kayobe that's a standard16:00
yoctozeptomgoddard, mnasiadka: can we test with in-flight/depends-on patches and a collection?16:00
yoctozeptoif yes, then it's no brainer and let's just go collection :-)16:00
mgoddardsure, if it's maintained in opendev16:00
mgoddardwe have talked about using ansible-core and collections for kolla-ansible before16:01
mnasiadkayup16:01
mnasiadkaso a collection it is?16:02
yoctozeptook, then it all makes sense to me16:02
yoctozeptoyeah, seems so16:02
opendevreviewDoug Szumski proposed openstack/kolla-ansible master: Support copying static Vendordata file into Nova API container  https://review.opendev.org/c/openstack/kolla-ansible/+/81914016:02
mgoddard#link https://review.opendev.org/c/openstack/kayobe/+/81829016:03
mgoddardthat's the initial PoC16:03
mnasiadkaok then16:04
mnasiadkamgoddard: will you handle the addition repo creation and creating a collection?16:04
mgoddardI will16:05
mnasiadkaOk then, seems like another priority for Yoga, initiated on Kayobe side, but affecting Kolla-Ansible16:05
mnasiadkaAnd I think we went a bit over time.16:06
mnasiadkaThanks for the meeting :)16:07
mnasiadka#stopmeeting16:07
mnasiadka#endmeeting16:07
opendevmeetMeeting ended Wed Nov 24 16:07:07 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:07
opendevmeetMinutes:        https://meetings.opendev.org/meetings/kolla/2021/kolla.2021-11-24-15.01.html16:07
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/kolla/2021/kolla.2021-11-24-15.01.txt16:07
opendevmeetLog:            https://meetings.opendev.org/meetings/kolla/2021/kolla.2021-11-24-15.01.log.html16:07
mnasiadkaegh16:07
yoctozepto#stopallthemeetings16:07
yoctozeptothanks mnasiadka for chairing :-)16:07
mgoddardmnasiadka: btw I'm updating hte meetings doc16:08
opendevreviewPierre Riteau proposed openstack/kayobe master: Build overcloud host image directly with DIB  https://review.opendev.org/c/openstack/kayobe/+/77260916:08
opendevreviewMark Goddard proposed openstack/kolla master: docs: weekly meetings page  https://review.opendev.org/c/openstack/kolla/+/81549416:08
mnasiadkamgoddard: ok, then I'll not update it ;)16:09
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: openvswitch: move from docker exec to openvswitch_db  https://review.opendev.org/c/openstack/kolla-ansible/+/81914316:14
opendevreviewPierre Riteau proposed openstack/kayobe master: Build overcloud host image directly with DIB  https://review.opendev.org/c/openstack/kayobe/+/77260916:21
opendevreviewPierre Riteau proposed openstack/kayobe master: Build overcloud host image directly with DIB  https://review.opendev.org/c/openstack/kayobe/+/77260917:23
hrwINFO:kolla.common.utils.nova-base:INFO: This is taking longer than usual. You might need to provide the dependency resolver with stricter constraints to reduce runtime. If you want to abort this run, you can press Ctrl + C to do so. To improve how pip performs, tell us what happened here: https://pip.pypa.io/surveys/backtracking17:32
hrwINFO:kolla.common.utils.nova-base:INFO: pip is looking at multiple versions of oslo-upgradecheck to determine which version is compatible with other requirements. This could take a while.17:33
hrwhm..17:33
hrwand this 'a while' is long17:33
yoctozeptomgoddard, mnasiadka: ansible-core 2.12 seems worky with k-a :-) 17:46
yoctozepto~> https://review.opendev.org/c/openstack/kolla-ansible/+/81913517:46
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible master: CI: Test minimum and maximum supported ansible versions  https://review.opendev.org/c/openstack/kolla-ansible/+/81792517:49
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible master: [WIP] Add Ansible 5 aka core 2.12 support  https://review.opendev.org/c/openstack/kolla-ansible/+/81913517:50
*** amoralej is now known as amoralej|off17:51
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible master: [DNM] Fully test new Ansible  https://review.opendev.org/c/openstack/kolla-ansible/+/81915217:52
hrwok, restart helped17:59
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible stable/wallaby: Specify log file name for Nova API  https://review.opendev.org/c/openstack/kolla-ansible/+/81705918:04
hrwmeh.18:15
hrwpip lacks some good way to check which package requires other18:16
hrwnova -> pypowervm -> futures18:17
hrwand futures is py2/318:17
hrwand futures is py2, pypowervm is py2/318:18
hrwand pypowervm needs futures only on python 3.618:20
hrwhttps://github.com/powervm/pypowervm/pull/17 so removing it is in progress18:23
hrwuf18:23
hrwonce that done centos source builds should be quick again18:27
* hrw out18:29
opendevreviewMerged openstack/kolla-ansible stable/xena: Specify log file name for Nova API  https://review.opendev.org/c/openstack/kolla-ansible/+/81890519:27
opendevreviewMerged openstack/kolla-ansible stable/victoria: Specify log file name for Nova API  https://review.opendev.org/c/openstack/kolla-ansible/+/81890619:27
daryllHi Folks. I'm setting up my first cluster. I've got a 1 control & 1 compute and everything seems to deploy. When I run my test instance, it can't allocate a port. Digging into ovs ports, I think the tunnel may not be setup between the nodes. Any ideas?19:47
gueswhatguys? is not possible to install kolla without ip assigned to interface for external neutron interface ?  thats weird, why do i need to assign ip to that interface at the first place .... ( rabbitmq will fail ... ERROR: epmd error for host openstack: address (cannot connect to host/port) )21:54

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