Monday, 2021-08-23

*** sshnaidm|afk is now known as sshnaidm06:34
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Include openstack_services for murano role  https://review.opendev.org/c/openstack/openstack-ansible/+/80537307:11
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Update pip version  https://review.opendev.org/c/openstack/openstack-ansible/+/80558307:15
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Replace deprecated collection names  https://review.opendev.org/c/openstack/openstack-ansible/+/80558507:31
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Replace deprecated include statement  https://review.opendev.org/c/openstack/openstack-ansible/+/80558707:38
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-os_neutron master: Make calico non voting  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/80424007:40
jrosserlets merge https://review.opendev.org/c/openstack/openstack-ansible/+/80486807:44
jrossernoonedeadpunk: i missed your last comment here - should we change it again https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/803990 ?07:51
*** rpittau|afk is now known as rpittau07:51
noonedeadpunknah, I think it's fine07:56
noonedeadpunkI think we also might want to merge https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/804324/207:57
noonedeadpunkjrosser: I think it might be time to decide on the future of https://review.opendev.org/c/openstack/openstack-ansible/+/504795 08:09
noonedeadpunkbecause while concept is kind of interesting, but it's soooo tricky imo...08:09
noonedeadpunkwith so much ways to f**k things up down the road...08:10
noonedeadpunkdamn, bloody erlang repo...09:06
admin1\o09:24
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Include openstack_services for murano role  https://review.opendev.org/c/openstack/openstack-ansible/+/80537310:16
noonedeadpunk\o/10:16
*** arxcruz|off is now known as arxcruz11:01
opendevreviewMerged openstack/openstack-ansible-galera_server stable/wallaby: Update galera to 10.5.12  https://review.opendev.org/c/openstack/openstack-ansible-galera_server/+/80486711:14
mgariepygood morning eveyone12:34
mgariepyeveryone**12:34
opendevreviewMerged openstack/openstack-ansible-os_neutron stable/wallaby: Switch calico job from bionic to focal  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/80471013:25
DanG_hey folks, I'm still trying to debug a network connectivity failure for instances in our openstack which have an IP address in the 10.0.3.0/24 range. These instances can be pinged, but fail to get a response from the metadata service, when an SSH key is hard written into the image their booting from they can be SSHed to but then can't reach the internet. Has anyone got any advice about how to debug or trace the n13:28
DanG_I believe we're running an almost identical configuraton to the prod-ceph example openstack-ansible on victoria13:29
opendevreviewMerged openstack/openstack-ansible-galera_server stable/wallaby: Partial Revert "Bump MariaDB version to 10.5.9"  https://review.opendev.org/c/openstack/openstack-ansible-galera_server/+/80513513:33
opendevreviewMerged openstack/openstack-ansible-os_ceilometer master: Fix wrong variable name in ceilometer.conf.j2 template.  https://review.opendev.org/c/openstack/openstack-ansible-os_ceilometer/+/80086913:38
fricklerDanG_: do you happen to have dedicated security groups on these instances? make sure to allow outbound access, then. access to the metadata service needs to be allowed by the security group rules, too.14:26
frickler(I just had that same issue the other week)14:26
fricklerif that doesn't help, doing tcpdumps in various locations along the path would likely be the next debug step. the details for that depend on your type of network deploment14:27
DanG_frickler: they're identical to instances in the same subnet which are in the ranges 10.0.2.0/24 10.0.1.0/24 or 10.0.4.0/24, and they are working fine, when I was taking a look at this before I noticed the address is in the same range for the LXC containers, so I guess it will likely be a tcpdump hunt :) 14:34
*** rpittau is now known as rpittau|afk15:58
jrosserDanG_: are your network nodes also container hosts (infra1/2/3...) ?15:58
jrosseri think that you need to look in the network namespace for one of the neutron routers on your L3 agent node and look at the routing table15:59
jrosserip netns exec <ns-name> ip r15:59
jrossertraffic that wants to get to the internet should have a next hop of the gateway in your external network16:00
DanG_jrosser: thanks for your suggestion, they are yes, I'll take a look16:02
jrossersomehow the traffic is ending up on the infra host outside the L3 agent network namespace (vrf in network-speak) and interacting with the host routing table16:03
jrosserthat should never happen imho16:03
DanG_thanks jrosser, I'll follow this up tomorrow now :)16:09
opendevreviewMerged openstack/openstack-ansible stable/wallaby: Add shallow_since to parallel git clone  https://review.opendev.org/c/openstack/openstack-ansible/+/80486816:19
opendevreviewMerged openstack/openstack-ansible stable/victoria: Fix permissions for files created on repo server  https://review.opendev.org/c/openstack/openstack-ansible/+/80469317:13
-opendevstatus- NOTICE: The Gerrit service on review.opendev.org has been restarted for a patch version upgrade, resulting in a brief outage21:41
*** gilou_ is now known as Gilou21:43

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