thecodeteam / vagrant

All {code] by Dell EMC related Vagrant projects

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Error installing REX-ray for scaleio caused by line ending

devulrix opened this issue · comments

Vagrant: 1.9.1
VirtualBox: 5.1.14
Windows 10

Starting the vagrant scaleio file I get the error below.

If you check out the files on Windows the git default behavior is to convert all line endings into Windows(CRLF) format. As the rexray.sh file is executed under linux the line endings should be in LF. If I change the line ending into LF the installation works.

==> tb: Installing REX-Ray
==> tb: curl: (6) Could not resolve host: <head><title>400; Name or service not known
==> tb: curl: (6) Could not resolve host: Bad; Name or service not known
==> tb: curl: (6) Could not resolve host: Request<; Name or service not known
==> tb: curl: (6) Could not resolve host: <center><h1>400; Name or service not known
==> tb: curl: (6) Could not resolve host: Bad; Name or service not known
==> tb: curl: (6) Could not resolve host: Request<; Name or service not known
==> tb: curl: (6) Could not resolve host: <hr><center>nginx<; Name or service not known
==> tb: curl: (6) Could not resolve host: <; Unknown error
==> tb: curl: (6) Could not resolve host: <; Name or service not known
==> tb: <html>
==> tb: <head><title>400 Bad Request</title></head>
==> tb: <body bgcolor="white">
==> tb: <center><h1>400 Bad Request</h1></center>
==> tb: <hr><center>nginx</center>
==> tb: </body>
==> tb: </html>
==> tb: curl: (6) Could not resolve host: <head><title>400; Name or service not known
==> tb: curl: (6) Could not resolve host: Bad; Name or service not known
==> tb: curl: (6) Could not resolve host: Request<; Name or service not known
==> tb: curl: (6) Could not resolve host: <center><h1>400; Name or service not known
==> tb: curl: (6) Could not resolve host: Bad; Name or service not known
==> tb: curl: (6) Could not resolve host: Request<; Name or service not known
==> tb: curl: (6) Could not resolve host: <hr><center>nginx<; Name or service not known
==> tb: curl: (6) Could not resolve host: <; Name or service not known
==> tb: curl: (6) Could not resolve host: <; Name or service not known
==> tb: curl: (6) Could not resolve host: <head><title>400; Name or service not known
==> tb: curl: (6) Could not resolve host: Bad; Name or service not known
==> tb: curl: (6) Could not resolve host: Request<; Name or service not known
==> tb: curl: (6) Could not resolve host: <center><h1>400; Name or service not known
==> tb: curl: (6) Could not resolve host: Bad; Name or service not known
==> tb: curl: (6) Could not resolve host: Request<; Name or service not known
==> tb: curl: (6) Could not resolve host: <hr><center>nginx<; Name or service not known
==> tb: curl: (6) Could not resolve host: <; Name or service not known
==> tb: curl: (6) Could not resolve host: <; Name or service not known
==> tb: /vagrant/scripts/rexray.sh: line 24: warning: here-document at line 2 delimited by end-of-file (wanted `EOF')

@devulrix I'm not that familiar with windows. Can you suggest a fix? Or help me understand what needs to be changed

@kacole2 I'm note a Windows expert myself. I think it could be fixed with a .gitattributes file. If you put in:

# force LF line endings on checkout for windows.
*.sh eol=lf

Have a look at https://help.github.com/articles/dealing-with-line-endings/ for more details.

@kacole2 I'll run a test, if it fixes the issue I'll send you a pull request.

@kacole2 #49 fixes the issue for me.