Closed
Description
When wgetting to this address during the installation process, this just fails silently. Turns out the issue is that if you take a raw kube.vmdk and curl that address you get a TLS error. I've fixed it by changing https://bootstrap.saltstack.com to http://bootstrap.saltstack.com, but obviously that's more risky.
Metadata
Metadata
Assignees
Labels
No labels
Activity
jbeda commentedon Nov 11, 2014
Related (filed after an email exchange around wget) saltstack/salt-bootstrap#491
I don't have easy access to the vSphere kube.vmdk so I can't verify how it relates to my debian install.
benjsmi commentedon Nov 11, 2014
Yes, that is exactly the error I was experiencing.
jbeda commentedon Nov 11, 2014
@programsam Does curl work? Or is it busted too?
pietern commentedon Nov 11, 2014
Curl is not installed on the image by default. I'm building a new image based on Debian 7.7 where I pull in curl by default, so we can switch to using that everywhere (instead of an awkward mix of wget and curl).
pietern commentedon Nov 12, 2014
Thanks for reporting this @programsam, I hadn't seen this yet. I uploaded a new VMDK that includes curl and updated the deployment scripts to use curl. I verified that deployment works again for me.
Use curl exclusively in vSphere deployment
benjsmi commentedon Nov 12, 2014
I can confirm that this works now with latest build from master on ESX. Probably still won't work with v0.4.3 (even w new image) since the scripts still used wget back then.
jbeda commentedon Nov 12, 2014
We are probably going to fork for v0.5 soon. But I can backport if this
trips folks up.
sent from tiny keyboard
On Nov 12, 2014 9:09 AM, "Ben Smith" notifications@github.com wrote: