Wednesday, 2025-01-08

jrossero/ morning08:46
noonedeadpunkgood morning!08:53
jrossernoonedeadpunk: something to watch out for - ~/.ansible is shared between everything that you use molecule for on the same host09:04
noonedeadpunkyeah...09:06
noonedeadpunkI already realized that yesterday evening09:06
noonedeadpunkstil seems systemd roles were not cleaned up09:06
kleinimgariepy, things get moving!09:30
opendevreviewJonathan Rosser proposed openstack/ansible-role-httpd master: Initial commit to the role  https://review.opendev.org/c/openstack/ansible-role-httpd/+/93824509:46
opendevreviewDmitriy Rabotyagov proposed openstack/ansible-role-systemd_service master: Replace functional tests with molecule  https://review.opendev.org/c/openstack/ansible-role-systemd_service/+/93849209:47
opendevreviewDmitriy Rabotyagov proposed openstack/ansible-role-systemd_mount master: Replace functional tests with molecule  https://review.opendev.org/c/openstack/ansible-role-systemd_mount/+/93848909:56
jrosserdo we want to standardise on ansible-role-requirements.yml or requirements.yml ?10:01
noonedeadpunkgiven that we're feeding it to galaxy - ansible-role-requirements.yml doesn't make much sense to me10:02
noonedeadpunkas a-r-r in integrated repo isn't really in galaxy compatible format iirc10:02
noonedeadpunk*feeding to ansible0galaxy through molecule10:03
opendevreviewJonathan Rosser proposed openstack/ansible-config_template master: Replace functional tests with molecule  https://review.opendev.org/c/openstack/ansible-config_template/+/93851310:05
jrosseri do like how you can use the same vm (or your laptop) to test many roles very quickly10:07
jrosserwithout messing up the local environment10:07
* jrosser wonders what kind of adventure lxc-inside-docker might be10:08
noonedeadpunkyeah, that is really nice. I'm just not sure how valuable that's gonna be for openstack roles10:14
noonedeadpunkor well. that depends on tests we wanna do for them kinda10:15
noonedeadpunkbut yes, I'm kind of very happy of progress we have with molecule, as it's very neat10:16
noonedeadpunkworth also updating contributor docs wrt to it...10:16
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_ceilometer master: Remove support for amqp1  https://review.opendev.org/c/openstack/openstack-ansible-os_ceilometer/+/93844410:23
opendevreviewMerged openstack/openstack-ansible master: [doc] Document pretty endpoint namings  https://review.opendev.org/c/openstack/openstack-ansible/+/93453610:24
jrosserthe only thing we might have to maintain is lots more places with collection versions10:24
noonedeadpunkoh yes. especially on stable branches10:28
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-os_manila master: Switch ubuntu zuul jobs from jammy to noble  https://review.opendev.org/c/openstack/openstack-ansible-os_manila/+/93864210:29
noonedeadpunkso in fact for molecule we might indeed need to take a-c-r or smth from integrated repo. but having generic requirements.yml still makes sense for non-opinionated roles10:29
jrosserit might be possible in zuul to have a pre job that prepares the on-disk collections (like we do for the integrated repo), and the we point an env var to those10:31
jrosserthat would make depends-on work10:31
noonedeadpunkthis actually can work, yes10:32
noonedeadpunkand we can control that in integrated repo, I assume10:32
jrossersomething like that, yes10:33
noonedeadpunkbut also I guess important part - to keep ability to run molecule locally without zuul hackery...10:40
noonedeadpunkand that's a tricky part and balance to keep10:41
noonedeadpunkand also would be great to finally figure out publishing to galaxy...10:45
opendevreviewDmitriy Rabotyagov proposed openstack/ansible-role-systemd_service master: Replace functional tests with molecule  https://review.opendev.org/c/openstack/ansible-role-systemd_service/+/93849210:45
opendevreviewDmitriy Rabotyagov proposed openstack/ansible-role-frrouting master: Use FQCN for module calls  https://review.opendev.org/c/openstack/ansible-role-frrouting/+/93827310:59
harunhi all, I am trying to run cluster API but getting an error on magnum-conductor. Logs are in the below. I would appreciate it if you help me. Thank you. 11:03
harunhttps://paste.openstack.org/show/bpHDD146Z0YJBneD7zmZ/11:03
noonedeadpunkI can recall having same issue with absent namespace in k8s cluster11:04
noonedeadpunkbut already can't recall how I've worked around that :D11:04
noonedeadpunkit could be I've just manually created namespace....11:05
jrosserthat didnt happen in the CI jobs though11:05
noonedeadpunkcould be related to certs ofc...11:05
jrosserharun - which versions of OSA etc are you using there?11:05
harunjrosser caracal11:12
harun29.0.211:12
noonedeadpunkI do recall having exact same thing though.....11:12
opendevreviewMerged openstack/openstack-ansible-lxc_container_create master: Solving naming issue of OVS ports for lxc  https://review.opendev.org/c/openstack/openstack-ansible-lxc_container_create/+/93842411:13
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-lxc_container_create stable/2024.2: Solving naming issue of OVS ports for lxc  https://review.opendev.org/c/openstack/openstack-ansible-lxc_container_create/+/93864511:14
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-lxc_container_create stable/2024.1: Solving naming issue of OVS ports for lxc  https://review.opendev.org/c/openstack/openstack-ansible-lxc_container_create/+/93864611:14
noonedeadpunkharun: btw, did you try to use later version of driver? ie - override magnum_magnum_cluster_api_git_install_branch11:15
noonedeadpunkas right now I have it set to smth like v0.24.011:15
noonedeadpunkor well, I'm using own fork which is very close to 0.24.011:16
noonedeadpunkand then also have overrides like this: https://paste.openstack.org/show/bV6xaaUFX93zXnPd26S8/11:17
harunthis is my user variables magnum file: https://paste.openstack.org/show/bdPEaIYe8RweYfdfMiI9/11:21
haruni use 0.24.011:21
noonedeadpunkso ca_file and openstack_ca_file canb totally be problematic points11:21
noonedeadpunkthat would work only if you;re using self-signed certs for both public and internal url11:22
noonedeadpunkin my variant we use lte's encrypt for public and self-signed for internal11:23
jrosseri think the AIO tests this all pretty well?11:24
jrosserthough what is the default for internal TLS at the moment?11:24
jrossertbh the error that harun is getting does not look like tls trouble11:24
noonedeadpunkyeah, true11:25
jrosserthere is an actual response from curl with fields in it11:25
noonedeadpunkthough I really can't recall how I've fixed it... But recall that I had around same defenitions for TLS when I had it11:25
jrosserso i would be checking that the magnum-system namespace is properly present11:25
noonedeadpunkand magnum-system namespace should be created by the driver iirc11:26
jrosseryes it should11:26
noonedeadpunk(and still worh fixing TLS setup for them)11:26
jrossersomething on our to-do list is implement k8s RBAC so the driver only has access to the magnum-system namespace11:27
harunmagnum-system namespace is present and was created by driver11:27
jrosserthat would need creation of the namespace moving out to the playbooks11:27
haruni got also the same error when i did insecure = True11:27
jrosserlike i say this does not look like TLS, you would get a much more obvious SSL error11:28
jrosser`cannot get resource \"openstackmachinetemplates\" in API group \"infrastructure.cluster.x-k8s.io\"` this suggests some problem with cluster-api installation in the management k8s cluster11:29
jrosserharun: you should be able to use something like `kubectl api-resources` to check that the cluster-api resources are present (perhaps with | grep cluster.x)11:33
harunjrosser - this is the output https://paste.openstack.org/show/bzOgFScGVPPyKcz8A4om/11:34
harunthere are present but i don't know why i am getting an error11:36
jrosseryou have the kubeconfig file in place on magnum-conductor?11:37
harunyes, the path is /var/lib/magnum/.kube/config 11:38
jrosserit's perhaps getting beyond my understanding but does `system:anonymous` feel right?11:41
jrosseras the user in your paste which is getting access denied11:41
jrosserwhen the user defined in the kube config file is 'kubernetes-admin'11:42
jrosseroh /o\ sorry i'm misreading this - harun you can't use curl like that on the k8s api11:45
jrosserthat will never work as it wont be using the credentials in the kube config file11:45
haruni got it but i don't understand why magnum is getting an error, it says that 'not found for url: https:<IP>:6443/apis...'12:38
harunWhat do you suggest i do12:41
jrosserwell, magnum-conductor is trying to access a k8s resource that does not exist13:01
jrossernoonedeadpunk: so i have lxc_hosts running in molecule/docker, including able to start an lxc inside docker13:04
jrosserthis is just hacking for now but the only thing i had to do was https://paste.opendev.org/show/bC3PWjNzWb8BEYQ4H3VD/13:05
noonedeadpunkmaybe apparmor is just not installed in docker? Or it refuses to start?13:18
noonedeadpunkso well. this kind of means we indeed can do mnaio in molecule?13:18
noonedeadpunkas given we can pass and wire multiple interfaces, systemd_networkd works to configure bridges in docker...13:19
noonedeadpunkand then lxc can utilize these bridges13:19
noonedeadpunkwe totally will be short on ram though13:19
jrosserit refuses to start, but i think i can work around that13:22
jrosserif you do `aa-teardown` then restart the service, it comes up13:23
jrosseri wonder if it's a mismatch between loaded profiles on the host vs those supposedly present in the docker container13:26
jrossernoonedeadpunk: do you have an example of networking with molecule - we would need to ssh in (with our custom plugin) rather than use the docker connection to actually use lxc_container_create13:31
noonedeadpunkI had _some_ for frrouting: https://opendev.org/openstack/ansible-role-frrouting/src/branch/master/molecule/default/molecule.yml#L17-L2314:26
noonedeadpunkbut then we'd kinda need to generate some kind of openstack_user_config or so... not sure in fact14:27
noonedeadpunkas for our connection plugin to work, it expects some extras in inventory14:27
jrosserspatel: for magum + gpu you need to make a gpu flavor that your reference in your magnum cluster template for the worker nodes, it really is very simple14:37
jrosserif you have nova + gpu working today, really nothing much to do to have magnum workers with gpu14:38
opendevreviewMerged openstack/openstack-ansible-apt_package_pinning master: Replace functional tests with molecule  https://review.opendev.org/c/openstack/openstack-ansible-apt_package_pinning/+/93847614:39
* jrosser feels like am missing some part of the molecule documentation14:58
noonedeadpunkregarding drivers - is in drivers kinda...15:07
noonedeadpunkin code :D15:08
noonedeadpunkhttps://github.com/ansible-community/molecule-plugins/blob/main/src/molecule_plugins/docker/driver.py#L3215:08
noonedeadpunkand then they run playbooks where create/delete networks15:10
noonedeadpunkhttps://github.com/ansible-community/molecule-plugins/blob/main/src/molecule_plugins/docker/playbooks/tasks/create_network.yml15:10
opendevreviewDmitriy Rabotyagov proposed openstack/ansible-role-systemd_mount master: Replace functional tests with molecule  https://review.opendev.org/c/openstack/ansible-role-systemd_mount/+/93848915:27
opendevreviewDmitriy Rabotyagov proposed openstack/ansible-role-httpd master: Initial commit to the role  https://review.opendev.org/c/openstack/ansible-role-httpd/+/93824515:36
opendevreviewDmitriy Rabotyagov proposed openstack/ansible-role-httpd master: Initial commit to the role  https://review.opendev.org/c/openstack/ansible-role-httpd/+/93824515:37
spateljrosser Thank you for the reply on GPU magnum support. I will give it a try as soon as I have GPU in my DC 15:46
opendevreviewMerged openstack/ansible-role-systemd_networkd master: Liberalize static_route defenition  https://review.opendev.org/c/openstack/ansible-role-systemd_networkd/+/93762315:50
opendevreviewMerged openstack/openstack-ansible-os_nova master: Remove support for amqp1  https://review.opendev.org/c/openstack/openstack-ansible-os_nova/+/93845815:53
opendevreviewMerged openstack/openstack-ansible-os_designate master: Remove support for amqp1  https://review.opendev.org/c/openstack/openstack-ansible-os_designate/+/93844716:05
opendevreviewMerged openstack/openstack-ansible-os_keystone master: Remove support for amqp1  https://review.opendev.org/c/openstack/openstack-ansible-os_keystone/+/93845216:06
opendevreviewMerged openstack/openstack-ansible-os_ironic master: Remove support for amqp1  https://review.opendev.org/c/openstack/openstack-ansible-os_ironic/+/93845116:06
opendevreviewMerged openstack/openstack-ansible-os_tacker master: Remove support for amqp1  https://review.opendev.org/c/openstack/openstack-ansible-os_tacker/+/93846016:08
opendevreviewMerged openstack/openstack-ansible-repo_server master: Remove access limitations to repo vhost  https://review.opendev.org/c/openstack/openstack-ansible-repo_server/+/93844016:10
opendevreviewMerged openstack/openstack-ansible-os_heat master: Remove support for amqp1  https://review.opendev.org/c/openstack/openstack-ansible-os_heat/+/93844916:13
opendevreviewMerged openstack/openstack-ansible-os_magnum master: Remove support for amqp1  https://review.opendev.org/c/openstack/openstack-ansible-os_magnum/+/93845316:13
opendevreviewMerged openstack/openstack-ansible-os_aodh master: Remove support for amqp1  https://review.opendev.org/c/openstack/openstack-ansible-os_aodh/+/93844116:17
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-repo_server stable/2024.2: Remove access limitations to repo vhost  https://review.opendev.org/c/openstack/openstack-ansible-repo_server/+/93867616:17
opendevreviewMerged openstack/openstack-ansible-os_mistral master: Remove support for amqp1  https://review.opendev.org/c/openstack/openstack-ansible-os_mistral/+/93845616:18
opendevreviewMerged openstack/openstack-ansible-os_trove master: Remove support for amqp1  https://review.opendev.org/c/openstack/openstack-ansible-os_trove/+/93846116:32
opendevreviewMerged openstack/openstack-ansible-os_neutron master: Remove support for amqp1  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/93845716:37
opendevreviewMerged openstack/openstack-ansible-os_cinder master: Remove support for amqp1  https://review.opendev.org/c/openstack/openstack-ansible-os_cinder/+/93844516:38
opendevreviewMerged openstack/openstack-ansible master: Remove deployment of qdrouterd  https://review.opendev.org/c/openstack/openstack-ansible/+/93806016:44
opendevreviewMerged openstack/openstack-ansible master: Add release note for retirement of qdrouterd and amqp1 messaging  https://review.opendev.org/c/openstack/openstack-ansible/+/93847416:44
opendevreviewMerged openstack/openstack-ansible master: Add noop molecule job to the integrated repo  https://review.opendev.org/c/openstack/openstack-ansible/+/93845016:44
opendevreviewMerged openstack/openstack-ansible master: Add RockyLinux to molecule testing  https://review.opendev.org/c/openstack/openstack-ansible/+/93857116:48
jrosserhere is how to use the osa connection plugin in molecule converge playbook https://paste.opendev.org/show/bzydAerczMup4pBHOqLp/18:43
noonedeadpunkwell19:02
noonedeadpunkhave mixed feelings19:04
noonedeadpunkI guess we can use ssh_keypair role there as well... not sure it will make things much cleaner though19:05
jrosserthat is doing some of the things we expect the operator to do in host-preparation for a real deploy19:07
jrosserso it's not completely unrealistic19:07
jrossermaybe the ssh key belongs in prepare.yml really19:08
jrosserbut it looks like we can add extra inventory content for hosts that are not managed by molecule19:08
noonedeadpunkwhy new group is needed? is it different from what molecule can provide?19:08
jrosseroh you may be right there19:09
jrosserhmm but the IP needs to be somewhere for the ssh connection19:09
jrosserand you don't know what it's going to be up-front as the docker network is created dynamically19:10
noonedeadpunkbut regarding inventory I was thinking more about extra data, like container_tech or management_address or resulting stanza for lxc container itself (which is provided by our dynamic_inventory)19:11
jrosseryes, so i think we would do what the old style tests would do19:11
noonedeadpunkit depends on what is tested there19:11
jrosserwhich is define that in some group/host vars for like container1/container2 etc19:11
noonedeadpunkas openstack.osa.ssh mainly tricky for lxc_host -> lxc_container rather then deploy_host -> lxc_host connection19:12
noonedeadpunkor well...19:12
jrosserthis is doing deploy_host (my vm) ssh -> lxc_host (the docker container) -> then into lxc19:12
jrosser^ i only got half way down that so far19:13
noonedeadpunkI guess my question there would be - where you get from lxc container details?19:13
jrosseri make an extra static hosts in the molecule inventory19:14
noonedeadpunkas there are so many assumptions based on dynamic_inventory in lxc_container_create19:14
noonedeadpunkaha19:14
noonedeadpunkok, and together with host_vars - this may work indeed19:14
jrosseri think it would be best to ignore the dynamic inventory and copy the much simpler stuff from how the tests repo used to do this19:15
noonedeadpunktrue19:15
jrosserwhich really was just setting physical_host and some other minimal thing19:15
noonedeadpunkand then cover dynamic_inventory with python tests instead19:15
noonedeadpunk(if it's not yet)19:15
jrosserwhat i was aiming to do was replace `openstack-ansible-functional-ubuntu-*` in the plugins repo 19:17
jrosserwhich needs as a minimum lxc_hosts / lxc_container_create to test the ssh connection plugin19:17
jrosserthe others are much simpler19:18
noonedeadpunkso I guess that's why I was surprised - I don't see functional jobs for lxc_hosts19:19
noonedeadpunkneither for lxc_container_create19:19
noonedeadpunkas I was kind of under impression that all functional ones that present are already replaced19:20
jrosserahhh i see19:20
noonedeadpunkI was checking with https://codesearch.openstack.org/?q=openstack-ansible-role-jobs&i=nope&literal=nope&files=&excludeFiles=&repos= though19:20
jrosseri was just working initially in the lxc_hosts repo as its much easier to debug that role + molcule like that, rather than as an installed dependancy19:20
noonedeadpunkor well. last one was plugins actually...19:21
jrosserprobably a shift over into lxc_container_create tomorrow for that bit, then finally have something ready to drop into plugins19:22
noonedeadpunkah, and you're likely was working speicifcally on plugins19:22
*** jamesdenton_ is now known as jamesdenton19:24
opendevreviewMerged openstack/openstack-ansible-lxc_container_create stable/2024.2: Solving naming issue of OVS ports for lxc  https://review.opendev.org/c/openstack/openstack-ansible-lxc_container_create/+/93864519:53
opendevreviewMerged openstack/openstack-ansible-os_skyline stable/2024.2: Ensure proper db connection string with SSL enabled  https://review.opendev.org/c/openstack/openstack-ansible-os_skyline/+/93846419:57
opendevreviewMerged openstack/ansible-role-pki master: Add molecule testing  https://review.opendev.org/c/openstack/ansible-role-pki/+/83123620:44
opendevreviewDmitriy Rabotyagov proposed openstack/ansible-role-systemd_networkd master: Replace functional tests with molecule  https://review.opendev.org/c/openstack/ansible-role-systemd_networkd/+/93851720:59
opendevreviewDmitriy Rabotyagov proposed openstack/ansible-role-systemd_networkd master: Install role pre-requisite packages  https://review.opendev.org/c/openstack/ansible-role-systemd_networkd/+/93856020:59
opendevreviewJonathan Rosser proposed openstack/ansible-role-systemd_networkd stable/2024.2: Restart systemd-networkd on routes changes  https://review.opendev.org/c/openstack/ansible-role-systemd_networkd/+/93869921:02
opendevreviewJonathan Rosser proposed openstack/ansible-role-systemd_networkd stable/2024.1: Restart systemd-networkd on routes changes  https://review.opendev.org/c/openstack/ansible-role-systemd_networkd/+/93870021:02
opendevreviewMerged openstack/openstack-ansible-lxc_container_create stable/2024.1: Solving naming issue of OVS ports for lxc  https://review.opendev.org/c/openstack/openstack-ansible-lxc_container_create/+/93864623:16
opendevreviewMerged openstack/openstack-ansible-repo_server master: Remove not used paths on repo-server  https://review.opendev.org/c/openstack/openstack-ansible-repo_server/+/93826823:21
opendevreviewMerged openstack/openstack-ansible-repo_server master: Fix tags usage for the role  https://review.opendev.org/c/openstack/openstack-ansible-repo_server/+/93826923:21

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