Tagging Tasks

Hi guys, I've modified 'app/Resources/views/default/index.html.twig' in VM, then I run `ansible-playbook ansible/playbook.yml -i ansible/hosts.ini -t deploy` and my changes have gone (file 'app/Resources/views/default/index.html.twig' does not contain changes). What am I doing wrong? Looks like ansible deploy task ('Checkout Git repository') returns it to its original state
Suppose, in theory, I should commit and push changes in repo before run this task?

Hey Dmitriy,

Sure, you should avoid uncommitted changes in your repo before running playbooks that have Git module. Or you need to improve your playbook to skip Git checkout if there's uncommitted changes, but this I'd not recommend because you would need to double check if Git was checked or no manually. So, I think better to commit changes first and then run the playbook. And I think it makes sense, you probably want to deploy only when all the changes you made are committed into the repo to deliver it to host.

Cheers!

Ansible fails constantly on this command:

$ ansible-playbook ansible/playbook.yml -i ansible/hosts.ini -t permissions

PLAY [vb] ***********************************************************************************************

TASK [Gathering Facts] **********************************************************************************
ok: [192.168.33.10]

TASK [Fix var directory permissions] ********************************************************************
fatal: [192.168.33.10]: FAILED! => {"changed": false, "module_stderr": "Shared connection to 192.168.33.10 closed.\r\n", "module_stdout": "Traceback (most recent call last):\r\n  File \"/home/vagrant/.ansible/tmp/ansible-tmp-1539374113.5349424-162400146138678/AnsiballZ_file.py\", line 113, in <module>\r\n    _ansiballz_main()\r\n  File \"/home/vagrant/.ansible/tmp/ansible-tmp-1539374113.5349424-162400146138678/AnsiballZ_file.py\", line 105, in _ansiballz_main\r\n    invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\r\n  File \"/home/vagrant/.ansible/tmp/ansible-tmp-1539374113.5349424-162400146138678/AnsiballZ_file.py\", line 48, in invoke_module\r\n    imp.load_module('__main__', mod, module, MOD_DESC)\r\n  File \"/tmp/ansible_file_payload_rBkmeP/__main__.py\", line 863, in <module>\r\n  File \"/tmp/ansible_file_payload_rBkmeP/__main__.py\", line 849, in main\r\n  File \"/tmp/ansible_file_payload_rBkmeP/__main__.py\", line 571, in ensure_directory\r\n  File \"/tmp/ansible_file_payload_rBkmeP/__main__.py\", line 289, in recursive_set_attributes\r\n  File \"/tmp/ansible_file_payload_rBkmeP/ansible_file_payload.zip/ansible/module_utils/basic.py\", line 1546, in set_fs_attributes_if_different\r\n  File \"/tmp/ansible_file_payload_rBkmeP/ansible_file_payload.zip/ansible/module_utils/basic.py\", line 1313, in set_mode_if_different\r\nOSError: [Errno 1] Operation not permitted: '/var/www/project/var/sessions/prod'\r\n", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}
	to retry, use: --limit @/home/ivan/learn/SymfonyCasts/mootube/ansible/playbook.retry

PLAY RECAP **********************************************************************************************
192.168.33.10              : ok=1    changed=0    unreachable=0    failed=1```

But it does look like the permissions were partially changed back:

vagrant@vagrant-ubuntu-trusty-64:/var/www/project$ ls -ld var
drwxrwxrwx 5 vagrant vagrant 4096 Oct 12 19:51 var
vagrant@vagrant-ubuntu-trusty-64:/var/www/project$ ls -lR var
var:
total 104
-rwxrwxrwx 1 vagrant vagrant 55029 Oct 12 19:51 bootstrap.php.cache
drwxrwxrwx 2 vagrant vagrant 4096 Oct 12 19:53 cache
drwxrwxrwx 2 vagrant vagrant 4096 Oct 12 19:51 logs
drwxrwxrwx 4 vagrant vagrant 4096 Oct 12 19:51 sessions
-rwxrwxrwx 1 vagrant vagrant 34155 Oct 12 19:51 SymfonyRequirements.php

var/cache:
total 0

var/logs:
total 12
-r-xr-xr-x 1 vagrant vagrant 9772 Oct 12 19:51 dev.log

var/sessions:
total 8
drwxrwxrwx 2 vagrant vagrant 4096 Oct 12 19:51 dev
dr-xr-xr-x 2 www-data www-data 4096 Oct 12 19:51 prod

var/sessions/dev:
total 0

var/sessions/prod:
total 0`

Edit: nevermind, I see the problem: var/cache/prod was somewhen generated by the web server...

Hey Ivan,

Yes, files generated with web server will have different permissions. Btw, how did you fix the problem?

Cheers!

> how did you fix the problem?

I simply removed the folders owned by www-data :)

Hey Ivan,

Great, thanks for reaching back! I think it might be useful for other users.

Cheers!

Hi guys: why would you tags deploy for Move Compose globally when you just want to deploy your new code to server? Is this a one time thing when you install composer? I think most of time u just need to run composer install when you deploy ur new code to server.

Hey Jian,

Good question :) Actually, as Ryan said, this is debatable: you might consider Composer as a "Server setup" task, not deployment. It's up to you. But yeah, there's no a good reason to do it, especially if you're installing Composer globally. But it makes more sense if you do not want to install composer globally, i.e. just download composer.phar, use it and then remove it from the server at all. So fell free to remove deploy tag from tasks which install Composer and move it globally.

Cheers!