Friday, 2023-01-06

opendevreviewJake Yip proposed openstack/releases master: Release Magnum stable branches  https://review.opendev.org/c/openstack/releases/+/86687701:36
*** marios is now known as marios|rover06:04
*** blarnath is now known as d34dh0r5307:01
elodillesgmann: sorry i was on PTO yesterday, will check the things around Mistral08:49
elodillesfungi: Bobcat! nice! thanks, i've added it to our tracking page! (it's in the next week tasks)08:51
elodillesso just in time \o/08:51
opendevreviewElod Illes proposed openstack/releases master: [mistral] Release beta version for Antelope  https://review.opendev.org/c/openstack/releases/+/86944811:17
opendevreviewElod Illes proposed openstack/releases master: [adjutant] Release beta version for Antelope  https://review.opendev.org/c/openstack/releases/+/86944911:17
opendevreviewElod Illes proposed openstack/releases master: [mistral] Release for Antelope-2  https://review.opendev.org/c/openstack/releases/+/86947011:17
opendevreviewElod Illes proposed openstack/releases master: [adjutant] Release for Antelope-2  https://review.opendev.org/c/openstack/releases/+/86947111:17
*** dviroel|afk is now known as dviroel11:24
hberaudno meeting today?14:01
elodilleso//14:02
elodillesttx? :)14:02
ttxoops14:03
ttxSorry I got carried away slidedesigning14:03
hberaudnp14:03
ttx#startmeeting releaseteam14:04
opendevmeetMeeting started Fri Jan  6 14:04:07 2023 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.14:04
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:04
opendevmeetThe meeting name has been set to 'releaseteam'14:04
hberaudo/14:04
elodilleso/14:04
ttxPing list: hberaud armstrong elodilles14:04
ttx#topic Review task completion14:04
ttx    Generate a list of all cycle-with-intermediary libraries which did not release since the 2022-11-16 date of milestone-1 (hberaud)14:05
ttx#link https://review.opendev.org/q/topic:antelope-milestone-214:05
hberaudglance declined our release patch https://review.opendev.org/c/openstack/releases/+/86905914:05
hberaudI think we can abandon this one14:06
hberaudany opinion?14:06
ttxok for me14:06
elodillesnope, let's abandon then14:06
hberauddone14:06
ttxFix upper constraint redirection ( https://releases.openstack.org/constraints/upper/2023.1 ) (elod)14:06
hberaudand the only one remaining is the keystone patch14:06
hberaudI think we can merge it14:07
hberaudhttps://review.opendev.org/c/openstack/releases/+/86905314:07
ttxoh right sorry14:07
hberaudnp14:07
ttxLet's give it until Monday and we'll force it?14:07
ttxand maybe drop a message on the review to say so14:08
hberaudas keyston is under DLP and if I remember correctly both voter are team members14:08
elodillessounds ok14:08
ttxah ok then14:08
hberaudI don't know why the badge was not added14:08
ttxok, back to Fix upper constraint redirection ( https://releases.openstack.org/constraints/upper/2023.1 ) (elod)14:09
elodillessorry, i just started to look into the issue and don't have a solution yet for the redirection fix14:10
elodilleshere is the redirection added: https://opendev.org/openstack/releases/src/branch/master/doc/source/_templates/htaccess14:10
elodillesso probably we need some kind of mapping...14:10
elodillesantelope -> 2023.114:10
elodillesif you don't have better ideas14:11
ttxyeah that was the kind of issue I was expecting with not using the name in the branch14:12
elodillesyepp14:12
elodillesoriginally 2023.1 should have been used in the deliverables directory but that had problems in the beginning14:13
elodillesinstead of antelope14:13
ttxThe constraint name is based on the directory name?14:13
elodillesyes14:13
elodillesi think it comes from here: https://opendev.org/openstack/releases/src/branch/master/openstack_releases/_redirections.py14:14
ttxso we can either create some form of mapping... or just say that the branches should be named stable/antelope after all14:15
elodillesprobably the mapping is not that hard, just needs to be decided where to put14:16
ttxI don't think we need to solve it today, right14:16
elodillesanyway, I'll try to propose a patch early next week and we can discuss there14:16
ttxmaybe we can open a thread to discuss it on the list and make sure we pick the right solution14:16
ttxsince we may be overlooking something14:17
ttxand it's good that the TC knows that their numbering is creating all kinds of issues for us14:17
elodillesTC was quite clear about they want 2023.1, so let's try that first :)14:17
elodilles* stable/2023.114:18
ttxright, and we said that might create issues14:18
fungii take it "series" can me made to contain 2023.114:18
fungier, can't i mean14:18
elodillesdeliverables/2023.1 caused other issues14:19
ttxfungi: that would likely create a cascade of other issues14:19
ttxso far this one is the only we detected with the hybrid approach14:19
fungiwhat's building the _deliverables that gets passed into generate_constraints_redirections()?14:19
elodilleswe pass the _deliverables here: https://opendev.org/openstack/releases/src/branch/master/doc/source/_exts/deliverables.py#L51714:22
fungilooks like the series comes from here: https://opendev.org/openstack/releases/src/branch/master/openstack_releases/deliverable.py#L15514:22
elodillesso somewhere in that file14:22
ttxit comes from loading up the deliverables directory content14:22
ttxso it's based on the directory names14:22
fungiyeah, glob.glob(os.path.join(root_dir, '*/*.yaml'))14:22
fungiso would require having the directory named 2023.1 i guess, in order to avoid remapping14:23
ttxso yeah, either mapping, or using numbres in dir names, or using names in branch names :)14:23
elodilles:)14:23
ttxok let's move that off-meeting14:23
ttxCatch if there are acl issues in newly created repositories (elod)14:24
elodilles++14:24
elodillesthe aclissues.py reports issues with bifrost.config, ironic.config and ironic-inspector.config files14:24
elodillesadded by this patch: https://review.opendev.org/c/openstack/project-config/+/86693714:24
elodillesto handle bugfix branches14:24
elodillesfor ironic team14:25
elodillesso this is intentional14:25
ttxok so it's not happy that we don;t have control14:25
ttxthe script works as intended :)14:25
elodilleswe have control, but ironic team, too :)14:25
elodillesttx: yepp :)14:25
elodillesso in short: nothing that is a real ACL issue :)14:26
ttxok yeah we could update the script... or just keep it as-is as a reminder of that "exception" to the rule14:26
elodillesyepp14:26
ttxanything more to discuss on that?14:27
elodillesnope, i think14:27
elodillesi mean: nothing else :)14:27
ttxRequire a beta release for mistral and adjutant / intermediary releases then to doublecheck gates (elod)14:28
elodillesok14:29
elodillesso, i've propsed: https://review.opendev.org/q/topic:inactive-release-test14:29
elodillesbeta & intermediary releases ^^^14:29
elodillesat least our validators are happy14:29
fungiit came up in #openstack-infra last week that zaqar may need similar care14:30
fungiit's apparently not merged any changes for months, and still has broken zuul job configuration in master14:30
elodillesfungi: as I remember to zaqar's state, i'd say yes14:30
fungias in, right now the only change that could merge to zaqar is the one to trivially fix their named gate queue, it's been sitting there unreviewed since something like september14:31
elodillesfungi: was this topic on TC meeting as well?14:33
fungii raised it on the tc channel on sunday14:34
elodillesoh, i see, thanks for that!14:34
fungii was unable to attend the tc video call this week, so not sure if it got raised there14:34
elodilles:/14:34
ttxIs there anything more to be done on this at this stage?14:35
fungiwhen the tc started their meeting, i reminded them that this week was the deadline to decide what projects would be included in 2023.1 so hopefully they considered those situations14:36
ttxwe should probably reach out and see if there was anything specific decided14:38
ttxlet's add that to next week's actions14:40
elodillesoh, according to the TC meeting log they also has the action to ping me :)14:40
elodillesso the circle is closed :)14:40
ttxah lol14:41
elodillesOK, let's add it to next week's action then14:41
ttxI passive-sensed it14:41
elodilles:)14:41
ttxAlrigth, moving on14:41
ttx#topic Review countdown email14:41
ttx#link https://etherpad.opendev.org/p/relmgmt-weekly-emails14:41
ttxI prepared it, let me know if it looks good and I'll send it today14:42
elodillesdates are OK14:44
hberaudLGTM14:44
elodilles(i somehow marked Feb 15 as client lib freeze but it should be Thursday, so 16 is the right date)14:45
elodillesLGTM, too14:45
ttxokok14:45
ttx#topic Assign next week tasks14:46
ttxelodilles: the TC is likely to reach to you if that's what they have written down, so probably best if you cover that one14:46
ttxhberaud: I can take teh cycle planning if you don;t want it14:47
hberaudok thanks14:47
elodillesttx: ack, added my name to it14:47
ttxI'll just have to remember how to do it14:48
ttx#topic Open discussion14:48
elodillesttx: i can help to find the resources as I somehow managed it last occasions :)14:48
ttxI'll ask you if I don;t find my way14:50
ttxanything else, anyone?14:51
fungii pinged the tc members in #openstack-tc again to remind them the release managers were hoping to hear a decision this week on adjutant/mistral (potentially also zaqar)14:51
elodilles( tools/list_weeks.py is the entry point, as it is mentioned in the process page)14:52
ttxalright, if nothing else... thanks everyone!14:53
ttx#endmeeting14:53
opendevmeetMeeting ended Fri Jan  6 14:53:42 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:53
opendevmeetMinutes:        https://meetings.opendev.org/meetings/releaseteam/2023/releaseteam.2023-01-06-14.04.html14:53
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/releaseteam/2023/releaseteam.2023-01-06-14.04.txt14:53
opendevmeetLog:            https://meetings.opendev.org/meetings/releaseteam/2023/releaseteam.2023-01-06-14.04.log.html14:53
elodillesthanks ttx o/14:53
hberaudthanks ttx 14:53
ttxfirst meeting from Matrix bridge14:54
elodilles:-o14:54
elodilleswas it working well?14:54
ttxthere is a bit of lag (I'm using matrix.org) but otherwise good14:54
fungiorg.matrix:tcarrez14:55
fungilooks like you're identified with nickserv too14:55
fungipretty cool14:55
ttxthe full game14:55
elodillesi know that others, too, using matrix14:55
elodilles:)14:55
fungione thing to keep an eye out for... if the matrix oftc bridge has a convulsion, you may come back temporarily not identified with nickserv, which will then cause oftc to ban you from any private channels you might autojoin. `/msg chanserv unban #channel-name` after you re-identify and you should be able to /join them again14:57
fungiif you're not in any private irc channels, then it's nothing you need to worry about14:57
elodilleshberaud: i saw that meanwhile PTL-Approved arrived for 'Antelope-2 Release for keystonemiddleware' so I +2+W'd it now (late Friday release, yay o:))16:00
hberaudok16:00
hberaudthx16:00
elodillesnp :]16:09
opendevreviewMerged openstack/releases master: Antelope-2 Release for keystonemiddleware  https://review.opendev.org/c/openstack/releases/+/86905316:11
*** dviroel is now known as dviroel|lunch16:39
*** marios|rover is now known as marios|out16:44
*** dviroel|lunch is now known as dviroel17:50
gmannelodilles: for Mistral, the new maintainer wanted to reach out to the release team to discuss what all needs to be done to make Mistral release. I think they have fixed the gate. 17:56
gmannelodilles: and Adjutant, Dale (PTL) fixed the gate and might do release soon17:56
gmannMistral maintainers are not online here so if you can comment what is needed in this patch https://review.opendev.org/c/openstack/governance/+/86656217:58
gmannand let me ping dale (adjutant PTL) again on release status17:58
*** dviroel is now known as dviroel|pto21:12
gmannelodilles: I checked and both Adjutant and Mistral are with cycle-with-rc model so their gate is green and their release can be done at rc and at the final release. They do not need to release at m-2 right? 22:01

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