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

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

M. Scherer  changed:

   What|Removed |Added

 CC||msche...@redhat.com



--- Comment #1 from M. Scherer  ---
I suspect option 2 is not what we want. 

But yeah, nagios do handle this quite well, doing notification, etc, etc. But
would still need to do the basic script that do the API call anyway, the
difference would be between "send a email", or "do a api call to nagios to
trigger a alert", and I think we could switch between thel quite easily if
needed.

-- 
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 1665889] New: Too small restriction for commit topic length in review.gluster.org

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

Bug ID: 1665889
   Summary: Too small restriction for commit topic length in
review.gluster.org
   Product: GlusterFS
   Version: mainline
  Hardware: All
OS: All
Status: NEW
 Component: project-infrastructure
  Severity: high
  Assignee: b...@gluster.org
  Reporter: vpono...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org
  Target Milestone: ---
Classification: Community



Description of the problem:
We, OCS QE automation team, have goal to port our downstream project [1] to the
upstream [2]. And we are unable to do it, because new repo [2] has limitation
to the length of a commit topic as 50 symbols. In our downstream project we
followed 72 symbols length. So, need to make it be 72 symbols.

[1] http://git.app.eng.bos.redhat.com/git/cns-qe/cns-automation.git/
[2] https://github.com/gluster/glusterfs-containers-tests

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

How reproducible: 100%

Steps to Reproduce:
1. Create commit
2. Push it to the gerrit ->
https://review.gluster.org/#/q/project:glusterfs-containers-tests

Actual results:
Response from server:
remote: (W) efd7f6f: commit subject >50 characters; use shorter first paragraph

Expected results:
Success after attempt to push code.

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 1665889] Too small restriction for commit topic length in review.gluster.org

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

Nigel Babu  changed:

   What|Removed |Added

 Status|NEW |MODIFIED
 CC||nig...@redhat.com
   Assignee|b...@gluster.org|nig...@redhat.com



--- Comment #1 from Nigel Babu  ---
Ack. This needs a gerrit config change and a restart. I'm going to do that 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 1665889] Too small restriction for commit topic length in review.gluster.org

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

Nigel Babu  changed:

   What|Removed |Added

 Status|MODIFIED|CLOSED
 Resolution|--- |CURRENTRELEASE
Last Closed||2019-01-14 11:42:59



--- Comment #2 from Nigel Babu  ---
This still lead to some permission troubles around pushing merge commits that
did not go away despite granting merge permissions. I did the push instead and
that has 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 1658146] BZ incorrectly updated with "patch posted" message when a patch is merged

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

Nigel Babu  changed:

   What|Removed |Added

 Status|ASSIGNED|CLOSED
 Resolution|--- |CURRENTRELEASE
Last Closed||2019-01-14 14:49:42



--- Comment #3 from Nigel Babu  ---
This is now fixed.

-- 
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