18:04:03 #startmeeting F27 Server Final Go/No-Go meeting 18:04:03 Meeting started Thu Nov 30 18:04:03 2017 UTC. The chair is sgallagh. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:04:03 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:04:03 The meeting name has been set to 'f27_server_final_go/no-go_meeting' 18:04:03 #meetingname F27-server-final-Go-No-Go-meeting 18:04:03 The meeting name has been set to 'f27-server-final-go-no-go-meeting' 18:04:03 #topic Roll Call 18:04:04 #chair nirik adamw sgallagh mboddu 18:04:04 Current chairs: adamw mboddu nirik sgallagh 18:04:13 .hello mohanboddu 18:04:14 mboddu_: mohanboddu 'Mohan Boddu' 18:04:15 .hello2 18:04:16 18:04:17 sgallagh: sgallagh 'Stephen Gallagher' 18:04:36 #chair mboddu_ 18:04:36 Current chairs: adamw mboddu mboddu_ nirik sgallagh 18:04:38 * mboddu_ is outside and cannot access his bouncer since he didn't setup soft token on his new phone :D 18:05:12 .hello2 18:05:13 langdon: langdon 'Langdon White' 18:05:51 .hello2 18:05:52 smooge: smooge 'Stephen J Smoogen' 18:05:53 adamw, kparal: Can one of you represent QA? 18:05:58 running a meeting in another channel 18:06:11 i'm here 18:06:14 just having crashy issues 18:06:23 ok, thanks 18:06:34 #topic Purpose of this meeting 18:06:34 #info Purpose of this meeting is to check whether or not F27 Server Final is ready for shipment, according to the release criteria. 18:06:34 #info This is determined in a few ways: 18:06:34 #info * Release candidate compose is available 18:06:34 #info * No remaining blocker bugs 18:06:34 #info * Test matrices are fully completed 18:06:52 #topic Current status of F27 Server Final release 18:07:35 #info We have a release candidate compose (RC 1.6) 18:07:59 adamw: Can you provide a link to the test matrices? 18:08:03 sure 18:08:08 sgallagh: Is anyone tested how good is RC 1.6 in terms of Server variant? 18:08:24 https://fedoraproject.org/wiki/Test_Results:Fedora_27_RC_1.6_Server 18:08:32 https://fedoraproject.org/wiki/Test_Results:Fedora_27_RC_1.6_Base 18:08:50 https://fedoraproject.org/wiki/Test_Results:Fedora_27_RC_1.6_Installation 18:09:18 * mattdm is here 18:09:22 * mattdm lost track of time 18:09:33 so, missing things: 18:09:41 we haven't tested physical media boot of the images 18:11:02 adamw: Is that the only thing? 18:11:02 the active directory results aren't filled in, though sgallagh says he ran the tests, i think 18:11:23 adamw: I did, yes. 18:11:37 (successfully) 18:11:41 and the 'domain controller role' results are missing, because the openqa test for the compose happened to fail due to some kinda timeout or something... 18:11:49 can you stick them in the table quickly then? 18:11:59 let me see if i can re-run that test 18:12:47 it may fail due to garbage collected assets, though. 18:13:22 adamw: I would, but relval is throwing an error trying to log in with my FAS account 18:13:31 sgallagh: oh, you need the latest wikitcms 18:13:35 it's in updates-testing 18:13:44 (or should be...) 18:13:45 * mboddu_ will be back in 10 min 18:13:55 wiki auth changed with the upgrade 18:14:35 yeah, i can't re-run just the openqa test we need, as it depends on an uploaded hard disk iamge that's been garbage collected. i'd have to re-run the whole set of server dvd tests. 18:14:37 eh, i can do that. 18:14:40 adamw: Broken dependencies; fedfind is missing 18:15:53 OK, a point of order. 18:16:10 We know that the Infra team has an outage next week and so releasing next week is not ideal. 18:16:47 Should we just postpone this decision by a week, since we won't announce until at least the 11th anyway? 18:16:49 mattdm: ^^ 18:17:12 sgallagh: should be in the same update 18:17:14 but yeah, we could do that 18:17:15 sgallagh: this is fine with me. 18:17:28 adamw: Ah, my favorite word... "should" 18:17:29 we can dot some i's and cross some t's in the meantime 18:17:41 i can use this time to ask you some modularity questions instead :) 18:17:52 well, we may want to decide what to do about the freeipa upgrade bug 18:18:14 adamw: Shall we do the mini blocker review now then? 18:18:22 very mini! 18:18:23 sure 18:18:31 Would you be so kind, adamw ? 18:18:40 Anything to avoid mattdm's questions 18:18:42 we could also just announce today/tomorrow... 18:18:46 #topic Mini-Blocker Review 18:18:47 but that needs ducks in row 18:18:56 and friday is horrible for announcing things. 18:18:58 nirik: Websites and stuff needs prepping. 18:19:04 I'd prefer not to rush them 18:19:14 nirik: I have no ducks in a row at this point 18:19:19 all of my ducks are running in circles 18:19:24 #info we have just one proposed blocker 18:19:32 #topic (1503321) FreeIPA server upgraded from F26 to F27 fails to start with "ModuleNotFoundError: No module named 'ipapython.secrets'" 18:19:32 #link https://bugzilla.redhat.com/show_bug.cgi?id=1503321 18:19:32 #info Proposed Blocker, freeipa, NEW 18:19:34 there is a 3lb pomapoo puppy chasing them 18:19:36 🦆🦆🦆 18:19:41 all my ducks ran away to join the yak farm 18:20:14 so we still have this bug, which becomes more relevant if we're actually doing a 'traditional' server release: if you have a freeipa server and upgrade it to f27, the server will fail to start after the upgrade. 18:20:48 the reason is that the freeipa upgrade script fails when run during the upgrade because the network isn't up, and there is a pretty simple workaround: run the upgrade script manually with the network up. 18:20:59 * sgallagh nods 18:21:34 From conversations with the FreeIPA folks, a fix for this is non-trivial for $REASONS. 18:21:53 this is a TOTALLY different "module" than "modularity" right? 18:21:57 iirc we have a couple of threads on fixing this, one involving making it possible for the rpm scriptlet to bring the network up during the upgrade process, one which is about changing the freeipa approach so that the script gets run during freeipa startup if it needs to be run 18:22:02 because _that's_ not confusing 18:22:11 mattdm: Python module 18:22:26 The latter one is probably the right one 18:22:27 yeah. python definitely got there first, i'm afraid. :P 18:22:33 I figured. Which is... fine. It just makes it extra hard to document given the circumstances 18:22:47 i know, let's call our modules 'flavors' instead! 18:22:50 We REALLY don't want to have the network live during updates. That's... kind of the point of "offline updates". 18:22:51 * adamw runs away very fast 18:23:41 but we don't need to solve ithere 18:24:00 The crux of the situation is that we don't *strictly* have a blocker criterion for this case on upgrade. 18:24:07 We only require that a fresh installation works. 18:24:15 It *is* really ugly though. 18:25:23 i think we decided before that upgrade criteria apply to release-blocking roles, no? 18:26:06 * adamw will have to check notes 18:26:15 still, though, i think i'm OK with just documenting this, since it *is* a pretty easy workaround 18:26:31 +1 sad but documentable 18:26:33 and since it's an upgrade issue, we can fix it with an update at any time 18:26:50 adamw: I think we said we probably should propose it, but hadn't 18:27:05 I feel conflicted. 18:27:10 i thought we'd agreed that that's how it should be and we'd act on that basis, but we need to formalize it... 18:27:14 i thought i'd written a proposal but can't find it now. 18:27:44 I probably *would* have blocked on this if we were on the regular schedule. But it's fixable with an update and everything else about this process is out of whack, so... 18:27:47 I'd feel different if the IPA team had an idea for how to fix it 18:27:49 I guess document it and move on 18:27:51 well, we have an *idea* 18:27:57 Several! 18:27:59 it just seems to be a bit of work to implement 18:28:20 a non-trivial bit of work, from above 18:28:48 I guess the thing is: people can actually upgrade and get this error *today* 18:29:06 we just haven't documented that. it's probably *better* to document the problem 18:29:52 proposed #agreed 1503321 - RejectedBlocker (Final) - while we do generally consider upgrade issues in release-blocking roles as potentially release-blocking, we feel this one is easy enough to work around, and it seems the FreeIPA team isn't sure the proper fix can be implemented super promptly. also, we note that there's nothing stopping Fedora Server users from upgrading at present anyhow, so 'blocking' on this is somewhat meaningless. 18:30:29 +1 18:31:11 +1 18:31:14 ack/nack/patch ? 18:31:19 ack 18:31:23 ack 18:31:24 ack 18:31:43 #agreed 1503321 - RejectedBlocker (Final) - while we do generally consider upgrade issues in release-blocking roles as potentially release-blocking, we feel this one is easy enough to work around, and it seems the FreeIPA team isn't sure the proper fix can be implemented super promptly. also, we note that there's nothing stopping Fedora Server users from upgrading at present anyhow, so 'blocking' on this is somewhat meaningless. 18:32:19 and that's all we had, unless someone wanted to add anything. 18:32:24 no point doing FEs as we're not respinning. 18:32:31 right 18:33:03 #topic F27 Server Final Go/No-Go decision 18:33:33 In light of having our ducks line up and be counted, I propose we defer the decision for a week 18:33:45 That way we have time to get that extra round of automated results run 18:33:48 quack. 18:33:56 I mean, ack 18:33:57 * sgallagh groans 18:34:01 .fire mattdm 18:34:01 adamw fires mattdm 18:35:08 proposed #agreed We defer the final Go/No-Go decision by a week to rerun the openqa tests, get websites in order, and avoid the Infrastructure outage. 18:35:23 ackity ack 18:35:28 Don't talk back 18:35:39 Don't *quack* back 18:35:51 * mattdm is sorry he started t his 18:36:14 NOT SORRY ENOUGH 18:36:19 Hello! 18:36:25 Sorry for been late 18:36:28 hi kohane 18:36:34 .fas lailah 18:36:36 Kohane: lailah 'Sylvia Sánchez' 18:36:37 we're just deciding not to decide 18:36:42 hi adamw 18:36:48 proposed #agreed We defer the final Go/No-Go decision by a week to rerun the openqa tests, get websites in order, and avoid the Infrastructure outage. 18:36:49 LOL 18:37:17 ack 18:37:35 * mboddu is back 18:37:44 and test if physical boot works? 18:38:03 ack 18:39:14 * mboddu has a question to adamw and nirik which I will ask after we complete this topic 18:39:21 #agreed We defer the final Go/No-Go decision by a week to rerun the openqa tests, get websites in order, and avoid the Infrastructure outage. 18:39:22 smooge: yeah, we should probably do that too. 18:39:28 #topic Open floor 18:39:31 ack 18:39:35 mboddu: Go for it 18:39:36 mboddu: do you mean you're....b'ack ? 18:39:37 thanks everyone 18:39:54 adamw: nope 18:40:36 adamw, nirik : Lets say we find a blocker and that means we need a new respin of the RC compose for just server variant? 18:40:50 mboddu: We aren't doing one. The end :) 18:40:53 we don't do it. 18:40:59 yeah, what sgallagh said. 18:41:05 yup. 18:41:24 i'd say we either release what we have or don't 'release' at all. 18:41:24 So what happens if someone finds a blocker? 18:41:25 sgallagh, nirik, adamw : Okay, that worried me a little bit 18:41:26 If we discover a blocker we can't fudge, we just don't ship F27 Server 18:41:36 Kohane: well, *first* we dig a shallow grave... 18:41:46 sgallagh: Okay, got it 18:41:53 Okay, got it adamw 18:43:13 adamw: And the tombstone says "Hit by a blocker" 18:43:29 no, it says RESOLVED WONTFIX 18:43:44 hahaha 18:43:47 LMAO 18:43:55 I don't know that it's all that funny but... 18:43:58 I think NEEDSINFO would be the real salt in the wound 18:44:03 ahahahaha 18:44:13 WORKSFORME 18:44:23 we're all terrible people. 18:44:37 Oh, yeah... 18:45:40 Are we done here? 18:45:48 * mboddu has nothing 18:45:48 Kellin: Did you have a question? 18:45:53 I suppose.... 18:46:05 sgallagh: I have nothing constructive at this time. 18:46:16 Fair enough 18:46:22 #endmeeting