Saturday, 2020-11-07

*** jonaspaulo has quit IRC00:13
*** ricolin has quit IRC01:13
*** Limech has quit IRC02:27
*** also_stingrayza has joined #openstack-kolla03:23
*** stingrayza has quit IRC03:25
*** SmearedBeard has quit IRC03:29
*** SmearedBeard has joined #openstack-kolla03:30
*** SmearedBeard has quit IRC03:33
*** SmearedBeard has joined #openstack-kolla03:33
*** TrevorV has quit IRC03:36
*** k_mouza has joined #openstack-kolla05:03
*** SmearedBeard has quit IRC05:04
*** k_mouza has quit IRC05:07
*** lxkong has quit IRC05:23
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-kolla05:33
*** shyamb has joined #openstack-kolla05:38
*** k_mouza has joined #openstack-kolla06:43
*** k_mouza has quit IRC06:48
*** LinPeiWen has quit IRC07:20
*** lxkong has joined #openstack-kolla08:50
*** lxkong has quit IRC08:51
yoctozeptomnasiadka: yeah, that mongodb disappearance is a huge lol; well, it also says we made the right decision by dropping it09:49
*** shyam89 has joined #openstack-kolla10:32
*** shyamb has quit IRC10:34
*** shyam89 has quit IRC10:44
*** shyam89 has joined #openstack-kolla10:45
*** e0ne has joined #openstack-kolla10:46
*** shyam89 has quit IRC10:52
*** kevko_ has quit IRC11:42
*** kevko_ has joined #openstack-kolla11:43
*** kwazar has quit IRC11:49
*** e0ne has quit IRC11:49
*** e0ne has joined #openstack-kolla11:49
*** e0ne has quit IRC12:11
*** k_mouza has joined #openstack-kolla14:12
*** k_mouza has quit IRC14:47
*** k_mouza has joined #openstack-kolla14:48
r3ap3rIf one of your Kolla-Ansible jobs fails in Zuul, can you go back and look at the actual Ansible error on the task that failed or does Zuul just say, "hey, this pipeline failed here" and you have to go an look somewhere else for the full error?14:51
r3ap3rI'm trying to get a better way of "recording" my deployments and what fails than just redirecting the output to a file and then looking through the file at the failed task error. :-)14:52
*** k_mouza has quit IRC14:52
r3ap3rI've been looking at this but I haven't built my CI/CD environment to deploy Kolla and all of my other little projects yet. https://ara.recordsansible.org/blog/2016/11/09/visualizing-kolla-ansible-playbooks-with-ara/14:58
dmsimardr3ap3r: that's an old blog post :)15:44
r3ap3rdmsimard: I know right. lol15:44
dmsimardI've been testing with https://review.opendev.org/#/c/720902/15:44
dmsimardyou can see what it looks like here: https://api.demo.recordsansible.org/?path=kolla-ansible15:45
dmsimardI've otherwise recorded production kolla-ansible runs just by installing ara and enabling the callback plugin15:47
dmsimarddoesn't need specific integration, just install it and enable it before running site.yml15:47
r3ap3rdmsimard: Ok, that is cool. At first I wasn't finding anything that failed that actually returned a message which is kind of what I was wanting. I did find this one: https://api.demo.recordsansible.org/results/201162.html that returns the failed message. Only thing I would like to verify is that if an individual play fails, will it take the message that is returned below the failed play and show it in ARA?15:53
r3ap3rIt would make things easier when going to report "bugs" I think.15:54
*** patchbot has joined #openstack-kolla16:11
*** kevko_ has quit IRC16:47
dmsimardr3ap3r: I'm not sure I understand what you mean :/ ara has the notion of plays but it doesn't currently do much with them17:20
dmsimardtask results are associated to a play, e.g for the result you linked: https://api.demo.recordsansible.org/api/v1/results/20116217:21
dmsimardI guess we can add information about the play in the details panel at the top, that should be trivial and a good addition17:23
r3ap3rTASK [Check zun containers] ****************************************************************************************************************************************************************************************************************17:23
r3ap3r***17:23
r3ap3rskipping: [compute01] => (item={'key': 'zun-api', 'value': {'container_name': 'zun_api', 'group': 'zun-api', 'enabled': True, 'image': 'kolla/ubuntu-source-zun-api:victoria', 'volumes': ['/etc/kolla/zun-api/:/var/lib/kolla/config_files/17:23
r3ap3r:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', '', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}, 'haproxy': {'zun_api': {'enabled': 'yes', 'mode': 'http', 'external': False, 'port': '9517'}, 'zun_api_exte17:23
r3ap3rrnal': {'enabled': 'yes', 'mode': 'http', 'external': True, 'port': '9517'}}}})17:23
r3ap3rskipping: [compute01] => (item={'key': 'zun-wsproxy', 'value': {'container_name': 'zun_wsproxy', 'group': 'zun-wsproxy', 'enabled': True, 'image': 'kolla/ubuntu-source-zun-wsproxy:victoria', 'volumes': ['/etc/kolla/zun-wsproxy/:/var/lib17:23
r3ap3r/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', '', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}, 'haproxy': {'zun_wsproxy': {'enabled': 'yes', 'mode': 'http', 'external': False, 'port'17:23
r3ap3r: '6784'}, 'zun_wsproxy_external': {'enabled': 'yes', 'mode': 'http', 'external': True, 'port': '6784'}}}})17:23
r3ap3rskipping: [compute02] => (item={'key': 'zun-api', 'value': {'container_name': 'zun_api', 'group': 'zun-api', 'enabled': True, 'image': 'kolla/ubuntu-source-zun-api:victoria', 'volumes': ['/etc/kolla/zun-api/:/var/lib/kolla/config_files/17:23
r3ap3r:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', '', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}, 'haproxy': {'zun_api': {'enabled': 'yes', 'mode': 'http', 'external': False, 'port': '9517'}, 'zun_api_exte17:23
r3ap3rrnal': {'enabled': 'yes', 'mode': 'http', 'external': True, 'port': '9517'}}}})17:23
r3ap3rskipping: [compute02] => (item={'key': 'zun-wsproxy', 'value': {'container_name': 'zun_wsproxy', 'group': 'zun-wsproxy', 'enabled': True, 'image': 'kolla/ubuntu-source-zun-wsproxy:victoria', 'volumes': ['/etc/kolla/zun-wsproxy/:/var/lib17:23
r3ap3r/kolla/config_files/:ro', '/etc/localtime:/etc/localtime:ro', '/etc/timezone:/etc/timezone:ro', '', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}, 'haproxy': {'zun_wsproxy': {'enabled': 'yes', 'mode': 'http', 'external': False, 'port'17:23
r3ap3r: '6784'}, 'zun_wsproxy_external': {'enabled': 'yes', 'mode': 'http', 'external': True, 'port': '6784'}}}})17:23
r3ap3rmy bad, wrong thing.17:24
r3ap3rhttps://paste.centos.org/view/42e3b1d617:25
r3ap3rThis is what was looking for in ARA instead of redirecting the playbook output to a file and then using that in "bug reports" and for historical information.17:26
dmsimardok, and did you find what you were looking for ? sorry my brain is tired today :p17:27
r3ap3rI hear ya, I messed up my code input into irc above. lol...17:28
r3ap3rNo, haven't found that specific output yet, looks more geared for things like failed shell script output and telling you what play failed but not why, ie the failed play output. I'll keep looking around though. Thanks for the information you have given me so far. :-)17:30
dmsimardara saves whatever ansible sends to it17:31
dmsimardif there is something missing it's a bug17:31
dmsimardare you looking for actual console output as you pasted it ? ara doesn't actually save that by default17:31
r3ap3rOk, looks like yet another lab project. ;-)17:31
r3ap3rYes, precisely. ^^17:32
dmsimardhttps://ara.readthedocs.io/en/latest/ansible-plugins-and-use-cases.html#adding-records-to-playbooks-after-their-completion17:32
*** imcsk8 has joined #openstack-kolla17:33
dmsimardso you can do, for example, "ansible-playbook foo.yml | tee -a ansible.log" and then attach that to the playbook report in ara17:33
r3ap3rThat actually looks like what I am looking for. I'll give it a shot. Thanks.17:34
dmsimardto get the playbook id you'll need https://ara.readthedocs.io/en/latest/ansible-plugins-and-use-cases.html#ara-playbook-get-the-running-playbook-or-one-in-specific17:35
dmsimardsince you'd be using a callback, action and lookup plugin from ara, you'll want to make sure Ansible is configured to enable them: https://ara.readthedocs.io/en/latest/ansible-configuration.html17:37
dmsimardafk for a while, there's also #ara if you have questions :)17:37
r3ap3rThanks. :-)17:38
*** hrww has joined #openstack-kolla18:43
*** hrww has quit IRC18:44
*** kevko_ has joined #openstack-kolla19:08
*** kevko_ has quit IRC19:16
*** k_mouza has joined #openstack-kolla20:34
*** k_mouza has quit IRC20:39
openstackgerritRadosÅ‚aw Piliszek proposed openstack/kolla-ansible stable/victoria: switch master to victoria  for kolla-ansible  https://review.opendev.org/76182220:49
openstackgerritRadosÅ‚aw Piliszek proposed openstack/kolla-ansible stable/victoria: Switch to Victoria images  https://review.opendev.org/76182220:50
*** ChanServ sets mode: +o yoctozepto21:37
*** yoctozepto changes topic to "IRC meetings on Wednesdays @ 15:00 UTC - agenda @ https://goo.gl/OXB0DL | Whiteboard: https://bit.ly/2MM7mWF | IRC channel is *LOGGED* @ http://goo.gl/3mzZ7b"21:38
*** yoctozepto sets mode: -o yoctozepto21:38
openstackgerritMerged openstack/kolla stable/stein: Add mongodb to skipped images  https://review.opendev.org/76172321:50
openstackgerritMerged openstack/kolla stable/ussuri: Use upper constraints for virtualenv in openstack-base  https://review.opendev.org/76056621:58
openstackgerritMerged openstack/kolla stable/ussuri: rally: add rally-openstack in source - follow up  https://review.opendev.org/76057422:01

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