Omnitruck API Question


#1

I’m troubleshooting some test-kitchen on Windows failures and I’m noticing that chef is not getting installed onto the node. After some troubleshooting It looks like the omnitruck API may not be returning results for Chef 11 on Windows, but I’ve never looked into the omnitruck API before so I’m not sure if this is a red herring or not. I’m hoping if someone can tell me if this first curl should yield a 200 or not (I suspect it should)

➜  ~ curl -i "https://www.chef.io/chef/metadata?p=windows&m=x86_64&pv=2008r2&v=11"   
HTTP/1.1 404 Not Found
Content-Type: text/html;charset=utf-8
Server: nginx/1.4.6 (Ubuntu)
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Length: 0
Accept-Ranges: bytes
Date: Wed, 16 Mar 2016 01:18:52 GMT
Via: 1.1 varnish
Age: 91
Connection: keep-alive
X-Served-By: cache-sjc3122-SJC
X-Cache: HIT
X-Cache-Hits: 1
Vary: Accept-Encoding
Strict-Transport-Security: max-age= 7776000; includeSubDomains
X-Frame-Options: SAMEORIGIN

➜  ~ curl -i "https://www.chef.io/chef/metadata?p=windows&m=x86_64&pv=2008r2&v=12"
HTTP/1.1 200 OK
Cache-Control: max-age=300, public
Content-Type: text/html;charset=utf-8
Expires: Wed, 16 Mar 2016 01:22:28 GMT
Server: nginx/1.4.6 (Ubuntu)
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Content-Length: 228
Accept-Ranges: bytes
Date: Wed, 16 Mar 2016 01:19:02 GMT
Via: 1.1 varnish
Age: 94
Connection: keep-alive
X-Served-By: cache-sjc3125-SJC
X-Cache: HIT
X-Cache-Hits: 1
Vary: Accept-Encoding
Strict-Transport-Security: max-age= 7776000; includeSubDomains
X-Frame-Options: SAMEORIGIN

url	https://opscode-omnibus-packages.s3.amazonaws.com/windows/2012r2/x86_64/chef-client-12.8.1-1-x64.msi
md5	cf356a44978254a3629e3f4e7a2ff9a0
sha256	05aa2cd84842dcfa51ad1bbbf1f7fe54102a46bee11d4e0819561f88b284fec4
version	12.8.1%  

Thanks


Incoming Updates to Windows 64-bit Build Availability
#2

curl -i "https://www.chef.io/chef/metadata?p=windows&m=i386&pv=2008r2&v=11" works (32bit arch). We didn’t make 64bit builds back then, we’re starting to now.

I think we broke some backwards compatibility though. We’re discussing what to do about that now.


#3

We’ve reverted the changes to Omnitruck from the last day. Everything should be back to normal now.


#4

Looks good, thanks for the fix.