| *** bauzas4 is now known as bauzas | 02:08 | |
| opendevreview | OpenStack Proposal Bot proposed openstack/project-config master: Normalize projects.yaml https://review.opendev.org/c/openstack/project-config/+/1003397 | 02:10 |
|---|---|---|
| frickler | this seems to be fully up to the sender's policy: 550-5.7.26 Unauthenticated email from purestorage.com is not accepted due to domain's DMARC policy. | 06:04 |
| frickler | simondodsley: ^^ fyi | 06:06 |
| *** bauzas0 is now known as bauzas | 07:43 | |
| fungi | yes, fwiw that's fairly typical for dmarc-enforcing domains though | 13:34 |
| fungi | where the problem generally comes in is the list of fields covered by the dkim signature in the message, as i said | 13:35 |
| fungi | one of those probably ended up altered at least subtly by mailman on the way through causing it to no longer hash to the same value | 13:36 |
| opendevreview | Merged openstack/project-config master: Normalize projects.yaml https://review.opendev.org/c/openstack/project-config/+/1003397 | 13:42 |
| opendevreview | Merged openstack/project-config master: Add a few more wandertracks and inaugust repos https://review.opendev.org/c/openstack/project-config/+/1002832 | 15:26 |
| opendevreview | Merged openstack/project-config master: Clean up log-classify jobs https://review.opendev.org/c/openstack/project-config/+/993691 | 16:32 |
| gouthamr | ty for debugging the ml issue fungi, frickler! | 18:05 |
| gouthamr | simondodsley: i know you're probably in the middle of a rebrand.. do you know if "@everpure.com" uses a relaxed DMARC policy compared to "@purestorage.com"? | 18:05 |
| gouthamr | maybe that may solve the issue, if not, you can see why some of us won't get your emails :) | 18:06 |
| fungi | we could in theory fix that by doing dmarc mitigations in the mailing list configuration, but the various options there each have their own down-sides | 18:07 |
| gouthamr | agreed | 18:08 |
| fungi | (rewriting from addresses, wrapping messages as mime attachments inside a container message, et cetera) | 18:09 |
| cardoe | So there is a Zuul issue right now right? | 20:11 |
| fungi | cardoe: i don't believe so, what problem are you experiencing? | 20:12 |
| cardoe | https://zuul.opendev.org/t/openstack/status look at 965415 it's just a doc and it's been 6+ hours | 20:13 |
| cardoe | 999158 had jobs with "ERROR Failed to update project openstack/glance" | 20:13 |
| fungi | there were some queue items stuck earlier after we restarted executors for a memory performance fix so 965415 may need to be unapproved/reapprived if it's not moving, and i think corvus suggested there was a rare chance for merge failures as a result of the restart which i guess could explain 999158 | 20:15 |
| cardoe | okay | 20:21 |
| * cardoe stares at the screen and pokes it with a stick. | 20:21 | |
| cardoe | oh it just moved higher up in the list | 20:24 |
| fungi | i'm mowing the lawn so didn't have a browser up, but yeah 965415 isn't stuck, there's just a backlog in the shared "integrated" gate queue because of the earlier problem | 20:26 |
| fungi | 999158 does look like it needed a recheck because of the merge problem but haleyb took care of that roughly an hour ago | 20:28 |
| cardoe | fungi: 1002828,2 seems to be the stuck integrated job | 21:18 |
| cardoe | Last log line to the console is 2 hours ago | 21:18 |
| fungi | indeed, it looks like maybe reeenqueuing that earlier during the last executor restart may have ended with it stuck on wrapping up the same job again | 21:23 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!