| Message ID | 20170508045715.21770-4-f4bug@amsat.org (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
Philippe Mathieu-Daudé <f4bug@amsat.org> writes: > shippable logs: > -------------- > git_sync > - ssh-agent bash -c 'ssh-add /tmp/ssh/01_deploy; git clone https://github.com/philmd/qemu.git /root/src/github.com/philmd/qemu' > Identity added: /tmp/ssh/01_deploy (rsa w/o comment) > Cloning into '/root/src/github.com/philmd/qemu'... > fatal: unable to access 'https://github.com/philmd/qemu.git/': Problem with the SSL CA cert (path? access rights?) > retrying 1 of 3 times... I've not seen this before but which git_sync stage is it. The host or the container? If it is the container that probably just means we are missing the CA Cert package. > > Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org> > --- > .shippable.yml | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/.shippable.yml b/.shippable.yml > index 5170486ff9..b661e667b3 100644 > --- a/.shippable.yml > +++ b/.shippable.yml > @@ -2,6 +2,10 @@ language: c > env: > global: > - LC_ALL=C > + # sometimes Shippable fails to clone from github (git_sync stage): > + # "Problem with the SSL CA cert (path? access rights?)" > + # for now disable SSL verification. > + - GIT_SSL_NO_VERIFY=1 > matrix: > - IMAGE=debian-armhf-cross > TARGET_LIST=arm-softmmu,arm-linux-user -- Alex Bennée
Hi Alex, On 05/08/2017 07:58 AM, Alex Bennée wrote: > > Philippe Mathieu-Daudé <f4bug@amsat.org> writes: > >> shippable logs: >> -------------- >> git_sync >> - ssh-agent bash -c 'ssh-add /tmp/ssh/01_deploy; git clone https://github.com/philmd/qemu.git /root/src/github.com/philmd/qemu' >> Identity added: /tmp/ssh/01_deploy (rsa w/o comment) >> Cloning into '/root/src/github.com/philmd/qemu'... >> fatal: unable to access 'https://github.com/philmd/qemu.git/': Problem with the SSL CA cert (path? access rights?) >> retrying 1 of 3 times... > > I've not seen this before but which git_sync stage is it. The host or > the container? If it is the container that probably just means we are > missing the CA Cert package. You are right! Adding the ca-certificates package in the docker image solves this issue I had in container's git_sync stage :) Thank for the review, Phil. > >> >> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org> >> --- >> .shippable.yml | 4 ++++ >> 1 file changed, 4 insertions(+) >> >> diff --git a/.shippable.yml b/.shippable.yml >> index 5170486ff9..b661e667b3 100644 >> --- a/.shippable.yml >> +++ b/.shippable.yml >> @@ -2,6 +2,10 @@ language: c >> env: >> global: >> - LC_ALL=C >> + # sometimes Shippable fails to clone from github (git_sync stage): >> + # "Problem with the SSL CA cert (path? access rights?)" >> + # for now disable SSL verification. >> + - GIT_SSL_NO_VERIFY=1 >> matrix: >> - IMAGE=debian-armhf-cross >> TARGET_LIST=arm-softmmu,arm-linux-user > > > -- > Alex Bennée >
diff --git a/.shippable.yml b/.shippable.yml index 5170486ff9..b661e667b3 100644 --- a/.shippable.yml +++ b/.shippable.yml @@ -2,6 +2,10 @@ language: c env: global: - LC_ALL=C + # sometimes Shippable fails to clone from github (git_sync stage): + # "Problem with the SSL CA cert (path? access rights?)" + # for now disable SSL verification. + - GIT_SSL_NO_VERIFY=1 matrix: - IMAGE=debian-armhf-cross TARGET_LIST=arm-softmmu,arm-linux-user
shippable logs: -------------- git_sync - ssh-agent bash -c 'ssh-add /tmp/ssh/01_deploy; git clone https://github.com/philmd/qemu.git /root/src/github.com/philmd/qemu' Identity added: /tmp/ssh/01_deploy (rsa w/o comment) Cloning into '/root/src/github.com/philmd/qemu'... fatal: unable to access 'https://github.com/philmd/qemu.git/': Problem with the SSL CA cert (path? access rights?) retrying 1 of 3 times... Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org> --- .shippable.yml | 4 ++++ 1 file changed, 4 insertions(+)