Saturday, 2023-01-14

opendevreviewMerged openstack/ansible-role-systemd_mount stable/xena: Fix mount's systemd unit dependency logic  https://review.opendev.org/c/openstack/ansible-role-systemd_mount/+/86993900:20
opendevreviewMerged openstack/openstack-ansible stable/xena: Bump OpenStack-Ansible Xena  https://review.opendev.org/c/openstack/openstack-ansible/+/86981000:30
chandl3rHello08:57
chandl3rDeploying the 3rd script, this the error encountered: `Could not find the requested service neutron-ovn-metadata-agent: host`08:58
chandl3rWhere is this agent expected to be installed, on infra hosts, on computes, or in neutron-* containers?09:00
jrosserchandl3r: its probably going to be pretty quiet here over the weekend09:07
jrosserchandl3r: but if you could paste the relevant output to paste.opendev.org so that it's clear exactly which task/role has failed that would be helpful09:08
jrosserand also to know which exact version you are deploying and on which OS09:08
chandl3rTha latest released version, Zed09:15
chandl3rYour weekend; I see.09:15
chandl3rhttps://paste.opendev.org/show/bS6GMj0nbbUkdEzyBHxe/09:15
chandl3rI checked computes and the package `neutron-ovn-metadata-agent` was not installed there09:16
jrosserwell, it's a service not a package09:18
jrosserdid you start by building an all-in-one deployment?09:18
jrosserhttps://docs.openstack.org/openstack-ansible/zed/user/aio/quickstart.html09:19
chandl3rfor `neutron_plugin_base:` which one is correctt: `neutron.services.ovn_l3.plugin.OVNL3RouterPlugin` or `ovn-router`?09:19
jrosseris would also recommend that at the current time you use stable/zed rather than the 26.0.0 tag09:19
jrosserwe are about to release 26.1.0 which will roll up all the bug fixes since the initial Zed release, but it's not quite done yet09:20
jrosseryou should use the all-in-one build as your reference as the config is auto-generated and is exactly what we use in CI tests09:20
chandl3rI use ovn-router, don't I?09:21
chandl3rI use stable/zed *, don't I?09:21
chandl3rDo you mean coping all-in-one config to my current env later?09:22
jrosserwell you said you use the latest release, which is tag 26.0.009:23
chandl3rcopying*09:23
jrosserno i mean run an all-in-one in a VM and compare that against your multnode deploy09:23
jrosserbut i'd also recommend using the codesearch tool like this https://codesearch.opendev.org/?q=neutron_plugin_base09:23
jrosserthat would take you to the default setting for neutron_plugin_base here https://opendev.org/openstack/openstack-ansible-os_neutron/src/branch/master/defaults/main.yml#L347-L34809:24
jrossersorry i have to go now09:25
chandl3r"OpenStack-Ansible Zed series was first released with the 26.0.0 tag on 14 December 2022." at https://docs.openstack.org/openstack-ansible/zed/ 09:25
chandl3rI used stable/zed during cloning.09:25
chandl3rThanks jrosser09:26
jrosseroh right ok, thats fine09:26
jrosserbut do try the AIO separately09:26
jrosserit defaults to OVN and should "just work" and give you something to compare against09:26
chandl3rGonna deal with it09:26
opendevreviewMerged openstack/openstack-ansible-os_nova stable/yoga: Fix scheduler track_instance_changes option  https://review.opendev.org/c/openstack/openstack-ansible-os_nova/+/87005912:37
moha7The command `ovn-nbctl lr-list` prints the external router12:48
moha7in OVS world, I could log in to the router (indeed attach to the namespace) by `ip netns exec  <qrouter name> bash`12:51
moha7Here, by OVN backend, how can I go on top of the router?12:52
moha7I want to do `tcpdump` to see what's the Provider issue.12:52
moha7Right hand of the router: 10.9.8.112:53
moha7Left hand of the router: 172.17.235.6212:53
moha7Subnet gateway: 172.17.235.112:53
moha7I can ping the both router hands12:54
moha7But pinging the subnet gateway or something in the internet, 9.9.9.9, is Unreachable!12:54
opendevreviewMerged openstack/openstack-ansible-galera_server stable/yoga: Prevent mariadbcheck.socket to wait for network.target  https://review.opendev.org/c/openstack/openstack-ansible-galera_server/+/87005713:07
jamesdentonmoha7 there is no qrouter namespace for OVN, so your best best is to probably tcpdump using the interface connected to the provider bridge (br-provider or br-ex, etc)13:20
jamesdentonthere is supposedly a trace command, i just don't recall the syntax13:20
moha7jamesdenton: Do we need to define any ACL? for example `ovn-nbctl acl-add` on the ports of external network (switch)?13:42
moha7`tcpdump -i ens224`on infra1 or compute1?13:48
moha7these are available commands on the neutron-ovn-northd-container:13:49
moha7ovn-appctl  ovn-nbctl   ovn-northd  ovn-sbctl   ovn-trace13:50
moha7and there is  trace one13:50
opendevreviewMerged openstack/openstack-ansible stable/zed: Skip haproxy with setup-infrastructure for upgrades  https://review.opendev.org/c/openstack/openstack-ansible/+/87006813:52
jamesdentonif you're looking to capture traffic out the external provider network, that will be via a "gateway" node that you defined as part of the build. You can put a filter on the capture, like "host 9.9.9.9" (ie. tcpdump -i ens224 -n host 9.9.9.9)17:48
moha7I think my issue is somewhere in `openstack_user_config` file; I wrote a new one adding the a part for the Provider as flat network; It's here: https://pastebin.com/zpAZ9wJ720:23
moha7jamesdenton: May you please take a glance at it? ^20:24
moha7This one: https://pastebin.com/VBGf8yi2 20:35
moha7Should I use `network_interface:` for both flat and vlan provider networks? If yes, can the interface be the same for both of them?20:37
opendevreviewMerged openstack/openstack-ansible-os_nova stable/xena: Fix scheduler track_instance_changes option  https://review.opendev.org/c/openstack/openstack-ansible-os_nova/+/87006021:31
opendevreviewMerged openstack/openstack-ansible-lxc_container_create master: Add bridge_type to lxc_container_networks  https://review.opendev.org/c/openstack/openstack-ansible-lxc_container_create/+/86860421:46

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