| rdogerrit | rdo-trunk rdo-trunk proposed rdoinfo master: Promote CBS tags update for bobcat-9s-release https://review.rdoproject.org/r/c/rdoinfo/+/51669 | 00:50 |
|---|---|---|
| rdogerrit | rdo-trunk rdo-trunk proposed rdoinfo master: Promote CBS tags update for zed-9s-release https://review.rdoproject.org/r/c/rdoinfo/+/51670 | 00:56 |
| rdogerrit | rdo-trunk rdo-trunk proposed rdoinfo master: Promote CBS tags update for yoga-9s-release https://review.rdoproject.org/r/c/rdoinfo/+/51671 | 00:56 |
| rdogerrit | rdo-trunk rdo-trunk proposed rdoinfo master: Promote CBS tags update for yoga-8s-release https://review.rdoproject.org/r/c/rdoinfo/+/51672 | 00:57 |
| rdogerrit | Merged rdoinfo master: Promote CBS tags update for bobcat-9s-release https://review.rdoproject.org/r/c/rdoinfo/+/51669 | 07:06 |
| rdogerrit | Merged rdoinfo master: Promote CBS tags update for yoga-9s-release https://review.rdoproject.org/r/c/rdoinfo/+/51671 | 07:07 |
| rdogerrit | Marios Andreou proposed rdo-jobs master: Adding new data-plane-adoption-osp17-multinode-to-extracted-crc https://review.rdoproject.org/r/c/rdo-jobs/+/51227 | 07:29 |
| karolinku[m] | Hey, our promotion in caracal-promote-puppet-scenario002 looks like being affected by bug: https://bugs.launchpad.net/tempest/+bug/2053026 | 07:59 |
| jcapitao[m] | karolinku: I see it's failing at first puppet run | 08:37 |
| jcapitao[m] | so no tempest tests were run | 08:38 |
| jcapitao[m] | ah | 08:39 |
| jcapitao[m] | ok I see the failure | 08:39 |
| jcapitao[m] | it failed at tempest init :/ | 08:39 |
| jcapitao[m] | it's because of baribcan test | 08:42 |
| jcapitao[m] | what is strange is the fact that scenario003 is working (it enables barbican as well) | 08:43 |
| karolinku[m] | yep | 08:43 |
| rdogerrit | Marios Andreou proposed rdo-jobs master: Adding new data-plane-adoption-osp17-multinode-to-extracted-crc https://review.rdoproject.org/r/c/rdo-jobs/+/51227 | 08:43 |
| jcapitao[m] | ah no, barbican is disabled in scenario003 | 08:44 |
| jcapitao[m] | https://logserver.rdoproject.org/openstack-periodic-daily/review.rdoproject.org/rdoinfo/master/weirdo-caracal-promote-puppet-scenario003-centos-stream-9/218b37b/logs/weirdo-project/logs/tempest.conf.txt.gz | 08:45 |
| jcapitao[m] | barbican=False | 08:45 |
| jcapitao[m] | I was relying on the table in README https://github.com/openstack/puppet-openstack-integration | 08:45 |
| jcapitao[m] | karolinku: let's wait and see for the resolution in the ticket | 08:50 |
| rdogerrit | Joel Capitao proposed rdo-infra/weirdo master: Revert "Exclude libvirt-9.10.0-1 from appstream repo" https://review.rdoproject.org/r/c/rdo-infra/weirdo/+/51576 | 08:52 |
| rdogerrit | Merged rdoinfo master: Promote CBS tags update for yoga-8s-release https://review.rdoproject.org/r/c/rdoinfo/+/51672 | 08:57 |
| apevec | jcapitao: re. libvirt 10.0.0-2 just landed in CS9 mirrors - did it show up in openinfra AFS too? | 09:15 |
| jcapitao[m] | not yet in openinfra AFS | 09:16 |
| jcapitao[m] | see comment in https://review.opendev.org/c/openstack/puppet-openstack-integration/+/908927 | 09:16 |
| apevec | amoralej: ahh, so your patch to use direct CS primary seed wasn't merged by opendev infra yet? | 09:16 |
| jcapitao[m] | IIRC it was rejected | 09:17 |
| jcapitao[m] | but I'm not sure | 09:17 |
| apevec | ah no it is merged https://review.opendev.org/c/opendev/system-config/+/908030 | 09:17 |
| amoralej | mmm, wait, i thought it's merged | 09:17 |
| amoralej | yeah | 09:17 |
| jcapitao[m] | ah nice | 09:18 |
| amoralej | synchronization to AFS is periodic, so it can take some hours to land in AFS | 09:19 |
| jcapitao[m] | ah ok, this is a recent patch, the following-up of the discussion with arrfab | 09:19 |
| apevec | yeah I guess it just missed last CS9 push | 09:20 |
| jcapitao[m] | what is the frequency ? | 09:21 |
| amoralej | i think some hours | 09:21 |
| amoralej | logs for synchornization are public | 09:21 |
| apevec | actually now I see ykarel reported to opendev: frickler, seeing Disk quota exceeded (122) again | 09:21 |
| apevec | http://mirror.iad.rax.opendev.org/logs/rsync-mirrors/centos-stream.log | 09:21 |
| jcapitao[m] | I see latest zuul jobs in openinfra are still pulling old libvirt | 09:22 |
| amoralej | every 6 hours | 09:23 |
| amoralej | you can also see the compose id | 09:24 |
| amoralej | synced | 09:24 |
| amoralej | http://mirror.regionone.vexxhost-nodepool-tripleo.rdoproject.org/centos-stream/9-stream/COMPOSE_ID | 09:24 |
| amoralej | still the old one | 09:24 |
| apevec | see the log, no disk :( | 09:25 |
| amoralej | ah, last sync contains libvirt | 09:25 |
| apevec | but also, why do we sync autosd ? | 09:25 |
| amoralej | but the error seems to be only in the sigs update | 09:26 |
| amoralej | not in centos | 09:26 |
| amoralej | so, i think it should be there | 09:26 |
| amoralej | art autosd, because when the script was created, it didn't exist, i guess | 09:27 |
| amoralej | we excluded other sigs | 09:27 |
| amoralej | maybe it takes some time to sync from the mirror update server to the rest of AFS members? | 09:28 |
| rdogerrit | Alfredo Moralejo proposed rdoinfo master: Revert "Add rhos-bootstrap" https://review.rdoproject.org/r/c/rdoinfo/+/51577 | 10:15 |
| rdogerrit | Alfredo Moralejo proposed rdoinfo master: Revert "Add rhos-bootstrap" https://review.rdoproject.org/r/c/rdoinfo/+/51577 | 10:19 |
| rdogerrit | mathieu bultel proposed openstack/os-diff-distgit rpm-master: Add os-diff specfile for rdo-package https://review.rdoproject.org/r/c/openstack/os-diff-distgit/+/51560 | 10:42 |
| rdogerrit | mathieu bultel proposed openstack/os-diff-distgit rpm-master: Add os-diff specfile for rdo-package https://review.rdoproject.org/r/c/openstack/os-diff-distgit/+/51560 | 11:08 |
| rdogerrit | mathieu bultel proposed openstack/os-diff-distgit rpm-master: Add os-diff specfile for rdo-package https://review.rdoproject.org/r/c/openstack/os-diff-distgit/+/51560 | 11:29 |
| rdogerrit | Merged rdoinfo master: Promote CBS tags update for zed-9s-release https://review.rdoproject.org/r/c/rdoinfo/+/51670 | 11:39 |
| rdogerrit | mathieu bultel proposed openstack/os-diff-distgit rpm-master: Add os-diff specfile for rdo-package https://review.rdoproject.org/r/c/openstack/os-diff-distgit/+/51560 | 11:44 |
| jcapitao[m] | #startmeeting RDO meeting - 2024-02-14 | 14:01 |
| opendevmeet | Meeting started Wed Feb 14 14:01:54 2024 UTC and is due to finish in 60 minutes. The chair is jcapitao[m]. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:01 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:01 |
| opendevmeet | The meeting name has been set to 'rdo_meeting___2024_02_14' | 14:01 |
| jcapitao[m] | it's meeting time | 14:01 |
| amoralej_ | o/ | 14:02 |
| jcapitao[m] | please add your topic in https://etherpad.opendev.org/p/RDO-Meeting | 14:02 |
| *** amoralej_ is now known as amoralej | 14:02 | |
| jcapitao | #topic roll call | 14:03 |
| karolinku[m] | o/ | 14:03 |
| jcapitao | #chair amoralej karolinku[m] | 14:03 |
| jcapitao | ok let's start with first topic | 14:07 |
| jcapitao | #topic Moving from RHBZ to Jira | 14:07 |
| amoralej | I added that | 14:07 |
| amoralej | #info RDO is moving the activity tracking to https://issues.redhat.com/projects/RDO/ | 14:08 |
| amoralej | #info a new component has been created for packstack, all packstack issues should be reported to RDO jira project now | 14:09 |
| amoralej | we should include it in packstack README file i think | 14:10 |
| jcapitao | +1 | 14:10 |
| amoralej | there is some info in https://wiki.openstack.org/wiki/Packstack btw | 14:10 |
| amoralej | I'm not sure how is that maintained | 14:11 |
| amoralej | apparently i can update it | 14:12 |
| jcapitao | #action RDO core team to edit packstack documentation to set RDO JIRA as new issue tracker | 14:12 |
| spotz[m] | o/ Sorry I'm late had a quick impromptue meeting | 14:13 |
| jcapitao | #chair spotz[m] | 14:13 |
| jcapitao | hey spotz | 14:13 |
| amoralej | i just updated https://wiki.openstack.org/wiki/Packstack#Bugs so it seems to work :) | 14:13 |
| jcapitao | oh nice ! | 14:14 |
| jcapitao | it was quick | 14:14 |
| amoralej | yep, just wiki direct edit | 14:14 |
| karolinku[m] | huh, no code kept | 14:14 |
| jcapitao | ahh ok | 14:15 |
| amoralej | i guess any authenticated user can edit it | 14:17 |
| amoralej | so, it's done :) | 14:17 |
| spotz[m] | clicked through for me but I might be logged in | 14:18 |
| jcapitao | do we still want to add JIRA reference in packstack README ? | 14:18 |
| jcapitao | https://github.com/redhat-openstack/packstack/ | 14:19 |
| jcapitao | well there is a link redirecting to https://wiki.openstack.org/wiki/Packstack | 14:19 |
| jcapitao | so it should be ok | 14:19 |
| spotz[m] | Yeah there should be how to report a bug | 14:19 |
| amoralej | yep, i think that'd be good | 14:19 |
| jcapitao | ok, so I keep the action I put in meeting notes | 14:20 |
| amoralej | #info a banner has been added to bugzilla.redhat.com for RDO product bugs with message "RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/ " | 14:21 |
| spotz[m] | Good work! | 14:21 |
| amoralej | so, from now on, requests should be reported in jira | 14:22 |
| jcapitao | https://issues.redhat.com/browse/RDO-240 FTR | 14:22 |
| amoralej | i've added to epic "Migration to Jira" :) | 14:22 |
| jcapitao | good | 14:23 |
| spotz[m] | Do we have all the tags we need? | 14:23 |
| amoralej | you mean components ? | 14:23 |
| spotz[m] | Maybe, let me click the link again:) | 14:24 |
| amoralej | we have created three components | 14:24 |
| amoralej | https://issues.redhat.com/projects/RDO?selectedItem=com.atlassian.jira.jira-projects-plugin:components-page | 14:24 |
| spotz[m] | Or labels | 14:24 |
| amoralej | yeah, so there are two different things, component and labels, components are more project-admin think, while label are any text, and created under demand | 14:25 |
| spotz[m] | I don't know if we need everything that an internal project has but we might want what we had in Bugzilla | 14:25 |
| amoralej | in bugzilla we had one component per package (hundreds of them), i think we don't need that much | 14:26 |
| jcapitao | actually we reproduced the same component we had in BZ | 14:26 |
| jcapitao | I mean the used one | 14:26 |
| amoralej | for new packages, i think a label new-package would be appropiate | 14:26 |
| amoralej | or something similar | 14:27 |
| jcapitao | under contenido comp ? | 14:27 |
| amoralej | yes | 14:27 |
| jcapitao | WFM | 14:27 |
| spotz[m] | Just looked at the components so I'm definitely talking labels like a First Issue, etc | 14:27 |
| amoralej | yes, that'd be good | 14:28 |
| jcapitao | +1 | 14:28 |
| jcapitao | we definitely need "easy finx" kind of label | 14:28 |
| jcapitao | fix* | 14:28 |
| spotz[m] | Maybe a docs one too, not sure which others we might need | 14:29 |
| amoralej | actually, we were discussing if docs should be a component or a label | 14:30 |
| amoralej | we thought a label may be enough | 14:30 |
| spotz[m] | If you can do it outside of the current components it should be a component if it only applies to components a label | 14:31 |
| amoralej | labels and components are unrelated, you can assign a ticket to only one component and the labels you want | 14:32 |
| amoralej | and there is no restrictions, i mean, labels can be applied to any ticket on any component | 14:33 |
| amoralej | i'm not sure if that's the question | 14:33 |
| spotz[m] | But can you have an issue with no component? | 14:33 |
| amoralej | yes | 14:33 |
| amoralej | most of the tickets we currently have have no component | 14:33 |
| amoralej | as we created them just today :) | 14:33 |
| karolinku[m] | I would use labels as general grouping, as sth which is jist a label (not very important) so I thin for docs should be rather component | 14:33 |
| karolinku[m] | we discover components just today :D | 14:34 |
| amoralej | i'd like to see if we can create some kind of kanban or report by labels or components | 14:34 |
| karolinku[m] | good point | 14:35 |
| amoralej | actually, it seems we can assign more that one component to an issue | 14:36 |
| amoralej | https://issues.redhat.com/browse/RDO-13?jql=project%20%3D%20RDO%20AND%20component%20%3D%20maquinaria | 14:36 |
| amoralej | that's list of issues to one component, i.e. | 14:37 |
| amoralej | i just added one to test | 14:37 |
| amoralej | ah, there we can also list by label | 14:37 |
| amoralej | https://issues.redhat.com/browse/RDO-181?jql=project%20%3D%20RDO%20AND%20labels%20%3D%20RDO-TRUNK-INFRA | 14:38 |
| rdogerrit | mathieu bultel proposed openstack/os-diff-distgit rpm-master: Add os-diff specfile for rdo-package https://review.rdoproject.org/r/c/openstack/os-diff-distgit/+/51560 | 14:38 |
| amoralej | label:RDO-TRUNK-INFRA | 14:38 |
| amoralej | i've just created a favorit filter "RDO-TRUNK-INFRA issues" , i'm not sure if that's just visible for me or for the project | 14:39 |
| jcapitao | I can see it too | 14:40 |
| jcapitao | personnally, I think we should create doc comp | 14:40 |
| spotz[m] | Where in Jira? | 14:40 |
| jcapitao | and keep label to increase flexibility if we want to group some issues together | 14:41 |
| jcapitao | like we do in Gerrit | 14:41 |
| amoralej | works for me | 14:41 |
| amoralej | i mean, adding a new documentation component | 14:42 |
| karolinku[m] | yeah, like we can have different kind of docs in one compnent | 14:42 |
| karolinku[m] | so we can differ them by labels | 14:42 |
| amoralej | ok, go ahead and create it, you should be able to do it | 14:42 |
| amoralej | spotz[m], in https://issues.redhat.com/issues/?jql= | 14:43 |
| amoralej | there is "Favorite Filters" in the left pannel | 14:43 |
| amoralej | i see "RDO-TRUNK-INFRA issues" | 14:43 |
| amoralej | that's what i created, you see it or just me? | 14:43 |
| spotz[m] | Ahh I was looking in jira:) btw I’m not logged and could see everything in RDO which is good | 14:44 |
| amoralej | yep | 14:44 |
| jcapitao | https://issues.redhat.com/projects/RDO?selectedItem=com.atlassian.jira.jira-projects-plugin:components-page | 14:45 |
| jcapitao | 15 min left | 14:45 |
| amoralej | yep | 14:47 |
| jcapitao | amoralej: is there something else for this topic ? | 14:47 |
| amoralej | wrt bz triage, we have done some progress but still in progress | 14:47 |
| amoralej | we will keep working on it ansynchronously and will report next week | 14:47 |
| jcapitao | I cleaned the "Package Review" comp | 14:48 |
| amoralej | let me put some number | 14:48 |
| jcapitao | 3 leftovers but sill active | 14:48 |
| jcapitao | os-diff cyborg and edpm-ansible | 14:48 |
| amoralej | #info the number of open bz to RDO component is 254 | 14:48 |
| jcapitao | in distribution comp you mean ? | 14:49 |
| amoralej | it was > 300 yesterday i think | 14:49 |
| amoralej | in all comps | 14:49 |
| jcapitao | ah! | 14:49 |
| jcapitao | that's a good progress | 14:49 |
| amoralej | https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=__open__&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cshort_desc%2Cchangeddate%2Cbug_severity&list_id=13414005&order=summary%2C%20&product=RDO&query_format=advanced | 14:49 |
| amoralej | actually, 253 right now, one has been closed :) | 14:50 |
| jcapitao | I'll keep working on the CVEs async | 14:50 |
| amoralej | ok, let's sync jcapitao as i'm also working on it | 14:50 |
| jcapitao | ok | 14:50 |
| jcapitao | let's move to next topic | 14:51 |
| karolinku[m] | anything left besides CVE's? | 14:51 |
| jcapitao | #topic RDO Caracal 2024.1 preparation | 14:51 |
| spotz[m] | Wow it's that time already | 14:51 |
| jcapitao | karolinku[m]: I didn't check the other BZ tbh | 14:51 |
| amoralej | how fast it runs | 14:52 |
| jcapitao | so this week is R-6 | 14:52 |
| karolinku[m] | ok, we can sync later | 14:52 |
| jcapitao | #link https://releases.openstack.org/caracal/schedule.html | 14:52 |
| amoralej | so one of the priorities now should be to handle all the dep updates we have in gerrit | 14:52 |
| jcapitao | #info it's R-6 - Final release for non-client libraries | 14:53 |
| amoralej | https://review.rdoproject.org/r/q/branch:c9s-caracal-rdo+status:open | 14:53 |
| amoralej | 53 | 14:53 |
| jcapitao | +1 for the deps | 14:54 |
| jcapitao | #link https://issues.redhat.com/browse/RDO-208 | 14:54 |
| jcapitao | we should split the work to address that | 14:54 |
| karolinku[m] | omg | 14:54 |
| amoralej | yep | 14:54 |
| karolinku[m] | let's create a ticket! :D as share the work | 14:55 |
| spotz[m] | hehe | 14:55 |
| amoralej | i have the list of reviews | 14:56 |
| amoralej | i can paste it in somewhere (etherpad)? to distribute | 14:56 |
| jcapitao | WFM | 14:56 |
| karolinku[m] | ok | 14:56 |
| jcapitao | otherwise the DLRN bootstrap can be started next week I'd say, wdyt ? | 14:56 |
| amoralej | as soon as libs are released and frozen | 14:57 |
| jcapitao | starting Feb 26 then | 14:58 |
| amoralej | https://review.rdoproject.org/etherpad/p/caracal-deps-updates | 14:58 |
| jcapitao | so we can focus on dep update | 14:58 |
| amoralej | i'll just split in three similar groups by order | 14:58 |
| jcapitao | #info the DLRN bootstrap for Caracal will start around Feb 26 | 14:59 |
| jcapitao | thanks amoralej | 14:59 |
| jcapitao | I take last group | 15:00 |
| jcapitao | #topic chair next week | 15:00 |
| spotz[m] | #link https://review.rdoproject.org/etherpad/p/caracal-deps-updates | 15:00 |
| jcapitao | who's willing to chair next week ? | 15:00 |
| karolinku[m] | I can take it | 15:00 |
| jcapitao | #action karolinku[m] to chair next week | 15:01 |
| jcapitao | thanks karolinku[m] | 15:01 |
| jcapitao | and we are out of time ! | 15:01 |
| spotz[m] | Thanks karolinku | 15:01 |
| jcapitao | the JIRA topic was too verbose :D | 15:02 |
| *** d34dh0r5- is now known as d34dh0r53 | 15:02 | |
| jcapitao | I'm gonna close the meeting | 15:02 |
| jcapitao | #endmeeting | 15:02 |
| opendevmeet | Meeting ended Wed Feb 14 15:02:34 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:02 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/rdo_meeting___2024_02_14/2024/rdo_meeting___2024_02_14.2024-02-14-14.01.html | 15:02 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/rdo_meeting___2024_02_14/2024/rdo_meeting___2024_02_14.2024-02-14-14.01.txt | 15:02 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/rdo_meeting___2024_02_14/2024/rdo_meeting___2024_02_14.2024-02-14-14.01.log.html | 15:02 |
| jcapitao | thank you all for joining | 15:02 |
| karolinku[m] | thanks jcapitao[m]! | 15:03 |
| amoralej | FYI, i've updated https://issues.redhat.com/browse/RDO-188 for the deps | 15:04 |
| jcapitao[m] | amoralej apevec : FYI openinfra AFS are now synced http://mirror.regionone.vexxhost-nodepool-tripleo.rdoproject.org/centos-stream/9-stream/COMPOSE_ID | 15:48 |
| amoralej | great! | 15:49 |
| jcapitao[m] | I rechecked the p-o-i and weirdo patches | 15:49 |
| jcapitao[m] | https://review.rdoproject.org/r/c/rdo-infra/weirdo/+/51576 | 15:49 |
| jcapitao[m] | https://review.opendev.org/c/openstack/puppet-openstack-integration/+/908927 | 15:49 |
| rdogerrit | Alfredo Moralejo proposed deps/python-elasticsearch c9s-caracal-rdo: Import python-elasticsearch-7.17.4-1.el9 https://review.rdoproject.org/r/c/deps/python-elasticsearch/+/51673 | 16:12 |
| rdogerrit | Merged deps/python-elasticsearch c9s-caracal-rdo: Import python-elasticsearch-7.17.4-1.el9 https://review.rdoproject.org/r/c/deps/python-elasticsearch/+/51673 | 16:39 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!