cloudfoundry / diego-windows-release

Apache License 2.0
9 stars 13 forks source link

Cloud issue? #1

Closed prysmakou closed 9 years ago

prysmakou commented 9 years ago

Tried to deploy it with Cloud Formation. During investigating found the reason - lack of internet connection for windows box. I specified id of my NAT VM (based on amazon's NAT AMI) and CIDR for new subnet. What do you mean for NATZ? A NAT instance? Looks like it is needed to modify NAT instance somehow before deployment of Windows cell?

I already have CF and Diego deployed, so I have public and private subnet and NAT instance. Why we need to create additional subnet for Windows cells instead of using existing (private) subnet?

cfn-init.log contains:

2015-10-11 10:40:40,540 [DEBUG] CloudFormation client initialized with endpoint https://cloudformation.us-east-1.amazonaws.com
2015-10-11 10:40:40,540 [DEBUG] Describing resource GardenWindowsInstanceConfiguration in stack arn:aws:cloudformation:us-east-1:754058048930:stack/win2/da263ce0-7003-11e5-b978-50e2416294a8
2015-10-11 10:41:01,618 [ERROR] ConnectionError
Traceback (most recent call last):
  File "cfnbootstrap\util.pyc", line 159, in _retry
  File "cfnbootstrap\util.pyc", line 231, in _timeout
ConnectionError: ('Connection aborted.', error(10060, 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'))