| opendevreview | Merged openstack/openstack-ansible stable/xena: Backport openstack_testing from Yoga https://review.opendev.org/c/openstack/openstack-ansible/+/876434 | 00:39 |
|---|---|---|
| Elnaz | "Node.js 6.x LTS Boron is no longer actively supported" | 01:07 |
| Elnaz | `apt` issue: | 01:24 |
| Elnaz | The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5EDB1B62EC4926EA | 01:24 |
| Elnaz | Hit:6 https://artifacts.elastic.co/packages/7.x/apt stable InRelease | 01:24 |
| Elnaz | the elk deployed successfully. But `apt update` returns the above failure in loggingX-elastic-logstash containers | 01:26 |
| Elnaz | It solved by `apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5EDB1B62EC4926EA`. | 01:29 |
| Elnaz | "Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead" | 01:30 |
| Elnaz | Only on `logging01-elastic-logstash-container-78f159d3`, I have this issue: https://paste.ubuntu.com/p/dTbKtyBy28/ that does not allow me to update the container with this error: `Aborted (core dumped)... 99%`. Anyway, I'm going to destroy this container with the command: | 10:49 |
| Elnaz | `openstack-ansible containers-lxc-destroy.yml --limit logging01_elastic-logstash_container-78f159d3` | 10:49 |
| Elnaz | or | 10:49 |
| Elnaz | `openstack-ansible lxc-containers-destroy.yml --limit elk_all` | 10:49 |
| Elnaz | but it's skipped: https://paste.ubuntu.ir/toovu | 10:49 |
| Elnaz | How can I delete an LXC container and create just it again? | 10:51 |
| Elnaz | Ooooooh, it was because of `nohup`! | 10:54 |
| Elnaz | `nohup openstack-ansible /opt/openstack-ansible/playbooks/lxc-containers-destroy.yml --limit elk_all & tail -f nohup.out` ((= | 11:07 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible stable/xena: Fix comment typo in nova install playbook https://review.opendev.org/c/openstack/openstack-ansible/+/876680 | 11:08 |
| tr | jrosser, i guess my problem is related to haproxy. frontend galera-front-1 (bind 172.29.236.11:3306) - iam not able to connect to mysql - but iam able to connect via backend galera-back (server infra1_galera_container-8cbb8765 172.29.238.111:3306) | 14:04 |
| jrosser | tr: you should check connectivity between haproxy and the galera container | 14:05 |
| jrosser | look at how haproxy checks the health of galera, it’s with a service on port 9200 I think | 14:06 |
| jrosser | and make sure that the haproxy ip is allowed to connect to that service, there is a set of allowed addresses in the health each service systemd unit | 14:06 |
| jrosser | you can test with curl/get from the haproxy node too | 14:07 |
| jrosser | *wget | 14:07 |
| opendevreview | Merged openstack/ansible-role-python_venv_build stable/xena: Drop empty elements from constraint/requirement files https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/874736 | 14:36 |
| Elnaz | jrosser: https://opendev.org/openstack/openstack-ansible-ops/src/branch/master/elk_metrics_7x :: `ansible-playbook setupKibanaDashboard.yml $USER_VARS` :: but: https://paste.ubuntu.com/p/mb67wP3GG6/ | 15:02 |
| Elnaz | I manually run `curl -sL https://deb.nodesource.com/setup_6.x | sudo -E bash -` in logging1-elastic-logstash-container-78f159d3, and this is the problem: `Your distribution, identified as "jammy", is not currently supported, please contact NodeSource` :: whole output: https://paste.ubuntu.com/p/8k9M7FwGWM/ | 15:06 |
| Elnaz | (What I'm here going to do is to add kibana custom dashboard.) | 15:07 |
| jrosser | well we need to update the node version there I guess :) | 15:08 |
| Elnaz | `curl -sL https://deb.nodesource.com/setup_18.x -o nodesource_setup.sh` :: Ref: https://digitalocean.com/community/tutorials/how-to-install-node-js-on-ubuntu-22-04 | 15:13 |
| Elnaz | jrosser: What if I manually edit the version here: `vim +31 /opt/openstack-ansible-ops/elk_metrics_6x/setupKibanaDashboard.yml`, from 6 in the url to 18? | 15:15 |
| jrosser | Elnaz: perhaps - I’m not really in front of a computer right now :) | 15:16 |
| jrosser | just a phone - so can’t really read the code | 15:16 |
| Elnaz | I edited it to 18.x and passed the step `TASK [Add nodejs 6.x source] `. Let's see what happens next... | 15:20 |
| Elnaz | vim +25 /opt/openstack-ansible-ops/elk_metrics_7x/roles/elastic_kibana/defaults/main.yml | 15:47 |
| Elnaz | `kibana_index_on_elasticsearch: "http://{{ hostvars[groups['elastic'][0]]['ansible_host'] }}:{{ elastic_port}}/.kibana"` | 15:47 |
| Elnaz | the part `http://{{ hostvars[groups['elastic'][0]]['ansible_host'] }}:{{ elastic_port}}/.kibana` translates to what? | 15:48 |
| Elnaz | I get this error: `The error was: 'kibana_index_on_elasticsearch' is undefined\n\nThe error appears to be in '/opt/openstack-ansible-ops/elk_metrics_7x/setupKibanaDashboard.yml'` [https://paste.ubuntu.com/p/dnjjpqCfjZ/] | 15:50 |
| Elnaz | /opt/openstack-ansible-ops/elk_metrics_7x/setupKibanaDashboard.yml: `shell: "/opt/elasticdump/node_modules/elasticdump/bin/elasticdump --input=/tmp/openstack-log-dashboard.json --output={{ kibana_index_on_elasticsearch }} --type=data"` | 15:51 |
| Elnaz | How should I define `kibana_index_on_elasticsearch`? | 15:52 |
| jrosser | Elnaz: sorry I can’t look at this today - but you run on Ubuntu 22.04? | 17:04 |
| Elnaz | I see' All nodes are 22.04. | 17:13 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!