Bug 1657860 - Archives for ci-results mailinglist are getting wiped (with each mail?)
Summary: Archives for ci-results mailinglist are getting wiped (with each mail?)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-10 15:42 UTC by Niels de Vos
Modified: 2019-01-07 03:15 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-01-07 03:15:21 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)
current message on ci-results to check later (79.01 KB, image/png)
2018-12-10 15:42 UTC, Niels de Vos
no flags Details

Description Niels de Vos 2018-12-10 15:42:39 UTC
Created attachment 1513102 [details]
current message on ci-results to check later

Description of problem:

Not all mails sent to ci-results are in the archives at https://lists.gluster.org/pipermail/ci-results/2018-December/thread.html

There have been a few mail with CC gluster-devel, and the emails are available in the archives there. This was noticed with the thread at https://lists.gluster.org/pipermail/gluster-devel/2018-December/055722.html

ci-results only has this message https://lists.gluster.org/pipermail/ci-results/2018-December/000000.html for December, and it changes... The attached screenshot shows the current message. There is only one mail for November as well. Still, daily results should have been received.

Comment 1 M. Scherer 2018-12-10 21:31:36 UTC
We did had a issue on https://bugzilla.redhat.com/show_bug.cgi?id=1653733 ?  

Looking at the log, there was a error in 
/var/log/mailman/error :

Dec 10 15:06:14 2018 (1347) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/ci-results/index.html'

I fixed it, let's see how it goes.

Comment 2 Nigel Babu 2019-01-07 03:15:21 UTC
The fix seems to be working. Closing bug.


Note You need to log in before you can comment on or make changes to this bug.