| *** syd is now known as Guest7701 | 01:05 | |
| opendevreview | Michal Nasiadka proposed openstack/kolla-ansible master: Revert "CI: Use 2023.2 image for rabbitmq on ipv6 scenario" https://review.opendev.org/c/openstack/kolla-ansible/+/920359 | 07:42 |
|---|---|---|
| opendevreview | Michal Nasiadka proposed openstack/kolla-ansible master: Revert "CI: Use 2023.2 image for rabbitmq on ipv6 scenario" https://review.opendev.org/c/openstack/kolla-ansible/+/920359 | 07:43 |
| opendevreview | Michal Nasiadka proposed openstack/kolla-ansible master: Revert "CI: Use 2023.2 image for rabbitmq on ipv6 scenario" https://review.opendev.org/c/openstack/kolla-ansible/+/920359 | 07:43 |
| sylvr | Hello ! it seems that my seed-bifrost nodes can't manage nodes via their bmc(idrac) on the oob network, but the PXEboot with the IPA works (well only partially as my nodes are stuck in the enroll state), did I missunderstood proviosionning and oob management ? | 08:05 |
| Core5531 | Do any of you actively use Watcher in your environment for dynamically migrating the instances? | 08:40 |
| frickler | bbezak: mnasiadka: remember to set non-zero backport-candidate flag, else patches will not be processed by zuul with no other warning https://review.opendev.org/c/openstack/kolla-ansible/+/920359 | 10:32 |
| frickler | (and I wonder if that rule is really doing more good than bad) | 10:32 |
| bbezak | seems a bit off, this NonZeroBackportCandidate rule | 10:44 |
| bbezak | as backporting is a decision of core team anyway - regardless of this zuul rule. or maybe I'm missing sth about it | 10:46 |
| frickler | well anyone can propose a backport, the core team will then decide whether to approve or reject it, so allowing setting this flag by anyone seems fine to me, if that's your issue | 10:52 |
| bbezak | I just meant preventing zuul running without this flag seems overly sensitive, but maybe that's just me | 11:02 |
| mnasiadka | frickler: should we patch the stable branches without that requirement? | 11:21 |
| mnasiadka | frickler, bbezak: https://review.opendev.org/c/openstack/kolla-ansible/+/920460 - this is ready | 11:24 |
| mnasiadka | question if we should drop docker-py pin only in D onwards, or also backport to C | 11:24 |
| mnasiadka | (centos is failing because it's always building) | 11:25 |
| opendevreview | Michal Nasiadka proposed openstack/kolla master: Drop docker-py pin https://review.opendev.org/c/openstack/kolla/+/920279 | 11:29 |
| SvenKieske | well I proposed that rule to prevent changes being merged which actually need to be backported. I find it weird to argue about it after the fact, decisions can be always revisited of course, but imho that feedback would have been nice during the review: https://review.opendev.org/c/openstack/project-config/+/910212 | 11:36 |
| frickler | mnasiadka: if we don't backport to C, we'll have to carry it around until E I guess, so I'm in favor of backporting | 11:37 |
| SvenKieske | see the history - which is also linked to in the change why we wanted something like this: https://meetings.opendev.org/irclogs/%23openstack-kolla/%23openstack-kolla.2024-02-26.log.html | 11:37 |
| frickler | SvenKieske: well IMO it was an experiment and now we are considering the results of that experiment | 11:37 |
| mnasiadka | I'm fine with requiring backport vote in master, but doing that in stable branch is unnecessary? | 11:38 |
| mnasiadka | Unless somebody wants to convince me | 11:38 |
| SvenKieske | frickler: okay, but it's still looks off to me, let something in review for 3 months, without much talk about it, and then conduct opinions after it being merged for 10 days. | 11:38 |
| SvenKieske | mnasiadka: yeah, for stable probably not needed. ack | 11:39 |
| SvenKieske | not sure how to make this per branch to be honest, would need to consult the gerrit docs again | 11:40 |
| SvenKieske | should be possible with "applicableIf = -branch:stable/* OR -branch:unmaintained/*" | 11:45 |
| frickler | "applicableIf = branch:master" sounds easier ;) | 11:46 |
| mnasiadka | yeah | 11:47 |
| SvenKieske | wondering if that really must be spelled "refs/heads/master"? | 11:48 |
| SvenKieske | I _guess_ not | 11:49 |
| mnasiadka | searching in gerring using branch:master works | 11:49 |
| mnasiadka | so I guess that's the same language | 11:49 |
| SvenKieske | I'll prepare a patch | 11:49 |
| SvenKieske | https://review.opendev.org/c/openstack/project-config/+/920472 | 11:51 |
| opendevreview | Merged openstack/kolla-ansible master: Revert "CI: Use 2023.2 image for rabbitmq on ipv6 scenario" https://review.opendev.org/c/openstack/kolla-ansible/+/920359 | 12:06 |
| opendevreview | Merged openstack/kolla master: CI: pin codespell to <2.3.0 https://review.opendev.org/c/openstack/kolla/+/920461 | 12:06 |
| mnasiadka | SvenKieske: hard tab missing :) | 12:06 |
| mnasiadka | well | 12:06 |
| mnasiadka | it's there | 12:06 |
| mnasiadka | so why CI barfed, hmm | 12:06 |
| SvenKieske | it's just listing 10 possible bug classes, nice :D | 12:07 |
| SvenKieske | not alphabetically sorted? | 12:08 |
| opendevreview | Michal Nasiadka proposed openstack/kolla master: Drop packaging requirement https://review.opendev.org/c/openstack/kolla/+/920279 | 12:08 |
| SvenKieske | yes | 12:08 |
| SvenKieske | I should have not followed the example in the gerrit docs | 12:08 |
| SvenKieske | should hopefully be fixed now | 12:10 |
| sylvr | `| last_error | Failed to validate power driver interface for node <node-uuid>. Error: Missing the following IPMI credentials in node's driver_info: ['ipmi_address'].` I don't understand this error, and I'd like to use the idrac driver and not the ipmitools, any idea what I'm missing ? | 12:11 |
| SvenKieske | seems it's missing the ip address? but some of those error messages are indeed hard to parse. | 12:12 |
| sylvr | but I specified an adresse in etc/kayobe/bmc.yml | 12:14 |
| sylvr | and I'm trying to use the idrac driver, so why is it trying with IPMI ? | 12:14 |
| SvenKieske | as I said, the error messages are often terribly worded. I never used the idrac driver, either the error messages are not per driver, so maybe referring to ipmi_address for every driver, or something is misconfigured to actually use impi. | 12:16 |
| sylvr | okay, and the ipmi_address is the one of the seed to access the network where all the BMC(idrac) are ? (with DHCP) | 12:17 |
| SvenKieske | usually no, for all setups I know you need to specify per baremetal server one ipmi address, I'm not aware of proxy solutions in this space, outside of windows server stuff. but again, I don't have exposure to "modern" idrac, maybe they use something like this? But I doubt it. | 12:19 |
| sylvr | hum... I thought that bifrost/ironic could listen on the network for bmc trying to DHCP and then connect to them (using redfish for exemple) and inspect/introspect the node and report to the seed node | 12:22 |
| sylvr | and populate the correct group to deploy/provision machines depending on their specs/network attached | 12:23 |
| SvenKieske | you are right, but redfish is not used when you use the idrac driver, idrac is used in that case. https://docs.openstack.org/ironic/latest/admin/drivers.html | 12:24 |
| SvenKieske | regardless this is really more of a question for the ironic project I guess, as long as there is no config bug in kolla wrt ironic. | 12:25 |
| opendevreview | Martin Hiner proposed openstack/kolla-ansible master: Fix missing commas in kolla_podman_worker https://review.opendev.org/c/openstack/kolla-ansible/+/920476 | 12:31 |
| sylvr | SvenKieske: hum... okay I see, I think I misconfigured some files in kayobe-config... | 12:33 |
| sylvr | thanks a lot ! I'm learning and it's hard but I love the projects | 12:34 |
| SvenKieske | sylvr: it's always hard at the beginning :) good luck! | 12:34 |
| SvenKieske | could we get RP: +1 on this? https://review.opendev.org/c/openstack/kolla-ansible/+/900528 it's cooking for quite some time now :) | 12:44 |
| opendevreview | scoopex proposed openstack/kolla-ansible master: rabbitmq: configuration improvements https://review.opendev.org/c/openstack/kolla-ansible/+/900528 | 12:55 |
| frickler | SvenKieske: can't you just set that yourself? also, for me it is difficult to assess the value of the config changes and to assert that they do not cause regressions | 12:55 |
| SvenKieske | frickler: no, I can't set that, afaik only you and mnasiadka can set that, at least that is what the onMouseOver Tooltip suggests? | 12:57 |
| frickler | hmm ... "label-Review-Priority = -1..+2 group kolla-core" ... so any core can do it at least, but maybe we can consider unrestricting the RP+1 vote? | 13:02 |
| SvenKieske | so, should we require some kind of testing in a production environment or something before merging this? I think it should at least be possible to write down what is expected to be done, like concrete action items, which would need to be addressed so we can merge something? | 13:03 |
| SvenKieske | frickler: very fine with me regarding Review Priority, but I don't know if it would be misused | 13:03 |
| opendevreview | Verification of a change to openstack/kolla-ansible master failed: CI: drop docker pin https://review.opendev.org/c/openstack/kolla-ansible/+/920460 | 13:05 |
| frickler | SvenKieske: in general words what needs to be done: convince reviewers that the expected benefits outweigh the possible risks. for me that has not happened in that review, but I'm also pretty conservative in that regard most of the time, so maybe other reviewers judge this differently | 13:10 |
| SvenKieske | well honestly you should be able to tell, especially in such changes which couple multiple changes, "change a seems risky, change b seems fine" or "split this up, to reduce risk" or "don't change the default for feature z". a generic: "i fear this might cause regressions" is always true and thus lazy? | 13:13 |
| SvenKieske | so have some concrete points you want to have changed or you are unsure if they are good or cause regressions. that should be possible imho. | 13:13 |
| SvenKieske | I think it's very valid to fear for regression, to be clear, but I just try to move at least the communication forward that we can reduce the actual risk of regressions :) | 13:18 |
| opendevreview | Michal Arbet proposed openstack/kolla-ansible master: Bash replacement https://review.opendev.org/c/openstack/kolla-ansible/+/920368 | 13:36 |
| opendevreview | Rafal Lewandowski proposed openstack/kayobe master: Add ironic config files clean up tasks to overcloud deprovision https://review.opendev.org/c/openstack/kayobe/+/920546 | 14:36 |
| SvenKieske | do we still want this? https://review.opendev.org/c/openstack/kolla-ansible/+/912585 | 15:20 |
| opendevreview | Michal Nasiadka proposed openstack/kolla-ansible stable/2024.1: Revert "CI: Use 2023.2 image for rabbitmq on ipv6 scenario" https://review.opendev.org/c/openstack/kolla-ansible/+/920496 | 15:22 |
| opendevreview | Michal Nasiadka proposed openstack/kolla master: Drop packaging requirement https://review.opendev.org/c/openstack/kolla/+/920279 | 15:29 |
| opendevreview | Verification of a change to openstack/kayobe master failed: Bump up Ansible supported versions to 8.x/9.x https://review.opendev.org/c/openstack/kayobe/+/910513 | 15:30 |
| opendevreview | Michal Nasiadka proposed openstack/kayobe master: Bump up Ansible supported versions to 8.x/9.x https://review.opendev.org/c/openstack/kayobe/+/910513 | 15:31 |
| opendevreview | Michal Arbet proposed openstack/kolla-ansible master: Bash replacement https://review.opendev.org/c/openstack/kolla-ansible/+/920368 | 15:43 |
| opendevreview | Merged openstack/kayobe stable/2023.1: Add python3-devel to Kayobe dependencies https://review.opendev.org/c/openstack/kayobe/+/917881 | 17:24 |
| opendevreview | Michal Arbet proposed openstack/kolla-ansible master: Bash replacement https://review.opendev.org/c/openstack/kolla-ansible/+/920368 | 17:32 |
| opendevreview | Pierre Riteau proposed openstack/kolla master: Add packaging as an explicit dependency https://review.opendev.org/c/openstack/kolla/+/920381 | 19:04 |
| opendevreview | Michal Nasiadka proposed openstack/kolla master: Drop packaging requirement https://review.opendev.org/c/openstack/kolla/+/920279 | 19:08 |
| opendevreview | Michal Nasiadka proposed openstack/kolla master: WIP: Move pre tasks into roles https://review.opendev.org/c/openstack/kolla/+/920590 | 19:32 |
| opendevreview | Merged openstack/kolla-ansible stable/2024.1: Revert "CI: Use 2023.2 image for rabbitmq on ipv6 scenario" https://review.opendev.org/c/openstack/kolla-ansible/+/920496 | 19:56 |
| opendevreview | Michal Arbet proposed openstack/kolla-ansible master: Bash replacement https://review.opendev.org/c/openstack/kolla-ansible/+/920368 | 20:28 |
| opendevreview | Michal Arbet proposed openstack/kolla-ansible master: Bash replacement https://review.opendev.org/c/openstack/kolla-ansible/+/920368 | 23:21 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!