topic Re: WaitCondition timed out. Received 0 conditions when expecting 1 in Cloud Firewall

WaitCondition timed out. Received 0 conditions when expecting 1

Paul_Warnagiris — Wed, 25 Oct 2017 18:55:13 GMT

Didn't see much on this in the support portal. This occurs 45-60 minutes after I kick off a cloudformation template for r80.10 management into a pre-existing VPC. Template #6 from sk111013 (top section -- first #6). Any recommendations on next steps?

Physical ID:arn:aws:cloudformation:us-east-1:709709569732:stack/Check-Point-Management/cefceab0-b9aa-11e7-b989-50a686e4bbe3/ReadyHandle
	Client Request Token:Console-CreateStack-262cdf0a-5109-4f76-ba24-39e5272c7a4a

Re: WaitCondition timed out. Received 0 conditions when expecting 1

Paul_Warnagiris — Wed, 25 Oct 2017 19:06:12 GMT

If you look in the template, there is a wait condition of 3600 seconds, waiting for the instance to come up. In the boot script of the instance, there is a curl command that is supposed to trigger the wait condition to be released. There is no internet connected to any of these subnets yet as this is a highly secured environment. We will be connecting to the management and the gateways via an on-prem VPN and during the cut window we will allow access which will be ultimately guarded by the Check Point. Until that time however, no Internet access is available. Is Internet access a mandatory requirement? My guess is that since there is no Internet this wait thing requires public internet access. Is my only option allowing Internet access to this box?

Re: WaitCondition timed out. Received 0 conditions when expecting 1

PhoneBoy — Wed, 25 Oct 2017 19:26:57 GMT

The wait condition appears to be the act of allocating a Public IP address:

 "ReadyCondition": {
 "Type": "AWS::CloudFormation::WaitCondition",
 "Condition": "AllocatePublicAddress",
 "DependsOn": [
 "Instance"
 ],
 "Properties": {
 "Handle": {
 "Ref": "ReadyHandle"
 },
 "Timeout": "3600"
 }
 },

My guess is that you will need to modify the template so that it doesn't do this.

Also, choose a different wait condition

Re: WaitCondition timed out. Received 0 conditions when expecting 1

Paul_Warnagiris — Fri, 27 Oct 2017 17:43:22 GMT

Just to let you know I removed the wait condition and the device provisioned as expected. Not sure what was going on with that particular AWS cloud or the template, but simply removing the wait allowed it to provision properly... Odd...

Re: WaitCondition timed out. Received 0 conditions when expecting 1

LostBoY — Wed, 04 Dec 2019 09:32:51 GMT

I have come across the same problem... how did you manage to remove the wait condition.. how to edit the template ?

Re: WaitCondition timed out. Received 0 conditions when expecting 1

Nir_Shamir — Mon, 25 Jan 2021 13:46:19 GMT

the issue is usually with internet connectivity or DNS resolve.

check it on the Gateways after deployment.

Re: WaitCondition timed out. Received 0 conditions when expecting 1

LostBoY — Thu, 19 Jan 2023 11:22:09 GMT

Stack roll backs and deletes all the GWs or Management Server due to this WaitCondition

Re: WaitCondition timed out. Received 0 conditions when expecting 1

LostBoY — Thu, 19 Jan 2023 11:23:05 GMT

Can you please share how did you delete the wait condition ..did you remove the entire "Type" or just deleted "Condition" ?

Re: WaitCondition timed out. Received 0 conditions when expecting 1

Edan_Leventhal — Wed, 05 Jul 2023 07:18:41 GMT

Hi LostBoY,
Don't know if this is still relevant for you, but to answer your questions:
1. How to edit the template-
You can find the method to manually load a template in our GitHub page. you will need to edit the relevant .yaml file.
CloudGuardIaaS/aws/templates at master · CheckPointSW/CloudGuardIaaS · GitHub

2. The section you need to delete from the yaml file to bypass the wait condition:

ManagementReadyCondition: Type: AWS::CloudFormation::WaitCondition Condition: EIP DependsOn: ManagementInstance Properties: Handle: !Ref ManagementReadyHandle Timeout: 1800