Tuesday, 2023-12-05

opendevreviewJorhson Deng proposed openstack/kolla master: Unify curl use  https://review.opendev.org/c/openstack/kolla/+/90251401:09
opendevreviewJorhson Deng proposed openstack/kolla master: Unify curl use  https://review.opendev.org/c/openstack/kolla/+/90251401:29
opendevreviewwu.chunyang proposed openstack/kolla-ansible master: CI: Trove: Create a database instance  https://review.opendev.org/c/openstack/kolla-ansible/+/86352103:25
opendevreviewwu.chunyang proposed openstack/kolla-ansible master: CI: Trove: Create a database instance  https://review.opendev.org/c/openstack/kolla-ansible/+/86352106:21
opendevreviewJorhson Deng proposed openstack/kolla master: Unify curl use  https://review.opendev.org/c/openstack/kolla/+/90251406:37
SvenKieskeo/08:04
SvenKieskedcapone2004: glad you could work it out, what was the issue, if I may ask? :)08:04
opendevreviewPierre Riteau proposed openstack/kayobe master: Pin ansible-core at 2.15.6  https://review.opendev.org/c/openstack/kayobe/+/90261408:15
mnasiadkafrickler: do we want to merge gnocchi patch in Kolla before final release?08:28
mnasiadkahttps://review.opendev.org/c/openstack/kolla/+/901574?tab=change-view-tab-header-zuul-results-summary08:29
fricklermnasiadka: we can merge it, the question is whether we want to do a backport and an rc2? though I think we need the latter anyway due to bifrost/kayobe?08:32
mnasiadkafrickler: yes, we need rc2 for kolla08:37
fricklerok, so let's add gnocchi to that08:40
opendevreviewMerged openstack/kolla master: Revert "Disable build of Gnocchi containers"  https://review.opendev.org/c/openstack/kolla/+/90157410:30
fricklermnasiadka: mgoddard: what about https://review.opendev.org/c/openstack/kolla-ansible/+/805598 ? at least let's merge it into master now and we can look at backporting later?10:43
mnasiadkawell, that has merge conflict - so once that's solved - sure10:44
fricklerthat's what I was pinging mgoddard for ;) though it seems kevko did the last rebase? sigh, let me check it myself then10:47
opendevreviewDr. Jens Harbott proposed openstack/kolla-ansible master: Support Ansible max_fail_percentage  https://review.opendev.org/c/openstack/kolla-ansible/+/80559810:52
fricklerah, that was an easy one for once10:52
opendevreviewMichal Nasiadka proposed openstack/kolla stable/2023.2: Revert "Disable build of Gnocchi containers"  https://review.opendev.org/c/openstack/kolla/+/90253910:59
mnasiadkaok then, this merges and then rc211:00
andreykurilinHi folks! Can someone help me understand how properly override horizon policies with kolla-ansible of 2023.1+ ? I think I’m facing some bug (regression of ansible) which is also reproducible in CI11:03
opendevreviewPierre Riteau proposed openstack/kayobe master: Fix Ansible failure with new ansible-core  https://review.opendev.org/c/openstack/kayobe/+/90263411:04
fricklerandreykurilin: where do you see the failure in the ci?11:18
andreykurilinfrickler: I made a small commit to try reproduce the issue https://review.opendev.org/c/openstack/kolla-ansible/+/90176111:26
andreykurilinfrickler: I have not submitted a bug report yet (idk whether it should be submitted to kolla-ansible or Ansible itself)11:26
andreykurilinIt looks like a regression of https://github.com/ansible/ansible/issues/39389 . I can reproduce it with min required ansible of kolla-ansible 2023.1 and latest version as well11:28
andreykurilinhttps://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_2c0/901761/1/check/kolla-ansible-ubuntu/2c06b57/primary/logs/ansible/deploy here you can grep by ansible.errors.AnsibleFileNotFound11:30
andreykurilincurrently, we are bypassing this issue in our deployment by hacking kolla-ansible to use older ansible release as a short-term solution. It is ugly way, so want to hear whether we are doing something completely wrong, or it looks like a valid bug, etc11:32
fricklerandreykurilin: using the example from the issue I get "foo": "[] + [ 'one' ] + [ 'two' ] + [ 'three' ]" with ansible 2.15.2, so this seems to have indeed regressed again, but different than before12:15
fricklermnasiadka: ^^ not sure yet if this is a usage issue on our side or a real ansible bug, though?12:16
SvenKieskedid anybody already (re)opened a bug either in k-a or upstream about this?12:46
fricklerSvenKieske: andreykurilin: seems https://github.com/ansible/ansible/issues/80404 is the answer. so bug in k-a12:48
SvenKieskemhm, do we use this pattern often? oO12:52
fricklerI'm wondering that, too. see also https://docs.ansible.com/ansible-core/2.14/porting_guides/porting_guide_core_2.13.html#playbook12:52
andreykurilinfrickler: thank you for pointing to Ansible’s bug report and docs. I couldn't find it quickly12:55
fricklerandreykurilin: thanks for providing the original issue, I just searched for the title of that once more ;)12:56
fricklerandreykurilin: do you want to create the bug report for kolla-ansible since you discovered the issue? the fix should be pretty easy then, but we'll want to backport so having a bug attached will be better12:58
andreykurilinSvenKieske: it looks like this pattern is used only in one place - horizon role.12:58
andreykurilinfrickler: working on it12:58
mnasiadkaphew, situation solved itself :)13:00
fricklertwo easy issues in a row, what kind of holiday is this? ;)13:04
andreykurilinhttps://bugs.launchpad.net/kolla-ansible/+bug/2045660 I am not good at writing, but tried to put enough info13:08
SvenKieskety!13:14
mnasiadkaso where's the fix? :)13:18
mnasiadkahmm13:20
mnasiadka2023-12-05 12:59:09.582 971 ERROR oslo_service.service amqp.exceptions.PreconditionFailed: Queue.declare: (406) PRECONDITION_FAILED - inequivalent arg 'x-queue-type' for queue 'cinder-volume' in vhost '/': received the value 'quorum' of type 'longstr' but current is none13:20
mnasiadkain https://zuul.opendev.org/t/openstack/build/7a5631bcfd0b4c2cb7d2e4d7f1dcff8e/logs13:21
andreykurilinmnasiadka: I can work on it, but as @frickler found the solution, it makes sense to give all the credits to him13:23
mnasiadkaYou can add "Co-Authored-By: " in the commit message, I'm sure frickler will be happy ;)13:24
andreykurilinOk, start working on it13:25
* frickler sure is happy, will happily approve such a patch :)13:25
opendevreviewAndriy Kurilin proposed openstack/kolla-ansible master: Fix broken list concatenation in horizon role  https://review.opendev.org/c/openstack/kolla-ansible/+/90265913:45
opendevreviewAndriy Kurilin proposed openstack/kolla-ansible master: Fix broken list concatenation in horizon role  https://review.opendev.org/c/openstack/kolla-ansible/+/90265913:50
opendevreviewAndriy Kurilin proposed openstack/kolla-ansible master: Fix broken list concatenation in horizon role  https://review.opendev.org/c/openstack/kolla-ansible/+/90265913:59
opendevreviewPierre Riteau proposed openstack/kayobe stable/2023.1: Pin ansible-core at 2.14.11  https://review.opendev.org/c/openstack/kayobe/+/90266014:00
opendevreviewMerged openstack/kolla stable/2023.2: Revert "Disable build of Gnocchi containers"  https://review.opendev.org/c/openstack/kolla/+/90253915:06
mnasiadkaok, gnocchi is there, time for rc215:21
andreykurilinhttps://review.opendev.org/c/openstack/kolla-ansible/+/902659 upgrade jobs are failing due to new steps that I introduced. I do not know how upgrade jobs are designed, so I am wondering whether moving tests into a separate follow-up change will fix an issue or not. Any suggestions?15:25
opendevreviewPierre Riteau proposed openstack/kayobe master: Install setuptools before creating virtualenv  https://review.opendev.org/c/openstack/kayobe/+/88195715:26
SvenKieskemhhm15:28
SvenKieskeandreykurilin: are you sure the failure is related to your change? unfortunately the arm64 pipeline fails regularly for all kind of reasons.15:29
fricklerwe need to backport the fix to 2023.1 before the upgrade jobs work I think15:32
fricklerandreykurilin: so maybe split the fix and the new tests into two patches, we can backport the fix first then15:33
SvenKieskeah of course15:34
frickleralso we need to change master to upgrade from 2023.2 now? or do we wait for the official release first?15:35
SvenKieskemhm, isn't that specified in our release docs? I guess it isn't?15:36
SvenKieskewould there be any negative side effect by already switching now?15:36
SvenKieskeI can't think of any right now, but I never thought about this problem before.15:37
mnasiadkafrickler: actually - did we update master upgrade jobs to use 2023.1?15:44
mnasiadkaerm 2023.215:45
mnasiadkabut the images in master are 2023.215:45
mnasiadkaso the upgrade is not an upgrade now :D15:45
mnasiadkawell, we upgrade from 2023.1 to 2023.2 (master)15:45
mnasiadkasorry, my brain probably decided to shut off15:45
mnasiadkalet's get 2023.2 released as final, then we can do some crazy things15:46
SvenKieskewhat about the slurp upgrade stuff? there are no volunteers to implement that yet, right? (sorry for making stuff even more complicated)15:46
mnasiadkanormally we did not switch in the past for a couple of weeks, to get some stability15:46
mnasiadkaSvenKieske: SHPC is going to work on SLURP15:46
SvenKieske:)15:46
SvenKieskeso wait for some stability it is?15:48
mnasiadkaI think so, let's release final for bobcat15:48
mnasiadkaand then think what next tomorrow15:48
opendevreviewMerged openstack/kolla-ansible master: Support Ansible max_fail_percentage  https://review.opendev.org/c/openstack/kolla-ansible/+/80559815:55
opendevreviewAndriy Kurilin proposed openstack/kolla-ansible master: Fix broken list concatenation in horizon role  https://review.opendev.org/c/openstack/kolla-ansible/+/90265916:01
opendevreviewAndriy Kurilin proposed openstack/kolla-ansible master: [ci] check ability to override horizon policies  https://review.opendev.org/c/openstack/kolla-ansible/+/90176116:01
fricklerhave we ever seen module failures with error -13? just found out about https://review.opendev.org/c/openstack/openstack-ansible/+/851426 and similar issues in opendev16:14
mnasiadkanot really16:15
mnasiadkahmm, there are those issues with host unreachable or something similar16:16
mnasiadkabut those are extremely rare16:16
SvenKieskewell not in the cephadm upgrade jobs? it's rather common there? and these are the only jobs that could trigger host unreachable?16:20
SvenKieskecould be worth it to check if cephadm jobs are more stable with this imho.16:21
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible master: CI: Use ControlPersist and ControlMaster  https://review.opendev.org/c/openstack/kolla-ansible/+/90269916:24
mnasiadkalet's see16:24
SvenKieskeat least the ubuntu cephadm job is green, no failure so far :)17:55
fricklerbut again some rmq queue declare failure in cinder during upgrade. I get the feeling that our handling of the queue changes is not working really well https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_09c/902699/1/check/kolla-ansible-ubuntu-upgrade-cephadm/09cdc7f/primary/logs/kolla/all-ERROR.txt18:59
mnasiadkafrickler: wonder that's only cinder19:15
mnasiadkafrickler: I'll have a look tomorrow19:15
mnasiadkafrickler: I have a feeling we could be better at checking MariaDB/RabbitMQ state after we upgrade it19:18
opendevreviewMerged openstack/kayobe stable/2023.1: Pin ansible-core at 2.14.11  https://review.opendev.org/c/openstack/kayobe/+/90266019:48
dcapone2004SvenKieske, my issue was I had ran the "certificates" command at some point trying to fix the issue when I had the initial nova/neutron problem....what I didn't know was that that command overwrote existing certs at the paths specified in globals.yml21:26
dcapone2004so everytime I kept copying what I thought was "our cert" to haproxy.pem, I was actually copying the generated cert that overwrote our cert (but because the filename didn't change, I didn't realize that is what KA did)21:27
dcapone2004I thought KA would only generate certificates that DIDN'T EXIST already at the paths specified in the globals.yml file21:28
dcapone2004as a side note, that behavior makes more it tricky to use a hybrid of self-signed and CA issued certs21:32

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