Install using apt-get fails about liberica

[den1ska]

@jujoramos
Hi Juan,
Could you please provide the output of the following commands:

curl -fSsL https://apt.bell-sw.com/dists/stable/Release | grep Date
curl -fSsL https://apt.bell-sw.com/dists/stable/InRelease | grep Date

It should be exactly like that

Date: Fri, 22 Jan 2021 13:38:03 GMT

If not, then probably there might be an intermediary cache in between your workstation and our CDN provider which keeps the metadata a bit outdated.

[jujoramos]

Hey @den1ska,

Thanks for your reply. I've executed the commands and the second Date doesn't seem correct:

curl -fSsL https://apt.bell-sw.com/dists/stable/Release | grep Date
Date: Fri, 22 Jan 2021 13:38:03 GMT

curl -fSsL https://apt.bell-sw.com/dists/stable/InRelease | grep Date
Date: Fri, 06 Nov 2020 10:18:19 GMT

If not, then probably there might be an intermediary cache in between your workstation and our CDN provider which keeps the metadata a bit outdated.

No idea regarding how to do that at the moment, will investigate a little bit, thanks again!.

[jujoramos]

Another weird thing I'm noticing is that the curl command returns fine when ran from my laptop terminal, but it returns the old Date when ran from within the ubuntu:bionic docker container...

Terminal
➜  jramos:~$ curl -fSsL https://apt.bell-sw.com/dists/stable/InRelease | grep Date
Date: Fri, 22 Jan 2021 13:38:03 GMT

Docker Container
root@42e62d507481:/# curl -fSsL https://apt.bell-sw.com/dists/stable/InRelease | grep Date
Date: Fri, 06 Nov 2020 10:18:19 GMT

I'm closing this issue as it seems entirely related to my environment but, if you have any pointers about how can I solve, please let me know 👍 .
Thanks!.

[den1ska]

@jujoramos
Hmm, this is really weird. Can you please share the output of

curl --head https://apt.bell-sw.com/dists/stable/InRelease

run from both your terminal and docker container?

[jujoramos]

Sure @den1ska !.
Below are the outputs:

##### TERMINAL
➜  jramos:~$ curl --head https://apt.bell-sw.com/dists/stable/InRelease

HTTP/2 200 
date: Fri, 26 Feb 2021 11:23:05 GMT
content-type: text/plain; charset=UTF-8
content-length: 4160
set-cookie: __cfduid=dd4a987296c945b66e626bb0d0365f6401614338585; expires=Sun, 28-Mar-21 11:23:05 GMT; path=/; domain=.bell-sw.com; HttpOnly; SameSite=Lax
x-content-type-options: nosniff
content-security-policy: sandbox allow-forms allow-modals allow-popups allow-presentation allow-scripts allow-top-navigation
x-xss-protection: 1; mode=block
last-modified: Fri, 22 Jan 2021 13:38:04 GMT
cache-control: public, max-age=2592000
cf-cache-status: HIT
age: 1823405
expires: Sun, 28 Mar 2021 11:23:05 GMT
accept-ranges: bytes
cf-request-id: 087fad0ba90000a6f9292e6000000001
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 62794abf7eb5a6f9-DUB


##### DOCKER CONTAINER (started with docker run -it --rm ubuntu:bionic)
root@9f897a409f01:/#  curl --head https://apt.bell-sw.com/dists/stable/InRelease

HTTP/2 200 
date: Fri, 26 Feb 2021 11:24:58 GMT
content-type: text/plain; charset=UTF-8
content-length: 4154
set-cookie: __cfduid=dc497786aae1665bbd3c58849f18ac5531614338698; expires=Sun, 28-Mar-21 11:24:58 GMT; path=/; domain=.bell-sw.com; HttpOnly; SameSite=Lax
x-content-type-options: nosniff
content-security-policy: sandbox allow-forms allow-modals allow-popups allow-presentation allow-scripts allow-top-navigation
x-xss-protection: 1; mode=block
last-modified: Fri, 06 Nov 2020 10:18:20 GMT
cache-control: public, max-age=2592000
cf-cache-status: HIT
age: 6667058
expires: Sun, 28 Mar 2021 11:24:58 GMT
accept-ranges: bytes
cf-request-id: 087faec5b900002cbf2631f000000001
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 62794d82cc6a2cbf-LHR

[jujoramos]

Okay, I don't know if you did something on your end (please let me know if you did so we know what to do if it happens again in the future) but it's working just fine now, even though I haven't changed anything 🤔 .
Again, thanks a lot for your help!!.

[den1ska]

Yes, actually we've just done a few actions. ;)
Thank you a lot for helping us to diagnose this issue. As it turned out, one of the CDN edges had a stale cache. We fixed this.

[jujoramos]

Nice!!, and thanks again for the quick help!! 👍