| opendevreview | Merged openstack/tempest master: Run cindet-tempest-plugin tests in tempest-extra-tests https://review.opendev.org/c/openstack/tempest/+/937739 | 01:01 |
|---|---|---|
| *** mhen_ is now known as mhen | 02:54 | |
| opendevreview | Christian Berendt proposed openstack/tempest master: Add missing space in enable_volume_image_dep_tests description https://review.opendev.org/c/openstack/tempest/+/937859 | 10:52 |
| *** ykarel_ is now known as ykarel | 12:28 | |
| kopecmartin | frickler: hi, do you think that this https://bugs.launchpad.net/devstack/+bug/2082617 is easily fixable on devstack's side by requiring a value (removing the omit filter) from devstack_localrc or setting it by default to {} ? | 15:19 |
| clarkb | kopecmartin: I suspect that if you default to {} you may haev the same issue? since you'll get a null config and apply defaults | 15:31 |
| clarkb | kopecmartin: instead I think you either make it required or before passing it to the module code you can assert things about the state of the values | 15:32 |
| clarkb | basically my hunch is that if you evaluate the variable without the | default(omit) then errors in evaluating the variable may bubble up and not be covered up by | default(omit) | 15:32 |
| clarkb | but figuring out the correct way to express that in ansible may require some testing | 15:33 |
| kopecmartin | yeah, i understand it the same way, it just looks too easy ;) .. but logically, if the value is always expected then we can get rid of the | default(omit) as the value is mandatory | 15:35 |
| clarkb | ya if it is a required value then removing the default(omit) makes sense. I wasn't sure if that was the case though since devstack can run without providing any configuration | 15:35 |
| kopecmartin | exactly, therefore it looks suspiciously easy | 15:36 |
| mnasiadka | Hello - I'll ask here because maybe that has been observed in Devstack/Tempest jobs as well. We've been observing Ubuntu jobs failing in Kolla with 2024-12-17 16:07:57.695 1075 ERROR neutron.agent.linux.iptables_manager ; Stdout: ; Stderr: ip6tables-restore v1.8.7 (nf_tables): unknown option "--set-xmark" | 18:26 |
| mnasiadka | It looks like related to a kernel bug that was fixed by https://lore.kernel.org/all/20241019-xtables-typos-v2-1-6b8b1735dc8e@0upti.me/ | 18:26 |
| mnasiadka | Anybody seen that anywhere else? | 18:26 |
| mnasiadka | (some logs here: https://383f0bb9b59cf020f443-876e6cf3d0029a37566bbddfa6060dfe.ssl.cf2.rackcdn.com/937891/2/check/kolla-ansible-ubuntu-upgrade/ec2133e/primary/logs/kolla/all-ERROR.txt) | 18:27 |
| -opendevstatus- NOTICE: Gerrit will be restarted to pick up a small configuration update. You may notice a short Gerrit outage. | 21:01 | |
| gmann | mnasiadka: i have not seen this error before but it will be good to ask in neutron channel | 22:03 |
| -opendevstatus- NOTICE: You may have noticed the Gerrit restart was a bit bumpy. We have identified an issue with Gerrit caches that we'd like to address which we think will make this better. This requires one more restart | 22:13 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!