[Gluster-infra] [Bug 1754017] New: request a user account for the blog on gluster.org

2019-09-20 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1754017

Bug ID: 1754017
   Summary: request a user account for the blog on gluster.org
   Product: GlusterFS
   Version: mainline
Status: NEW
 Component: project-infrastructure
  Assignee: b...@gluster.org
  Reporter: nde...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org
  Target Milestone: ---
Classification: Community



Hi, I used to have a user account on the blog on gluster.org before it was
migrated to a new platform. I'd like to have an account again so that I can
post some articles about Gluster and some of its related projects.

Thanks!

username: ndevos
email: nde...@redhat.com

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1753587] https://build.gluster.org/job/compare-bug-version-and-git-branch/41059/ fails for public BZ

2019-09-20 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1753587



--- Comment #10 from M. Scherer  ---
now I can't reproduce much, so I have left debugging output and will wait until
next run

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1753587] https://build.gluster.org/job/compare-bug-version-and-git-branch/41059/ fails for public BZ

2019-09-20 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1753587



--- Comment #9 from M. Scherer  ---
ok, so that explain the cleaned_output line in the code. So I guess we are back
on the drawing board to figure why it break

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1753587] https://build.gluster.org/job/compare-bug-version-and-git-branch/41059/ fails for public BZ

2019-09-20 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1753587



--- Comment #8 from M. Scherer  ---
mhh, then why did it broke suddenly ?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1753587] https://build.gluster.org/job/compare-bug-version-and-git-branch/41059/ fails for public BZ

2019-09-20 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1753587



--- Comment #7 from Niels de Vos  ---
>From https://review.gluster.org/Documentation/rest-api.html#output :

To prevent against Cross Site Script Inclusion (XSSI) attacks, the JSON
response body starts with a magic prefix line that must be stripped before
feeding the rest of the response body to a JSON parser:

  )]}'
  [ ... valid JSON ... ]

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1753587] https://build.gluster.org/job/compare-bug-version-and-git-branch/41059/ fails for public BZ

2019-09-20 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1753587



--- Comment #6 from Niels de Vos  ---
I think Gerrit does it on purpose. Quite a while ago I have used Gerrit(Hub)
and scripts needed to drop the 1st line 'magic' value before parsing the
response.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1753587] https://build.gluster.org/job/compare-bug-version-and-git-branch/41059/ fails for public BZ

2019-09-20 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1753587

Deepshikha khandelwal  changed:

   What|Removed |Added

 CC||dkhan...@redhat.com



--- Comment #5 from Deepshikha khandelwal  ---
And this issue is not even persistent. We are getting random invalid JSON when
using gerrit API and sometimes not.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1753587] https://build.gluster.org/job/compare-bug-version-and-git-branch/41059/ fails for public BZ

2019-09-20 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1753587



--- Comment #4 from M. Scherer  ---
so, now we face a interesting issue, gerrit produce invalid json:

~ $ curl -s
"https://review.gluster.org/changes/glusterfs~master~I4fbb5c924fb3a144e415d2368126b784dde760ea/revisions/1/commit";
|head -n 5
)]}'
{
  "commit": "13f8432734f8fd3fe59f05a48d297a7e72c33301",
  "parents": [
{


Why, I have no idea. We flushed caches, etc just in case, and I will look at
the DB side, but maybe we will need to restart gerrit quickly before I get to
dig the source code.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1753587] https://build.gluster.org/job/compare-bug-version-and-git-branch/41059/ fails for public BZ

2019-09-19 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1753587



--- Comment #3 from M. Scherer  ---
ok, so I suspect it might have been partially due to a mix of pip package (for
github3-py) and the rpms.  let's see if my cleanup is working.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1753587] https://build.gluster.org/job/compare-bug-version-and-git-branch/41059/ fails for public BZ

2019-09-19 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1753587

M. Scherer  changed:

   What|Removed |Added

 CC||msche...@redhat.com



--- Comment #2 from M. Scherer  ---
python-requests is installed, and so is python-urllib3. But it seems there was
some fluck and we have a faulty package. I will fix.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1753587] https://build.gluster.org/job/compare-bug-version-and-git-branch/41059/ fails for public BZ

2019-09-19 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1753587



--- Comment #1 from Niels de Vos  ---
The error seems to be related to some missing Python package:

ImportError: No module named 'requests.packages.urllib3'


Maybe these additional RPM needs to be installed:
- python-requests.noarch : HTTP library, written in Python, for human beings
- python-urllib3.noarch : Python HTTP library with thread-safe connection
pooling and file post

With those RPMs installed, the package requests.packages.urllib3 can be
imported.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1753587] New: https://build.gluster.org/job/compare-bug-version-and-git-branch/41059/ fails for public BZ

2019-09-19 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1753587

Bug ID: 1753587
   Summary: https://build.gluster.org/job/compare-bug-version-and-
git-branch/41059/ fails for public BZ
   Product: GlusterFS
   Version: 6
Status: NEW
 Component: project-infrastructure
  Assignee: b...@gluster.org
  Reporter: nbala...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org
  Target Milestone: ---
Classification: Community



Description of problem:
https://build.gluster.org/job/compare-bug-version-and-git-branch/41059/ fails
for a public bug.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1751081] ModuleNotFoundError: No module named 'prettytable'

2019-09-11 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1751081



--- Comment #3 from M. Scherer  ---
I closed that because I think this do fix the bug, but if this is not
sufficient, of course, do not hesitate to reopen.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1751081] ModuleNotFoundError: No module named 'prettytable'

2019-09-11 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1751081

M. Scherer  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 CC||msche...@redhat.com
 Resolution|--- |CURRENTRELEASE
Last Closed||2019-09-11 09:40:19



--- Comment #2 from M. Scherer  ---
yeah, fixed by
https://github.com/gluster/gluster.org_ansible_configuration/commit/0ad1994965209aeef7d5010173538d0f0e617c64

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1751081] ModuleNotFoundError: No module named 'prettytable'

2019-09-11 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1751081



--- Comment #1 from Sunny Kumar  ---
Form gluster spec:



 686 %setup -q -n %{name}-%{version}%{?prereltag}
 687 %if ( ! %{_usepython3} )
 688 echo "fixing python shebangs..."
 689 for f in api events extras geo-replication libglusterfs tools xlators; do
 690 find $f -type f -exec sed -i 's|/usr/bin/python3|/usr/bin/python2|' {} \;
 691 done
 692 %endif

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1751081] New: ModuleNotFoundError: No module named 'prettytable'

2019-09-11 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1751081

Bug ID: 1751081
   Summary: ModuleNotFoundError: No module named 'prettytable'
   Product: GlusterFS
   Version: mainline
Status: NEW
 Component: project-infrastructure
  Assignee: b...@gluster.org
  Reporter: sunku...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org
  Target Milestone: ---
Classification: Community



Description of problem:

New test case is failing with below error:


from prettytable import PrettyTable
ModuleNotFoundError: No module named 'prettytable'



Additional info:

https://build.gluster.org/job/centos7-regression/7694/console

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1744671] Smoke is failing for the changeset

2019-09-03 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1744671

Deepshikha khandelwal  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 CC||dkhan...@redhat.com
 Resolution|--- |NOTABUG
Last Closed||2019-09-04 06:06:06



--- Comment #1 from Deepshikha khandelwal  ---
It was working fine. Multiple rechecks for a single patchset lead to this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1711945] create account on download.gluster.org

2019-08-22 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1711945

spame...@redhat.com changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
  Flags||needinfo?(mscherer@redhat.c
   ||om)



--- Comment #2 from spame...@redhat.com ---
Hi Michael

Please create the account for me as well.
Below are the required details:
Public ssh key: 

ssh-rsa
B3NzaC1yc2EDAQABAAABAQDHKKTwASBKVg4nN3p1vUj87906qFi8KQb/gTmt7ITPDg1GAvVhMJhbC4pT58/k9YjDf2Ez07VZ7fTYs9hqWHF4ZsJ2rbO2MPaHl4Fnfb8MP+Wq33juiznKRZU9+TRTFt83rDoRjDFwzhfGt6zdBPam6Etu0mR55OvWg8XM35wbdW0OP/pjIdQdjVoDp+YdpaX43lCr3M80NsbjAxk7xcPTrpqAK90qpVw1C5mqwHNeqJIGK/enADhaDaMhBPoNpWK1cy5xMnJcBbYXjrUZ4yqmhzJ48yUQiHYzlZZkx4JirbdZzE7FfRZt88crec9KTp1a/GLznP3L0dFA59SWAMKV
root@shep-mac

User name: spamecha

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1744671] New: Smoke is failing for the changeset

2019-08-22 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1744671

Bug ID: 1744671
   Summary: Smoke is failing for the changeset
   Product: GlusterFS
   Version: 6
Status: NEW
 Component: project-infrastructure
  Assignee: b...@gluster.org
  Reporter: shegg...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org
  Target Milestone: ---
Classification: Community



Description of problem:

Smoke job is failing for https://review.gluster.org/#/c/glusterfs/+/23284/ .
Recheck is also not working properly. Please fix the issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1711950] Account in download.gluster.org to upload the build packages

2019-08-22 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1711950



--- Comment #12 from M. Scherer  ---
I created the user, tell me if it doesn't work. The server is
download.rht.gluster.org (not download.gluster, who is a proxy).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1727727] Build+Packaging Automation

2019-08-22 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1727727



--- Comment #18 from hari gowtham  ---
(In reply to hari gowtham from comment #13)
> (In reply to M. Scherer from comment #12)
> > Ok, so I will install the packages on the builder we have, and then have it
> > added to jenkins. 
> > (and while on it, also have 2nd one, just in case)
> 
> Forgot to mention that this script file is also necessary:
> https://github.com/Sheetalpamecha/packaging-scripts/blob/master/
> generic_package.sh
> Will send a patch to have it in the repo.

The above mentioned file is sent as a patch at:
https://review.gluster.org/#/c/build-jobs/+/23289

> 
> > 
> > As for running different job running on specific machine, that's indeed
> > pretty annoying on jenkins. I do not have enough experience with jjb, but
> > JobTemplate is likely something that would help for that:
> > https://docs.openstack.org/infra/jenkins-job-builder/definition.html#id2 
> 
> Will look into it. I'm new to writing jobs for jenkins. 
> 
> > 
> > But afaik, gluster is not dependent on the kernel, so building that with
> > pbuilder in a chroot should be sufficient no matter what Debian, as long as
> > it is a up to date one, no ?
> 
> Yes, gluster is not dependent on kernel, but I'm unaware of using chroot 
> for different debian version .
> For this Kaleb would be the better person to answer.
> @kaleb can you please answer this?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1727727] Build+Packaging Automation

2019-08-22 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1727727



--- Comment #17 from Kaleb KEITHLEY  ---
(In reply to M. Scherer from comment #15)
> I did push the installation and I would like to defer the gnupg integration
> for now, as it likely requires a bit more discussion (like, how do we
> distribute the keys, etc, do we rotate it).
> 
> And for the pbuilder cache, I would need to know the exact matrix of
> distribution we want to build and how. That part seems not too hard:
> https://wiki.debian.org/
> PbuilderTricks#How_to_build_for_different_distributions
> 
> And if we aim to build on unstable, we also may need to do some work to keep
> the chroot updated (same for stable in fact).

The keys that we've been using were generated on an internal machine and
distributed to the build machines, which are all internal as well. 

We were using a new, different key for every major version through 4.1, but
some people complained about that, so for 5.x, 6.x, and now 7.x we have been
using the same key. As 4.1 is about to reach EOL that essentially means we are
only using a single key now for all the packages we build.

AFAIK people expect the packages to be signed. And best practices suggests to
me that they _must_ be signed.

Given that 7.0rc0 is now out and packages will be signed with the current key,
that suggests to me that we must keep using that key for the life of 7.x. We
can certainly create a new key for 8.x, when that rolls around.

And yes, we need a secure way to get the private key onto the jenkins build
machines somehow.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1727727] Build+Packaging Automation

2019-08-22 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1727727

Kaleb KEITHLEY  changed:

   What|Removed |Added

  Flags|needinfo?(kkeithle@redhat.c |
   |om) |



--- Comment #16 from Kaleb KEITHLEY  ---
yes, pbuilder is a chroot tool, similar to mock. Each time you build you get a
clean chroot.

We are currently building for stretch/9, buster/10, and bullseye/unstable/11.

AFAIK the buildroot should be updated periodically for all of them;
bullseye/unstable should probably be updated more frequently than the others.

I don't know anything about pbuilder apart from what I mentioned above, and
specifically I don't know anything about how to use pbuilder to build for
different distributions on a single machine. I've been using separate stretch,
buster, and bullseye installs on dedicated boxes to build the packages for that
release of Debian.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1711950] Account in download.gluster.org to upload the build packages

2019-08-22 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1711950



--- Comment #11 from M. Scherer  ---
ok so 3 months is enougn (cause i also do not want to push unrealisitic
deadline or more pressure, plus shit happen), I will add the account as soon as
the previous ansible run finish. And if that's not enough, we can of course
keep it open longer, just to be clear. But after jenkins issue last month, and
the old compromise last time, we can't let stuff open too long if they are not
going to clean themself.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1727727] Build+Packaging Automation

2019-08-22 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1727727



--- Comment #15 from M. Scherer  ---
I did push the installation and I would like to defer the gnupg integration for
now, as it likely requires a bit more discussion (like, how do we distribute
the keys, etc, do we rotate it).

And for the pbuilder cache, I would need to know the exact matrix of
distribution we want to build and how. That part seems not too hard:
https://wiki.debian.org/PbuilderTricks#How_to_build_for_different_distributions

And if we aim to build on unstable, we also may need to do some work to keep
the chroot updated (same for stable in fact).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1711950] Account in download.gluster.org to upload the build packages

2019-08-22 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1711950

hari gowtham  changed:

   What|Removed |Added

  Flags|needinfo?(hgowtham@redhat.c |
   |om) |



--- Comment #10 from hari gowtham  ---
We are trying to finish it within this sprint (each sprint is for 3 weeks).
So we will assume that we should be done in a month with the automation.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1711950] Account in download.gluster.org to upload the build packages

2019-08-22 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1711950

Shwetha K Acharya  changed:

   What|Removed |Added

 CC||hgowt...@redhat.com
  Flags||needinfo?(hgowtham@redhat.c
   ||om)



--- Comment #9 from Shwetha K Acharya  ---
Hari, Can you please address the above query?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1711950] Account in download.gluster.org to upload the build packages

2019-08-22 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1711950



--- Comment #8 from M. Scherer  ---
As said in the comment #2 and comment #4, what is the deadline for the account
closure ? 

If I do not get a answer, then I will just decide on "3 month after the
creation" and then deploy.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1711950] Account in download.gluster.org to upload the build packages

2019-08-22 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1711950



--- Comment #7 from Shwetha K Acharya  ---
@misc (In reply to M. Scherer from comment #4)
> Sure give me a deadline, and I will create the account. I mean, I do not
> even need a precise one.
> 
> Would you agree on "We do in 3 months", in which case I create the account
> right now (with expiration as set).
> 
> (I need a public ssh key and a username)

We have already taken up the task of automating building and packaging. Details
can be found at https://bugzilla.redhat.com/show_bug.cgi?id=1727727. 

Please create the account.
Below are the required details:
Public ssh key: 
ssh-rsa
B3NzaC1yc2EDAQABAAABAQCifwFXjkLXFwnlTBMXFgTEHAA1Vavzti41B4Yp1RJYtCuJ91s+P5YHc2j4a/wpVquPJboNuv9wtqknmd5SJYBXB11dinNfHfvE+gCN9Osdn64/om9i3pIpQQeY6uvF4MF9yfyx8huEWFZeaOiljvmTZ3//4kzsJHK2yKCmJFhy5Zcg9+WMM2bjfACjlFDIuOG2kqaRM8tGggOQG9iQ/VElWOTxJkHUJaP50PWdwEHHoiCKmipe5xEcSR/6qubaF6VpMfBLmrjmJMqkjVozryVweHBLn3oQfOkJmlErwJox7hLFuk5V4fvVine5xrWKygw/kA2Mpr7Q1zXg5moZHbCP
root@localhost.localdomain

User name: sacharya

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1727727] Build+Packaging Automation

2019-08-22 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1727727



--- Comment #14 from M. Scherer  ---
Pbuilder do setup chroots, afaik, so that's kinda like mock, if you are maybe
more familliar with the Fedora/Centos tooling. Now, maybe there is limitation
and they do not work exactly the same, but I would have expected a clean chroot
created each time, to build the package. I didn't do debian package since a
long time.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1727727] Build+Packaging Automation

2019-08-22 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1727727

hari gowtham  changed:

   What|Removed |Added

 CC||kkeit...@redhat.com
  Flags||needinfo?(kkeithle@redhat.c
   ||om)



--- Comment #13 from hari gowtham  ---
(In reply to M. Scherer from comment #12)
> Ok, so I will install the packages on the builder we have, and then have it
> added to jenkins. 
> (and while on it, also have 2nd one, just in case)

Forgot to mention that this script file is also necessary:
https://github.com/Sheetalpamecha/packaging-scripts/blob/master/generic_package.sh
Will send a patch to have it in the repo.

> 
> As for running different job running on specific machine, that's indeed
> pretty annoying on jenkins. I do not have enough experience with jjb, but
> JobTemplate is likely something that would help for that:
> https://docs.openstack.org/infra/jenkins-job-builder/definition.html#id2 

Will look into it. I'm new to writing jobs for jenkins. 

> 
> But afaik, gluster is not dependent on the kernel, so building that with
> pbuilder in a chroot should be sufficient no matter what Debian, as long as
> it is a up to date one, no ?

Yes, gluster is not dependent on kernel, but I'm unaware of using chroot 
for different debian version .
For this Kaleb would be the better person to answer.
@kaleb can you please answer this?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1727727] Build+Packaging Automation

2019-08-22 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1727727



--- Comment #12 from M. Scherer  ---
Ok, so I will install the packages on the builder we have, and then have it
added to jenkins. 
(and while on it, also have 2nd one, just in case)

As for running different job running on specific machine, that's indeed pretty
annoying on jenkins. I do not have enough experience with jjb, but JobTemplate
is likely something that would help for that:
https://docs.openstack.org/infra/jenkins-job-builder/definition.html#id2 

But afaik, gluster is not dependent on the kernel, so building that with
pbuilder in a chroot should be sufficient no matter what Debian, as long as it
is a up to date one, no ?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1727727] Build+Packaging Automation

2019-08-22 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1727727



--- Comment #11 from hari gowtham  ---
By setup i meant doing the following prerequisites:

these two steps are the ones necessary as of now:
- `deb.packages.dot-gnupg.tgz`: has the ~/.gnupg dir with the keyring
needed to build & sign packages
- packages required: build-essential pbuilder devscripts reprepro
debhelper dpkg-sig

And for the first time we need to do this:

# First time create the /var/cache/pbuilder/base.tgz
# on debian: sudo pbuilder create --distribution wheezy --mirror
ftp://ftp.us.debian.org/debian/ --debootstrapopts
"--keyring=/usr/share/keyrings/debian-archive-keyring.gpg"
# on raspbian: sudo pbuilder create --distribution wheezy --mirror
http://archive.raspbian.org/raspbian/ --debootstrapopts
"--keyring=/usr/share/keyrings/raspbian-archive-keyring.gpg"

NOTE:
In future if any change is made here (
https://github.com/semiosis/glusterfs-debian/tree/wheezy-glusterfs-3.5/debian)
then we might have to change it.




The reason to go for the above two level implementation was, I wasn't aware of
how to make the 
job run on a particular machine based on the arguments it gets.

Like stretch has to be run on
rhs-vm-16.storage-dev.lab.eng.bOS.redhat.com(which will be one of the jenkins
debian slaves)
And we have to run the script on multiple machines based on the number of
distributions we want to build.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1727727] Build+Packaging Automation

2019-08-20 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1727727

M. Scherer  changed:

   What|Removed |Added

  Flags|needinfo?(mscherer@redhat.c |
   |om) |



--- Comment #10 from M. Scherer  ---
I am not sure to understand what do you mean by "setup them up". 

I do expect the setup be done with ansible, using our playbooks, and not give
direct access to people (because experience showed that when people have a way
to bypass automation, they do bypass it sooner or later, causing us trouble
later).

So far, the only patch I found is
https://review.gluster.org/#/c/build-jobs/+/23172/ which is not exactly
something that should be merged, since that's a job that do replicate the work
of jenkins. I kinda do expect a job that just run generic-package.sh on the
builder, and that's it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1738778] Unable to setup softserve VM

2019-08-19 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1738778



--- Comment #4 from Ravishankar N  ---
Deleting that line worked.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1738778] Unable to setup softserve VM

2019-08-19 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1738778

M. Scherer  changed:

   What|Removed |Added

 CC||msche...@redhat.com



--- Comment #3 from M. Scherer  ---
That is not a infra issue, the inventory is wrong:

https://github.com/gluster/softserve/blob/master/playbooks/inventory#L6

Regular non infra folks do not have access to that server to serve as a
bastion.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1738778] Unable to setup softserve VM

2019-08-08 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1738778



--- Comment #2 from Ravishankar N  ---
I'm trying this on Fedora 30. Here is the verbose output if it helps. I can ssh
into the VM as centos user just fine.
-
fatal: [builder500.cloud.gluster.org]: UNREACHABLE! => {
"changed": false,
"msg": "Failed to connect to the host via ssh: OpenSSH_8.0p1, OpenSSL
1.1.1c FIPS  28 May 2019\r\ndebug1: Reading configuration data
/home/ravi/.ssh/config\r\ndebug1: Reading configuration data
/etc/ssh/ssh_config\r\ndebug3: /etc/ssh/ssh_config line 51: Including file
/etc/ssh/ssh_config.d/05-redhat.conf depth 0\r\ndebug1: Reading configuration
data /etc/ssh/ssh_config.d/05-redhat.conf\r\ndebug2: checking match for 'final
all' host 18.219.69.93 originally 18.219.69.93\r\ndebug3:
/etc/ssh/ssh_config.d/05-redhat.conf line 3: not matched 'final'\r\ndebug2:
match not found\r\ndebug3: /etc/ssh/ssh_config.d/05-redhat.conf line 5:
Including file /etc/crypto-policies/back-ends/openssh.config depth 1 (parse
only)\r\ndebug1: Reading configuration data
/etc/crypto-policies/back-ends/openssh.config\r\ndebug3: gss kex names ok:
[gss-gex-sha1-,gss-group14-sha1-,gss-group1-sha1-]\r\ndebug3: kex names ok:
[curve25519-sha256,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1]\r\ndebug1:
configuration requests final Match pass\r\ndebug2: resolve_canonicalize:
hostname 18.219.69.93 is address\r\ndebug1: re-parsing configuration\r\ndebug1:
Reading configuration data /home/ravi/.ssh/config\r\ndebug1: Reading
configuration data /etc/ssh/ssh_config\r\ndebug3: /etc/ssh/ssh_config line 51:
Including file /etc/ssh/ssh_config.d/05-redhat.conf depth 0\r\ndebug1: Reading
configuration data /etc/ssh/ssh_config.d/05-redhat.conf\r\ndebug2: checking
match for 'final all' host 18.219.69.93 originally 18.219.69.93\r\ndebug3:
/etc/ssh/ssh_config.d/05-redhat.conf line 3: matched 'final'\r\ndebug2: match
found\r\ndebug3: /etc/ssh/ssh_config.d/05-redhat.conf line 5: Including file
/etc/crypto-policies/back-ends/openssh.config depth 1\r\ndebug1: Reading
configuration data /etc/crypto-policies/back-ends/openssh.config\r\ndebug3: gss
kex names ok: [gss-gex-sha1-,gss-group14-sha1-,gss-group1-sha1-]\r\ndebug3: kex
names ok:
[curve25519-sha256,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1]\r\ndebug1:
auto-mux: Trying existing master\r\ndebug1: Control socket
\"/home/ravi/.ansible/cp/d35c8610b6\" does not exist\r\ndebug1: Executing proxy
command: exec ssh -q -W 18.219.69.93:22 r...@logs.aws.gluster.org\r\ndebug3:
timeout: 1 ms remain after connect\r\ndebug1: identity file
/home/ravi/.ssh/id_rsa type 0\r\ndebug1: identity file
/home/ravi/.ssh/id_rsa-cert type -1\r\ndebug1: identity file
/home/ravi/.ssh/id_dsa type -1\r\ndebug1: identity file
/home/ravi/.ssh/id_dsa-cert type -1\r\ndebug1: identity file
/home/ravi/.ssh/id_ecdsa type -1\r\ndebug1: identity file
/home/ravi/.ssh/id_ecdsa-cert type -1\r\ndebug1: identity file
/home/ravi/.ssh/id_ed25519 type -1\r\ndebug1: identity file
/home/ravi/.ssh/id_ed25519-cert type -1\r\ndebug1: identity file
/home/ravi/.ssh/id_xmss type -1\r\ndebug1: identity file
/home/ravi/.ssh/id_xmss-cert type -1\r\ndebug1: Local version string
SSH-2.0-OpenSSH_8.0\r\nkex_exchange_identification: Connection closed by remote
host",
"unreachable": true
}

PLAY RECAP
**
builder500.cloud.gluster.org : ok=0changed=0unreachable=1failed=0  
 skipped=0rescued=0ignored=0
-

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1738778] Unable to setup softserve VM

2019-08-08 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1738778

Deepshikha khandelwal  changed:

   What|Removed |Added

 CC||dkhan...@redhat.com



--- Comment #1 from Deepshikha khandelwal  ---
It's working fine for me.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1738778] New: Unable to setup softserve VM

2019-08-08 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1738778

Bug ID: 1738778
   Summary: Unable to setup softserve VM
   Product: GlusterFS
   Version: mainline
Status: NEW
 Component: project-infrastructure
  Assignee: b...@gluster.org
  Reporter: ravishan...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org
  Target Milestone: ---
Classification: Community



Description of problem:
After creating a VM from https://softserve.gluster.org/dashboard, when I try to
use
https://github.com/gluster/softserve/wiki/Running-Regressions-on-loaned-Softserve-instances,
it doesn't connect to the VM. This is not just me, I believe even Sac tried it
out on his setup and saw the same issue today.

When I run `ansible-playbook -v -i inventory regressions-final.yml --become -u
centos`, I get:

TASK [Gathering Facts]
**
fatal: [builder555.cloud.gluster.org]: UNREACHABLE! => {"changed": false,
"msg": "Failed to connect to the host via ssh: kex_exchange_identification:
Connection closed by remote host", "unreachable": true}

PLAY RECAP
**
builder555.cloud.gluster.org : ok=0changed=0unreachable=1failed=0  
 skipped=0rescued=0ignored=0

I believe this is an infra issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1727727] Build+Packaging Automation

2019-08-06 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1727727

hari gowtham  changed:

   What|Removed |Added

  Flags||needinfo?(mscherer@redhat.c
   ||om)



--- Comment #9 from hari gowtham  ---
Hi Misc,

Can you please create the machines as mentioned above, so we can setup them up?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1731067] Need nightly build for release 7 branch

2019-07-29 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1731067



--- Comment #1 from Deepshikha khandelwal  ---
Patch for review https://review.gluster.org/#/c/build-jobs/+/23126/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1727727] Build+Packaging Automation

2019-07-29 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1727727



--- Comment #8 from M. Scherer  ---
We can increase the disk size if needed when we hit problems, that shouldn't be
a worry.

About the password, we can also just store the key on a emulated smartcard on
the builder side, and use a password stored on the builder. Therefore, no one
will have to type it or share it, and it can't be copied. And that permit
automated setup.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1727727] Build+Packaging Automation

2019-07-28 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1727727



--- Comment #7 from hari gowtham  ---
@Misc, I see debian machines have 20GB disks each and Ubuntu has 30GB disk in
the current machines. And we did come across debian machine not having enough
space to build lately.
So a bit more for the new machines in jenkins would be better.

About signing, is it fine if we get the password to the machines as a parameter
from the person who triggers the jenkins' job and proceed with it to sign in?
This way we can make use of the same machine for building and signing the
package. But I'm not sure if the parameters are logged somewhere. Which will
let others know the password.
If that's the case, do we have a work around for this? If manual intervention
is necessary for signing, it sort of defeats a portion of this effort. 

@Kaleb, I wanted to ask about the steps for the initial environment setup.
Thanks for informing about it, will look into it once the machines are
available.
I want to know if the package that are already built on these lab machines have
to be moved to these new jenkins' machine as a part of keeping track of
packages. 
And will there be any other work to be done as a part of this movement.

Thanks,
Hari.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1730962] My emails to gluster-users are not hitting the list

2019-07-28 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1730962

Deepshikha khandelwal  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution|--- |NOTABUG
Last Closed||2019-07-29 05:51:34



-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1730962] My emails to gluster-users are not hitting the list

2019-07-28 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1730962

Ravishankar N  changed:

   What|Removed |Added

  Flags|needinfo?(ravishankar@redha |
   |t.com)  |



--- Comment #4 from Ravishankar N  ---
Yes I have changed to my alias ID while emailing the list and the messages are
now getting delivered.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1730962] My emails to gluster-users are not hitting the list

2019-07-28 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1730962

Deepshikha khandelwal  changed:

   What|Removed |Added

 CC||dkhan...@redhat.com
  Flags||needinfo?(ravishankar@redha
   ||t.com)



--- Comment #3 from Deepshikha khandelwal  ---
@Ravi Is this resolved for you now?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1727727] Build+Packaging Automation

2019-07-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1727727



--- Comment #5 from Kaleb KEITHLEY  ---
(In reply to hari gowtham from comment #4)
> The requirements from the infra side are:
> 1) check if the lab machines are reachable from the jenkins' slave

They are not reachable.

You probably need four new build machines in Jenkins: Debian stretch/9,
buster/10, and bullseye/11; and Ubuntu bionic/18.04. The debian boxes need lots
of disk space, the ubuntu needs slightly less as packages aren't actually built
on it, it sends them to Launchpad to build.

The machines _must_ be secure as they will, by necessity, have to have gpg
private keys that are used to sign the packages  installed on them.

The machines should be apt update + apt upgraded periodically.  There's a small
amount of pbuilder setup (see the ~glusterpackager/HOWTO file on the current
builders in the lab) that should be updated periodically as well.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1713391] Access to wordpress instance of gluster.org required for release management

2019-07-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1713391



--- Comment #6 from M. Scherer  ---
Ok, so I found a way to enter, I created myself a account, and created a
account for rinku, who should have received a email.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1713391] Access to wordpress instance of gluster.org required for release management

2019-07-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1713391



--- Comment #5 from M. Scherer  ---
So, I do not have the admin credentials for that wordpress instance (I have
access for wpengine, which we inherited). I guess that mean I have to find
somehow a way to enter.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1727727] Build+Packaging Automation

2019-07-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1727727

M. Scherer  changed:

   What|Removed |Added

 CC||msche...@redhat.com



--- Comment #6 from M. Scherer  ---
We have debian builders (well, we have one, but I can create more quite
easily). How much is lots of disk space ?

Also, I would prefer a separate step to sign, so we can run that on a separate
server that the one where stuff are being built.

And yes, we are not going to build stuff in the lab, we can't ssh there.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1727727] Build+Packaging Automation

2019-07-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1727727

hari gowtham  changed:

   What|Removed |Added

 CC||hgowt...@redhat.com



--- Comment #4 from hari gowtham  ---
For automating the packaging for debian and ubuntu, we have wrote two scripts.
packaging. sh is one which the jenkins' slave has to run based on a job that is
being triggered by one of us.
This will ssh to the respective lab machine and run the generic_script.sh in
the machine to build the packages.
(We will take care of having the generic_script.sh made available in the lab
machine.)

The requirements from the infra side are:
1) check if the lab machines are reachable from the jenkins' slave
2) map the credentials that the package.sh needs to ssh to the lab machines, so
we can use the key instead of passing passwords.
3) trigger permissions are to be given only for a specific set of people.
Amar, Shyam, Kaleb, Sunny, Rinku, Shwetha, Sheetal, and Hari.

The scripts are available at:
https://github.com/Sheetalpamecha/packaging-scripts/

Will send the package.sh script as a patch to build-jobs once the keys to login
are available.
And will work on the job simulatenously as well.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1731067] Need nightly build for release 7 branch

2019-07-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1731067

Deepshikha khandelwal  changed:

   What|Removed |Added

 CC||dkhan...@redhat.com
   Assignee|b...@gluster.org|dkhan...@redhat.com



-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1731067] New: Need nightly build for release 7 branch

2019-07-18 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1731067

Bug ID: 1731067
   Summary: Need nightly build for release 7 branch
   Product: GlusterFS
   Version: mainline
Status: NEW
 Component: project-infrastructure
  Severity: high
  Assignee: b...@gluster.org
  Reporter: rkoth...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org
  Target Milestone: ---
Classification: Community



-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1730962] My emails to gluster-users are not hitting the list

2019-07-18 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1730962



--- Comment #2 from Ravishankar N  ---
Thanks Michael, that explains it. I had configured Thunderbird on my fresh
Fedora install using my kerberos email ID rather than my alias which I use for
mailing lists. Let me fix it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1730962] My emails to gluster-users are not hitting the list

2019-07-18 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1730962

M. Scherer  changed:

   What|Removed |Added

 CC||msche...@redhat.com



--- Comment #1 from M. Scherer  ---
It does fall under our purview. it seems the address you used is not a member
of the list and it seems no one moderated the list since months. I am cleaning
the moderation queue, it should appear soon.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1730962] New: My emails to gluster-users are not hitting the list

2019-07-17 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1730962

Bug ID: 1730962
   Summary: My emails to gluster-users are not hitting the list
   Product: GlusterFS
   Version: mainline
Status: NEW
 Component: project-infrastructure
  Assignee: b...@gluster.org
  Reporter: ravishan...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org
  Target Milestone: ---
Classification: Community



Description of problem:

I replied to a user on the 16th of July but my email hasn't been delivered to
the list yet.The user got my email though and he replied, which made it to the
list: https://lists.gluster.org/pipermail/gluster-users/2019-July/036799.html.
Follow-up emails from me on the same thread have not been delivered either. I
did not get any error for the sent messages.

I sent an email to gluster-users-ow...@gluster.org for help but I haven't
received any response. 

I'm not sure if the mailing list administration falls under the infra team's
purview. If it doesn't feel free to close the bug and possibly point me to whom
I can get in touch with regarding the issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1564130] need option 'cherry-pick to release-x.y' in reviews

2019-07-15 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1564130

Deepshikha khandelwal  changed:

   What|Removed |Added

  Flags|needinfo?(dkhandel@redhat.c |
   |om) |



--- Comment #4 from Deepshikha khandelwal  ---
No. Jenkins part of automation is pending. I'll pick this up next week.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1727727] Build+Packaging Automation

2019-07-15 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1727727

spame...@redhat.com changed:

   What|Removed |Added

 Status|NEW |ASSIGNED



-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1697812] mention a pointer to all the mailing lists available under glusterfs project(https://www.gluster.org/community/)

2019-07-15 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1697812

Amar Tumballi  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution|--- |CURRENTRELEASE
Last Closed||2019-07-16 04:37:17



--- Comment #2 from Amar Tumballi  ---
Page updated, please check.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1728120] Not able to access core https://build.gluster.org/job/regression-test-with-multiplex/1402/consoleFull

2019-07-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1728120

Deepshikha khandelwal  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution|--- |CURRENTRELEASE
Last Closed||2019-07-15 05:49:09



-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1724957] Grant additional maintainers merge rights on release branches

2019-07-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1724957

Deepshikha khandelwal  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution|--- |CURRENTRELEASE
Last Closed||2019-07-15 05:47:50



--- Comment #3 from Deepshikha khandelwal  ---
Fixed. Closing bug

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1728120] Not able to access core https://build.gluster.org/job/regression-test-with-multiplex/1402/consoleFull

2019-07-09 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1728120



--- Comment #4 from Deepshikha khandelwal  ---
Fix: https://review.gluster.org/#/c/build-jobs/+/23019/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1728120] Not able to access core https://build.gluster.org/job/regression-test-with-multiplex/1402/consoleFull

2019-07-09 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1728120

Deepshikha khandelwal  changed:

   What|Removed |Added

 CC||dkhan...@redhat.com



--- Comment #3 from Deepshikha khandelwal  ---
Yes. Log thing never worked for this job. I will add the credential binding for
this job.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1728120] Not able to access core https://build.gluster.org/job/regression-test-with-multiplex/1402/consoleFull

2019-07-09 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1728120



--- Comment #2 from M. Scherer  ---
Seems that this job never worked, there is no binding for the ssh key.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1728120] Not able to access core https://build.gluster.org/job/regression-test-with-multiplex/1402/consoleFull

2019-07-09 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1728120

M. Scherer  changed:

   What|Removed |Added

 CC||msche...@redhat.com



--- Comment #1 from M. Scherer  ---
20:29:51 + scp -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -i
''
/archives/archived_builds/build-install-regression-test-with-multiplex-1402.tar.bz2
_logs-collec...@logs.aws.gluster.org:/var/www/glusterfs-logs/regression-test-with-multiplex-1402.bz2
20:29:51 Warning: Identity file  not accessible: No such file or directory.
20:29:51 Warning: Permanently added 'logs.aws.gluster.org,18.219.45.211'
(ECDSA) to the list of known hosts.
20:29:51 Permission denied (publickey,gssapi-keyex,gssapi-with-mic).

seems there is a key that wasn't deployed properly, I am looking at it.

In the mean time, I ill copy the file manually.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1728120] New: Not able to access core https://build.gluster.org/job/regression-test-with-multiplex/1402/consoleFull

2019-07-08 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1728120

Bug ID: 1728120
   Summary: Not able to access core
https://build.gluster.org/job/regression-test-with-mul
tiplex/1402/consoleFull
   Product: GlusterFS
   Version: mainline
Status: NEW
 Component: project-infrastructure
  Assignee: b...@gluster.org
  Reporter: moagr...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org
  Target Milestone: ---
Classification: Community



Description of problem:

Not able to access the core from the link
https://build.gluster.org/job/regression-test-with-multiplex/1402/consoleFull
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1727724] New: Build+Packaging Automation

2019-07-07 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1727724

Bug ID: 1727724
   Summary: Build+Packaging Automation
   Product: GlusterFS
   Version: mainline
Status: NEW
 Component: project-infrastructure
  Assignee: b...@gluster.org
  Reporter: spame...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org
  Target Milestone: ---
Classification: Community



Description of problem:

Currently for every release, packages for Debian(9 & 10) and
Ubuntu(bionic,cosmic,eoan,disco,xenial) need to be built manually. To automate
this process in the same way as fedora and centos are triggered.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1727727] New: Build+Packaging Automation

2019-07-07 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1727727

Bug ID: 1727727
   Summary: Build+Packaging Automation
   Product: GlusterFS
   Version: mainline
Status: NEW
 Component: project-infrastructure
  Assignee: b...@gluster.org
  Reporter: spame...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org
  Target Milestone: ---
Classification: Community



Description of problem:

Currently for every release, packages for Debian(9 & 10) and
Ubuntu(bionic,cosmic,eoan,disco,xenial) need to be built manually. To automate
this process in the same way as fedora and centos are triggered.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1727722] New: Build+Packaging Automation

2019-07-07 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1727722

Bug ID: 1727722
   Summary: Build+Packaging Automation
   Product: GlusterFS
   Version: mainline
Status: NEW
 Component: project-infrastructure
  Assignee: b...@gluster.org
  Reporter: spame...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org
  Target Milestone: ---
Classification: Community



Description of problem:

Currently for every release, packages for Debian(9 & 10) and
Ubuntu(bionic,cosmic,eoan,disco,xenial) need to be built manually. To automate
this process in the same way as fedora and centos are triggered.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1727723] New: Build+Packaging Automation

2019-07-07 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1727723

Bug ID: 1727723
   Summary: Build+Packaging Automation
   Product: GlusterFS
   Version: mainline
Status: NEW
 Component: project-infrastructure
  Assignee: b...@gluster.org
  Reporter: spame...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org
  Target Milestone: ---
Classification: Community



Description of problem:

Currently for every release, packages for Debian(9 & 10) and
Ubuntu(bionic,cosmic,eoan,disco,xenial) need to be built manually. To automate
this process in the same way as fedora and centos are triggered.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1720453] Unable to access review.gluster.org

2019-07-07 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1720453

Deepshikha khandelwal  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 CC||dkhan...@redhat.com
 Resolution|--- |CURRENTRELEASE
Last Closed||2019-07-08 02:40:39



--- Comment #4 from Deepshikha khandelwal  ---
It is fixed now. Closing it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1641021] gd2-smoke do not seems to clean itself after a crash

2019-07-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1641021

Michael S.  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 CC||m...@zarb.org
 Resolution|--- |CURRENTRELEASE
Last Closed||2019-07-04 16:42:15



--- Comment #3 from Michael S.  ---
Yup

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1516198] Create jenk...@build.gluster.org and send to /dev/null

2019-07-01 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1516198

M. Scherer  changed:

   What|Removed |Added

 CC||msche...@redhat.com
 Resolution|WONTFIX |CURRENTRELEASE



--- Comment #2 from M. Scherer  ---
This was done, so it should't be closed won't fix.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1503529] Investigate having a mirror of download server

2019-07-01 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1503529

M. Scherer  changed:

   What|Removed |Added

  Flags|needinfo?(mscherer@redhat.c |
   |om) |



--- Comment #3 from M. Scherer  ---
Still relevant but I want first make sure tarball generation is automated
before.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1641021] gd2-smoke do not seems to clean itself after a crash

2019-06-30 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1641021

Yaniv Kaul  changed:

   What|Removed |Added

  Flags||needinfo?(mscherer@redhat.c
   ||om)



--- Comment #2 from Yaniv Kaul  ---
Patch merged. Can we close this?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1503529] Investigate having a mirror of download server

2019-06-30 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1503529

Yaniv Kaul  changed:

   What|Removed |Added

  Flags||needinfo?(mscherer@redhat.c
   ||om)



--- Comment #2 from Yaniv Kaul  ---
Still relevant?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1516198] Create jenk...@build.gluster.org and send to /dev/null

2019-06-30 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1516198

Yaniv Kaul  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution|--- |WONTFIX
Last Closed||2019-07-01 06:04:56



--- Comment #1 from Yaniv Kaul  ---
Closing old BZs.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1514369] Make Gluster code history available with cregit

2019-06-30 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1514369

Yaniv Kaul  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution|--- |WONTFIX
Last Closed||2019-07-01 06:04:34



--- Comment #1 from Yaniv Kaul  ---
Unlikely to happen if did not happen by now.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1716097] infra: create suse-pack...@lists.nfs-ganesha.org alias

2019-06-28 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1716097



--- Comment #4 from Marc Dequènes (Duck)  ---
Could someone give some status update please?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] [Bug 1724957] Grant additional maintainers merge rights on release branches

2019-06-28 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1724957



--- Comment #1 from Deepshikha khandelwal  ---
Can you please check now?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1724957] New: Grant additional maintainers merge rights on release branches

2019-06-28 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1724957

Bug ID: 1724957
   Summary: Grant additional maintainers merge rights on release
branches
   Product: GlusterFS
   Version: mainline
Status: NEW
 Component: project-infrastructure
  Assignee: b...@gluster.org
  Reporter: rkoth...@redhat.com
CC: b...@gluster.org, dkhan...@redhat.com,
gluster-infra@gluster.org, hgowt...@redhat.com,
rkoth...@redhat.com, srang...@redhat.com,
sunku...@redhat.com
Depends On: 1708257
  Target Milestone: ---
Classification: Community




Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1708257
[Bug 1708257] Grant additional maintainers merge rights on release branches
-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1708257] Grant additional maintainers merge rights on release branches

2019-06-28 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1708257

Rinku  changed:

   What|Removed |Added

 Blocks||1724957




Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1724957
[Bug 1724957] Grant additional maintainers merge rights on release branches
-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1665361] Alerts for offline nodes

2019-06-20 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1665361

PnT Account Manager  changed:

   What|Removed |Added

   Assignee|narek...@redhat.com |b...@gluster.org



-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1721353] Run 'line-coverage' regression runs on a latest fedora machine (say fedora30).

2019-06-18 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1721353

Kotresh HR  changed:

   What|Removed |Added

 CC||khire...@redhat.com



--- Comment #2 from Kotresh HR  ---
I have also witnessed the small difference when I was working to improve lcov
of glusterd-georep.c. On fedora 30, I used to see 70.1 % but on centos 69.9 %. 
I didn't spend time debugging that though. Didn't expect it was platform
dependent.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1721353] Run 'line-coverage' regression runs on a latest fedora machine (say fedora30).

2019-06-17 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1721353



--- Comment #1 from Amar Tumballi  ---
Ok, when I used the lcov tool with the same commands as that of lcov.sh from
build-jobs repo, I got below numbers for stack.h (which I used as an example
above).

on current builder :  stack.h - lines(262/497 - 52.7%), functions(17/41 -
41.5%) 
on fedora29 (local):  stack.h - lines(94/111  - 84.7%), functions(6/7 - 85.7%)

I hope just by running the regression on fedora, we would get more up-to-date
information, and more coverage details. Just note that I suspect this to be
more of an header file specific details, and even then, up-to-date information
is better than stale info.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1721353] New: Run 'line-coverage' regression runs on a latest fedora machine (say fedora30).

2019-06-17 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1721353

Bug ID: 1721353
   Summary: Run 'line-coverage' regression runs on a latest fedora
machine (say fedora30).
   Product: GlusterFS
   Version: mainline
Status: NEW
 Component: project-infrastructure
  Severity: high
  Priority: high
  Assignee: b...@gluster.org
  Reporter: atumb...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org
  Target Milestone: ---
Classification: Community



Description of problem:

I suspect the code coverage tool with centos7 is not covering all the details.


Check
https://build.gluster.org/job/line-coverage/lastCompletedBuild/Line_20Coverage_20Report/libglusterfs/src/glusterfs/stack.h.gcov.html
for example, and you can see that it says, 17/41 functions are covered. But if
you notice there are only 17 inline functions, and all of them are actually
covered.

If it reported it properly, we should have had 100% coverage there.

With that detail, I hope having newer version would get this sorted.

Also note, we recently fixed all the issues with python3 in regression runs
too, so moving to fedora should help us identify issues sooner with python3 (if
any).

Version-Release number of selected component (if applicable):
master

How reproducible:
100%


Expected results:
Nightly line-coverage runs to run on fedora systems.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1716097] infra: create suse-pack...@lists.nfs-ganesha.org alias

2019-06-17 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1716097



--- Comment #3 from Marc Dequènes (Duck)  ---
Is this ok?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] [Bug 1719388] infra: download.gluster.org /var/www/html/... is out of free space

2019-06-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1719388



--- Comment #5 from M. Scherer  ---
so, / was full, i cleand things (especially since that's now behind the proxy,
no need to keep log there). Should be compressed in the future.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1489417] Gerrit shouldn't offer http or git for code download

2019-06-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1489417

Amar Tumballi  changed:

   What|Removed |Added

   Priority|unspecified |low
 CC||atumb...@redhat.com
   Severity|unspecified |low



-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1720453] Unable to access review.gluster.org

2019-06-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1720453



--- Comment #3 from M. Scherer  ---
So, i think the root cause is fixed (at least from my perspective), so DNS
propagation should occurs quickly and fix it for others.

Writing the post mortme at the moment.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1720453] Unable to access review.gluster.org

2019-06-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1720453

M. Scherer  changed:

   What|Removed |Added

 CC||msche...@redhat.com



--- Comment #2 from M. Scherer  ---
yeah, there is a DNS issue. I am on it and I suspect that I found the exact
issue. Postmortem will explain if that fix, right now, I am waiting on DNS
propagation.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1720453] New: Unable to access review.gluster.org

2019-06-14 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1720453

Bug ID: 1720453
   Summary: Unable to access review.gluster.org
   Product: GlusterFS
   Version: mainline
Status: NEW
 Component: project-infrastructure
  Assignee: b...@gluster.org
  Reporter: ravishan...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org
  Target Milestone: ---
Classification: Community



Created attachment 1580537
  --> https://bugzilla.redhat.com/attachment.cgi?id=1580537&action=edit
browser screenshot

Description of problem:
Not able to access the website, see attached screenshot.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1719388] infra: download.gluster.org /var/www/html/... is out of free space

2019-06-13 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1719388



--- Comment #4 from M. Scherer  ---
So, that was a missing package (optional dep), breaking the acl on munin. Not
sure how to clear that cleanly, but alerting shoulw work. Now, to clean
stuff...

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1719388] infra: download.gluster.org /var/www/html/... is out of free space

2019-06-13 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1719388



--- Comment #3 from M. Scherer  ---
ok so not only is monitoring out (not sure why, it worked when deployed), but /
is full, because /var/log is taking 5G (why, dunno, I guess a lot of requests
or something), and no compression, this filled the server.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1719388] infra: download.gluster.org /var/www/html/... is out of free space

2019-06-13 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1719388



--- Comment #2 from M. Scherer  ---
So:
https://download.gluster.org/pub/gluster/glusterfs/nightly/sources/ is taking
8G, and seems unused and no longer up to date.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1719388] infra: download.gluster.org /var/www/html/... is out of free space

2019-06-13 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1719388

M. Scherer  changed:

   What|Removed |Added

 CC||msche...@redhat.com



--- Comment #1 from M. Scherer  ---
Fixed, I have added 2G (only 5G free without more commands). 
I will now see if there is some missing cleanup, and why I got no nagios alert
for that metrics :/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1711950] Account in download.gluster.org to upload the build packages

2019-06-13 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1711950

M. Scherer  changed:

   What|Removed |Added

  Flags|needinfo?(sankarshan@redhat |
   |.com)   |



--- Comment #6 from M. Scherer  ---
Yup, but clearly, as long as someone was doing the job manually, this was set
as a lesser priority than a lot of things (like fixing the fires all over the
place). The increasing backlog of tasks do not make me think we can do it
without someone taking ownership of that, and as you rightfully point, that's
something we all want since more than 2 years :/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1711950] Account in download.gluster.org to upload the build packages

2019-06-13 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1711950

Kaleb KEITHLEY  changed:

   What|Removed |Added

 CC||sankars...@redhat.com
  Flags||needinfo?(sankarshan@redhat
   ||.com)



--- Comment #5 from Kaleb KEITHLEY  ---
(In reply to M. Scherer from comment #2)
> Ok so before opening a account, I would like to discuss the plan for
> automating that.
> I kinda feel unease of the fact we are still doing everything manually
> (especially after the nfs ganesha issue that we found internally), and while
> I do not have personnaly the ressources nor time to automate (was on TODO
> list, but after Nigel departure and the migration to AWS, this was pushed
> down the line), I would like to take on this opportunity to first discuss
> that, and then open the account. 
> 
> In that order, because experience show that the reverse order is not
> consecutive of any action (curiously, folks listen to me more when they wait
> on me for something, so I hope folks will excuse me for that obvious
> blackmail, but ot should be quick).
> 
> So, how long would it take to automate the release from Jenkins to
> download.gluster, and who would be dedicated on it on the gluster side ?
> (once we agree on a deadline, I will create a account that expire
> automatically after that time, just to make sure we do not leave a gapping
> hole open)

You, NIgel, and I had a discussion in Berlin over two years ago about this and
Nigel was supposed to automate it in Jenkins.

Someone like Sankarshan will have to identify a resource for doing the work
now.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1711950] Account in download.gluster.org to upload the build packages

2019-06-13 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1711950

M. Scherer  changed:

   What|Removed |Added

  Flags|needinfo?(mscherer@redhat.c |
   |om) |



--- Comment #4 from M. Scherer  ---
Sure give me a deadline, and I will create the account. I mean, I do not even
need a precise one.

Would you agree on "We do in 3 months", in which case I create the account
right now (with expiration as set).

(I need a public ssh key and a username)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1711950] Account in download.gluster.org to upload the build packages

2019-06-13 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1711950

Shwetha K Acharya  changed:

   What|Removed |Added

  Flags|needinfo?(sacharya@redhat.c |needinfo?(mscherer@redhat.c
   |om) |om)



--- Comment #3 from Shwetha K Acharya  ---
Hi Misc,

We have built the debian packages for glusterfs 6.2, and waiting for the
creation of accounts to upload the packages. Here,
https://github.com/gluster/glusterfs/issues/683 is a github issue, asking
reasons for delay on the same. It will be helpful if we are unblocked by this
soon. Can you do the needful?

About automating the procedure, I will initiate a discussion with the team, and
get back to you.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


<    1   2   3   4   5   6   7   8   9   10   >