Chef Omnitruck Web Errors

I'm running into issues when updating Chef with the chef_client_updater cookbook.

From what I can tell, the Omnitruck website that gives package metadata is having issues:

root@ip-172-31-64-68:~# curl -IL "https://omnitruck.chef.io/stable/chef/metadata?v=latest&p=ubuntu&pv=18.04&m=x86_64"
HTTP/2 200
server: WEBrick/1.3.1 (Ruby/2.4.5/2018-10-18)
accept-ranges: bytes
date: Wed, 14 Aug 2019 15:42:04 GMT
via: 1.1 varnish
age: 2351
x-served-by: cache-sea1024-SEA
x-cache: HIT
x-cache-hits: 1
x-timer: S1565797325.743741,VS0,VE0
content-length: 0

root@ip-172-31-64-68:~# curl -L "https://omnitruck.chef.io/stable/chef/metadata?v=latest&p=ubuntu&pv=18.04&m=x86_64"

Normally this returns the package data so that it can be compared to what's installed (and then downloaded for an upgrade, if necessary).

But it's returning blank results. So I assume this is a server-side issue, but I just want to make sure.

i can see it

curl -L "https://omnitruck.chef.io/stable/chef/metadata?v=latest&p=ubuntu&pv=18.04&m=x86_64"

sha1 e477450abbebb6d3716b20ca0cf573f5039f67bb

sha256 87a68213c9440900bd750b871ea375dc46badb5d643a67c8c54cf7237963180b

url https://packages.chef.io/files/stable/chef/15.2.20/ubuntu/18.04/chef_15.2.20-1_amd64.deb

curl -IL "https://omnitruck.chef.io/stable/chef/metadata?v=latest&p=ubuntu&pv=18.04&m=x86_64"

HTTP/1.1 200 OK

Content-Type: text/html;charset=utf-8

Server: WEBrick/1.3.1 (Ruby/2.4.5/2018-10-18)

X-Content-Type-Options: nosniff

X-Frame-Options: SAMEORIGIN

X-Xss-Protection: 1; mode=block

Content-Length: 226

Accept-Ranges: bytes

Via: 1.1 varnish

Age: 31

Connection: keep-alive

X-Served-By: cache-scl19424-SCL

X-Cache: HIT

X-Cache-Hits: 1

X-Timer: S1565798472.660881,VS0,VE12

Yeah, it's working now. If someone fixed it, thanks! If not, go go automated recovery?

Hi Folks! Our Ops team is looking at the issues with omnitruck. Status updates via https://status.chef.io/incidents/6zw9ynmj5lfq?u=mhw2566vl4k8

thanks!

Thanks for the update! I didn't see anything on your statuspage when I first ran into this, so I figured this was an appropriate place to post. In the future, is there a more appropriate place to report issues like this, or is this fine?

in here is just fine. helps triangulate who's seeing what and where. :slight_smile: