Hey,
since today's midnight there don't seem to be any email notifications delivered from our AWS OCP Jenkins instance (apps.ocp.cloud.ci.centos.org). However, I can successfully trigger a notification from the old instance (apps.ocp.ci.centos.org), both using smtp.ci.centos.org. Is there some ongoing routing issue/manitenance?
apps.ocp.cloud.ci.centos.org
apps.ocp.ci.centos.org
smtp.ci.centos.org
nope but wondering if you configured the sender at the ocp.cloud side (and @phsmoura upgraded that cluster yesterday so hopefully it wasn't resetting some settings in pods) :
what I see from smtp.ci maillog :
Mar 7 08:25:11 smtp postfix/smtp[723]: 88E2060B0B: to=<frantisek@sumsal.cz>, relay=mail.centos.org[208.100.23.70]:25, delay=934, delays=934/0.46/0.18/0.03, dsn=4.1.8, status=deferred (host mail.centos.org[208.100.23.70] said: 450 4.1.8 <nobody@nowhere.ci.centos.org>: Sender address rejected: Domain not found (in reply to RCPT TO command))
So can you verify the From: at the origin side ?
From:
If I compare with before :
Mar 5 04:38:39 smtp postfix/qmgr[19426]: E89B5600AC: from=<builder@jenkins-systemd.apps.ocp.cloud.ci.centos.org>, size=15941, nrcpt=1 (queue active)
So it was sent from a various From:
Can you verify at your side ?
Ah, you're right - for some reason only the system admin email address was reset to default after the cluster update. After configuring it again it seems to be working fine. Thanks!
Metadata Update from @mrc0mmand: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Metadata Update from @arrfab: - Issue assigned to arrfab
Metadata Update from @arrfab: - Issue tagged with: centos-ci-infra, low-trouble, medium-gain
Login to comment on this ticket.