https://bugzilla.redhat.com/show_bug.cgi?id=1685813
--- Comment #3 from Mohit Agrawal ---
Thanks, Michael there is some issue in my patch.
I will upload a new patch.
You can close the bugzilla.
Thanks,
Mohit Agrawal
--
You are receiving this mail because:
You are on the CC list for the bug.
Yes, Mohit is looking into it. There's some issue in the patch itself.
I forgot to link the bug filed for this:
https://bugzilla.redhat.com/show_bug.cgi?id=1685813
On Wed, Mar 6, 2019 at 5:54 PM Sankarshan Mukhopadhyay <
sankarshan.mukhopadh...@gmail.com> wrote:
> On Wed, Mar 6, 2019 at 5:38 PM
https://bugzilla.redhat.com/show_bug.cgi?id=1685813
--- Comment #2 from M. Scherer ---
I did reboot the broken builders and they are back. And I also looked at the
patch, but didn't found something, so I suspect there is some logic that escape
me.
--
You are receiving this mail because:
You
https://bugzilla.redhat.com/show_bug.cgi?id=1685576
M. Scherer changed:
What|Removed |Added
Flags|needinfo?(mscherer@redhat.c |
|om)
https://bugzilla.redhat.com/show_bug.cgi?id=1685813
M. Scherer changed:
What|Removed |Added
CC||msche...@redhat.com
--- Comment #1 from
https://bugzilla.redhat.com/show_bug.cgi?id=1686034
Bug ID: 1686034
Summary: Request access to docker hub gluster organisation.
Product: GlusterFS
Version: experimental
Status: NEW
Component: project-infrastructure
https://bugzilla.redhat.com/show_bug.cgi?id=1686034
--- Comment #3 from M. Scherer ---
Nope, we do not allow direct push (or shouldn't). If you want a new image
there, you have to explain what it is, why it should be there, etc, etc. And
automate the push, for example, using a jenkins job. See
https://bugzilla.redhat.com/show_bug.cgi?id=1686034
--- Comment #2 from Sridhar Seshasayee ---
I have built a docker image locally and pushed it to my repository on docker
hub with user ID: sseshasa.
However, I need to push the same image under the gluster organisation on docker
hub
https://bugzilla.redhat.com/show_bug.cgi?id=1686034
M. Scherer changed:
What|Removed |Added
CC||msche...@redhat.com
--- Comment #1 from
Le mercredi 06 mars 2019 à 17:53 +0530, Sankarshan Mukhopadhyay a
écrit :
> On Wed, Mar 6, 2019 at 5:38 PM Deepshikha Khandelwal
> wrote:
> >
> > Hello,
> >
> > Today while debugging the centos7-regression failed builds I saw
> > most of the builders did not pass the instance status check on
On Wed, Mar 6, 2019 at 8:47 PM Michael Scherer wrote:
>
> Le mercredi 06 mars 2019 à 17:53 +0530, Sankarshan Mukhopadhyay a
> écrit :
> > On Wed, Mar 6, 2019 at 5:38 PM Deepshikha Khandelwal
> > wrote:
> > >
> > > Hello,
> > >
> > > Today while debugging the centos7-regression failed builds I
Le mercredi 06 mars 2019 à 21:31 +0530, Sankarshan Mukhopadhyay a
écrit :
> On Wed, Mar 6, 2019 at 8:47 PM Michael Scherer
> wrote:
> >
> > Le mercredi 06 mars 2019 à 17:53 +0530, Sankarshan Mukhopadhyay a
> > écrit :
> > > On Wed, Mar 6, 2019 at 5:38 PM Deepshikha Khandelwal
> > > wrote:
> > >
https://bugzilla.redhat.com/show_bug.cgi?id=1685576
--- Comment #4 from Rohan CJ ---
It's working 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://bugzilla.redhat.com/show_bug.cgi?id=1686034
--- Comment #4 from Sridhar Seshasayee ---
Okay, thanks for the info and pointers. I will work with one of the developers
and get this done. This issue may be closed.
--
You are receiving this mail because:
You are on the CC list for the
14 matches
Mail list logo
