shinesolutions/puppet-aem-curator

AEM Author Standby runs InSpec tests before AEM is listening on designated port

Closed this issue · 1 comments

Due to collectd plugins provisioning being shifted to AMI creation, there is now less time for AEM Author Standby to get ready and this uncovers a problem with AEM not listening on the port by the time InSpec test is running, causing the failure below:

ct 15 22:27:40 ip-10-0-13-178 cloud-init: [aem-aws-stack-builder] Testing author-standby component using InSpec...
Oct 15 22:27:45 ip-10-0-13-178 cloud-init: Profile: tests from author-standby_spec.rb (tests from author-standby_spec.rb)
Oct 15 22:27:45 ip-10-0-13-178 cloud-init: Version: (not specified)
Oct 15 22:27:45 ip-10-0-13-178 cloud-init: Target:  local://
Oct 15 22:27:45 ip-10-0-13-178 cloud-init: Service aem-author
Oct 15 22:27:45 ip-10-0-13-178 cloud-init: #033[38;5;41m     ✔  should be enabled#033[0m
Oct 15 22:27:45 ip-10-0-13-178 cloud-init: #033[38;5;41m     ✔  should be running#033[0m
Oct 15 22:27:45 ip-10-0-13-178 cloud-init: Port 4502
Oct 15 22:27:45 ip-10-0-13-178 cloud-init: #033[38;5;208m     ∅  should be listening
Oct 15 22:27:45 ip-10-0-13-178 cloud-init: expected `Port 4502.listening?` to return true, got false#033[0m
Oct 15 22:27:45 ip-10-0-13-178 cloud-init: Port 5432
Oct 15 22:27:45 ip-10-0-13-178 cloud-init: #033[38;5;41m     ✔  should be listening#033[0m
Oct 15 22:27:45 ip-10-0-13-178 cloud-init: Test Summary: #033[38;5;41m3 successful#033[0m, #033[38;5;9m1 failure#033[0m, 0 skipped

Done. Included in 0.11.6, 1.2.3 .