Well I wiped the instance and added a new instance and tried it all again with the Ansible Playbook. I am at Composer now where I get the error:
TASK: [composer | Composer self update] ***************************************
failed: [xx.xxx.xx.xx] => {"changed": false, "cmd": ["composer", "self-update"], "delta": "0:01:00.854499", "end": "2015-11-05 10:20:41.857062", "rc": 1, "start": "2015-11-05 10:19:41.002563", "stdout_lines": [], "warnings": []}
stderr: Updating to version e8b6a08a51258726b5fc877c20f0b147d228b220.
Downloading: 100%
[Composer\Downloader\TransportException]
The "https://getcomposer.org/composer.phar" file could not be downloaded: failed to open stream: Connection timed out
self-update [-r|--rollback] [--clean-backups] [--no-progress] [version]
Trying to update composer manually gets stuck at premissions isuses:
dhc-user@name:~$ composer selfupdate
[Composer\Downloader\FilesystemException]
Filesystem exception:
Composer update failed: the "/usr/lib/composer/composer.phar" file could not
be written
as I guess that user dhc-user does not have enought rights or the web user that was added now does not… and the step with adding wpcli and WordPress have not been taken care of of course… Is there now way to continue with remaining tasks when one does not pass? Now I have an outdated Composer and no WP Cli nor WordPress…
Two, tried a setup a Digital Ocean Droplet (Ubuntu 14.0.4) as I thought Dreamhost perhaps had connectivity issues at DreamCompute network I tried the whole thing following the Trellis Ansible Playbook. And again things did not work out. Things hung at creating WordPress setup with the database and so on and restarting or reloading other items failed too:
TASK: [wordpress-setup | Create/assign database user to db and grant permissions] ***
fatal: [xxx.xxx.xxx.xxx] => error parsing argument string 'name="imagewize_dbuser" password="password"" priv="imagewize_staging.*:ALL" state=present login_host="localhost" login_user="root" login_password="stagingpw"', try quoting the entire line.
NOTIFIED: [common | restart memcached] ****************************************
FATAL: no hosts matched or all hosts have already failed -- aborting
NOTIFIED: [common | reload nginx] *********************************************
FATAL: no hosts matched or all hosts have already failed -- aborting
NOTIFIED: [common | reload php-fpm] *******************************************
FATAL: no hosts matched or all hosts have already failed -- aborting
NOTIFIED: [fail2ban | restart fail2ban] ***************************************
FATAL: no hosts matched or all hosts have already failed -- aborting
NOTIFIED: [ferm | restart ferm] ***********************************************
FATAL: no hosts matched or all hosts have already failed -- aborting
NOTIFIED: [ntp | restart ntp] *************************************************
FATAL: no hosts matched or all hosts have already failed -- aborting
NOTIFIED: [sshd | restart ssh] ************************************************
FATAL: no hosts matched or all hosts have already failed -- aborting
PLAY RECAP ********************************************************************
to retry, use: --limit @/Users/jasper/server.retry
146.185.152.145 : ok=77 changed=57 unreachable=1 failed=0
Seems the Ansible Playbook does not work on a 1 GB RAM VCPU Digital Ocean Droplet or DreamCompute instance. I did the setup 5 times now. Three or 4 setups with new instances on DreamCompute (Open Stack) and once on a Digital Ocean Droplet. And to no avail.
Update: Dreamhost said they might be experiencing issues at their Ashburn Virginia Data Center.
Why the DO Droplet setup failed at the database setup level I am not sure yet.