Re: [Gluster-infra] Fwd: Query regarding coverity scan

[Kaleb S. KEITHLEY]

On 03/15/2018 04:53 AM, Nigel Babu wrote:
> Hi Kaleb,
> 
> Do you know what's going wrong with Coverity jobs?

disk filled up due to a bug in clang-analyze script. Nobody noticed that
that's been broken for even longer. :-(

bug fixed, disk cleaned up, coverity runs corrected.

Are we getting closer to having a day-to-day delta coverity test in
jenkins? Or a per-patch delta test?

ISTR you saying (or hearing through the grapevine) that you have a
script that compares two coverity reports and finds the new defects? If
you do, would you share that with me please?

> 
> -- Forwarded message --
> From: *Varsha Rao* mailto:va...@redhat.com>>
> Date: Thu, Mar 15, 2018 at 10:15 AM
> Subject: Query regarding coverity scan
> To: Nigel Babu mailto:nb...@redhat.com>>
> 
> 
> Hello Nigel,
> 
> I have been observing the coverity scans generated for the past few days.
> I did not find the html page with the list of all errors as it used to be.
> 
> https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-03-14-f32f85c4/html/
> 
> 
> https://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-03-12-a96c7e74/html/
> 
> 
> Thanks,
> Varsha
> 
> 
> 
> -- 
> nigelb

___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] download.gluster.org: /dev/mapper/vg_download-lv_www_pub I/O errors

[Kaleb S. KEITHLEY]

FYI

At around 13:00 EST Reiner030 reported in #gluster that
download.gluster.org had been rejecting http requests for at least 30
minutes.

I signed on and saw that $subject was getting I/O errors. I unmounted
(remounted to replay the journal and unmounted again.) I ran xfs_repair,
then remounted.

This seemed to fix things. For now.

-- 

Kaleb
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [gluster-packaging] [Gluster-Maintainers] glusterfs-3.13.1 released

[Kaleb S. KEITHLEY]

https://build.gluster.org/job/release-new/lastSuccessfulBuild/artifact/glusterfs-3.13.1.tar.gz

Check with NigelB about the copy to bits.gluster.org

On 12/21/2017 05:07 AM, Niels de Vos wrote:

On Thu, Dec 21, 2017 at 02:07:50AM +, jenk...@build.gluster.org wrote:

SRC: 
https://build.gluster.org/job/release-new/35/artifact/glusterfs-3.13.1.tar.gz
HASH: 
https://build.gluster.org/job/release-new/35/artifact/glusterfs-3.13.1.sha512sum


The tarball is not at the usual place yet. Could it be copied to

  - http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.13.1.tar.gz
(maybe its there, but I get a 403 error message)
  - https://download.gluster.org/pub/gluster/glusterfs/3.13/ + subdir

Thanks,
Niels
___
packaging mailing list
packag...@gluster.org
http://lists.gluster.org/mailman/listinfo/packaging


___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] Where to request for adding versions in Bugzilla

[Kaleb S. KEITHLEY]

We don't do 3.X.y versions in bugzilla any more.

Just 3.8, 3.10, 3.11, and mainline.

On 05/15/2017 02:56 AM, Raghavendra Talur wrote:
> On Mon, May 15, 2017 at 5:49 AM, Vijay Bellur  wrote:
>>
>>
>> On Sun, May 14, 2017 at 8:04 PM, Vijay Bellur  wrote:
>>>
>>> On 05/14/2017 04:02 PM, Raghavendra Talur wrote:

 Hi All,

 I need 3.10.1 and 3.10.2 versions added to Glusterfs product. How do I do
 it?

>>>
>>> You would need to file a request with Red Hat's bugzilla admin. I will
>>> mail details about the process offline.
>>>
>>
>> I have forwarded you details. However I remember a discussion on not adding
>> bz versions for minor updates in 3.8.x. The expectation was that users would
>> provide details about the exact version in the bug description. Do we want
>> to follow a similar process for 3.10?
> 
> Thanks Vijay!
> May be this is why Shyam hasn't created 3.10.1 version already? If so,
> I will not send this request.
> 
>>
>> Thanks,
>> Vijay
> ___
> Gluster-infra mailing list
> Gluster-infra@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-infra
> 

-- 

Kaleb
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-devel] Cleaning up Jenkins

[Kaleb S. KEITHLEY]

On 04/20/2017 08:17 AM, Shyam wrote:

On 04/20/2017 01:27 AM, Nigel Babu wrote:

Hello folks,

As I was testing the Jenkins upgrade, I realized we store quite a lot
of old
builds on Jenkins that doesn't seem to be useful. I'm going to start
cleaning
them slowly in anticipation of moving Jenkins over to a CentOS 7
server in the
not-so-distant future.

* Old and disabled jobs will be deleted completely.
* Discard regression logs older than 90 days.
* Discard smoke and dev RPM logs older than 30 days.
* Discard post-build RPM jobs older than 10 days.
* Release job will be unaffected. We'll store all logs.


Above decisions seem fair enough to me. +1 from my end.


Agreed.





If we want to archive the old regression logs, I might looking at
storing them
some place that's not the Jenkins machine. If you have concerns or
comments,
please let me know.


Get rid of them after 30 days. I'd be amazed if anyone ever looks at them.

--

Kaleb


___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-devel] Dropping nightly build from download.gluster.org ?

[Kaleb S. KEITHLEY]

On 03/24/2017 09:39 AM, Niels de Vos wrote:
> On Thu, Mar 23, 2017 at 05:29:05PM -0400, Michael Scherer wrote:
>> Another example:
>> pub/gluster/glusterfs has various directory for versions of glusterfs,
>> but also do have libvirt, vagrant and nfs-ganesha, who are not version,
>> and might be rather served from a directory upstream (in fact,
>> nfs-ganesha and glusterfs-coreutils are also on
>> https://download.gluster.org/pub/gluster/ )
> 
> A cleanup is much appreciated! Maybe come up with a proposed directory
> structure and see from there what makes sense to keep or remove?
> 

What does "from a directory upstream" mean? There is no upstream
nfs-ganesha server.

There are versions of nfs-ganesha, even if there aren't very many, and
thus not to the same level of granularity as gluster.

And .../pub/gluster/glusterfs/nfs-ganesha is merely a symlink to
.../pub/gluster/nfs-ganesha — just a convenience. There are not two
copies of it. Likewise for -coreutils and the others.

I'm not opposed reorganizing the directories, but I don't believe
there's really anything wrong with it, per se, the way it is now.

-- 

Kaleb



signature.asc
Description: OpenPGP digital signature
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] Coverty report on another server than download

[Kaleb S. KEITHLEY]

On 02/21/2017 10:40 AM, Michael Scherer wrote:

Hi,

I am pondering on putting the result of coverty scan on a separate
website than download.gluster.org, or if possible, on a separate vhost.

I did deploy today a server that verify the integrity of
download.gluster.org, and I realize that since we host the coverty scan
results there, this will generate a ton of false positive.

While I could fix that in aide config, I think it might be better to
further isolate the downloads by splitting that on another server.

Do people have a opinion on that ?


Putting it on another machine is fine, and will free up a lot of space 
on download.gluster.org for packages.


Just tell me the name of the machine.

Likewise I presume for clang compile, clang analyze, and cppcheck; yes?

--

Kaleb


___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] Zuul?

[Kaleb S. KEITHLEY]

On 09/02/2016 06:36 AM, Nigel Babu wrote:
> 
> Here's the flow as I see it:
> 1. Propose a review request.
> 2. Smoke tests run as soon as a patchset is created or updated.
> 3. Reviewer gives +2.
> 4. Zuul will run regressions in the order than patches received Code Review 
> +2.
>If they pass regression, Zuul will merge them into the branch requested. 
> The
>documentation[1] has a good visualization that will help.
> 5. If the regression fails, we can still do a retry. Zuul will retry the job 
> on
>top of the existing patch queue rather than in isolation.
> 

A full _regression_?  Which takes hours? And is prone to spurious errors?

Eek!

Wouldn't a smoke, or just a compile (or rpmbuild) suffice for this?
Don't we already have periodic (hourly) regressions of the head of
master?  Maybe we should have the same for the release branches?

-- 

Kaleb
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] All rpm jobs are now in jenkins job builder

[Kaleb S. KEITHLEY]

On 06/28/2016 08:07 PM, Sankarshan Mukhopadhyay wrote:
> 
> I have a follow-up question on the production of these artifacts -
> when do we check whether the RPMs or, the images produced are sane?
> For example, that the RPMs are packaged well and as per specifications
> ...
> 

For Fedora/RHEL/CentOS rpms:

 + People file bugs, e.g. against Fedora/glusterfs or
GlusterFS/packaging, and we fix them.

 + Some of us  occasionally do package reviews for new packages and/or
closely follow the Fedora packaging guidelines and when we see something
that ought to be done in the glusterfs packaging we fix it.

 + Every once in a while I run rpmlint and address the things it finds.

 + And of course we get feedback from downstream packaging.

 + Finally, I  keep the Fedora dist-git .spec and our upstream .spec in
sync.

For SuSE RPMs I use a .spec file based on the one that SuSE uses/used
for their distribution's bundled packages.

For Debian/Ubuntu debs I use packaging bits provided by Louis Zuckerman
(irc nick: semiosis) that he developed with, I believe, the help of
Patrick Matthaei, the Debian packager who builds Debian's bundled
packages. Resyncing with Patrick's packaging bits is on my list of
things to do in my copious spare time. In the mean time people
occasionally report issues with the debs and I fix them.

-- 

Kaleb
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] Some gerrit email is getting "high" spam scores

[Kaleb S. KEITHLEY]

On 02/16/2016 04:47 PM, Michael Scherer wrote:
> Le lundi 15 février 2016 à 17:11 +0100, Michael Scherer a écrit :
>> Le lundi 15 février 2016 à 17:07 +0100, Michael Scherer a écrit :
>>> Le lundi 15 février 2016 à 08:03 -0500, Kaleb Keithley a écrit :
 Hi,

 e.g. 

 ...
 X-RedHat-Spam-Score: 2.614 ** (BAYES_50,MISSING_HEADERS,RDNS_NONE) 
 66.187.224.184 [66.187.224.184] 66.187.224.184 [66.187.224.184] 
 
 ...

 (yes, two asterisks is not really very high, but it's what I have to set 
 in my zimbra filter to catch the majority of the real spam.)

 Is there something we can do, e.g. add whatever missing headers are 
 necessary or an PTR record for dev.gluster.org to gluster.org DNS 
 somewhere, to yield lower scores?
>>>
>>> Yup, we can do that. I will ask IT as I do not have access.
>>
>> In fact, that's more complicated. 
>>
>> We have 1 IP address incoming (66.187.224.201), which is natted to the
>> internal IP of the server, and we have 1 ip for outgoing connexion,
>> which is shared (66.187.224.184). 
> 
> So rdns is done.
> 
> For missing_headers, there is this page:
> https://wiki.apache.org/spamassassin/Rules/MISSING_HEADERS
> 
> I am a bit puzzled about it. Could you look at a previous mail header to
> see if something changed ?
> 

I'm not sure what a previous mail header is, or would tell us. Here are
the headers from one of the mails that had a MISSING_HEADERS hit. As you
can see it does not have a To: line. I guess Du really did only sent to CC:

Is there somewhere I can set my ~/.spamassassin/user_prefs and adjust my
score for MISSING_HEADERS?

From - Wed Feb 17 08:06:34 2016
X-Mozilla-Status: 0001
X-Mozilla-Status2: 
X-Mozilla-Keys:
Return-Path: rev...@dev.gluster.org^M
Received: from zmta06.collab.prod.int.phx2.redhat.com (LHLO^M
 zmta06.collab.prod.int.phx2.redhat.com) (10.5.81.13) by^M
 zmail12.collab.prod.int.phx2.redhat.com with LMTP; Mon, 15 Feb 2016^M
 21:50:44 -0500 (EST)^M
Received: from int-mx11.intmail.prod.int.phx2.redhat.com
(int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24])^M
by zmta06.collab.prod.int.phx2.redhat.com (Postfix) with ESMTP
id D79CE169703;^M
Mon, 15 Feb 2016 21:50:43 -0500 (EST)^M
Received: from mx1.redhat.com (ext-mx07.extmail.prod.ext.phx2.redhat.com
[10.5.110.31])^M
by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4)
with ESMTP id u1G2ohQA012057^M
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256
verify=NO);^M
Mon, 15 Feb 2016 21:50:43 -0500^M
Received: from dev.gluster.org (unknown [66.187.224.184])^M
by mx1.redhat.com (Postfix) with ESMTP id CF83BC0BBE51;^M
Tue, 16 Feb 2016 02:50:41 + (UTC)^M
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])^M
by dev.gluster.org (Postfix) with ESMTP id E2046505F2;^M
Mon, 15 Feb 2016 18:46:43 -0800 (PST)^M
Date: Mon, 15 Feb 2016 18:46:43 -0800^M
From: "Raghavendra G (Code Review)" ^M
CC: Gluster Build System ,^M
NetBSD Build System ,^M
Pranith Kumar Karampuri ,^M
Raghavendra Talur ,^M
Vijaikumar Mallikarjuna ,^M
soumya k ^M
Reply-To: rgowd...@redhat.com^M
X-Gerrit-MessageType: comment^M
List-Id: ^M
List-Unsubscribe: ^M
Subject: Change in glusterfs[master]: performance/write-behind:
guaranteed retry after a short write^M
X-Gerrit-Change-Id: I73a18b39b661a7424db1a7855a980469a51da8f9^M
X-Gerrit-ChangeURL: ^M
X-Gerrit-Commit: db8849a6285334aab502e1be9bd5dc876eaf89c3^M
In-Reply-To:
^M
References:
^M
MIME-Version: 1.0^M
Content-Type: text/plain; charset=UTF-8^M
Content-Transfer-Encoding: 8bit^M
Content-Disposition: inline^M
User-Agent: Gerrit/2.9.4^M
Message-Id: <20160216024643.e204650...@dev.gluster.org>^M
X-RedHat-Spam-Score: 2.614 ** (BAYES_50,MISSING_HEADERS,RDNS_NONE)
66.187.224.184 [66.187.224.184] 66.187.224.184 [66.187.224.184]
^M
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.24^M
X-Scanned-By: MIMEDefang 2.78 on 10.5.110.31^M




-- 

Kaleb
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] add Manikandan-Selvaganesh to github glusterfs-debian team

[Kaleb S. KEITHLEY]

Hi,

I thought I had privs to do this myself, but I'm not seeing how to do it
atm.

Please add Manikandan (Manikandan-Selvaganesh) to glusterfs-debian team
members. Maybe add him to GlusterFS team too?

Thanks


-- 

Kaleb
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] broken link

[Kaleb S. KEITHLEY]

On 09/09/2015 01:27 PM, Joe Julian wrote:
> http://download.gluster.org/pub/gluster/glusterfs/LATEST/CentOS/glusterfs-epel.repo
> is broken. Should CentOS be a symlink to EPEL.repo?
> 
> Michael, is that handled in salt or is it a manual thing?

It's manual. Whatever stuckee^h^h^h^h^h^h^hvolunteer gets there first
and creates the dirs and symlinks.

A short script would probably be good.

-- 

Kaleb
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] nfs-ganesha-de...@gluster.org?

[Kaleb S. KEITHLEY]

The NFS-ganesha project is looking for somewhere to host their mailing
lists after SourceForge's most recent meltdown.

Could we — would we be willing to — host their lists? (All two of them I
think. Probably with a few dozen subscribers at most I'm guessing.)


-- 

Kaleb
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-devel] Gluster and GCC 5.1

[Kaleb S. KEITHLEY]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 07/05/2015 06:54 PM, Michael Scherer wrote:
> Le lundi 29 juin 2015 à 18:48 -0400, Kaleb Keithley a écrit :
>> 
>> 
>>> From: "Niels de Vos" 
>>> 
>>> On Mon, Jun 29, 2015 at 02:45:50PM -0400, Kaleb S. KEITHLEY
>>> wrote:
>>>> On 06/29/2015 02:40 PM, Anoop C S wrote:
>>>>> 
>>>> 
>>>> Niels and I had a brief chat a while back about adding a
>>>> Fedora 22 VM to Jenkins to catch these. I don't think
>>>> anything ever happened though.
>>> 
>>> I'm waiting for the new Jenkins slaves to become available...
>>> We should try to not exceed the Rackspace budget too much.
> 
> Well, I still do not know what kind of VM do we want to have there.
> And Since people didn't really see this as a question last time we 
> discussed, the question is "what should I plan to provision ?"
> 
> ie, just centos 6, fedora 14, or something different, and how much
> ?

Fedora 22.

> 
>> We have been granted access to the CentOS Jenkins by virtue of
>> the Storage SIG.
>> 
>> We should start deploying Jenkins slaves there. There's plenty of
>> capacity and it's free.
>> 
> 
> I do not have any access to the centos infra, I can just redirect
> to the people who you discussed with during summit.
> 

Brian, Fabian: can you please provide Michael with the things he needs
to start using the CentOS CI infra?

Thanks

- -- 

Kaleb
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJVmmuIAAoJEDcw3UmJzK6LUxEH/0DIF8BCb2iHp1+1qhNwk3Gg
2ceTqcVq6Q5T4fbNWrl5B7UGQCmz8qCnPNQ4+a5JOuFX1tckDI8EXj15ju2xeIJF
Z8khQHYwPFTuz9FlvwxVwUttRewAnkQq3VKZjYOUltsdJoMiJZynq/rQAbFn2ywp
maIrJl8Y6m/F6c1JswJz6eWD/D6I1R6gn4Aghup9SgQ1q7eTx3O+13lLm3n+Utse
6QT8iD8UURVYoCv2OgDbhZETO+9QJz0eIHY2884WU5MT4X1i6mVVkNkehDcKwI+9
nTwW9T67hBAJuX7M2nlTEs7htrMWO4GDvkYghvMVwOq7EHuo2aYXKHtHjEJ+QiQ=
=yQDh
-END PGP SIGNATURE-
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-devel] Gluster and GCC 5.1

[Kaleb S. KEITHLEY]

On 06/29/2015 02:45 PM, Kaleb S. KEITHLEY wrote:
>>
>>> E.g. by building on Fedora Rawhide last year, reporting the bugs,
>>> and getting them fixed before Rawhide turned into Fedora 22.
>>
>>
>> Immediately after the Fedora 22 release, we had a similar issue
>> reported from a user with gcc v5 and was fixed through [1].
>>
> 
> Yes, there were still some, and/or some had crept (back) in, when
> Fedora22 was released.
> 
> I think we're still finding some more. Not all of the developers are
> using Fedora 22 yet. I know a few that are still on Fedora 19!
> 
> Niels and I had a brief chat a while back about adding a Fedora 22 VM to
> Jenkins to catch these. I don't think anything ever happened though.

Or perhaps we could just get everyone to stop using 'inline'


-- 

Kaleb
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-devel] Gluster and GCC 5.1

[Kaleb S. KEITHLEY]

On 06/29/2015 02:40 PM, Anoop C S wrote:
> 
> 
> On 06/29/2015 11:56 PM, Kaleb S. KEITHLEY wrote:
>> On 06/29/2015 02:04 PM, Anoop C S wrote:
>>>
>>> Reading through gcc docs I could see that with gcc v5, it
>>> defaults to C99 semantics and compiling with -fgnu89-inline
>>> solves the above issue. I'm wondering how glusterfs compiled
>>> successfully without providing this flag.
> 
>> Well, it didn't originally.
> 
>> Most of the bugs were fixed before Fedora 22 arrived with gcc-5.
   

I didn't say all of them had been fixed. ;-)

> 
>> E.g. by building on Fedora Rawhide last year, reporting the bugs,
>> and getting them fixed before Rawhide turned into Fedora 22.
> 
> 
> Immediately after the Fedora 22 release, we had a similar issue
> reported from a user with gcc v5 and was fixed through [1].
>

Yes, there were still some, and/or some had crept (back) in, when
Fedora22 was released.

I think we're still finding some more. Not all of the developers are
using Fedora 22 yet. I know a few that are still on Fedora 19!

Niels and I had a brief chat a while back about adding a Fedora 22 VM to
Jenkins to catch these. I don't think anything ever happened though.

-- 

Kaleb
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra