| *** gthiemon1e is now known as gthiemonge | 06:54 | |
| tkajinam | hi. it'd be nice if I can ask for review about https://review.opendev.org/c/openstack/releases/+/897428 early this week. | 08:02 |
|---|---|---|
| tkajinam | (this is a huge patch covering multiple repos, though | 08:02 |
| hberaud | ack | 08:03 |
| hberaud | tkajinam: I left a comment concerning puppet-openstacklib | 08:19 |
| hberaud | fungi: I still face the email delivering issue when sending emails to openstack-discuss ("Recipient server unavailable or busy."), I'm using gmail, so I'm not sure what I can do to solve that issue, any idea? | 08:22 |
| opendevreview | Takashi Kajinami proposed openstack/releases master: Puppet OpenStack 2023.2 release https://review.opendev.org/c/openstack/releases/+/897428 | 08:32 |
| tkajinam | hberaud, ugh. thanks. that's a good catch! | 08:32 |
| frickler | hberaud: do you get an immediate failure or a bounce message? can you show the complete failure message? | 09:46 |
| opendevreview | Martin Magr proposed openstack/releases master: Add python-observabilityclient https://review.opendev.org/c/openstack/releases/+/896910 | 09:58 |
| hberaud | frickler: here is the failure that I received https://paste.openstack.org/show/bJhNwcalhrSV2GrQ10ac/ | 10:22 |
| hberaud | frickler: and apparently the last message stored here was from October 12 https://lists.openstack.org/pipermail/openstack-discuss/2023-October/ | 10:23 |
| hberaud | however, I still receive new messages from this list on my gmail inbox, where those message are not listed in the previous link | 10:25 |
| frickler | hberaud: the current archive has a new URL https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/, the old URLs are still there for convenience to keep old links working, but will not get new content | 11:23 |
| frickler | that failure is from some redhat mail system and not gmail | 11:24 |
| fungi | hberaud: frickler: i've proposed https://review.opendev.org/898280 to fix the deferral errors | 11:44 |
| fungi | sorry, travelling out of town at a conference since saturday and trying to work from a phone, so my availability is rather limited | 11:44 |
| frickler | fungi: the error that hberaud is seeing seems to be a different issue to me, like still trying to use the old DNS entry | 11:47 |
| fungi | oh, never mind, now that i look at the paste i see it's a connection refused error. i expect that's the problem mimecast server that is still holding onto the old server ip address | 11:47 |
| fungi | frickler: yep, i agree. trying to browse that paste from the phone took me a minute, sorry | 11:48 |
| fungi | ralonsoh already opened a ticket about that with red hat's admins, i think | 11:49 |
| fungi | and also the fact that mimecast is greylisting the new server | 11:49 |
| ralonsoh | fungi, 1 min ago I've received this message: | 11:51 |
| ralonsoh | The message you sent to openstack-discuss@lists.openstack.org hasn't been delivered yet due to: Recipient server unavailable or busy. | 11:51 |
| hberaud | redhat's support said to me 'but I don't think this web page / email address is maintained by Red Hat at all so I'm not quite sure we can do something about it on our side,' | 11:52 |
| ralonsoh | I've also talked to RH sys admins just to know if we can allow these new IPs by default | 11:52 |
| hberaud | (I'm using the gmail webclient) | 11:53 |
| fungi | mimecast is a third-party service red hat is using for sending and receiving their corporate e-mail. it'll come down to finding who in corporate has admin rights to red hat's mimecast settings | 11:54 |
| fungi | but that's more for adjusting the greylisting of messages delivered to red hat addresses. as far as the mimecast relay that's holding onto the old name resolution for lists.openstack.org that's probably going to involve someone in rh corporate who has access to mimecast's support tracker opening a trouble ticket with them to report the problem | 11:56 |
| fungi | short story, mimecast is apparently a pretty terrible and poorly-maintained service that anyone using a redhat.com e-mail address is forced to rely on anyway | 11:58 |
| ralonsoh | I'll copy-paste this into the ticket I've opened | 11:58 |
| ralonsoh | (maybe not the last sentence) | 11:58 |
| fungi | and probably something that most of the corporate it department is completely unaware of even existing | 11:58 |
| fungi | could even be possible it's someone on the ibm side who maintains that relationship, i really have no idea | 11:59 |
| fungi | anyway, i need to disconnect. conference sessions beckon | 11:59 |
| hberaud | thx fungi | 12:00 |
| ttx | I approved https://review.opendev.org/c/openstack/releases/+/897428 but tkajinam should update their email address in governance as that makes PTL+1 checks fail | 14:47 |
| frickler | ttx: already proposed https://review.opendev.org/c/openstack/governance/+/898151 | 14:56 |
| ttx | neat! | 15:01 |
| opendevreview | Martin Magr proposed openstack/releases master: Add python-observabilityclient https://review.opendev.org/c/openstack/releases/+/896910 | 15:05 |
| opendevreview | Merged openstack/releases master: Puppet OpenStack 2023.2 release https://review.opendev.org/c/openstack/releases/+/897428 | 15:12 |
| opendevreview | Martin Magr proposed openstack/releases master: Add python-observabilityclient https://review.opendev.org/c/openstack/releases/+/896910 | 15:19 |
| clarkb | re caching dns entries beyond their TTLs this is a symptom of old JVMs iirc. They will cache a DNS record the first time they resolve it and then never refresh it regardless of TTL | 15:56 |
| clarkb | I can't say that is what is happening here but it wouldn't surprise me if there is some java 8 from 2012 running somewhere | 15:57 |
| clarkb | java 8 is from 2014 so java 7 then :) | 15:57 |
| clarkb | google says that maybe java 5 was the last one to be affected by this behavior by default | 16:00 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!