| opendevreview | Kristi Nikolla proposed openstack/project-team-guide master: Update docs for Unmaintained https://review.opendev.org/c/openstack/project-team-guide/+/897505 | 15:06 |
|---|---|---|
| opendevreview | Kristi Nikolla proposed openstack/project-team-guide master: Update docs for Unmaintained https://review.opendev.org/c/openstack/project-team-guide/+/897505 | 15:36 |
| *** ralonsoh is now known as ralonsoh_ooo | 16:33 | |
| JayF | tc-members: meeting in ~an hour | 16:59 |
| spotz[m] | As of last night there was one scheduled operator hour | 17:12 |
| JayF | that cannot be true | 17:13 |
| JayF | I scheduled two myself | 17:13 |
| JayF | one for bm sig, one for a cinder person who was having trouble with the tool | 17:13 |
| JayF | I see three etherpads listed; os-ansible, cinder, baremetal sig (ironic) | 17:13 |
| JayF | although the os-ansible one does not have a scheduled time, the bm-sig and cinder ones do (on Monday) | 17:14 |
| JayF | (I will note the BM Sig is the only one with any content whatsoever in the etherpad) | 17:14 |
| dansmith | nova just discussed today so there should be another coming | 17:19 |
| JayF | spotz[m]: aha, looks like the os-ansible operator hours are scheduled outside the PTG window | 17:33 |
| JayF | noonedeadpunk: can you make sure the etherpad for operator-hour-os-ansible is either updated or pointed to a populated ehterpad, especially since the timing is outside the window? https://etherpad.opendev.org/p/oct2023-ptg-operator-hour-os-ansible | 17:34 |
| noonedeadpunk | Yeah, I was actually thinking what to do with that and if it's worth to have a separate etherpad or not | 17:35 |
| gmann | in past, many project used the main etherpad so ether should be ok | 17:35 |
| JayF | well in this case; I think it's valuable to have a separate ehterpad | 17:35 |
| JayF | just to publish the time | 17:36 |
| gmann | depends on how much populated your main etherpad are and if difficult to find operators feedback there | 17:36 |
| JayF | even if you link people back to the main one for notes | 17:36 |
| JayF | since 1700-1800 UTC is not a window on ptg.opendev.org | 17:36 |
| JayF | so only way people know about this is if you get it out on social media, mailing list, or via os-ansible contributor-portion ptg etherpad | 17:36 |
| gmann | sending that in ML is better along with etherpad. not everyone notice the etherpad | 17:36 |
| JayF | ++ ML is good place, I just want us to get as many places as possible | 17:37 |
| gmann | for TC out of window hrs we did the same and there was no gap in communication. | 17:37 |
| gmann | having those in ptgbot is easy but I already gave up on that feedback | 17:37 |
| noonedeadpunk | We had good presence on operator hours just on the first year | 17:37 |
| gmann | *easy to know | 17:37 |
| noonedeadpunk | then it really dropped a lot and folks were just coming to ptgs | 17:38 |
| noonedeadpunk | So yeah, as I've already sent ML, will just combine these 2 together | 17:38 |
| gmann | ++ | 17:38 |
| noonedeadpunk | As it's not really have too much content | 17:38 |
| noonedeadpunk | thanks for the ping JayF | 17:39 |
| JayF | thanks for running ansible ptg things :D | 17:39 |
| spotz[m] | OSA has always been an operator friendly project and channel | 17:41 |
| * noonedeadpunk would love to give a flag to someone else, but there're not lot of volunteers for an administrative overburden | 17:41 | |
| JayF | noonedeadpunk: heh, there's a lot of that going around. That's why I stated publically+definitively I'm giving up the mantle for Ironic this cycle. Private conversations and trying to do a soft handover were not effective in getting people to prioritize leadership work :( | 17:42 |
| JayF | tc-members: meeting | 18:00 |
| JayF | #startmeeting tc | 18:00 |
| opendevmeet | Meeting started Tue Oct 17 18:00:27 2023 UTC and is due to finish in 60 minutes. The chair is JayF. Information about MeetBot at http://wiki.debian.org/MeetBot. | 18:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 18:00 |
| opendevmeet | The meeting name has been set to 'tc' | 18:00 |
| spotz[m] | o/ | 18:00 |
| gmann | o/ | 18:00 |
| JayF | Welcome to the weekly meeting of the OpenStack Technical Committee. A reminder that this meeting is held under the OpenInfra Code of Conduct available at https://openinfra.dev/legal/code-of-conduct. | 18:00 |
| JayF | #topic Roll call | 18:00 |
| JayF | Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee. | 18:00 |
| slaweq | o/ | 18:00 |
| dansmith | o/ | 18:00 |
| rosmaita | o/ | 18:01 |
| JayF | #info James Page has noted an absense for today's meeting. | 18:01 |
| knikolla | o/ | 18:01 |
| JayF | Going to allow until 1805 utc for any other folks to arrive. | 18:01 |
| frickler | \o | 18:03 |
| JayF | Alright, moving on. | 18:04 |
| JayF | #topic Follow up on tracked action items | 18:04 |
| JayF | First one is me, I've made no progress and am pushing it forward. Still on track to have something to present by next video meeting. | 18:04 |
| JayF | #action JayF Before next video meeting, write up a short document on pros/cons of moving TC video meetings to jitsi-meet. | 18:04 |
| JayF | knikolla: anything further to update on DB usage patterns in keystone devstack? I will not be pulling this action forward as we'll be discussing in PTG next week. | 18:05 |
| knikolla | no updates from me this week. | 18:05 |
| JayF | Ack, thank you. As noted, not going to push it forward as that will be discussed at PTG. | 18:05 |
| JayF | #info knikolla research into keystone db usage in devstack will be topic at PTG next week | 18:05 |
| JayF | next up, slaweq was going to sync with a potential monasca ptl candidate to inform the inactivity proposal | 18:06 |
| slaweq | I sent email to the Monasca team | 18:06 |
| slaweq | but I got no reply | 18:06 |
| slaweq | and also patch which marks Monasca as inactive is now merged | 18:06 |
| JayF | #info slaweq reports Monasca team was nonresponsive to email; Monasca project was marked inactive by TC resolution earlier this week. | 18:07 |
| slaweq | we can remove it from inactive list if there will be any volunteer(s) for it before Milestone 2 | 18:07 |
| JayF | If anyone interested in that project reads this log, you're welcome to reverse that action along with taking actions needed to restore CI and maintain the project. | 18:07 |
| JayF | looks like we're on the same page slaweq :D | 18:08 |
| JayF | Thank you for reaching out to them and for writing up that proposal. | 18:08 |
| gmann | do we want to retire it if no leader? | 18:08 |
| slaweq | yw :) | 18:08 |
| JayF | gmann: I'd personally prefer discuss that once we get past the M-2 milestone without any volunteers. | 18:08 |
| gmann | inactive marking is ok but question is should we wait for m-2 with clear no maintainer? | 18:08 |
| slaweq | gmann according to the inactive projects policy, if there will be no volunteers before Milestone 2, we should | 18:09 |
| gmann | yeah that is true but this is case of no PTL where we might want to take action soon? | 18:09 |
| slaweq | I have some reminders set for myself to try to ping people before this deadline | 18:09 |
| JayF | I think the waiting period is sensible to ensure people have time to get the information if they aren't plugged into the community, and I see little/no benefit to rushing. | 18:09 |
| slaweq | JayF++ | 18:10 |
| JayF | In fact, it occurs to me we might not have even mailed the list about the merge of that resolution. I'll check and if not, will do that after the meeting. | 18:10 |
| JayF | Last action item to review; rosmaita was going to engage i18n sig about possibility of translating governance docs | 18:10 |
| rosmaita | they are in the middle of the weblate migration | 18:11 |
| rosmaita | #link https://meetings.opendev.org/irclogs/%23openstack-i18n/%23openstack-i18n.2023-10-13.log.html | 18:11 |
| JayF | Thanks for the update. | 18:11 |
| rosmaita | they'll have a presence at the PTG and we can get more details then | 18:11 |
| rosmaita | but the short version is, the faster we get migrated to weblate, the sooner we can do other stuff | 18:12 |
| JayF | #info i18n team has to prioritize their tool migrations; discussion about how governance translation fits into that will happen at PTG | 18:12 |
| JayF | #undo | 18:12 |
| opendevmeet | Removing item from minutes: #info i18n team has to prioritize their tool migrations; discussion about how governance translation fits into that will happen at PTG | 18:12 |
| JayF | #info i18n team has to prioritize their tool migrations; discussion about how governance doc translation fits into that will happen at PTG | 18:12 |
| JayF | thank you | 18:12 |
| JayF | That's all for tracked action items. | 18:12 |
| JayF | #topic Gate Health Check | 18:12 |
| JayF | Any update on the general health of the gate? | 18:12 |
| dansmith | there's something going on with the grenade job, | 18:12 |
| rosmaita | oh noes | 18:13 |
| JayF | skip-level, normal, or "yes"? | 18:13 |
| dansmith | which isn't new (apparently) but the fail rate seems higher this week | 18:13 |
| dansmith | this is a normal one | 18:13 |
| dansmith | it's in the cinder pre-validation stuff, | 18:13 |
| dansmith | but I haven't dug in deep yet | 18:13 |
| gmann | we recently updated the setting of upgrade of stable/2023.2 to master and skip level job from stable/2023.1 to master | 18:14 |
| gmann | which one failing? | 18:14 |
| clarkb | There is some post failure thing when trying to get qemu/libvirt logs as well. Has that been addressed (I don't see as much orange on hte zuul status today) | 18:14 |
| dansmith | [ERROR] /opt/stack/new/grenade/inc/plugin:123 Failed to run /opt/stack/new/grenade/projects/70_cinder/resources.sh verify pre-upgrade | 18:14 |
| dansmith | 18:14 | |
| dansmith | clarkb: I haven't seen that one.. are you talking about the lxml failure in post? | 18:15 |
| dansmith | clarkb: we're trying to land a fix for that but the cinder grenade verify has nailed it three times in a row :( | 18:15 |
| dansmith | clarkb: that's this patch: https://review.opendev.org/c/openstack/nova/+/898435 | 18:15 |
| clarkb | dansmith: I saw the lxml thing but on a random job I looked at it appeared to fail elsewhere when trying to find a file. But maybe I misparsed it | 18:15 |
| dansmith | clarkb: okay I haven't seen that one | 18:15 |
| dansmith | but the rash of post_failures yesterday were from the lxml thing, at least that I've seen | 18:16 |
| clarkb | oh ya I think it may be side effects of the lxml thing? | 18:16 |
| clarkb | https://zuul.opendev.org/t/openstack/build/920b297afc9a43c08c4599460a1b0ab2/console is the error I'm talking about and elsewhere it complains about lxml | 18:16 |
| dansmith | the qemu dump message is always there unless qemu crashed during a run AFAIK | 18:17 |
| dansmith | unrelated to any failure | 18:17 |
| clarkb | its just annoying because it makes the jobs record post failure instead of failure | 18:18 |
| clarkb | maybe it should be made to not error if it fails to make the actual errors more clear | 18:18 |
| dansmith | the lxml thing is causing the post_failure | 18:18 |
| dansmith | because in post-run we use ansible's virt module and that requires lxml but doesn't actually depend on it so it doesn't get installed | 18:19 |
| dansmith | and somewhere around when we moved everything to a venv, we stopped getting lxml for free on the host | 18:19 |
| clarkb | ah | 18:20 |
| JayF | Is there any action we need to take or ask the cinder team to take for the grenade issue? | 18:21 |
| dansmith | I haven't dug into the issue yet so I don't know if we can fully blame them yet or not | 18:21 |
| dansmith | but it always happens in the cinder phase, so definitely happy to have any help from them :) | 18:21 |
| JayF | heh, sounds good. Thank you for looking into that. Is there anything else of note for the gate health check/ | 18:22 |
| JayF | Moving on then. | 18:24 |
| JayF | #topic Leaderless projects | 18:24 |
| JayF | gmann: how are leaderless projects looking? | 18:24 |
| JayF | #link https://etherpad.opendev.org/p/2024.1-leaderless | 18:24 |
| JayF | We have multiple late candidacies listed in there, a couple that have already landed as well. | 18:25 |
| gmann | we have 9 volunteer for leaderless projects | 18:25 |
| gmann | and 3 a re already there but invalid candidacy which include Monasca also | 18:25 |
| gmann | I asked them to propose patch in governance and a few of them did but not all | 18:25 |
| gmann | I will ask remaining one and we can discuss/ask question in gerrit | 18:25 |
| gmann | but it is good that we have volunteer for all 12 leaderless project | 18:26 |
| gmann | and we can discuss each one by one in PTG | 18:26 |
| JayF | I'd highly recommend TC members take time to review them async before the PTG as well :) | 18:27 |
| gmann | I will try to get governance change before PTG | 18:27 |
| gmann | ++ | 18:27 |
| JayF | Is there anything else we want to address around this in our meeting today? | 18:27 |
| gmann | nothing else from my side. | 18:27 |
| JayF | Moving on | 18:28 |
| JayF | #topic PTG Reminder | 18:28 |
| JayF | Reminder: PTG is next week | 18:29 |
| JayF | #link https://etherpad.opendev.org/p/tc-ptg-october-2023 | 18:29 |
| JayF | I will be assigning topics to time windows later today/tomorrow, trying to ensure we won't go over as much as possible. | 18:29 |
| JayF | If you have preferences or need me to put certain categories somewhere, please reach out. | 18:29 |
| JayF | Also related and somewhat obvious: | 18:29 |
| JayF | #info TC Weekly Meeting next week cancelled due to PTG | 18:30 |
| JayF | Any other comments/questions/etc about PTG planning? | 18:30 |
| JayF | Alright, moving on. | 18:32 |
| spotz[m] | Monday morning and&I session will be the leadership shadowing topic | 18:32 |
| JayF | I'm not sure what you mean? | 18:32 |
| JayF | spotz[m]: did you have a scheduling request? I'm confused | 18:35 |
| JayF | I'm going to move on and assume that was intended for another window? If there's something we need to circle back to, we can./ | 18:38 |
| JayF | #topic Open Discussion & Reviews | 18:38 |
| JayF | #link https://review.opendev.org/q/projects:openstack/governance+is:open | 18:38 |
| JayF | One thing here, seanmooney had the 2024.1 runtime requirements change up | 18:39 |
| JayF | there is some contention on that, but a clear majority wants to keep 3.8, but there is a CR-1 for content issues on it | 18:39 |
| clarkb | I wanted to note that it appears RH mail servers cannot send email to our new list server because they are using stale DNS records. Unsure of where the stale records are being found. POssibly the mail servers aren't respecting the TTLs or some DNS server is returning old records improperly. | 18:39 |
| JayF | Does someone want to volunteer to update that patch, or post a follow-up patch, addressing the issues? | 18:40 |
| dansmith | AFAIK our mail servers are google | 18:40 |
| dansmith | clarkb: ^ | 18:40 |
| clarkb | dansmith: there is another third party service you use in between aiui and I think fungi suspected that | 18:40 |
| clarkb | mimecast | 18:41 |
| JayF | Can we table that until after the meeting, please? | 18:41 |
| dansmith | isn't that google? | 18:41 |
| JayF | We're very close to wrapping up. | 18:41 |
| dansmith | sure | 18:41 |
| clarkb | JayF: sure I just wanted the TC to be aware of it which is why I brought it up in the meeting | 18:41 |
| JayF | I appreciate the notice; not sure there's any action we can take | 18:41 |
| JayF | In lieu of another volunteer to update that patch, I guess I will? We need a PTI landed that is clear | 18:42 |
| rosmaita | well, the PTI is already landed, this was just a clarification, i think | 18:42 |
| JayF | I'll push a follow-up on top of that patch which will resolve the issues which garnered a CR-1, then get that vote lifted and land it all | 18:42 |
| spotz[m] | @jayf just a heads up on our session | 18:42 |
| JayF | spotz[m]: ack | 18:42 |
| gmann | yes, this is adding more clarification and no change in PTI | 18:43 |
| JayF | Anything additional for open discussion or open reviews? Going to wait a couple of minutes then close out the meeting (then we can all turn into the MX troubleshooting gang) | 18:43 |
| gmann | I still need to land the job template change as per PTI. need to do one quick update | 18:44 |
| rosmaita | JayF: is your plan to push a new patch set, that will clear the votes, and then everyone re-votes? | 18:44 |
| JayF | rosmaita: no, I'm going to do a follow-up to avoid clearing votes | 18:44 |
| gmann | ++ | 18:44 |
| JayF | rosmaita: and ask whoever did the CR-1 to flip it after I push a follow-up, then we can land the follow-up as a trivial/typo fix | 18:45 |
| rosmaita | well, i wonder about that ... looking at the history of the patch, there was at least one person who voted +1 on the original proposal to remove py3.8 in PS 1, and then +1 also to keep py3.8 | 18:45 |
| rosmaita | i think it would be good to have a clean set of votes | 18:45 |
| rosmaita | but that's not what i wanted to talk about in open discussion | 18:46 |
| JayF | I am extremely hesitant to reset the clock on that change and ask folks to revote. I don't think it's justified and just creates more work for folks having to mash the buttons again | 18:47 |
| rosmaita | what i wanted to ask is, what is the status of changes to the TC charter in light of the proposed foundation bylaws changes? | 18:47 |
| JayF | I actually don't know the answer to that question; I think some of that is in the hands of the oif lawyer | 18:47 |
| gmann | changes are in review by legal team | 18:47 |
| JayF | I'll take an action to try and get a meaningful update for PTG | 18:47 |
| gmann | and as next it will be voted in Board meeting | 18:47 |
| rosmaita | right, but i thought the situation is that they won't remove stuff from the bylaws until it's already been moved to the TC charter? | 18:48 |
| JayF | #action JayF to reach out to OIF for a meaningful update on potential TC charter updates | 18:48 |
| gmann | and after that we can do the charter changes, I will push those charter changes but waiting for it to be formally ready and voted in board | 18:48 |
| spotz[m] | Which.would be November | 18:48 |
| rosmaita | otherwise, we are in a limbo situation were we can do almost anything we want | 18:48 |
| JayF | I don't know the answer to those questions; I trust the OIF to; I'm going to take that action and ask and try and get some first-party information. | 18:48 |
| gmann | JayF: I am on that. we discussed in strategic meeting to wait till legacl check and board vote | 18:48 |
| rosmaita | ok, sounds good | 18:49 |
| JayF | So there is zero action for us until after Nov board meeting? | 18:49 |
| JayF | #undo | 18:49 |
| opendevmeet | Removing item from minutes: #action JayF to reach out to OIF for a meaningful update on potential TC charter updates | 18:49 |
| gmann | rosmaita: it will be done before bylaws change | 18:49 |
| rosmaita | gmann: ok, that was my understanding ... do you need help on the charter change, or is it easier to just do it yourself? | 18:49 |
| JayF | gmann: can we ensure timeline allows TC members significant time to review those charter changes before the board meeting? I don't want anyone feeling pressured to approve things based on the timeline. | 18:49 |
| gmann | I mean after board vote but before individual members vote. after individuals members vote (during board election in jan) only Bylaws get officially change | 18:49 |
| JayF | aha | 18:50 |
| gmann | rosmaita: thanks, I will catchup with you on that as you were present in all those discussion so it will be good help | 18:50 |
| JayF | Thank you for bringing it up, it's a good topic to stay on top of. | 18:50 |
| rosmaita | sounds good ... i wonder about the timing though, because the bylaws changes will remove some restrictions on the TC | 18:50 |
| spotz[m] | All bylaw changes are voted on same time as board elections | 18:50 |
| rosmaita | but if we haven't already adopted those ourselves in the charter, then i think that is a problem | 18:51 |
| spotz[m] | Use best judgement | 18:51 |
| JayF | My (weak) understanding is: bylaws changes are staged by a vote of the board; in Jan when individual members vote them, they go into effect | 18:51 |
| gmann | JayF: sure, I will monitor how far the legal checks are and when in baord meeting we have those proposal | 18:51 |
| JayF | between those votes is our window to update the TC charter | 18:51 |
| gmann | yes, Individual Members votes are final agreement to byLaws change and we will put things in TC charter before that | 18:51 |
| JayF | so we'll have a clock running in any event, I guess | 18:51 |
| JayF | just by nature of the coordinatino | 18:52 |
| gmann | we cannot do it now because we want it to be legally check and board agreement as overall | 18:52 |
| gmann | otherwise we might need to revert few things | 18:52 |
| JayF | We have about 6 minutes left, anything else for open discussion? | 18:53 |
| gmann | these are the steps: 1. strategic discussions - DONE 2. Legal checks - in progress 3. Board vote - future 4. TC charter change - future 5. Individual members vote - future 6. bylaws change - future and last step | 18:54 |
| gmann | so TC charter will be changed before bylaws | 18:54 |
| JayF | Alright, thank you :) I'm glad you're helping translate some of this. Let me know when the next gmann foundationing-101 class is and I'll attend ;) | 18:55 |
| gmann | sure | 18:55 |
| JayF | Going to give another minute for new topics before closing the meeting. | 18:56 |
| dansmith | end it. | 18:56 |
| JayF | #endmeeting | 18:57 |
| opendevmeet | Meeting ended Tue Oct 17 18:57:10 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 18:57 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tc/2023/tc.2023-10-17-18.00.html | 18:57 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tc/2023/tc.2023-10-17-18.00.txt | 18:57 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tc/2023/tc.2023-10-17-18.00.log.html | 18:57 |
| JayF | dansmith: don't ever say I haven't listened to you :D | 18:57 |
| slaweq | o/ | 18:57 |
| dansmith | \o/ | 18:57 |
| JayF | thanks all, see you here in 2 weeks (and next week for ptg) | 18:57 |
| clarkb | dansmith: fungi did primary debugging, but my understanding is that red hat uses Mimecast which is another third party service independent of google for sending and receiving email. | 18:57 |
| clarkb | https://paste.openstack.org/show/bJhNwcalhrSV2GrQ10ac/ shows mimecast reporting that email could not be delivered to openstack-discuss because lists.openstack.org refused their connection. This occurred because we stopped the smtp server on the old list server because prior to stopping exim there RH emails were being delivered to the wrong server | 18:58 |
| clarkb | In that email it indicates mimecast could not deliver the email implying they are the service with bad DNS resolution | 18:58 |
| dansmith | clarkb: yeah I see a lot of inbound google-users with mimecast wrapping so I figured it was a google shadow thing, but yep. | 18:59 |
| clarkb | We have received emails from gmail to the new list serve so I don't think google is at fault. I can also resolve the proper IPs through 8.8.8.8 (though that is anycast and it could be a region specific issue) | 18:59 |
| fungi | i'm at a conference and not really here, but i suppose it's possible google bought mimecast or something | 18:59 |
| dansmith | fungi: apparently not, I was just assuming | 18:59 |
| fungi | k | 18:59 |
| dansmith | clarkb: the A record seems TTL=300 which means it's pretty long to be caching that | 19:00 |
| clarkb | dansmith: correct. And its been days since it was updated | 19:00 |
| clarkb | one hunch I had was that mimecast is using a jvm either too old to respect ttls or configured to ignore them | 19:00 |
| dansmith | clarkb: there's no mx record for lists.o.o, which used to be fine but lately some people refuse to deliver to non-mx-having addreses | 19:00 |
| JayF | ++ even back in the day it would cause you to get bad deliverability to e.g. AOL/Yahoo/etc | 19:01 |
| clarkb | (this was a very common thing with java back in the day because by default they resolved names once and cached them forever. This is no longer the default but can be configured iirc) | 19:01 |
| * JayF 's first job may have been at a spam house | 19:01 | |
| rosmaita | JayF: did you work on mailgun? | 19:01 |
| clarkb | dansmith: I don't think that is the issue bcause they are getting connection refused and prior to that were delivering email to the old server | 19:01 |
| dansmith | JayF: I'm talking about the other direction, fwiw | 19:01 |
| clarkb | dansmith: basically they seem to happily be using the old A record its just not valid anymore | 19:01 |
| dansmith | clarkb: ack, just sayin'... I had to add one for one of my machines because some people would refuse to deliver | 19:02 |
| JayF | rosmaita: my first professional job was with Broadwick Corp., makers of iContact (which exited to Vocus after I left ... ) ... basically in the same market as constantcontact. I quit the job when someone I convinced them to terminate for abuse got reinstated for agreeing to pay 4x our posted fee. | 19:02 |
| clarkb | dansmith: yup I brought it up as something we should consider with fungi too. I just don't think it will help this situation after debugging a bit | 19:02 |
| dansmith | clarkb: as a mail proxy service, you'd really think they'd not have something so blatantly broken as no respecting a 5m TTL days later, but... you know. | 19:03 |
| rosmaita | JayF: sounds like elon's twitter business model | 19:03 |
| clarkb | dansmith: antoher theory was that rax dns is serving the stale dns records but we've been unabel to reproduce that resolving against the authoritative NS servers directly or google, cloudflare, and quad9 | 19:04 |
| clarkb | could be some other dns service mimecast is using though | 19:04 |
| JayF | rosmaita: tbh, I think there was a single, highly unethical individual there, who had the ear of the young impressionable ceo (I was the first hire they had younger than the CEO, I was 19 on hire there.) | 19:05 |
| JayF | rosmaita: Rackspace (Email & Apps) was the job that rescued me from that one, nicely enough :D | 19:06 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!