| *** dasp has joined #openstack-kolla | 00:01 | |
| *** bsanjeewa has joined #openstack-kolla | 01:24 | |
| *** bsanjeewa has quit IRC | 01:26 | |
| *** bsanjeewa_ has quit IRC | 01:26 | |
| *** diurnalist has quit IRC | 01:56 | |
| *** alanmeadows has quit IRC | 02:40 | |
| *** mnasiadka has quit IRC | 03:14 | |
| *** mnasiadka has joined #openstack-kolla | 03:16 | |
| *** alanmeadows has joined #openstack-kolla | 03:21 | |
| *** kevko has joined #openstack-kolla | 03:38 | |
| *** mnasiadka has quit IRC | 03:45 | |
| *** alanmeadows has quit IRC | 03:46 | |
| *** diurnalist has joined #openstack-kolla | 03:47 | |
| *** mnasiadka has joined #openstack-kolla | 03:50 | |
| *** alanmeadows has joined #openstack-kolla | 03:58 | |
| *** alanmeadows has quit IRC | 04:03 | |
| *** alanmeadows has joined #openstack-kolla | 04:15 | |
| *** factor has quit IRC | 04:22 | |
| *** evrardjp has quit IRC | 04:33 | |
| *** kevko has quit IRC | 04:33 | |
| *** evrardjp has joined #openstack-kolla | 04:33 | |
| openstackgerrit | XiaojueGuan proposed openstack/kolla master: Fix bug 1883340 https://review.opendev.org/735410 | 04:46 |
|---|---|---|
| openstack | bug 1883340 in kolla "kolla failed to build tempest" [Undecided,New] https://launchpad.net/bugs/1883340 - Assigned to XiaojueGuan (xiaojuegaun) | 04:46 |
| *** bsanjeewa has joined #openstack-kolla | 06:38 | |
| *** wuchunyang has joined #openstack-kolla | 06:42 | |
| *** eliaswimmer has joined #openstack-kolla | 07:12 | |
| *** bsanjeewa_ has joined #openstack-kolla | 07:22 | |
| *** bsanjeewa has quit IRC | 07:25 | |
| openstackgerrit | Radosław Piliszek proposed openstack/kolla-ansible stable/train: CI: Fix periodics https://review.opendev.org/735419 | 07:37 |
| *** jonaspaulo has joined #openstack-kolla | 07:57 | |
| *** bsanjeewa has joined #openstack-kolla | 08:11 | |
| *** bsanjeewa_ has quit IRC | 08:13 | |
| *** wuchunyang has quit IRC | 08:18 | |
| *** wuchunyang has joined #openstack-kolla | 08:49 | |
| *** born2bake has joined #openstack-kolla | 08:52 | |
| *** bsanjeewa_ has joined #openstack-kolla | 08:53 | |
| *** bsanjeewa has quit IRC | 08:57 | |
| *** bsanjeewa has joined #openstack-kolla | 09:26 | |
| *** bsanjeewa_ has quit IRC | 09:29 | |
| admin0 | good morning | 10:40 |
| admin0 | let me paste the configs and the failure | 10:41 |
| admin0 | kplant, can kolla be installed in focal ? | 10:42 |
| admin0 | because the getting started does not exact mention the OS | 10:42 |
| *** wuchunyang has quit IRC | 10:44 | |
| *** diurnalist has quit IRC | 10:53 | |
| admin0 | first qustion .. when i want to do kolla-verify , which is done from the deployment host .. it searches for network_interface name locally which is on the servers meant for openstack | 11:05 |
| admin0 | and it fails | 11:06 |
| *** bsanjeewa has quit IRC | 11:32 | |
| *** zijlboot has joined #openstack-kolla | 12:10 | |
| *** zijlboot_ has quit IRC | 12:14 | |
| *** also_stingrayza has joined #openstack-kolla | 12:19 | |
| *** stingrayza has quit IRC | 12:22 | |
| *** wuchunyang has joined #openstack-kolla | 12:36 | |
| *** wuchunyang has quit IRC | 15:12 | |
| *** wuchunyang has joined #openstack-kolla | 15:12 | |
| r3ap3r | admin0: I believe born2bake answered your question before and as I mentioned during the same time, the Kolla project as of this date doesn't appear to "officially" support Focal but as born2bake mentioned, it can be done with some modification to the instructions. | 15:13 |
| admin0 | i went with 18.04 just to not do any modifications | 15:14 |
| r3ap3r | Ok, better to probably start with something supported and once you get familiar with the intricacies of the project, then go experimenting. At least that is my philosophy. :-) | 15:15 |
| admin0 | i got an error right now :) https://gist.github.com/a1git/d9c9147ddbd5e6927b9c4f13c2bfcdb4 | 15:16 |
| admin0 | error on line 87 | 15:16 |
| r3ap3r | Ok, how did you run the `kolla-ansible` command? As root or a regular user? | 15:18 |
| admin0 | root | 15:18 |
| admin0 | deloy is a lxc container | 15:19 |
| admin0 | deploy host is a lxc container and i used root .. no virtualenvs | 15:19 |
| r3ap3r | So everything up to this point has been run as root, correct? | 15:19 |
| admin0 | that is correct | 15:19 |
| admin0 | https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html -- this is the page i am following | 15:21 |
| r3ap3r | What Python and Ansible versions are you using? It looks like a "permissions" issue but from the conversation above it looks like you may have gotten the `python-selinux` requirement and your running everything as root soooo, yeah. | 15:22 |
| admin0 | the python-selinux was fixed when i did a apt-get update .. so i can confirm every package is there | 15:23 |
| r3ap3r | Ok. | 15:23 |
| admin0 | i ran the playbook again .. stuck in the same error | 15:27 |
| born2bake | you just need to remember that in focal python 2 was deprecated therefore, you just need to change all packages to python3 instead of python | 15:27 |
| admin0 | i am on bionic | 15:28 |
| admin0 | not focal | 15:28 |
| born2bake | so you are ok then | 15:28 |
| admin0 | everything is bionic .. servers and the deploy host | 15:28 |
| admin0 | i disabled the enable_octavia line ( the error said something about cacerts ) .. can I rerun the playbook again or do I need to delete facts ( it might have cached octavia = yes somewhere ? | 15:31 |
| *** wuchunyang has quit IRC | 15:32 | |
| r3ap3r | admin0: I have never tried deploying Kolla-Ansible from a container, I've only done VM's and Physical hosts. From my experience so far with Containers, permissions to files and external locations are "tricky". I'm by no means a Container expert, didn't start learning anything about Containers until I started trying to deploy Openstack but maybe the "permissions" issue you are having is due to your setup of the | 15:32 |
| r3ap3r | Container you are using to deploy Kolla-Ansible? | 15:32 |
| admin0 | the hosts are physical hosts | 15:34 |
| admin0 | my deployment host is a lxc container | 15:34 |
| admin0 | do i need a bare-metal system as a deployment host ? | 15:34 |
| *** wuchunyang has joined #openstack-kolla | 15:35 | |
| r3ap3r | No, I have deployed from VM's, just not containers. | 15:35 |
| admin0 | the error is coming from ansible command via ssh from the control on permission denied .. it should not have anything to do with the local deployment host | 15:36 |
| r3ap3r | Ok, what version of Ansible do you have installed? | 15:38 |
| admin0 | ansible is 2.9.9 | 15:38 |
| r3ap3r | And you have the deployment host ssh keys copied to all of the physical hosts to the root user? | 15:40 |
| admin0 | deployment host can ssh to all the hosts as root | 15:41 |
| admin0 | this appears like 20+ minutes in the ansible run | 15:41 |
| admin0 | i can gist the full log if required but i have to run it again | 15:41 |
| r3ap3r | I'm not sure what would cause permission issues all of a sudden at bootstrapping a container on a remote host? It maybe a bug in the playbook that is running and setting the permissions incorrectly in the "copying over nova.conf file" play? | 15:45 |
| admin0 | keystone, glance, cinder seems to have no issues | 15:48 |
| admin0 | in the run | 15:48 |
| *** wuchunyang has quit IRC | 15:49 | |
| admin0 | https://asciinema.org/a/INgR4DXfMDzs83uPEExelGS98 | 15:49 |
| admin0 | that is the full run | 15:50 |
| admin0 | as you see, it does not give any error before .. only in the nova part | 15:50 |
| *** wuchunyang has joined #openstack-kolla | 15:50 | |
| r3ap3r | It maybe that play then. I would have to take a look and see what permission set changes there are as compared to maybe the Train deployment and maybe that will tell us something? | 15:51 |
| admin0 | i guess | 15:51 |
| admin0 | if i try train version, do i have to re-format and redo the servers ? | 15:52 |
| *** wuchunya_ has joined #openstack-kolla | 15:53 | |
| r3ap3r | Personnally, I wouldn't think so. Just make sure you do a `kolla-ansible -i multinode destroy` before hand to get rid of any containers that have already been deployed and you should be good. | 15:54 |
| admin0 | ok | 15:54 |
| admin0 | let me try the train version then | 15:54 |
| *** wuchunyang has quit IRC | 15:55 | |
| admin0 | doh .. it removes the multinode and globals file from the current folder :D | 15:55 |
| admin0 | # These hostname must be resolvable from your deployment host | 15:57 |
| admin0 | --- can i use IPs ? or it has to be hostnames specifically ? | 15:57 |
| r3ap3r | IPs can be used, IF you use hostnames, they have to be resolvable... | 15:58 |
| admin0 | how to fix the ansible deprecation warning? Distribution Ubuntu 18.04 on host 192.168.88.x should use /usr/bin/python3 but uses python2 | 16:02 |
| admin0 | it is in prechecks . after this, will run/record the deploy again to check if any errors come up | 16:03 |
| r3ap3r | I have just used Python 3 for my deployments but I use CentOS and not Ubuntu. Dropped Python 2 from all of my stuff as fast as I could. | 16:05 |
| r3ap3r | I would probably get a second opinion for Python 3 on Ubutnu 18.04 though? | 16:06 |
| admin0 | :) | 16:06 |
| admin0 | ok | 16:06 |
| admin0 | its in the deploy of train version now | 16:06 |
| admin0 | will report back if issues | 16:07 |
| r3ap3r | Ok, I should be here for a little while longer. Got some other projects to work on today. ;D | 16:07 |
| *** wuchunya_ has quit IRC | 16:11 | |
| *** wuchunyang has joined #openstack-kolla | 16:12 | |
| *** stokvis has quit IRC | 16:17 | |
| *** stokvis has joined #openstack-kolla | 16:21 | |
| *** wuchunyang has quit IRC | 16:33 | |
| *** wuchunyang has joined #openstack-kolla | 16:33 | |
| *** wuchunyang has quit IRC | 16:34 | |
| *** wuchunyang has joined #openstack-kolla | 16:34 | |
| openstackgerrit | Merged openstack/kolla master: add libibverbs package for openvswitch https://review.opendev.org/734755 | 16:41 |
| openstackgerrit | wu.chunyang proposed openstack/kolla-ansible master: fix deploy nova failed when use kolla_dev_mod https://review.opendev.org/735437 | 16:49 |
| openstackgerrit | Radosław Piliszek proposed openstack/kolla stable/ussuri: add libibverbs package for openvswitch https://review.opendev.org/735438 | 16:51 |
| openstackgerrit | wu.chunyang proposed openstack/kolla-ansible master: fix deploy nova failed when use kolla_dev_mod https://review.opendev.org/735437 | 16:51 |
| *** wuchunyang has quit IRC | 17:01 | |
| *** wuchunyang has joined #openstack-kolla | 17:01 | |
| *** wuchunyang has quit IRC | 17:05 | |
| *** strobert has joined #openstack-kolla | 17:33 | |
| openstackgerrit | Merged openstack/kolla master: Revert "[to-revert] Pin ovsdbapp in neutron to 1.1.0" https://review.opendev.org/732391 | 18:02 |
| *** ricolin has joined #openstack-kolla | 18:25 | |
| *** eliaswimmer has quit IRC | 18:37 | |
| *** eliaswimmer has joined #openstack-kolla | 18:38 | |
| *** eliaswimmer has quit IRC | 18:38 | |
| *** ricolin has quit IRC | 18:42 | |
| openstackgerrit | Radosław Piliszek proposed openstack/kolla-ansible master: Make /dev/kvm permissions handling more robust https://review.opendev.org/735441 | 19:06 |
| admin0 | r3ap3r, train worked fine | 19:08 |
| admin0 | the issue is in the current version | 19:08 |
| kplant | i don't think ussuri has been released for k/k-a yet | 19:19 |
| strobert | yeah. looks like not officially quite out yet. the RC is https://launchpad.net/kolla-ansible/ussuri/10.0.0.0rc1 (for KA) | 19:22 |
| r3ap3r | admin0: cool, glad Train is working out for you. Ussuri is still in the RC phase for Kolla-Ansible so I would probably report the issue you were experiencing. :) | 19:30 |
| admin0 | how do I report it ? | 20:29 |
| admin0 | never reported to kolla | 20:30 |
| admin0 | using cli there are no erros .. i can see endpoints and everything .. but port 80 does not seem to respond ( no gui ) .. checking that one out | 20:31 |
| admin0 | if I made a change to cinder, how to tell kolla-ansible to run only cinder related playbook ? | 20:38 |
| strobert | kolla-ansible -i <inv file> reconfigure --tags cinder | 20:39 |
| admin0 | where/how i can see a list of all available tags ? | 20:39 |
| admin0 | i mean do we have a summary page somewhere ? | 20:40 |
| strobert | I'm not sure (fellow user here). I know most components have one. and I've looked a lot at the playbooks for various reasons, so have picked up some others from that looking. | 20:41 |
| admin0 | also in the documentation, which talks about upgrade, talks about release 5 .. release 6 .. is that equal to tags in the github project ? | 20:42 |
| strobert | sounds like it. is this spot talking about using pip to upgrade the kolla-ansible code in your python virtual env... when yes. for example in traing to go from 9.0.0 to 9.1.0 | 20:45 |
| strobert | s/when yes/then yes/ | 20:46 |
| strobert | or are you talking about the openstack sofwtare itself and not the KA codebasE? | 20:50 |
| admin0 | https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html -- Openstack Release | 20:54 |
| admin0 | how to know what release is what number ? | 20:54 |
| *** e0ne has joined #openstack-kolla | 21:00 | |
| *** e0ne has quit IRC | 21:02 | |
| strobert | that I think would be the docker tag for kolla. I think we just have ours set to train. (sorry going from memory). that way gets the latest train tag. but yeah. likely would be the tags. | 21:03 |
| strobert | I just checked and can confirm. have openstack_release: "train" in my global.yml | 22:04 |
| *** wuchunyang has joined #openstack-kolla | 22:21 | |
| *** wuchunyang has quit IRC | 22:26 | |
| *** factor has joined #openstack-kolla | 22:43 | |
| *** born2bake has quit IRC | 23:07 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!