[automated-testing] CentOS-CI not pulling latest patches committed to glusto resulting in build failure

Nigel Babu nigelb at redhat.com
Tue Jan 8 09:13:32 UTC 2019

Hi Kshithij,

This is not an environment where we can control such variables,
unfortunately. We have to work with what we have. The environment gets
wiped every time. Even with your solution, I doubt it helps, because it
will still need an /etc/hosts entry. At which point whether there's a
hyphen or no hyphen doesn't matter. We could add what we wanted.

On Mon, Jan 7, 2019 at 8:16 PM Kshithij Iyer <kiyer at redhat.com> wrote:

> Hi Nigel,
> Thank you for the advise.
> However I have observed that there is one other issue with CentOS-CI or
> the Jenkins job(Not sure of what is wrong!), the domain names are not
> properly configured which leads to [1]. '*hostname -s*' is the command
> which is used to fetch network short names, however while running it on
> CentOS-CI it returns only *n16* instead of returning *n16.dusty. *This
> happens because *`hostname -s`* splits the hostname till the first *.
> (dot) *due to which it only returns a part of the actual network short
> name which causes the peer probe to fail with "*peer probe: failed: Probe
> returned with Transport endpoint is not connected" *error*.* The solution
> to this problem could be to configure the domain name such that *`hostname
> -s` *returns *n16-dusty *instead of *n16.dusty *by replacing the *.(dot) *with
> a
> *-(dash). *[1]:
> https://ci.centos.org/job/gluster_glusto-patch-check/1058/artifact/glustomain.log
> Thanks,
> Kshithij Iyer
> Gluster QE Intern
> On Mon, Jan 7, 2019 at 9:16 AM Nigel Babu <nigelb at redhat.com> wrote:
>> Hi Kshithij,
>> Let me restate the problem. Please correct me if I'm wrong. You have two
>> patches[1], [2] that are not passing Centos CI at the moment. Both your
>> patches are failing because you do not have Nag's fixes for peer detach[3].
>> It's not the CI's job to rebase your patch. You have to rebase your patch.
>> You can either do that manually with the git cli or you can use the rebase
>> button on Gerrit.
>> To verify it has worked correctly, after you rebase, look for the
>> "Parent(s)" line on Gerrit, click on "(cgit)" after the commit hash, which
>> will take you to the parent for your change. Make sure your parent is newer
>> than Nag's fix. Then retrigger Centos-CI and it should run with your fixes.
>> This is a mailing list. Please subscribe to the list on lists.gluster.org
>> before sending an email or you will be stuck in moderation.
>> [1]: https://review.gluster.org/#/c/glusto-tests/+/21862/
>> [2]: https://review.gluster.org/#/c/glusto-tests/+/21932/
>> [3]: https://review.gluster.org/#/c/glusto-tests/+/21983/
>> On Mon, Jan 7, 2019 at 8:54 AM Kshithij Iyer <kiyer at redhat.com> wrote:
>>> Hello,
>>> I have been trying to verify 2 of my patches through CentOS-CI and have
>>> faced issues where CentOS-CI is not being able to fetch the latest patches
>>> committed to glusto. The patch went in peer_detach() so all the testcases
>>> which use them might fail to verify. Have attached the links to the logs
>>> below. Please have a look at it.
>>> [ 1 ]
>>> https://ci.centos.org/job/gluster_glusto-patch-check/1055/artifact/glustomain.log
>>> [ 2 ]
>>> https://ci.centos.org/job/gluster_glusto-patch-check/1054/artifact/glustomain.log
>>> Thanks,
>>> Kshithij Iyer
>>> Gluster QE Intern
>>> _______________________________________________
>>> automated-testing mailing list
>>> automated-testing at gluster.org
>>> https://lists.gluster.org/mailman/listinfo/automated-testing
>> --
>> nigelb

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/automated-testing/attachments/20190108/8aca2101/attachment-0001.html>

More information about the automated-testing mailing list