Monday, 2023-03-20

elodilleshmm, there are some *new* final RC patches, and a tempest release as well. I thought that maybe we are too late for that, but i'm still hesitant07:53
elodilleshberaud ttx ^^^07:53
opendevreviewSlawek Kaplonski proposed openstack/releases master: Final RC patch for neutron  https://review.opendev.org/c/openstack/releases/+/87765408:13
hberaudelodilles: I replied with a comment on the patch08:23
hberaudelodilles: One solution could be to cut the RC2 at the commit before the one who requires the tempest changes, and then release it next week, once the final release is past. 08:26
hberaudwhat do you think about that?08:26
elodilleshberaud: sounds OK, though we have to discuss that with cinder and tempest folks as well, so it takes time too, and then we delay cinder's RC2 as well :/08:43
hberaudyeah08:43
elodillesI'm tend to accept the tempest release now that I read the story, though it's a bit unfortunate and we should avoid similar situations in the future :S08:44
hberaudwhoami-rajat: FYI ^ 08:45
elodilleswe have clear deadlines, of course exceptions can be made, but those should be well assessed08:45
hberaudyeah08:46
elodillesat least that is my view from release management perspective :)08:46
hberaudConcerning myself I'd prefer to ignore those tempest changes and requirements08:46
hberaudbut if we decide to continue with that I won't block08:47
elodillesOK, so you say that we should not release now Tempest 34.1.0, right?08:48
hberaudyes08:48
hberaudand cut cinder's RC2 the commit before the one related to the tempest changes08:49
elodilleshberaud: ++08:49
elodillessounds good to me.08:49
hberaudand I'd also ignore the skyline patches08:49
elodillesyepp, that should be our safest bet08:51
elodillesthough they were proposed on Friday ~ 3 PM (CET)08:52
elodillesso technically within the deadline we stated (March 17th)08:52
elodillesso I am hesitant with that as well08:54
hberaudindeed08:56
hberaudI don't think the skyline patches can be dangerous (in a widely manner), though08:56
hberaudso lets +2 skyline08:57
elodillesyes, they seems to be like bugfix + packaging patches08:57
hberaudbecause you are right the deadline was respected08:57
elodilleswe should make sure next time that rc2 patches are proposed much earlier :)08:58
elodilles(when I generated the rc2 patches I didn't find patches on skyline afair)08:58
hberaudand indeed they propose lot of fixes08:58
elodillesneutron rc2 was also updated, can you review that, too? https://review.opendev.org/c/openstack/releases/+/87765408:58
whoami-rajatelodilles, hberaud IIUC, we are going to ignore the cinder and tempest changes for RC2 but they're going to make it into the final 2023.1 GA release, right?09:01
elodilleswhoami-rajat: nope09:01
elodilleswhoami-rajat: if we ignore them for RC2 then they won't be part of the GA09:02
elodilles(as latest RC patches would be marked as final release)09:03
whoami-rajathmm, that doesn't sound good, the point of delaying RC2 was to include the cinder change, it is a major issue which came to our notice few weeks ago and was important to fix it in the 2023.1 release09:03
whoami-rajatwhat is the problem with inclusion in 2023.1? we can't release tempest right now?09:04
hberaudwhoami-rajat: we are hesitant to release a new version of tempest so close to the final deadline09:05
hberaudbecause if it contains an unforseen problem it could broke everything09:06
hberaudthat's our main point09:06
elodilleswhoami-rajat: yes, cycle-with-intermediary release deadline is way over. we don't say it's impossible to release now, but a release has to be well justified09:06
whoami-rajatok, gmann and I can guide through the changes if it helps understanding the risk situation of the changes09:07
elodilleswhoami-rajat: if you say that it is a major issue, and it is *safe* to release, then we can grant the exception09:08
elodilleshberaud: right? ^^^09:08
hberaudWFM09:08
whoami-rajatI agree it is a backward incompatible change but it's for a specific cinder feature, "multiattach" and we want to intentionally break the backward compatibility for those who are using it the wrong way (since it could lead to a data corruption issue)09:09
whoami-rajatnot all deployments enable multiattach so the tests won't run for them09:09
hberaudwhoami-rajat: so you say the tempest changes are really isolated?09:10
whoami-rajatcan we wait for gmann's response ? I think he can better explain the deployment scenarios of tempest and where it can/cannot break09:10
hberaudand won't impact the other deliverables?09:10
whoami-rajathberaud, it's isolated for a specific cinder feature09:10
whoami-rajathberaud, with other deliverables, do we mean other projects like nova, neutron etc?09:11
hberaudyeah09:11
elodillesand all the rest :)09:11
hberaudI meant the other deliverables that also relies on tempest09:12
whoami-rajatsince nova attaches the volume, the tests include nova and cinder but IIRC not other projects, glance for creating bootable volumes but yeah mostly they're nova cinder related changes09:12
whoami-rajatapart from nova and cinder, I don't think it should affect anything else09:13
hberaudcan we do tests against nova with this version to ensure that its gates are not broken?09:14
hberaud(this version of tempest)09:14
whoami-rajatsure, we can09:16
whoami-rajatalso the testing now relies on devstack so the deployment needs to happen with devstack to run these tests successfully09:17
whoami-rajatelse there are some manual config changes that need to be done in tempest (if deployment tool is not devstack)09:17
whoami-rajatI think tempest gate that approved the changes already runs all the relevant tests in tempest-full-py3, tempest-slow-py309:18
whoami-rajatalso it runs tests against Zed and Xena branches09:18
ttxHi hberaud and elodilles , I'm back09:20
hberaudttx: o/09:20
ttxlet me know if there is anything that needs my urgent attention, otherwise I'll continue to process email09:20
hberaudttx: yeah we need your feedback about our current discussion09:22
ttxok reading immediate backlog09:22
hberaudttx: thanks09:22
hberaudwe are discussing about a last minute release of tempest, required by cinder's RC2. elodilles and I thinks we are a bit late to release a new version of tempest, however, cinder require this new version because it fix cinder issues.09:24
ttxIf the tempest changes are very limited in scope I'd be tempted to grant it... We still have two days09:25
ttxLet me have a look09:25
hberaudthat's me or zuul is running nothing? https://zuul.opendev.org/t/opendev/status09:27
ttxIt's you https://zuul.opendev.org/t/openstack/status09:28
hberaudI 'rechecked' a patch ~1h ago so I'd expect to see it enqueued09:28
ttxwrong url09:28
hberaudah yes, good catch09:29
hberaudthanks09:29
ttxThat tempest change is slightly bigger than expected, but still mostly focused on cinder09:29
ttxIf that's the only thing we have in terms of exceptions, I'd support accepting it asap09:29
hberaudyeah that's our main exception09:30
ttxsame for neutron and skyline... get all the things in this morning and freeze there09:31
hberaudI +2'd the tempest patch09:32
ttxIt's better to get that cinder change in now than later09:32
hberaudyeah09:32
ttxsince it's breaking compat09:32
ttxok I'll +2a it09:33
hberaudI also +2d the skyline and neutron patches09:34
hberaudttx: FYI I decided to wait this morning to generate the final rc patch, I'll generate it soon09:35
ttx+109:36
hberaud(to wait those last RC2)09:36
ttxDo we need to hold on the Cinder release for Tempest to be released?09:36
hberaudgood question09:36
hberaudcan't hurt09:36
ttxi also like to test that we can still merge things after that lands :)09:37
ttxrather than discovering it Wednesday09:37
hberaudyeah good idea09:38
* ttx goes back to purging inbox09:38
elodillesnote that this skyline-apiserver rc2 is exactly the *same* as rc1, just realised it: https://review.opendev.org/c/openstack/releases/+/87779109:38
hberaudgood catch I missed that point09:40
elodillesalso, we shouldn't forget about oslo.log :/09:44
elodillesas I see one of the revert patch had a timeout O.o09:46
elodillesI've rechecked it now09:46
elodilles+1: when one of you have a bit of a time for a quick review for a reno link patch: https://review.opendev.org/c/openstack/releases/+/87728809:47
hberaudthanks, I requested Stephen's review 09:48
elodilleshberaud: cool, thanks!09:48
opendevreviewMerged openstack/releases master: Release skyline-console RC2 for Antelope  https://review.opendev.org/c/openstack/releases/+/87779309:49
opendevreviewMerged openstack/releases master: Final RC patch for neutron  https://review.opendev.org/c/openstack/releases/+/87765409:51
opendevreviewMerged openstack/releases master: Release tempest 34.1.0 for 2023.1  https://review.opendev.org/c/openstack/releases/+/87784009:51
hberaudttx: tempest is now merged, I think we can go with cinder09:56
ttxwfm10:01
opendevreviewMerged openstack/releases master: Add release notes links for 2023.1 Antelope  https://review.opendev.org/c/openstack/releases/+/87728810:04
opendevreviewHervĂ© Beraud proposed openstack/releases master: Fix propose-final-releases command to use release-id  https://review.opendev.org/c/openstack/releases/+/87781910:06
opendevreviewMerged openstack/releases master: Final RC patch for cinder  https://review.opendev.org/c/openstack/releases/+/87765210:20
hberaudNow I'm gonna go to generate the final rc patch.10:45
hberaudttx: how do you want to test that things can be merged now that the tempest patch is merged?10:47
ttxThe Cinder patch merged after it, so we should be good10:49
hberaudyeah but cinder was tailored to work with this release so I'm not sure this is a significant test...10:50
elodillesmeanwhile I got another question, namely magnum wants an rc2, but I suggested there to not do that but rather release gate fixes after the official 2023.1 Antelope release: https://review.opendev.org/c/openstack/magnum/+/87686611:00
opendevreviewHervĂ© Beraud proposed openstack/releases master: antelope final rc  https://review.opendev.org/c/openstack/releases/+/87794211:01
elodillesprobably it could just fit in before the release, but even the backports are not yet proposed, so it wouldn't be that convenient to push through everything...11:02
hberaudelodilles: yeah I agree with you11:03
hberaudmaybe we could use release-test instead to do this test11:03
elodillesrelease-test does not have tests as far as I know. could it be used to test this?11:13
hberaudno idea12:32
hberaudif it doesn't have tempest tests then that's ot really useful12:32
hberaud*not12:33
elodillesi think release-test is more like testing the release process itself12:54
elodilleshberaud: oslo.log patches got +2s from stephen: https://review.opendev.org/q/topic:revert-oslo-5.1.0-functional-content13:39
ralonsohelodilles, hi, sorry, I was in PTO. slaweq fixed the patch. Thanks!16:16
elodillesralonsoh: oh, i see, yes, fortunately slaweq helped us out so rc2 is now released and final release patch is uploaded as well \o/16:17
ralonsohthanks!16:18
elodillesnp :)16:18
gmannelodilles: hberaud ttx: thanks for understanding and grant the exception for tempest change. Change is mostly for cinder(for whoami-rajat cinder fix for multiattach) and Tempest change is tested in gate (for stable/xena till current master) since Mar 17.17:34
opendevreviewElod Illes proposed openstack/releases master: Release oslo.log for 2023.1 Antelope  https://review.opendev.org/c/openstack/releases/+/87799918:42
elodillesgmann: ack, no worries. (it was a bit unfortunate, we should try to avoid such late releases next time)18:44
gmannelodilles: completely agree. 18:59
elodilleshberaud ttx : the oslo.log release patch: https://review.opendev.org/c/openstack/releases/+/87799919:07
opendevreviewGhanshyam proposed openstack/releases master: Add releasenotes link for Tempest antelope release  https://review.opendev.org/c/openstack/releases/+/87800319:08
opendevreviewElod Illes proposed openstack/releases master: Add release notes links for 2023.1 Antelope  https://review.opendev.org/c/openstack/releases/+/87800419:28

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