Re: No access to git.haproxy.org from Travis CI
Hi Bjoern, On Wed, Aug 12, 2020 at 06:52:05PM +0200, bjun...@gmail.com wrote: > Am Sa., 13. Juni 2020 um 22:15 Uhr schrieb Willy Tarreau : > > > Hi William, > > > > On Sat, Jun 13, 2020 at 03:13:06PM +0200, William Dauchy wrote: > > > Hi, > > > > > > On Thu, Jun 11, 2020 at 1:10 PM Willy Tarreau wrote: > > > > Sure but what I wanted to say was that travis seems to be the only > > > > point experiencing such difficulties and we don't know how it works > > > > nor what are the rules in place. > > > > > > I don't know whether this is related to the issue described here but I > > just had: > > > > > > $ git pull --rebase > > > fatal: unable to access 'http://git.haproxy.org/git/haproxy.git/': The > > > requested URL returned error: 502 > > > $ git pull --rebase > > > error: The requested URL returned error: 502 (curl_result = 22, > > > http_code = 502, sha1 = f38175cf6ed4d02132e6b21cbf643f73be5ee000) > > > error: Unable to find f38175cf6ed4d02132e6b21cbf643f73be5ee000 under > > > http://git.haproxy.org/git/haproxy.git > > > Fetching objects: 4529, done. > > > Cannot obtain needed commit f38175cf6ed4d02132e6b21cbf643f73be5ee000 > > > while processing commit ff0e8a44a4c23ab36b6f67c4052777ac908d4211. > > > error: fetch failed. > > > > > > Third try was ok though :/ > > > > Thanks for the info, I'll have a look. However the issue reported about > > travis was a connection error, which likely indicates a routing issue. > > > > Cheers, > > Willy > > > > Hi, > > fyi, after 2 months and more than 20 emails Travis has fixed it. Ah, great, thanks for letting us know! Willy
Re: No access to git.haproxy.org from Travis CI
Am Sa., 13. Juni 2020 um 22:15 Uhr schrieb Willy Tarreau : > Hi William, > > On Sat, Jun 13, 2020 at 03:13:06PM +0200, William Dauchy wrote: > > Hi, > > > > On Thu, Jun 11, 2020 at 1:10 PM Willy Tarreau wrote: > > > Sure but what I wanted to say was that travis seems to be the only > > > point experiencing such difficulties and we don't know how it works > > > nor what are the rules in place. > > > > I don't know whether this is related to the issue described here but I > just had: > > > > $ git pull --rebase > > fatal: unable to access 'http://git.haproxy.org/git/haproxy.git/': The > > requested URL returned error: 502 > > $ git pull --rebase > > error: The requested URL returned error: 502 (curl_result = 22, > > http_code = 502, sha1 = f38175cf6ed4d02132e6b21cbf643f73be5ee000) > > error: Unable to find f38175cf6ed4d02132e6b21cbf643f73be5ee000 under > > http://git.haproxy.org/git/haproxy.git > > Fetching objects: 4529, done. > > Cannot obtain needed commit f38175cf6ed4d02132e6b21cbf643f73be5ee000 > > while processing commit ff0e8a44a4c23ab36b6f67c4052777ac908d4211. > > error: fetch failed. > > > > Third try was ok though :/ > > Thanks for the info, I'll have a look. However the issue reported about > travis was a connection error, which likely indicates a routing issue. > > Cheers, > Willy > Hi, fyi, after 2 months and more than 20 emails Travis has fixed it. Best regards / Mit freundlichen Grüßen Bjoern
Re: No access to git.haproxy.org from Travis CI
Hi William, On Sat, Jun 13, 2020 at 03:13:06PM +0200, William Dauchy wrote: > Hi, > > On Thu, Jun 11, 2020 at 1:10 PM Willy Tarreau wrote: > > Sure but what I wanted to say was that travis seems to be the only > > point experiencing such difficulties and we don't know how it works > > nor what are the rules in place. > > I don't know whether this is related to the issue described here but I just > had: > > $ git pull --rebase > fatal: unable to access 'http://git.haproxy.org/git/haproxy.git/': The > requested URL returned error: 502 > $ git pull --rebase > error: The requested URL returned error: 502 (curl_result = 22, > http_code = 502, sha1 = f38175cf6ed4d02132e6b21cbf643f73be5ee000) > error: Unable to find f38175cf6ed4d02132e6b21cbf643f73be5ee000 under > http://git.haproxy.org/git/haproxy.git > Fetching objects: 4529, done. > Cannot obtain needed commit f38175cf6ed4d02132e6b21cbf643f73be5ee000 > while processing commit ff0e8a44a4c23ab36b6f67c4052777ac908d4211. > error: fetch failed. > > Third try was ok though :/ Thanks for the info, I'll have a look. However the issue reported about travis was a connection error, which likely indicates a routing issue. Cheers, Willy
Re: No access to git.haproxy.org from Travis CI
Hi, On Thu, Jun 11, 2020 at 1:10 PM Willy Tarreau wrote: > Sure but what I wanted to say was that travis seems to be the only > point experiencing such difficulties and we don't know how it works > nor what are the rules in place. I don't know whether this is related to the issue described here but I just had: $ git pull --rebase fatal: unable to access 'http://git.haproxy.org/git/haproxy.git/': The requested URL returned error: 502 $ git pull --rebase error: The requested URL returned error: 502 (curl_result = 22, http_code = 502, sha1 = f38175cf6ed4d02132e6b21cbf643f73be5ee000) error: Unable to find f38175cf6ed4d02132e6b21cbf643f73be5ee000 under http://git.haproxy.org/git/haproxy.git Fetching objects: 4529, done. Cannot obtain needed commit f38175cf6ed4d02132e6b21cbf643f73be5ee000 while processing commit ff0e8a44a4c23ab36b6f67c4052777ac908d4211. error: fetch failed. Third try was ok though :/ -- William
Re: No access to git.haproxy.org from Travis CI
Am Do., 11. Juni 2020 um 15:00 Uhr schrieb Willy Tarreau :
> By the way if that helps I've re-added the records for
> {git,www}.haproxy.org. It will take one hour or so to propagate, but
> you'll be able to see if using IPv6 causes the same issue or not. I'd
> guess it would work better since the routes are likely different.
>
> Willy
>
Thanks for your effort Willy, but the travis vm's which are used for my
jobs do not support IPv6. I've informed travis about the issue, let's wait
and see.
Best regards / Mit freundlichen Grüßen
Bjoern
Re: No access to git.haproxy.org from Travis CI
By the way if that helps I've re-added the records for
{git,www}.haproxy.org. It will take one hour or so to propagate, but
you'll be able to see if using IPv6 causes the same issue or not. I'd
guess it would work better since the routes are likely different.
Willy
Re: No access to git.haproxy.org from Travis CI
On Thu, Jun 11, 2020 at 01:35:34PM +0200, bjun...@gmail.com wrote: > Hi, > > one more question. Now that i have to use the github mirror, how can i get > the latest changes of the 2.1 tree? (as possible with " > https://git.haproxy.org/git/haproxy-2.1.git/;). > > There is no branch or tag on github with which i can get the latest changes > of the 2.1 tree. No, we don't put the stable branches there because that confuses the issue tracker (e.g. close issues by accident for each backport). We've thought about creating an alternate repo like "haproxy-stable" in the past but never decided whether or not it was the best solution. So for now the stable branches are solely on haproxy.org. Maybe it would be useful to file an issue at Travis about this so that they can at least traceroute. It's a bit annoying to have no more info than "cannot connect" :-( Willy
Re: No access to git.haproxy.org from Travis CI
Hi, one more question. Now that i have to use the github mirror, how can i get the latest changes of the 2.1 tree? (as possible with " https://git.haproxy.org/git/haproxy-2.1.git/;). There is no branch or tag on github with which i can get the latest changes of the 2.1 tree. Best regards / Mit freundlichen Grüßen Bjoern Am Do., 11. Juni 2020 um 13:17 Uhr schrieb Willy Tarreau : > On Thu, Jun 11, 2020 at 01:09:37PM +0200, bjun...@gmail.com wrote: > > Hello Willy, > > > > just for clarity, it's not only port 80. I've looked at it, it's > > definitely some issue/blocking within the travis infrastructure, routing > > from GCE Cloud (us-east1) is fine. > > OK, that's good to know. > > Thanks, > Willy >
Re: No access to git.haproxy.org from Travis CI
On Thu, Jun 11, 2020 at 01:09:37PM +0200, bjun...@gmail.com wrote: > Hello Willy, > > just for clarity, it's not only port 80. I've looked at it, it's > definitely some issue/blocking within the travis infrastructure, routing > from GCE Cloud (us-east1) is fine. OK, that's good to know. Thanks, Willy
Re: No access to git.haproxy.org from Travis CI
Hello Willy, just for clarity, it's not only port 80. I've looked at it, it's definitely some issue/blocking within the travis infrastructure, routing from GCE Cloud (us-east1) is fine. Best regards / Mit freundlichen Grüßen Bjoern Am Do., 11. Juni 2020 um 12:23 Uhr schrieb Willy Tarreau : > On Thu, Jun 11, 2020 at 03:17:07PM +0500, ??? wrote: > > we had to change libslz url as well > > > > > https://github.com/haproxy/haproxy/commit/13dd45178e24504504a02d89d9a81d4b80c63c93#diff-354f30a63fb0907d4ad57269548329e3 > > Fine! > > > however, I did not investigate deeper (traceroute, etc, ...) > > And it really seems that only travis is affected, nobody else complains > apparently. The server there is the same as the one running the mailing > list and the one that's pushing to github, so I really doubt it would be > a routing issue, which is why I more likely suspect some filtering of > port 80 from within travis' infrastructure. > > Regards, > Willy >
Re: No access to git.haproxy.org from Travis CI
On Thu, Jun 11, 2020 at 04:06:52PM +0500, ??? wrote: > pushing to github is not related to Travis. Those are different clouds:) Sure but what I wanted to say was that travis seems to be the only point experiencing such difficulties and we don't know how it works nor what are the rules in place.
Re: No access to git.haproxy.org from Travis CI
pushing to github is not related to Travis. Those are different clouds:) On Thu, Jun 11, 2020, 3:23 PM Willy Tarreau wrote: > On Thu, Jun 11, 2020 at 03:17:07PM +0500, ??? wrote: > > we had to change libslz url as well > > > > > https://github.com/haproxy/haproxy/commit/13dd45178e24504504a02d89d9a81d4b80c63c93#diff-354f30a63fb0907d4ad57269548329e3 > > Fine! > > > however, I did not investigate deeper (traceroute, etc, ...) > > And it really seems that only travis is affected, nobody else complains > apparently. The server there is the same as the one running the mailing > list and the one that's pushing to github, so I really doubt it would be > a routing issue, which is why I more likely suspect some filtering of > port 80 from within travis' infrastructure. > > Regards, > Willy >
Re: No access to git.haproxy.org from Travis CI
On Thu, Jun 11, 2020 at 03:17:07PM +0500, ??? wrote: > we had to change libslz url as well > > https://github.com/haproxy/haproxy/commit/13dd45178e24504504a02d89d9a81d4b80c63c93#diff-354f30a63fb0907d4ad57269548329e3 Fine! > however, I did not investigate deeper (traceroute, etc, ...) And it really seems that only travis is affected, nobody else complains apparently. The server there is the same as the one running the mailing list and the one that's pushing to github, so I really doubt it would be a routing issue, which is why I more likely suspect some filtering of port 80 from within travis' infrastructure. Regards, Willy
Re: No access to git.haproxy.org from Travis CI
we had to change libslz url as well https://github.com/haproxy/haproxy/commit/13dd45178e24504504a02d89d9a81d4b80c63c93#diff-354f30a63fb0907d4ad57269548329e3 however, I did not investigate deeper (traceroute, etc, ...) чт, 11 июн. 2020 г. в 14:59, Tim Düsterhus : > Bjoern, > Willy, > > Am 11.06.20 um 11:24 schrieb bjun...@gmail.com: > > i have a Travis CI job that is pulling/cloning a repo from > git.haproxy.org, > > but unfortunately this isn't working anymore (i believe since May, 12). > > > > Output Travis CI job: > > > > [...] > > > > Is there any IP blocking or something else in place? > > > > See also: > https://github.com/haproxy/haproxy/issues/49#issuecomment-633521350 > > Best regards > Tim Düsterhus > >
Re: No access to git.haproxy.org from Travis CI
Bjoern, Willy, Am 11.06.20 um 11:24 schrieb bjun...@gmail.com: > i have a Travis CI job that is pulling/cloning a repo from git.haproxy.org, > but unfortunately this isn't working anymore (i believe since May, 12). > > Output Travis CI job: > > [...] > > Is there any IP blocking or something else in place? > See also: https://github.com/haproxy/haproxy/issues/49#issuecomment-633521350 Best regards Tim Düsterhus
