Wednesday, 2023-04-26

opendevreviewMerged openstack/openstack-ansible stable/yoga: Switch spice-html5 source to freedesktop gitlab  https://review.opendev.org/c/openstack/openstack-ansible/+/88131701:09
psyminmaking more progress it seems, now when I log into horizon I get this output (and more) https://paste.opendev.org/show/beJ7D1e0NnOe9ObCD9Or/03:02
noonedeadpunkpsymin[m]: I don't actually see an end of the provided stack trace with result error message05:13
jrosseri would guess that neutron api is down maybe?05:38
noonedeadpunkyeah. might be that. at least it leans toward this 05:54
jrosserthis fails across the board on jammy which is odd https://review.opendev.org/c/openstack/openstack-ansible/+/879085?tab=change-view-tab-header-zuul-results-summary08:41
noonedeadpunkI kinda wonder if now ubuntu has packed faulty OVN version09:09
noonedeadpunkthat is simmilar to what we had with CentOS09:09
noonedeadpunk` nova.exception.PortBindingFailed: Binding failed for port 425f7fdf-455b-4783-84df-e63353ce5b37, please check neutron logs for more information.`09:10
noonedeadpunkyup, pretty much https://zuul.opendev.org/t/openstack/build/e66c75a713364ae69fca88ce3cb87e39/log/logs/host/ovn/ovn-northd.log.txt#3309:10
noonedeadpunkopenvswitch-common=3.1.0-1~cloud009:12
noonedeadpunkpfffff09:12
noonedeadpunkI think we've merged switch to antelope packages09:13
jrosserahha that would explain it09:15
noonedeadpunkhttps://bugs.launchpad.net/cloud-archive/+bug/201775709:45
noonedeadpunkIn the meanwhile I guess we need to update https://opendev.org/openstack/openstack-ansible-os_neutron/commit/f1a8c358531bdf86d8aeda725bc0b1c347d325c109:45
jrossernoonedeadpunk: so something about this comment is now changed? https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/878911/6/tasks/providers/ovn_config.yml#5511:41
noonedeadpunknope11:42
noonedeadpunkjsut affect jammy as well11:42
noonedeadpunkand well. RDO is fixed now :D11:42
noonedeadpunkSo yes, smth has changed :D11:42
jrosseri thought that `--no-record-hostname` would be helping11:44
noonedeadpunkit's `when: - ansible_facts['pkg_mgr'] == 'dnf'`12:33
noonedeadpunkthe reason why it's not12:34
noonedeadpunkalso path should be diffferent for Ubuntu12:34
noonedeadpunkI will patch it now12:34
NeilHanlonpsymin[m]: if you're using my openstack_user_config as a base, it's missing some config to use linux bridges with Zed.. i am updating my stuff now to use straight OVS instead of LXB..13:19
NeilHanlonbecause I can't be bothered to figure out OVN for my lab lol13:19
opendevreviewDamian Dąbrowski proposed openstack/openstack-ansible master: Fix protocol in magnum_url  https://review.opendev.org/c/openstack/openstack-ansible/+/88156514:02
opendevreviewDamian Dąbrowski proposed openstack/openstack-ansible master: [DNM] Do not define cluster template labels  https://review.opendev.org/c/openstack/openstack-ansible/+/88156614:02
opendevreviewDamian Dąbrowski proposed openstack/openstack-ansible-os_magnum master: Rename floating IP option for coe_cluster_template  https://review.opendev.org/c/openstack/openstack-ansible-os_magnum/+/88048414:02
damiandabrowskinoonedeadpunk: I spent some time on magnum issue. It's quite messed up :/14:05
damiandabrowskicommit msg in https://review.opendev.org/c/openstack/openstack-ansible/+/881566 describes the problem14:05
noonedeadpunkI still think it's module issue14:05
noonedeadpunkdamiandabrowski: do you have some sandbox/test playbook?14:06
noonedeadpunkor at least sandbox with magnum?:)14:07
damiandabrowskitechnically yes, but magnum tends to go down during tempest tests for some reason14:08
damiandabrowskibut magnum playbook works fine there, so you can jump in if you want :D 14:08
psymin[m]<NeilHanlon> "psymin: if you're using my..." <- I am using that config.  I added the variable neutron_plugin_type: "ml2.lxb"14:24
psymin[m]Not sure if that was the right thing to do or not, but it made it through the playbook.14:24
NeilHanlonthat works, too :)14:26
psymin[m]I'm open to using OVS, it might be a benefit, not sure.  I'm mostly eager to have a functional system before digging too deeply into which parts to tinker with14:29
NeilHanlonOVS is a bear, but with the LXB plugin going experimental, it might be worth looking at. Thankfully they can re-use the same bridges you're using, if you choose to14:29
NeilHanlonand that's definitely fair :) 14:30
psymin[m]I have three bridges set up on each server, br-mgmt, br-storage and br-vxlan.  Each tied to a separate physical nic.  I didn't set up any vlan tagging manually, I wonder if I should?  I also sort of wonder if I should use the private networks in the example rather than the private networks I'm using, just to be more similar to normal.14:31
psymin[m]I would prefer to do it the "normal" way, whichever way that is.  So if you do get a config working with OVS I'd love to see it :)14:35
psymin[m]<noonedeadpunk> "psymin: I don't actually see..." <- I'm not sure which portion of the webpage debug output to share.14:40
opendevreviewDamian Dąbrowski proposed openstack/openstack-ansible-haproxy_server master: Deprecate certbot-auto  https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/88157814:46
opendevreviewDamian Dąbrowski proposed openstack/openstack-ansible-haproxy_server master: Deprecate certbot-auto  https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/88157814:48
opendevreviewDamian Dąbrowski proposed openstack/openstack-ansible master: Deprecate certbot-auto  https://review.opendev.org/c/openstack/openstack-ansible/+/88157914:48
psymin[m]I did get this warning during the playbook.  Digging into apache stuff in that container now.  https://paste.opendev.org/show/bxzrIdXzJMD9iXu8tj1u/14:53
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_neutron master: Workaround ovs bug that resets hostname with add command  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/88158215:33
noonedeadpunkI hope that will fix ubuntu ^15:33
jamesdentondoh15:33
psyminI think every healthcheck is failing https://paste.opendev.org/show/byUddAo0IZee2EoZBfQ6/15:55
noonedeadpunkpsymin: but has playbook failed?16:01
psyminplaybooks had success16:02
psyminmy manually created linux bridges might be wrong?  or setting the variable neutron_plugin_type: "ml2.lxb" might have been the wrong option?16:03
psyminI guess the 404 for the healthcheck isn't occuring at the moment.16:08
NeilHanlonpsymin: run this and send a paste w/ the output `echo "show stat" | nc -U /run/haproxy.stat | cut -d "," -f 1,2,5-11,18,24,27,30,36,50,37,56,57,62 | column -s, -t `16:15
psyminhttps://paste.opendev.org/show/b3olFAdNqPiHLW09aqo8/16:16
NeilHanlon`lxc-attach infra1_neutron_server_container-a831628d` and then run `systemctl status neutron.slice`16:17
psyminnice, thank you.  I'm also seeing some errors in syslog on the host regarding neutron16:18
psyminhttps://paste.opendev.org/show/bVA3720OrSz5Z7ksE6Xb/16:18
noonedeadpunkpsymin: are you deploying OVN?16:21
noonedeadpunkAs then vxlan is not valid thing indeed16:21
noonedeadpunkWe haven't updated docs though...16:21
noonedeadpunk(everywhere)16:22
noonedeadpunkvxlan is valid for ovs/lxb networking16:22
noonedeadpunkand according to the paste it should be ovn16:22
psyminnoonedeadpunk, Okay.  I probably need to rethink my network and network config.  I wasn't intending to deploy ovn but if that is the path of least resistance I'm all for it.16:23
noonedeadpunkwell, it's just default which you can easily override16:24
noonedeadpunkbut then it should be geneve instead of vxlan16:24
admin1ovn works nicely  :) 16:44
NeilHanlonbut change is scary!16:45
admin1i deployed in new16:45
psyminIs there a URL I should be reading to help me configure the target servers, the openstack_user_config.yml and the user_variables.yml for ovn?16:46
psyminI manually configured br-mgmt, br-storage and br-vxlan on the targets, should I not do that for ovn?16:47
psyminhttps://docs.openstack.org/openstack-ansible-os_neutron/latest/app-ovn.html16:49
psyminadmin1, when you deployed in new, did you deploy antelope?  zed?  Did you deploy to Ubuntu 22.04.2 server?17:19
jrosserpsymin: it's always worth remembering that building an all-in-one will get you a reference deployment to work off17:26
jrosserthe default will be OVN17:26
jrosserand tbh it is not the right question to ask if some branch or other was a successful deployment17:27
jrosserbecasue it pretty much always comes down to getting the config right17:27
psyminokay, I'll deploy aio to baremetal after this 17:33
jrosserthe aio contains a bunch of config to make it fit in a small system too17:38
jrosserbut the openstack_user_config should be pretty close to what you need17:38
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_neutron master: Workaround ovs bug that resets hostname with add command  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/88158217:42
noonedeadpunkpsymin: you can also cheat by checking configs in CI ;)17:43
noonedeadpunkbut this is actually the doc https://docs.openstack.org/openstack-ansible-os_neutron/latest/app-ovn.html17:44
noonedeadpunkI think in your current state you need to ensure that neutron_plugin_base and neutron_ml2_drivers_type are correct17:44
noonedeadpunkor well, default :)17:45
noonedeadpunkso `neutron_plugin_base: ['ovn-router']` and neutron_ml2_drivers_type: "geneve,vlan,flat"17:46
psyminthank you17:57
admin1psymin, ubuntu 22.04 , tag 26.0.1 18:09
admin1got magnum on it deploying k8s .. octavia works good a well .. 18:09
admin1so far happy with it 18:09
psyminI haven't been setting up vlan tagging, since I have physical interfaces for each network.  I assume I should probably set up those tags.18:13
psyminhttps://docs.openstack.org/openstack-ansible/zed/_images/network-arch-multiple-interfaces.png18:14
jrosserit doesn’t matter so much, OSA cares about the bridges for the most part18:14
jrosserand neutron the interfaces you specify in provider_networks18:15
jrosserwhere I recommend using a vlan beyond just a lab toy is your external network because using type “flat” for that just stores up trouble for later18:16
jrosserbut even then, you would be using a trunk port for that and dealing with the vlan stuff 1) in your switch and 2) in the neutron setup via its api18:16
jrossernot as part of the deploy environment18:17
noonedeadpunkI'm usually setting a flat network to a vlan :D and then add vlan network as a parent interface :D18:29
noonedeadpunkProbably I could use jsut vlan....18:29
spateljamesdenton around?19:10
spatelI have quick question related OVN bridge mapping, I have ovn-bridge-mappings="physnet1:br-ex" 19:28
spatelhow does physnet map with our external interface? 19:28
psyminheh, in the aio page for zed, it says "The Zed release is only compatible with Debian 11 (bullseye), Ubuntu 20.04 (Focal Fossa), CentOS 9 Stream, and derivitives of CentOS Stream/RHEL such as Rocky Linux."  I'm booted to Ubuntu 22.04.2 :P19:37
psyminspatel, I'm way over my head on all this stuff, but here is a ChatGPTv3.5 answer to your query https://paste.opendev.org/show/bZSL0vdLh6Bp6GtkTpgL/19:39
spatelpsymin that is cool but still they didn't answer that question how physnet1 is map with my external interface (in my case br-vlan) 19:42
spatelI can understand physnet1 is logical name. It doesn't existing on OS 19:43
admin1psymin, it works on 22.0420:06
psymingood to hear, ran into an issue with task "TASK [openstack.osa.db_setup : Create database for service]"  Setting no_log: false and redoing20:09
psyminhttps://paste.opendev.org/show/bJy5VvHbY0tokpsBw67a/20:11
jrosserpsymin: here is the compatibility matrix https://docs.openstack.org/openstack-ansible/latest/admin/upgrades/compatibility-matrix.html20:27
psyminthat container has /usr/bin/python3.10 and a symlink for /usr/bin/python3 so I assume _oslodb_ansible_python_interpreter should resolve to one of those20:27
jrosserignore that :)20:28
jrosserlook that is says "See stdout/stderr for the exact error"20:28
jrosserthe interpreter message is a generic error message from the ansible module20:28
jrossernothing at all specific about what actually happened20:28
psyminhmm I wonder how to find the stdout for that20:28
jrosserunset no_log20:28
jrosserhttps://github.com/openstack/openstack-ansible-plugins/blob/stable/zed/roles/db_setup/tasks/main.yml20:29
jrosseris this your all-in-one build?20:30
psyminthis is aio, yes20:30
psyminthe paste that mentions stdout is when no_log: false20:30
psyminin keystone container path /openstack/venvs/ doesn't exist currently20:31
jrosserbut it's /openstack/venvs/utility-26.1.0/bin/python20:32
jrosser^ utility container20:32
jrosserthats where all the db operations are done20:32
psyminthat path also doesn't exist on utility container20:33
jrosserthen something has failed with deploying the utility container20:34
psyminI'll wipe out containers and rebuil20:34
psyminthis time with _venv_wheel_build_enable: "true"20:34
jrosserdid you start with a completely clean system for this AIO?20:35
psyminyes, fresh ubuntu 22.04.2 install20:35
jrosserthen it should work really without errors20:35
jrosseras thats exactly what we run in CI many many times a day20:36
jrosser+/- external factors of course20:36
jrosserthis is less than 24h ago https://zuul.opendev.org/t/openstack/build/4ba9aadda754468c8338fa0c5892f78620:37
jrosseryou can browse the logs there and compare20:37
jrosserhere is the start of setup-hosts.yml https://zuul.opendev.org/t/openstack/build/4ba9aadda754468c8338fa0c5892f786/log/job-output.txt#723420:39
psyminreinstalling and keeping a record of my steps21:02
psymin(reinstalling os)21:02
psyminI'm hopeful for this aio deploy to succeed.  Two changes from default BOOTSTRAP_OPTS="bootstrap_host_public_interface=eno4" and lxc_container_default_mtu: 146422:43

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