Unable to provision DigitalOcean server.

[jameswlane]

I been putting together my presentation for WordCamp. I was trying to provision the server and I seem to be having issues.

First I tried to provision the staging and production

Staging:

Jamess-MacBook-Pro-2 in ~/GitHub/jwl-wc.co ± |master ✓| → cap staging genesis:provision -S user=root -S password=XXXX triggering load callbacks

• 2014-06-08 23:42:44 executing staging' triggering start callbacks forgenesis:provision'
• 2014-06-08 23:42:44 executing `multistage:ensure'
• 2014-06-08 23:42:44 executing `genesis:provision'
• executing "mkdir -p /tmp/jwl-wc.co.2014-06-08.234244 /tmp/jwl-wc.co.2014-06-08.234244/bower_components/genesis-wordpress" servers: ["staging.jwl-wc.co"]

* Unable to provision as "root"! * Try running: $ cap staging genesis:provision -S user=... -S password=...

Production:

Jamess-MacBook-Pro-2 in ~/GitHub/jwl-wc.co ± |master ✗| → cap production genesis:provision -S user=root -S password=XXXX triggering load callbacks

• 2014-06-08 23:44:11 executing production' triggering start callbacks forgenesis:provision'
• 2014-06-08 23:44:11 executing `multistage:ensure'
• 2014-06-08 23:44:11 executing `genesis:provision'
• executing "mkdir -p /tmp/jwl-wc.co.2014-06-08.234411 /tmp/jwl-wc.co.2014-06-08.234411/bower_components/genesis-wordpress" servers: ["production.jwl-wc.co"]

* Unable to provision as "root"! * Try running: $ cap production genesis:provision -S user=... -S password=...

So I figured I would test to make sure I can log into the server and the login and pass are correct.

Staging:

Jamess-MacBook-Pro-2 in ~/GitHub/jwl-wc.co ± |master ✗| → ssh root@staging.jwl-wc.co root@staging.jwl-wc.co's password: Welcome to Ubuntu 12.04.4 LTS (GNU/Linux 3.8.0-29-generic x86_64)

• Documentation: https://help.ubuntu.com/

  System information as of Mon Jun 9 01:04:55 EDT 2014

  System load: 0.0 Processes: 65 Usage of /: 5.2% of 19.56GB Users logged in: 0 Memory usage: 10% IP address for eth0: 107.170.60.243 Swap usage: 0%

  Graph this data and manage this system at: https://landscape.canonical.com/

root@staging:~# ls root@staging:~# exit logout Connection to staging.jwl-wc.co closed.

Production:

Jamess-MacBook-Pro-2 in ~/GitHub/jwl-wc.co ± |master ✗| → ssh root@production.jwl-wc.co root@production.jwl-wc.co's password: Welcome to Ubuntu 12.04.4 LTS (GNU/Linux 3.8.0-29-generic x86_64)

• Documentation: https://help.ubuntu.com/

  System information as of Mon Jun 9 01:03:55 EDT 2014

  System load: 0.0 Processes: 65 Usage of /: 5.2% of 19.56GB Users logged in: 0 Memory usage: 10% IP address for eth0: 107.170.165.157 Swap usage: 0%

  Graph this data and manage this system at: https://landscape.canonical.com/

root@jwl-wc:~# ls root@jwl-wc:~# exit logout Connection to production.jwl-wc.co closed.

So I added the id_rsa.pub key to the servers so I wouldn't have to provision it with a login and pass and same thing.

Staging:

Jamess-MacBook-Pro-2 in ~/GitHub/jwl-wc.co ± |master ✗| → cap staging genesis:provision triggering load callbacks

• 2014-06-09 00:10:16 executing staging' triggering start callbacks forgenesis:provision'
• 2014-06-09 00:10:16 executing `multistage:ensure'
• 2014-06-09 00:10:16 executing `genesis:provision'
• executing "mkdir -p /tmp/jwl-wc.co.2014-06-09.001016 /tmp/jwl-wc.co.2014-06-09.001016/bower_components/genesis-wordpress" servers: ["staging.jwl-wc.co"]

* Unable to provision as "deploy"! * Try running: $ cap staging genesis:provision -S user=... -S password=...

Production:

Jamess-MacBook-Pro-2 in ~/GitHub/jwl-wc.co ± |master ✗| → cap production genesis:provision triggering load callbacks

• 2014-06-09 00:13:52 executing production' triggering start callbacks forgenesis:provision'
• 2014-06-09 00:13:52 executing `multistage:ensure'
• 2014-06-09 00:13:52 executing `genesis:provision'
• executing "mkdir -p /tmp/jwl-wc.co.2014-06-09.001352 /tmp/jwl-wc.co.2014-06-09.001352/bower_components/genesis-wordpress" servers: ["production.jwl-wc.co"]

* Unable to provision as "deploy"! * Try running: $ cap production genesis:provision -S user=... -S password=...

Have you guy ran into this and what's a good work around?

[ericclemmons]

We're working on resolving this now with another release of v0.2 and the upcoming v1