Comprehensive review-cr2

[chis0]

Hello,

I had an issue with this lab where it could not retrieve the content, it would fail with 403 forbidden and write to the error.log because it only retrieved the default (non-vhost) welcome page, with 403.

It wasn't retrieving the vhosts page(s).

Upon investigation I decided to manually restart httpd service on each server and the tests passed, I could also curl servera & serverb for the correct vhost index.

Therefore I want to work out why the handler is not notifying Restart httpd

Can someone run through the lab and see if it works? I destroyed and recreating the VMs are ran into the same issue.

Here is a snippet:

Thanks.

[ARoumiantsev]

Hi @chis0 

 There are no issues with the lab here. 

 The typical scenario you described can occur if the playbook doesn't work on the first try, and the problem arises within a task placed after the task that triggers the notification. In this lab, issues can arise with both copy tasks and firewall tasks. 

Best regards

[TravellingKiwi]

Check the status of the task "Deploy vhost template".

A notification will only be made on a change. So if the template isn't deployed (i.e. because the file is already there) then the status will be 'ok' instead of 'changed'. 
Notifications do not get made on 'ok'

The most common reason (for me anyway) is when you execute the playbook again. i.e. if the ttask after deploy fails, you fix that, run it again, and the notification then doesn't get made, because the deploy already worked on the failed run (And of course because that run failed, the notification won't get executed in the first run either)